Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added basic AWS Glue struct datatype support and JSON/CSV/PARQUET read_options #464

Conversation

firewall413
Copy link

Added basic AWS Glue struct datatype support and JSON/CSV/PARQUET read_options

@jwills
Copy link
Collaborator

jwills commented Oct 16, 2024

Amazing, thank you @firewall413! Looking forward to reading this one

@@ -23,11 +23,11 @@
"""

config_materialized_parquet_location = """
{{ config(materialized="external", location="{{ adapter.external_root() }}/test.parquet") }}
{{ config(materialized="external", location="{{ adapter.external_root() }}/test.parquet", format="parquet") }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah so this is a behavior change? i.e., you now have to specify the format arg for external materializations in order to get the read options right for the corresponding view?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given that we need this info to config the views correctly, can we just infer it from the extension on the file if the format isn't specified? (And if there is no extension at all and no format specified, I think the default is parquet)?

Context here is that I don't want to break existing users when they upgrade unless it is completely unavoidable and even then we want to provide as much warning that it is coming as possible.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok yep, I can give that (infer the type from the extension) a try!

Copy link
Collaborator

@jwills jwills left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yay, thank you again @firewall413!

@jwills jwills merged commit 02b3b86 into duckdb:master Oct 17, 2024
31 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants