beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Halperin (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (BEAM-69) TextIO/AvroIO numShards may not work in different runners
Date Tue, 12 Jul 2016 05:27:10 GMT

     [ 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)

Mime
View raw message