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/12/09 12:20:58 UTC

[jira] [Closed] (TINKERPOP-1582) TraversalOpProcessor does not support custom serializers

     [ https://issues.apache.org/jira/browse/TINKERPOP-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette closed TINKERPOP-1582.
---------------------------------------
       Resolution: Implemented
         Assignee: stephen mallette
    Fix Version/s: 3.2.4

> TraversalOpProcessor does not support custom serializers
> --------------------------------------------------------
>
>                 Key: TINKERPOP-1582
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1582
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.2.3
>            Reporter: Branden Moore
>            Assignee: stephen mallette
>             Fix For: 3.2.4
>
>
> The TraversalOpProcessor has its own ObjectMapper static instance, which cannot be configured via the gremlin-server's YAML file.  Within the YAML file, a user can configure serializers with custom IORegistries, to support serialization of custom types.   However, the TraversalOpProcessor creates its own ObjectMapper, for bytecode deserialization, which does not read configuration information from from the YAML file.
> This prevents deserialization of custom bytecode, such as references to a custom Predicate class.



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