[
https://issues.apache.org/jira/browse/BEAM-10475?focusedWorklogId=501187&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-501187
]
ASF GitHub Bot logged work on BEAM-10475:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Oct/20 17:05
Start Date: 15/Oct/20 17:05
Worklog Time Spent: 10m
Work Description: robertwb commented on pull request #13069:
URL: https://github.com/apache/beam/pull/13069#issuecomment-709463485
I don't think the runner can know, given a ShardedKey, that the shard id was
one that it chose (and, related, this would impose hidden restrictions on what
the SDK could choose here). However, we're not making this a magic type, rather
we're making GroupIntoBatches a magic transform (which seems a more sane
direction). So I'm OK with making it required, with no special meanings for
empty (or other) bytes.
The other question I'd like to bring up is the visibility of the ShardID. If
it's not opaque, is there any reason to not just use a KV here?
----------------------------------------------------------------
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: 501187)
Time Spent: 10h (was: 9h 50m)
> GroupIntoBatches with Runner-determined Sharding
> ------------------------------------------------
>
> Key: BEAM-10475
> URL: https://issues.apache.org/jira/browse/BEAM-10475
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Reporter: Siyuan Chen
> Assignee: Siyuan Chen
> Priority: P2
> Labels: GCP, performance
> Time Spent: 10h
> Remaining Estimate: 0h
>
> [https://s.apache.org/sharded-group-into-batches|https://s.apache.org/sharded-group-into-batches__]
> Improve the existing Beam transform, GroupIntoBatches, to allow runners to
> choose different sharding strategies depending on how the data needs to be
> grouped. The goal is to help with the situation where the elements to process
> need to be co-located to reduce the overhead that would otherwise be incurred
> per element, while not losing the ability to scale the parallelism. The
> essential idea is to build a stateful DoFn with shardable states.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
