[
https://issues.apache.org/jira/browse/BEAM-10914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232926#comment-17232926
]
Beam JIRA Bot commented on BEAM-10914:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Splittable DoFn and Dataflow, "conflicting bucketing functions"
> ---------------------------------------------------------------
>
> Key: BEAM-10914
> URL: https://issues.apache.org/jira/browse/BEAM-10914
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Reporter: Luke Cwik
> Priority: P2
> Labels: stale-P2
> Attachments: TsPointsStreamingFail.java
>
>
> When creating a pipeline with an SDF like:
> FileIO.match -> readMatches -> drive the upstream side input
> OR
> [unbounded watcher, sdf] -> [ParDo with side input from File.IO] -> [bounded
> sdf] -> [ParDo]
> Workflow failed. Causes: Step s22 has conflicting bucketing functions
> Attached to this bug is a repro supplied by the user
> (TsPointsStreamingFail.java)
> Source for reported issue:
> https://lists.apache.org/thread.html/r03c77ea03d7ff2678052bde412da19c4e13050652fd34d3e03a9e30f%40%3Cuser.beam.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
