You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/01/08 17:13:02 UTC
[jira] [Commented] (BEAM-10914) Splittable DoFn and Dataflow,
"conflicting bucketing functions"
[ https://issues.apache.org/jira/browse/BEAM-10914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261452#comment-17261452 ]
Beam JIRA Bot commented on BEAM-10914:
--------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.
> 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: P3
> 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)