[
https://issues.apache.org/jira/browse/BEAM-6021?focusedWorklogId=166839&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-166839
]
ASF GitHub Bot logged work on BEAM-6021:
----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Nov/18 10:59
Start Date: 16/Nov/18 10:59
Worklog Time Spent: 10m
Work Description: mareksimunek commented on issue #6998: [BEAM-6021] Use
KryoSerializer instead of JavaSerializer
URL: https://github.com/apache/beam/pull/6998#issuecomment-439358882
@iemejia pls code review
----------------------------------------------------------------
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: 166839)
Time Spent: 1h (was: 50m)
> Use Kryo spark.serializer instead of JavaSerializer
> ---------------------------------------------------
>
> Key: BEAM-6021
> URL: https://issues.apache.org/jira/browse/BEAM-6021
> Project: Beam
> Issue Type: Improvement
> Components: runner-spark
> Affects Versions: 2.8.0
> Reporter: Marek Simunek
> Assignee: Marek Simunek
> Priority: Major
> Fix For: 2.9.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> By default is set spark.serializer=org.apache.spark.serializer.JavaSerializer.
> Because all objects from user are using Beam coders it will affect only
> internal objects for spark translation.
> So why not use more optimal {{org.apache.spark.serializer.KryoSerializer}}
> and force spark runner contributors to register classes in
> {{BeamSparkRunnerRegistrator}} by setting
> {{spark.kryo.registrationRequired=true)}}.
> More information about benefits of [kryo
> serialization|https://spark.apache.org/docs/latest/tuning.html#data-serialization]
> over java serializer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
