-
Notifications
You must be signed in to change notification settings - Fork 984
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
[Bug]: SpannerChangeStreamsToBigQuery does not support null primary key column values. #831
Comments
As a followup i dug deeper and i think the issue is that
Details on null: https://stleary.github.io/JSON-java/org/json/JSONObject.html#NULL This differs from non PK fields where java null is used and works Line 142 in 1276f71
I think an explicit Line 209 in 1276f71
|
hi any updates here? |
This issue has been marked as stale due to 180 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the issue at any time. Thank you for your contributions. |
this still is not fixed |
This issue has been marked as stale due to 180 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the issue at any time. Thank you for your contributions. |
still not fixed |
Related Template(s)
SpannerChangeStreamsToBigQuery
What happened?
In Spanner it is valid to have nullable columns in a primary key.
However, the way the pipeline reads values out of json here it seems like it is extracting
null
when a column in the primary key is null and passing that value to bigquery.Bigquery does not seem accept this and throws "This field: XXX is not a record."
This is blocking us rolling out a new feature that relies on a null primary key column.
Full example:
say we delete row with the following values:
keysJson will be:
error is:
Beam Version
Newer than 2.46.0
Relevant log output
The text was updated successfully, but these errors were encountered: