[ https://issues.apache.org/jira/browse/TINKERPOP-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726889#comment-15726889 ]
stephen mallette commented on TINKERPOP-1582: --------------------------------------------- There are custom instances of {{P}} working with DSE Graph, so I wonder why they aren't working for you. I can't think of why that static {{ObjectMapper}} would get used unless you were not using the GraphSON 2.0 serializer somehow or like untyped GraphSON where the bytecode was coming in as a string value somehow. > 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)