Session: Saving changes

You can ask the server to wait until the indexes are caught up with changes made within the current session before the saveChanges returns.

• You can set a timeout (default: 15 seconds).
• You can specify whether you want to throw on timeout (default: false).
• You can specify indexes that you want to wait for. If you don't specify anything here, RavenDB will automatically select just the indexes that are impacted by this write.

session.advanced().waitForIndexesAfterSaveChanges(builder -> {
    builder.withTimeout(Duration.ofSeconds(30))
        .throwOnTimeout(true)
        .waitForIndexes("index/1", "index/2");

    Employee employee = new Employee();
    employee.setFirstName("John");
    employee.setLastName("Doe");
    session.store(employee);

    session.saveChanges();
});

Sometimes you might need to ensure that changes made in the session will be replicated to more than one node of the cluster before the saveChanges returns. It can be useful if you have some writes that are really important so you want to be sure the stored values will reside on multiple machines. Also it might be necessary to use when you customize the read balance behavior and need to ensure the next request from the user will be able to read what he or she just wrote (the next open session might access a different node).

You can ask the server to wait until the replication is caught up with those particular changes.

• You can set a timeout (default: 15 seconds).
• You can specify whether you want to throw on timeout, which may happen in case of network issues (default: true).
• You can specify to how many replicas (nodes) the currently saved write must be replicated, before the saveChanges returns (default: 1).
• You can specify whether the saveChanges will return only when the current write was replicated to majority of the nodes (default: false).

session
    .advanced()
    .waitForReplicationAfterSaveChanges(builder -> {
        builder.withTimeout(Duration.ofSeconds(30))
            .throwOnTimeout(false) //default true
            .numberOfReplicas(2)//minimum replicas to replicate
            .majority(false);
    });

Employee employee = new Employee();
employee.setFirstName("John");
employee.setLastName("Doe");

session.store(employee);
session.saveChanges();

Setting transactionMode to TransactionMode.CLUSTER_WIDE will enable the Cluster Transactions feature.

With this feature enabled the Session will support the following write commands:

• store
• delete
• createCompareExchangeValue
• updateCompareExchangeValue
• deleteCompareExchangeValue

Here is an example of creating a unique user with cluster wide.

try (IDocumentStore store = new DocumentStore()) {
    SessionOptions sessionOptions = new SessionOptions();
    // default is: TransactionMode.SINGLE_NODE
    sessionOptions.setTransactionMode(TransactionMode.CLUSTER_WIDE);
    try (IDocumentSession session = store.openSession(sessionOptions)) {
        Employee user = new Employee();
        user.setFirstName("John");
        user.setLastName("Doe");

        session.store(user);

        // this transaction is now conditional on this being
        // successfully created (so, no other users with this name)
        // it also creates an association to the new user's id
        session.advanced().clusterTransaction()
            .createCompareExchangeValue("usernames/John", user.getId());

        session.saveChanges();
    }
}