-
Notifications
You must be signed in to change notification settings - Fork 234
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
Feature/parse struct fields #203
Conversation
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Sergio Couto.
|
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Sergio Couto.
|
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Sergio Couto.
|
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Sergio Couto.
|
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Sergio Couto.
|
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Sergio Couto.
|
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Sergio Couto.
|
resolves #202
Description
The issue was when parsing the schema, the current regex deal with inner struct fields as root fields, hence causing an error later because the column was not found (check issue #202 for a more detailed description)
Current one:
Proposed one:
Checklist
CHANGELOG.md
and added information about my change to the "dbt next" section. (Not sure if I did this right, let me know if it's something else to improve)