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

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

                Author: ASF GitHub Bot
            Created on: 09/Nov/18 18:03
            Start Date: 09/Nov/18 18:03
    Worklog Time Spent: 10m 
      Work Description: lukecwik commented on issue #6998: [BEAM-6021] Use 
KryoSerializer instead of JavaSerializer
URL: https://github.com/apache/beam/pull/6998#issuecomment-437443824
 
 
   There have been issues in the past about using Kryo as the serializer, this 
a discussion about it just over a year ago: 
https://lists.apache.org/thread.html/a36d68b568377f8064463b7fc374e8304d59a26412360050333bb2aa@%3Cdev.beam.apache.org%3E
   
   It may not be an issue anymore though but wanted to provide context as to 
why this may have not worked in the past.

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


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

    Worklog Id:     (was: 164453)
    Time Spent: 40m  (was: 0.5h)

> 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: 40m
>  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)

Reply via email to