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

Enums are now treated as type INTEGER in BigQuery #54

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

stephenoken
Copy link

@stephenoken stephenoken commented Jan 15, 2025

Referring to the BigQuery schema compatibility page. Enums are mapped as integers and not strings. The following changes have been made to address this issue:

  • Enums are now represented as INTEGERS in BigQuery schemas.
  • Updated plugin_test to reflect the change.

* Enums are now represented as INTEGERS in BigQuery schemas.
* Updated pluging_test to reflect the change.
Copy link

google-cla bot commented Jan 15, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@stephenoken stephenoken changed the title Enums are now treated as type STRING in BigQuery Enums are now treated as type INTEGER in BigQuery Jan 16, 2025
* Enums are now represented as INTEGERS in BigQuery schemas.
* Updated pluging_test to reflect the change.
@stephenoken
Copy link
Author

Hello, can anyone take a look at this PR?

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.

1 participant