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

Posted to issues@beam.apache.org by "Amit Kumar (Jira)" <ji...@apache.org> on 2019/11/06 23:14:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16968788#comment-16968788 ] 

Amit Kumar commented on BEAM-1438:
----------------------------------

I have also recently seen failure withNumShards(0) for an unbounded source.

> 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: Major
>             Fix For: 2.5.0
>
>
> 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)