if customized schema is used the redshift macro writes the admin views in the wrong schema

[misteliy]

Describe the bug

If we use:
{{
config({
"materialized":"table",
"schema": "raw",
"sort": "load_dts",
"dist": "all",
"comprows": 1000,
"post-hook": [
"{{ redshift.compress_table(this.schema, this.table, drop_backup=True) }}"
]
})
}}

the schema field is not getting picked up by the redshift.compress_table expression and hence writing to the wrong schema

Steps to reproduce

Please use provided config for a model

Expected results

should use the same schema as passed in the config clause

Actual results

using the default schema as provided in the profiles.yml

Screenshots and log output

If applicable, add screenshots or log output to help explain your problem.

System information

The contents of your packages.yml file:

Which database are you using dbt with?

• postgres
• [x ] redshift
• bigquery
• snowflake
• other (specify: ____________)

The output of dbt --version:

<output goes here>

The operating system you're using:

The output of python --version:

Additional context

[jtcohen6]

Hey @misteliy, I haven't been able to replicate this (using dbt v0.18.1 and redshift package v0.4.1). The model builds in the correct schema, and then uses the compress_table macro to check for recommendations on the proper table.

Can you confirm that the model is building to a schema suffixed _raw? By any chance, do you have a generate_schema_name macro defined in your project?