[
https://issues.apache.org/jira/browse/TINKERPOP-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Mallette closed TINKERPOP-2864.
---------------------------------------
Resolution: Not A Bug
> GraphBinaryMessageSerializer cannot serialize DefaultComputerResult
> -------------------------------------------------------------------
>
> Key: TINKERPOP-2864
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2864
> Project: TinkerPop
> Issue Type: Bug
> Components: driver
> Affects Versions: 3.5.5
> Reporter: Redriver
> Priority: Major
>
> When I send the following request to gremlin-server, I got an error
> "{color:#1d1c1d}Serializer for type
> org.apache.tinkerpop.gremlin.process.computer.util.DefaultComputerResult not
> found{color}".
> {code:java}
> graph = GraphFactory.open('conf/fdb-psave-export.properties')
> graph.compute(SparkGraphComputer).program(CloneVertexProgram.build().create()).submit().get()
> {code}
> After investigation, I found GraphBinaryMessageSerializer cannot serialize
> DefaultComputerResult. The quick workaround is change the gremline to
> {code:java}
> graph = GraphFactory.open('conf/fdb-psave-export.properties')
> a=
> graph.compute(SparkGraphComputer).program(CloneVertexProgram.build().create()).submit().get()
> a.toString()
> {code}
> This asks the GraphBinaryMessageSerializer to serialize String instead of
> DefaultComputerGraph.
> I'm wondering is it possible to change the GraphBinaryMessageSerializer to
> automatically handle this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
