[ 
https://issues.apache.org/jira/browse/TINKERPOP-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Mallette updated TINKERPOP-3105:
----------------------------------------
    Description: 
Running 3.6.x {{gremlin-python}} with 3.7.x {{gremlin-server}} leads to 
serialization errors:
{code:java}
return self.deserializers[DataType(bt)].objectify(buff, self, nullable)
KeyError: <DataType.custom: 0>{code}
with or without using {{ReferenceElementStrategy}} set on the server, possibly 
due to a bug in how properties are being serialized and returned from Java that 
is not inline with the specification. 

  was:
Running 3.6.x `gremlin-python` with 3.7.x `gremlin-server` leads to 
serialization errors:
{code:java}
return self.deserializers[DataType(bt)].objectify(buff, self, nullable)
KeyError: <DataType.custom: 0>{code}
with or without using `ReferenceElementStrategy` set on the server, possibly 
due to how properties are being serialized and returned. 

     Issue Type: Bug  (was: Improvement)
       Priority: Blocker  (was: Major)

> Running 3.6.x python-driver with 3.7.x server leads to deserialization errors
> -----------------------------------------------------------------------------
>
>                 Key: TINKERPOP-3105
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-3105
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: io, python, server
>    Affects Versions: 3.7.2
>            Reporter: Yang Xia
>            Priority: Blocker
>
> Running 3.6.x {{gremlin-python}} with 3.7.x {{gremlin-server}} leads to 
> serialization errors:
> {code:java}
> return self.deserializers[DataType(bt)].objectify(buff, self, nullable)
> KeyError: <DataType.custom: 0>{code}
> with or without using {{ReferenceElementStrategy}} set on the server, 
> possibly due to a bug in how properties are being serialized and returned 
> from Java that is not inline with the specification. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to