[
https://issues.apache.org/jira/browse/BEAM-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215994#comment-17215994
]
Beam JIRA Bot commented on BEAM-1438:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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
> Priority: P2
> Labels: stale-P2
> Fix For: 2.5.0
>
> Time Spent: 4h 20m
> 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)
