-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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]: Storage Write API fails on Batch Pipelines on 2.49 #27670
Comments
this looks to be caused by this change: #26975 Pranav and I debugged offline, and it looks like this is specific to batch mode @reuvenlax any idea why we would get this issue when using storage write in batch, but not in streaming? |
@ahmedabu98 as well |
@pranavbhandari24 can you provide some more info? Is there a simple pipeline we can use to reproduce this? Does this fail consistently or under some conditions? |
The pipeline fails consistently. I was able to reproduce this error on Jdbc To BigQuery template. Let me try to reproduce this using a simple pipeline |
Couldn't reproduce it with the following pipeline (tried to make it as close as possible to the write configuration in the template):
|
Ahh, I was able to reproduce it with these rows:
looks like functions in |
Hmmm this is a pretty old bug.. I ran it with different versions and am tracing it back to |
Introduced in #17404 |
Have a PR addressing this in #27699. BTW this is in code shared by all Storage API modes (batch, streaming modes. also at_least_once), so probably affects all storage writes. |
BigQuery column names are not case sensitive, so we should fail if the schema has two such column names. |
Should we do this in the main BigQueryIO module? So it can apply to all write methods |
What happened?
When writing to a BigQuery sink in a Batch pipeline using Storage Write API the pipeline fails due to the following error,
The field
eventId
exists but for some reason the case of the field changes.This does not occur in when using File Loads method.
Issue Priority
Priority: 1 (data loss / total loss of function)
Issue Components
The text was updated successfully, but these errors were encountered: