You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2016/06/30 10:07:10 UTC
[jira] [Commented] (TINKERPOP-1091) Get KryoSerializer to work
natively.
[ https://issues.apache.org/jira/browse/TINKERPOP-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356851#comment-15356851 ]
stephen mallette commented on TINKERPOP-1091:
---------------------------------------------
[~okram] can we close this one now based on the gryo work that dan did?
> Get KryoSerializer to work natively.
> ------------------------------------
>
> Key: TINKERPOP-1091
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1091
> Project: TinkerPop
> Issue Type: Improvement
> Components: hadoop
> Affects Versions: 3.1.0-incubating
> Reporter: Marko A. Rodriguez
> Labels: breaking
> Fix For: 3.2.1
>
>
> Right now, if you use SparkServer (cluster mode) then you need to have {{GryoSerializer}} on all the machines in the cluster. That is, {{SparkContext.addJar()}} does NOT work for {{spark.serializer}}. This is really lame.
> I know we want to get make {{GryoSerializer}} able to work more generally ([~dalaro]). Lets see if we can't get {{KryoSerializer}} with custom added TinkerPop3 classes to work. This way, we don't have to copy jars to machines and can rely on {{loadJars()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)