[
https://issues.apache.org/jira/browse/TINKERPOP3-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP3-733:
----------------------------------------
Affects Version/s: (was: 3.0.0.GA)
Fix Version/s: 3.0.0.GA
I noticed that the other day, but hadn't come back to review it yet. I was
pretty sure that there were tests to validate the behavior but maybe there
aren't.
> Gremlin driver deserialization exception does not bubble up
> -----------------------------------------------------------
>
> Key: TINKERPOP3-733
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-733
> Project: TinkerPop 3
> Issue Type: Bug
> Components: driver
> Reporter: Adrian Gonzalez
> Assignee: stephen mallette
> Fix For: 3.0.0.GA
>
>
> I ran into this issue trying to use titan 0.9.0-M2 with gremlin-server
> 3.0.0.M9-incubator. Titan was returning a serialized RelationIdentifier
> which understandably could not be deserialized on the client side using the
> driver. I have managed to work around this by using the IoRegistry, however
> the SerializationException thrown in
> GryoMessageSerializerV1d0.deserializeResponse() does not bubble back up to
> the CompletableFuture<ResultSet> returned from the Client.submitAsync() nor
> the CompletableFuture<List<Result> returned from ResultSet.all(). A warning
> is logged in DefaultChannelPipeline.exceptionCaught(), but that is as far as
> it goes. Or am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
