[
https://issues.apache.org/jira/browse/BEAM-1438?focusedWorklogId=449567&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-449567
]
ASF GitHub Bot logged work on BEAM-1438:
----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jun/20 00:28
Start Date: 23/Jun/20 00:28
Worklog Time Spent: 10m
Work Description: pabloem commented on pull request #11850:
URL: https://github.com/apache/beam/pull/11850#issuecomment-647835759
@chamikaramj PTAL
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 449567)
Time Spent: 2h 20m (was: 2h 10m)
> 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
> Fix For: 2.5.0
>
> Time Spent: 2h 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)
