You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Redriver (Jira)" <ji...@apache.org> on 2023/02/03 08:38:00 UTC

[jira] [Created] (TINKERPOP-2864) GraphBinaryMessageSerializer cannot serialize DefaultComputerResult

Redriver created TINKERPOP-2864:
-----------------------------------

             Summary: 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


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)