[
https://issues.apache.org/jira/browse/BEAM-11934?focusedWorklogId=623869&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-623869
]
ASF GitHub Bot logged work on BEAM-11934:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Jul/21 20:46
Start Date: 16/Jul/21 20:46
Worklog Time Spent: 10m
Work Description: lukecwik commented on pull request #15178:
URL: https://github.com/apache/beam/pull/15178#issuecomment-881708784
> > > Do you think we should keep the old behavior as an option in case some
customers run into issues ?
> >
> >
> > We should make it the default for runner v2.
> > @reuvenlax Is it worth making this the default and requiring users to
pass in a flag to maintain support for pipeline update for older versions?
>
> I assume that you meant making runner determined sharding default for
runner v2.
>
> Older versions don't support runner determined sharding for unbounded data
(strictly speaking, versions before 2.29.0) so fixed sharding option will be
carried over on pipeline update. We could make new pipelines opt in by default.
SGTM
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 623869)
Time Spent: 5h 50m (was: 5h 40m)
> Dataflow GCS streaming file sink uses runner determined sharding
> ----------------------------------------------------------------
>
> Key: BEAM-11934
> URL: https://issues.apache.org/jira/browse/BEAM-11934
> Project: Beam
> Issue Type: Improvement
> Components: io-java-files, io-java-gcp, runner-dataflow
> Reporter: Siyuan Chen
> Priority: P2
> Time Spent: 5h 50m
> Remaining Estimate: 0h
>
> Integrate file sink with shardable `GroupIntoBatches` (BEAM-10475) to allow
> runner determined dynamic sharding for streaming use cases.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
