[
https://issues.apache.org/jira/browse/BEAM-11920?focusedWorklogId=564110&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-564110
]
ASF GitHub Bot logged work on BEAM-11920:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Mar/21 22:27
Start Date: 10/Mar/21 22:27
Worklog Time Spent: 10m
Work Description: pabloem commented on pull request #14139:
URL: https://github.com/apache/beam/pull/14139#issuecomment-796231173
ah yes thanks! I am a little concerned about this. The reason we group
everything is that we want to make sure all loads succeed before scheduling any
copy jobs. this makes sense for batch (stage n+1 won't execute before stage n
is completely finished) - but I worry about streaming - is it possible for keys
from a single destination to be processed by n+1 before all keys in stage N are
finalized?
@reuvenlax is this possible?
----------------------------------------------------------------
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: 564110)
Time Spent: 40m (was: 0.5h)
> Simplify the pipeline by grouping on TableDestination
> -----------------------------------------------------
>
> Key: BEAM-11920
> URL: https://issues.apache.org/jira/browse/BEAM-11920
> Project: Beam
> Issue Type: Improvement
> Components: extensions-java-gcp
> Affects Versions: 2.28.0
> Reporter: Fokko Driesprong
> Assignee: Fokko Driesprong
> Priority: P2
> Fix For: 2.29.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
