-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add functionality to persist descriptions to nested columns in bigquery #2550
Add functionality to persist descriptions to nested columns in bigquery #2550
Conversation
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Bob De Schutter.
|
Ok, I signed it :-) |
@cla-bot check |
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Bob De Schutter.
|
The cla-bot has been summoned, and re-checked this pull request! |
ok - thanks for signing it! I do see the signature, but the CLA bot is upset that your existing commit is not associated with your GitHub user :). This is the mechanism used to determine that commits to this repo are contributed by CLA signatories, so if you could try running
with your github email address, i think we should be in good shape. We'll take a look at this PR and add some comments inline! Thanks again for opening it :) |
Yeah, I signed the CLA with my personal email address and the commit was probably done with my professional address... I changed it locally so I think I should do a dummy commit to get it in? |
I think you'll want to |
You could also add your professional address to your github, if that works for you. The cla-bot actually goes by username, and the problem is that github doesn't know that your commit is from |
9021946
to
33b4e78
Compare
seems to be resolved now, thanks for the help :-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @bodschut, thanks for your contribution!
It looks like flake8 is upset with some of your line lengths so the unit tests are failing.
Can you also please add an integration test for this as well? I'm happy to help with that, there are some existing tests in test/integration/060_persist_docs_tests
that you could use as a starting point. You'd probably need to make a new models
directory entirely and point the new test there (so you don't break snowflake tests).
Edit: Also, please add yourself to the contributors section of CHANGELOG.md
and add a changelog entry for this PR/issue, so we can give you credit in our release notes!
fb90144
to
3a5db3c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is awesome! Thanks for sticking with it and getting that test in, this is a great addition.
I have 2 tiny comments here, no need for commenting out code if we can remove it, that's what version control is for! Once those are done I'll kick off the tests and we'll be good to merge this for 0.17.1
@drewbanin did you want to locally smoke test this? I feel pretty good about the tests!
Co-authored-by: Jacob Beck <[email protected]>
This is a weird result! The indices for the nested structs in the docs generate tests seem to have changed as a result of this PR - this is the part of the diff that actually reflects a failure:
Should those come back? |
Bigquery allows you to put a description on the parent field that has type STRUCT, that's why I removed the where clause that excluded these. Maybe we should take that into account in the test? |
resolves #2549
Description
Changed the existing function in the bigquery adapter implementation to recursively traverse nested columns in bigquery and add descriptions if they are provided in a schema.yml file. Requires that nested fields are addressed with dotted syntax in the schema file.
Checklist
CHANGELOG.md
and added information about my change to the "dbt next" section.