You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My use case is to have AWS Glue as my global metastore.
I have my databricks clusters linked to my glue metastore and I can successfully read / write tables in it.
Unfortunately I'm not able to write anything else than delta table (as it is hardcoded)
Expected Behavior
The table is materialized in the format specified in the file_format config.
github-actionsbot
changed the title
[Bug] Unable to materialize a table in iceberg
[ADAP-619] [Bug] Unable to materialize a table in iceberg
Jun 12, 2023
irsath
changed the title
[ADAP-619] [Bug] Unable to materialize a table in iceberg
[Bug] Unable to materialize table in anything else than delta
Jun 12, 2023
irsath
changed the title
[Bug] Unable to materialize table in anything else than delta
[ADAP 619][Bug] Unable to materialize table in anything else than delta
Jun 12, 2023
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.
Is this a new bug in dbt-spark?
Current Behavior
The
file_format
config is not taken into account.Table materialization is hard coded to be in
delta
.dbt-spark/dbt/include/spark/macros/materializations/table.sql
Line 101 in e741034
My use case is to have AWS Glue as my global metastore.
I have my databricks clusters linked to my glue metastore and I can successfully read / write tables in it.
Unfortunately I'm not able to write anything else than delta table (as it is hardcoded)
Expected Behavior
The table is materialized in the format specified in the
file_format
config.Steps To Reproduce
Execute this model:
Relevant log output
No response
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: