Michele Rastelli

What you describe should just work fine. In order to debug it further, you can enable debug level logging for requests and response (logger `com.arangodb.internal.net.Communication`) and verify the presence of...

I don't think that `arangoOperations.insert(edgeInstance, new DocumentCreateOptions().streamTransactionId(transaction.getId()));` is a mistake. You can double check whether it sends the transaction headers in the communication logs as mentioned above. Note that `ArangoOperations#insert(T,...

Thanks for clarifying, you are correct: the mapping layer has no awareness of the transaction. This means that the queries issued to populate the relations properties (eg. fields annotated with...

Exactly, the transaction is not propagated to the methods responsible to fetch the linked entities. You might want to have a look at the work in progress to support transactions...

Unfortunately due to internal prioritization, the related work has not been planned yet. Note that the PR linked above is a community contribution.

Fixed in https://github.com/arangodb/arangodb-java-driver/releases/tag/v7.0.0-ALPHA.1

Credentials are not logged anymore since version 7.0.0. https://github.com/arangodb/arangodb-java-driver/releases/tag/v7.0.0-RC.4

Closing as fixed in version [7.0.0](https://github.com/arangodb/arangodb-java-driver/releases/tag/v7.0.0).

Hi @obrunojava , thanks for your offer! In my opinion, the problem cannot be easily fixed, because in the `HttpConnection` (https://github.com/arangodb/arangodb-java-driver/blob/main/http/src/main/java/com/arangodb/http/HttpConnection.java) the username and password are converted to an `Authorization`...

Even if we could avoid interning the password string, this will be effectively a long-living String in the heap, living until the driver will be used, because we need to...