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

["stephen mallette (JIRA)" <ji...@apache.org>]

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

stephen mallette commented on TINKERPOP-1582:
---------------------------------------------

hmmm - The static {{ObjectMapper}} is only used to decode a {{String}} representation of traversal bytecode embedded in a message. That's a bit of a remnant of using untyped GraphSON i think. If the serializer you are using manages types well, like GraphSON 2.0 or Gryo (starting with 3.2.3) then you should needed to pass as a string. I think we will ultimately do away with untyped GraphSON very soon: TINKERPOP-1574

can you explain your environment a bit more so that I can understand why you need to submit your traversals this way?

> 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
>
> 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)