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/03/04 22:50:40 UTC

[jira] [Commented] (TINKERPOP-1201) Register Traversal with GryoMapper.

    [ https://issues.apache.org/jira/browse/TINKERPOP-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180603#comment-15180603 ] 

stephen mallette commented on TINKERPOP-1201:
---------------------------------------------

If you do this, it's might not be as simple as just registering the class in the {{GryoMapper}} if we also have {{Traversal}} concrete implementations out there also registered - I don't think we do, so maybe it is that easy.  if we do, then the {{GyroClassResolver}} also needs to be edited - see the {{getRegistration()}} method for the pattern.

> Register Traversal with GryoMapper.
> -----------------------------------
>
>                 Key: TINKERPOP-1201
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1201
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: io, process
>    Affects Versions: 3.1.1-incubating
>            Reporter: Marko A. Rodriguez
>             Fix For: 3.2.0-incubating
>
>
> I did not know you could register interfaces with Gryo. [~spmallette] says you can. If this is the case, we should register {{Traversal}}.
> {code}
>  add(Triplet.<Class, Function<Kryo, Serializer>, Integer>with(Traversal.class, kryo -> new JavaSerializer(), 00000000));
> {code}
> Man, had I known that, so many things would have been easier for me. If we do this, I can gut lots of random "if/else"-code I have.



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