[
https://issues.apache.org/jira/browse/TINKERPOP-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15729271#comment-15729271
]
stephen mallette commented on TINKERPOP-1582:
---------------------------------------------
I guess that would do it. I think we should migrate away from the {{String}}
approach (i'm not sure I remember why we allow it both ways). {{Bytecode}}
should be processed as a bytecode "object" not an embedded string. Since you
found the problem, do you want submit a pull request to fix that in
gremlin-python (i.e. submit the bytecode dictionary and not the string)? if you
don't have time, just let me know.
> 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)
