VelocyJack deserialization not always called

[rocketraman]

I have configured VelocyJack deserialization as per the docs. I note that in some cases, this deserializer is not called. Specifically, I am testing some code that simply does:

// 1
collection.insertDocument(doc)
...
// 2
collection.getDocument(key, MyDoc::class.java, DocumentReadOptions())

and the built-in default deserializer is being called at (2), not the VelocyJack deserializer. This was driving me nuts until I attached a debugger to the system to determine that the wrong deserializer was being called at ArangoExecutor.createResult.

ArangoExecutor upon initialization always requests the INTERNAL serializer, even if a custom one is defined.

Clearly the custom serialization is a work in progress. I'm gonna switch back to the default serialization for now.

[fdominik]

I run into the same issues. However I realized that query() is the only method, which works correctly. So in order to getDcoument, I am just calling query() method with "RETURN DOCUMENT(@docId)" as the String query.

Probably related to arangodb/arangodb-java-driver#271

[rashtao]

related slack thread: https://arangodb-community.slack.com/archives/C1R9YA869/p1561033350006100

[rashtao]

It could be caused by the usage of the INTERNAL (de)Serializer instead of the CUSTOM one.
As eg: https://github.com/arangodb/arangodb-java-driver/blob/5e7add2c19150830c8ed0bcc17e647372e780286/src/main/java/com/arangodb/internal/ArangoExecutor.java#L47

[rocketraman]

It could be caused by the usage of the INTERNAL (de)Serializer instead of the CUSTOM one.

Yup. As per my OP:

ArangoExecutor upon initialization always requests the INTERNAL serializer, even if a custom one is defined.

[rashtao]

fixed in https://github.com/arangodb/arangodb-java-driver-async/releases/tag/v6.0.0