You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Daniel Halperin (JIRA)" <ji...@apache.org> on 2016/07/12 05:27:10 UTC

[jira] [Closed] (BEAM-69) TextIO/AvroIO numShards may not work in different runners

     [ https://issues.apache.org/jira/browse/BEAM-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Halperin closed BEAM-69.
-------------------------------
       Resolution: Fixed
         Assignee: Daniel Halperin
    Fix Version/s: Not applicable

> TextIO/AvroIO numShards may not work in different runners
> ---------------------------------------------------------
>
>                 Key: BEAM-69
>                 URL: https://issues.apache.org/jira/browse/BEAM-69
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-core
>            Reporter: Daniel Halperin
>            Assignee: Daniel Halperin
>             Fix For: Not applicable
>
>
> See also: https://issues.apache.org/jira/browse/BEAM-68
> Because the Beam Model does not support limiting parallelism of a specific step, individual runners needs to add runner-specific overrides of TextIO.Write and AvroIO.Write to enforce the `numShards` parameter. 
> DataflowPipelineRunner and DirectPipelineRunner do that now; other runners will need to do so as well, or ignore/reject the writes, until BEAM-68 is resolved.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)