[
https://issues.apache.org/jira/browse/TINKERPOP-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637278#comment-17637278
]
Florian Hockmann commented on TINKERPOP-2828:
---------------------------------------------
Are you running into that problem with TinkerGraph or some other graph
provider? JanusGraph for example has its own type {{RelationIdentifier}} for
edge ids which naturally cannot be deserialized by Gremlin-Go as Gremlin has no
knowledge of such a provider-specific type. If that's the case here, you can
either implement a custom deserializer yourself for that type or see whether
you can change your application to work without needing to return edge ids.
If you for example already run into that problem when you really just want to
create a new edge ({{{}g.addE().from([...]).to([...]){}}}) which by default
also returns the edge, then you can just modify the traversal to not return the
edge any more: {{{}g.addE().from([...]).to([...]).none(){}}}.
> Golang driver cannot deserialize edge id
> ----------------------------------------
>
> Key: TINKERPOP-2828
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2828
> Project: TinkerPop
> Issue Type: Bug
> Components: go
> Affects Versions: 3.6.1, 3.5.4
> Reporter: Navgeet
> Priority: Major
> Labels: golang
> Attachments: main.go
>
>
> The issue occurs when we call {{ElementMap}} for edges. On further debugging,
> I found {{label}} can be deserialized but not {{{}id{}}}.
>
> {noformat}
> Error occurred during operation gremlinServerWSProtocol.readLoop(): 'E0408:
> unknown data type to deserialize 0x0'
> Read loop error 'E0408: unknown data type to deserialize 0x0', closing read
> loop.
> Connection error callback invoked, closing protocol.
> E0408: unknown data type to deserialize 0x0
> {noformat}
> Please see attached code for reproducing the issue.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
