Michele Rastelli

It will be based on Stream Transactions https://www.arangodb.com/docs/stable/http/transaction-stream-transaction.html , so requests could be sent immediately and not needed to be collected for later execution.

We are currently working on refactoring the java driver in order to make it return reactive types and behave accordingly to reactive principles. You can follow the development in https://github.com/arangodb/arangodb-java-driver/tree/reactor

The provided AQL query actually returns: ``` [ [ 1, 2 ] ] ``` therefore it is mapped to `ArrayList`. To return a flattened array that could be mapped to...

Thanks for clarifying, this seems indeed a bug.

You might also want to consider the alternative approach adopted in the upcoming reactive Java driver, which has an interface `ReplicationFactor` and 2 implementations `NumericReplicationFactor` and `SatelliteReplicationFactor`. However this is...

Consider that removing `PUT /_api/cursor/{cursor-identifier}` from the server-side API is a breaking change, which as of now is going to happen in ArangoDB 4.0, potentially together with others API breaking...

How is the subdomain name resolved? Do you get the port in the resolution? I.e. does it resolve to SRV records? As of now the driver requires hostname and port...

And soon after receiving the error, the client gets disconnected.

closing in favor of https://github.com/arangodb/arangodb-java-driver/pull/463

Fixed on the server side: https://github.com/arangodb/arangodb/pull/17426 It should be released in ArangoDB 3.11.