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

Contract data type of nested and repeated data (ARRAY of STRUCTs) in BigQuery #6645

Open
1 task done
dbeatty10 opened this issue Dec 11, 2024 · 0 comments
Open
1 task done
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear

Comments

@dbeatty10
Copy link
Contributor

dbeatty10 commented Dec 11, 2024

Contributions

  • I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

Here's a couple possibilities:

If the former, then the idea would be a section similar to https://docs.getdbt.com/reference/resource-configs/contract#size-precision-and-scale.

What part(s) of the page would you like to see updated?

The contract data_type of a nested and repeated fields in BigQuery should just be array like this:

      - name: repeated_struct.nested_repeated_struct
        data_type: array

rather than have the full detailed data type like this:

      - name: repeated_struct.nested_repeated_struct
        data_type: array<struct<`string_field` string>>

Additional information

See discussion here for background: dbt-labs/dbt-codegen#190 (comment)

This is spiritually similar to a data type issue that came up with Snowflake as it related to precision and scale of NUMERIC, but it is a distinct caveat.

Only tangentially related to #3322.

@dbeatty10 dbeatty10 added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear labels Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear
Projects
None yet
Development

No branches or pull requests

1 participant