-
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
beam.CombineValues
on DataFlow runner causes ambiguous failure with python SDK
#21432
Comments
Hi, I have faced the same issue as well. Is there any workaround or stable versions to use? thanks!
|
Hi, I'm facing the same issue here. Did anyone figure out a workaround? |
Hey, I was facing the same issue, whole pipeline worked with DirectRunner (all steps), but DataflowRunner failed after 1-3secs and emitted "ambiguous" logs, which didn't point at the CombineValues line. Else it worked fine without the the CountCombineFn Step in the DataflowRunner. Original Error Logs:
Update: Workaround I'm not sure if this is related to the Jira Ticket (BEAM-10297), but I found inspiration from this Apache Documentation about "CombinePerKey", and I wondered if I could just replace the Solution: Use See Original "AverageFn" here: https://beam.apache.org/documentation/transforms/python/aggregation/combineperkey/#example-5-combining-with-a-combinefn
Functions to group and combine values:
Later in the beam pipeline:
|
We started encountering this issue on Nov 2 2022 with a job running daily. So - how could this have happened? |
.take-issue |
The following beam pipeline works correctly using
DirectRunner
but fails with a very vague error when usingDataflowRunner
.Stacktrace:
Log output:
With the
CombineValues
step removed this pipeline successfully starts in dataflow.I thought this was an issue with Dataflow on the server side since the Dataflow API (v1b3.projects.locations.jobs.messages) is just returning the textPayload: "Error processing pipeline". But then I found the issue BEAM-12636 where a go SDK user has the same error message but seemingly as a result of bugs in the go SDK?
Imported from Jira BEAM-13795. Original Jira may contain additional context.
Reported by: Jake_Zuliani.
The text was updated successfully, but these errors were encountered: