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 2020/08/10 17:07:08 UTC

[jira] [Updated] (BEAM-1438) The default behavior for the Write transform doesn't work well with the Dataflow streaming runner

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

Beam JIRA Bot updated BEAM-1438:
--------------------------------
    Labels: stale-assigned  (was: )

> The default behavior for the Write transform doesn't work well with the Dataflow streaming runner
> -------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-1438
>                 URL: https://issues.apache.org/jira/browse/BEAM-1438
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>            Reporter: Reuven Lax
>            Assignee: Reuven Lax
>            Priority: P2
>              Labels: stale-assigned
>             Fix For: 2.5.0
>
>          Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> If a Write specifies 0 output shards, that implies the runner should pick an appropriate sharding. The default behavior is to write one shard per input bundle. This works well with the Dataflow batch runner, but not with the streaming runner which produces large numbers of small bundles.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)