We use Javers with Cosmosdb MongoDb API and it works nicely. The only problem we have is that cosmosdb does not support transactions on more than one collection. We have a MongoTransactionManager bean that we use for single collection transactions but Javers pick it and try to put up a transaction with jv_snapshots and the collection we are updating.
Is there a way to configure Javers to somehow ignore the MongoTransactionManager bean present in our service ?