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

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

                Author: ASF GitHub Bot
            Created on: 08/Feb/19 20:16
            Start Date: 08/Feb/19 20:16
    Worklog Time Spent: 10m 
      Work Description: kyle-winkelman commented on issue #6511: [BEAM-5519] 
Remove call to groupByKey in Spark Streaming.
URL: https://github.com/apache/beam/pull/6511#issuecomment-461932886
 
 
   Any thoughts on naming and package for SparkGroupAlsoByWindowViaWindowSet 
(SparkStreamingGroupByKey)? And the naming for the method within (groupByKey)?
   
   One thought was that groupByKey could instead be groupByKeyAndWindow.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 196388)
    Time Spent: 2h 40m  (was: 2.5h)

> Spark Streaming Duplicated Encoding/Decoding Effort
> ---------------------------------------------------
>
>                 Key: BEAM-5519
>                 URL: https://issues.apache.org/jira/browse/BEAM-5519
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-spark
>            Reporter: Kyle Winkelman
>            Assignee: Kyle Winkelman
>            Priority: Major
>              Labels: spark, spark-streaming, triaged
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> When using the SparkRunner in streaming mode. There is a call to groupByKey 
> followed by a call to updateStateByKey. BEAM-1815 fixed an issue where this 
> used to cause 2 shuffles but it still causes 2 encode/decode cycles.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to