[X] I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
Hi,
I believe this is more likely an issue with Athena therefore I contacted with internal team as well, however until there is an update from there maybe we can slightly update the repo to make this work.
Problem:
When running the following statement in AWS Athena. When I include AwsDataCatalog in the query, it fails, but it works fine if I drop it.
ALTER TABLE AwsDataCatalog.default.selman_schema_test REPLACE COLUMNS (column1 date, column2 string);
This statement works without AwsDataCatalog:
ALTER TABLE default.selman_schema_test REPLACE COLUMNS (column1 date, column2 string);
I'm using below option to test schema changes on parquet files with dbt-athena;
_+on_schema_change: "sync_allcolumns"
Therefore when there is a schema change, dbt-athena plugin generates replace columns statement as the first query above and it fails. maybe we can update the code to exclude datasource when generating SQL statement, if that's possible.
Is this a new bug in dbt-athena?
Current Behavior
Hi,
I believe this is more likely an issue with Athena therefore I contacted with internal team as well, however until there is an update from there maybe we can slightly update the repo to make this work.
Problem: When running the following statement in AWS Athena. When I include
AwsDataCatalogin the query, it fails, but it works fine if I drop it.This statement works without
AwsDataCatalog:I'm using below option to test schema changes on parquet files with dbt-athena;
_+on_schema_change: "sync_allcolumns"
Therefore when there is a schema change, dbt-athena plugin generates replace columns statement as the first query above and it fails. maybe we can update the code to exclude datasource when generating SQL statement, if that's possible.
Any suggestion is appreciated, thanks.
Expected Behavior
Expected behaivour mentioned above.
Steps To Reproduce
No response
Environment
Additional Context
No response