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

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

                Author: ASF GitHub Bot
            Created on: 16/Aug/19 17:57
            Start Date: 16/Aug/19 17:57
    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-522097498
 
 
   @iemejia I cleaned this up. Mainly just threw out the part where I was 
getting rid of the partitioner in batch mode, because 
[BEAM-7413](https://issues.apache.org/jira/browse/BEAM-7413) made me realize 
that approach would cause other issues.
 
----------------------------------------------------------------
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:
us...@infra.apache.org


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

    Worklog Id:     (was: 296477)
    Time Spent: 5h 40m  (was: 5.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
>             Fix For: 2.16.0
>
>          Time Spent: 5h 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.14#76016)

Reply via email to