[ 
https://issues.apache.org/jira/browse/BEAM-10914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251226#comment-17251226
 ] 

Beam JIRA Bot commented on BEAM-10914:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been 
labeled "stale-assigned". If you are still working on the issue, please give an 
update and remove the label. If you are no longer working on the issue, please 
unassign so someone else may work on it. In 7 days the issue will be 
automatically unassigned.

> 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
>            Assignee: Boyuan Zhang
>            Priority: P2
>              Labels: stale-P2, stale-assigned
>         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)

Reply via email to