You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/02/01 19:22:00 UTC

[jira] [Work logged] (BEAM-10475) GroupIntoBatches with Runner-determined Sharding

     [ https://issues.apache.org/jira/browse/BEAM-10475?focusedWorklogId=545531&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-545531 ]

ASF GitHub Bot logged work on BEAM-10475:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/Feb/21 19:21
            Start Date: 01/Feb/21 19:21
    Worklog Time Spent: 10m 
      Work Description: boyuanzz commented on pull request #13805:
URL: https://github.com/apache/beam/pull/13805#issuecomment-771095694






----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 545531)
    Time Spent: 27h 10m  (was: 27h)

> 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: 27h 10m
>  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)