A transaction is an access operation in the Record Store by another component, such as the CAS Server API or Forge. Transactions provide a means to keep one operation isolated from another operation and allow each to operate independently.

In other words, one transaction can read while another is writing. Each transaction is either a READ_WRITE transaction or a READ transaction:

Each transaction is assigned a transaction ID. When a transaction begins, the Record Store service logs an INFO message with the transaction type and ID, as in this example of Forge performing a READ transaction (with an ID of 2) for a baseline update:

Started transaction 2 of type READ

An example of a Write transaction message would be the following:

Started transaction 3 of type READ_WRITE

Each transaction has a status, which is one of the following:

The rules for transactions are as follows:


Copyright © Legal Notices