[
https://issues.apache.org/jira/browse/TINKERPOP-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-1327:
----------------------------------------
Labels: (was: breaking)
This didn't look like a "breaking" change to me as the system remain backward
compatible and we already require use of {{SerializerShim}}. Should this be
deprecated for 3.3.0 or 3.2.4? I think the preference would be to deprecate for
3.2.4 and simply removed for 3.3.0 on a separate ticket as a breaking change
for deprecation removal.
> Bring GryoRegistrator to the forefront and deprecate GryoSerializer
> -------------------------------------------------------------------
>
> Key: TINKERPOP-1327
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1327
> Project: TinkerPop
> Issue Type: Improvement
> Components: hadoop, io
> Affects Versions: 3.2.1
> Reporter: Marko A. Rodriguez
> Fix For: 3.3.0
>
>
> At the next major release (3.3.0), we should update the documentation and
> show the safer model for using Kryo with {{SparkGraphComputer}}.
> {code}
> spark.serializer=KryoSerializer
> spark.kryo.registrator=GryoRegistrator
> {code}
> {{GryoSerializer}} will simply be deprecated (and thus, backwards compatible).
> When deprecating {{GryoSerializer}} we should update the priority for the
> {{UnshadedKryoShimService}} as well. Also, in the documentation, we will have
> to explain that people should implement {{SerializerShim}} instead of
> {{Serializer}} if they want their custom classes to work moving forward. The
> change for them is as simple as replacing {{implements Serializer}} with
> {{implement SerializerShim}} and handling respective imports.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
