[
https://issues.apache.org/jira/browse/BEAM-5519?focusedWorklogId=219545&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-219545
]
ASF GitHub Bot logged work on BEAM-5519:
----------------------------------------
Author: ASF GitHub Bot
Created on: 27/Mar/19 19:28
Start Date: 27/Mar/19 19:28
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-477314579
I never really got a review so I think the answer is no.
----------------------------------------------------------------
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: 219545)
Time Spent: 4h (was: 3h 50m)
> 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
> Fix For: 2.12.0
>
> Time Spent: 4h
> 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)
