ExpectationsAwareTransaction (atlasdb-api 0.814.0 API)

All Superinterfaces:

Transaction
```
public interface ExpectationsAwareTransaction
extends Transaction
```
Implementors of this interface provide methods useful for tracking transactional expectations and whether they were breached as well as relevant metrics and alerts. Transactional expectations represent transaction-level limits and rules for proper usage of AtlasDB transactions (e.g. reading too much data overall). Todo(aalouane): move this out of API once part 4 is merged

Nested Class Summary
- Nested classes/interfaces inherited from interface com.palantir.atlasdb.transaction.api.Transaction
  Transaction.TransactionType

Method Summary

All Methods Instance Methods Abstract Methods
Modifier and Type	Method	Description
`long`	`getAgeMillis()`
`TransactionReadInfo`	`getReadInfo()`	Returns a point-in-time snapshot of transaction read information.
`void`	`reportExpectationsCollectedData()`	Update TEX data collection metrics for (post-mortem) transactions.

Methods inherited from interface com.palantir.atlasdb.transaction.api.Transaction
abort, commit, commit, delete, disableReadWriteConflictChecking, get, getAsync, getRange, getRanges, getRanges, getRanges, getRanges, getRangesLazy, getReadSentinelBehavior, getRows, getRowsColumnRange, getRowsColumnRange, getRowsColumnRangeIterator, getSortedColumns, getTimestamp, getTransactionType, isAborted, isUncommitted, markTableInvolved, onSuccess, put, setTransactionType, useTable

- Method Detail
  - getAgeMillis
```
long getAgeMillis()
```
  - getReadInfo
```
TransactionReadInfo getReadInfo()
```
    Returns a point-in-time snapshot of transaction read information.
  - reportExpectationsCollectedData
```
void reportExpectationsCollectedData()
```
    Update TEX data collection metrics for (post-mortem) transactions. Expected usage is that this method is called once after the transaction has been committed or aborted. This method won't report metrics if called on an in-progress transaction. Calling this twice after the transaction has committed or aborted will result in duplication. Clients should not call this method directly.