You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Rotem (JIRA)" <ji...@apache.org> on 2015/12/01 23:24:10 UTC

[jira] [Created] (SPARK-12080) Kryo - Support multiple user registrators

Rotem created SPARK-12080:
-----------------------------

             Summary: Kryo - Support multiple user registrators
                 Key: SPARK-12080
                 URL: https://issues.apache.org/jira/browse/SPARK-12080
             Project: Spark
          Issue Type: Improvement
          Components: Spark Core
            Reporter: Rotem
            Priority: Minor


Background: Currently when users need to have a custom serializer for their registered classes, they use the user registrator of Kryo using the spark.kryo.registrator configuration parameter.

Problem: If the Spark user is an infrastructure itself, it may receive multiple such registrators but won't be able to register them.

Important note: Currently the single registrator supported can't reach any state/configuration (it is instantiated by reflection with empty constructor)

Using SparkEnv from user code isn't acceptable.

Workaround:
Create a wrapper registrator as a user, and have its implementation scan the class path for multiple classes. 
Caveat: this is inefficient and too complicated.

Suggested solution - support multiple registrators + stay backward compatible
Option 1:
enhance the value of spark.kryo.registrator  to support a comma separated list for class names. This will be backward compatible and won't add new parameters. 
Option 2:
to be more logical, add spark.kryo.registrators new parameter, while keeping the code handling the old one.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org