public class BaseTransaction.TransactionTableOperations extends java.lang.Object implements TableOperations
| Constructor and Description |
|---|
TransactionTableOperations() |
| Modifier and Type | Method and Description |
|---|---|
void |
commit(TableMetadata underlyingBase,
TableMetadata metadata)
Replace the base table metadata with a new version.
|
TableMetadata |
current()
Return the currently loaded table metadata, without checking for updates.
|
EncryptionManager |
encryption()
Returns a
EncryptionManager to encrypt and decrypt data
files. |
FileIO |
io()
Returns a
FileIO to read and write table data and metadata files. |
LocationProvider |
locationProvider()
Returns a
LocationProvider that supplies locations for new new data files. |
java.lang.String |
metadataFileLocation(java.lang.String fileName)
Given the name of a metadata file, obtain the full path of that file using an appropriate base
location of the implementation's choosing.
|
long |
newSnapshotId()
Create a new ID for a Snapshot
|
TableMetadata |
refresh()
Return the current table metadata after checking for updates.
|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waittemppublic TableMetadata current()
TableOperationscurrent in interface TableOperationspublic TableMetadata refresh()
TableOperationsrefresh in interface TableOperationspublic void commit(TableMetadata underlyingBase, TableMetadata metadata)
TableOperationsThis method should implement and document atomicity guarantees.
Implementations must check that the base metadata is current to avoid overwriting updates. Once the atomic commit operation succeeds, implementations must not perform any operations that may fail because failure in this method cannot be distinguished from commit failure.
Implementations must throw a CommitStateUnknownException in cases where it cannot be
determined if the commit succeeded or failed. For example if a network partition causes the
confirmation of the commit to be lost, the implementation should throw a
CommitStateUnknownException. This is important because downstream users of this API need to
know whether they can clean up the commit or not, if the state is unknown then it is not safe
to remove any files. All other exceptions will be treated as if the commit has failed.
commit in interface TableOperationsunderlyingBase - table metadata on which changes were basedmetadata - new table metadata with updatespublic FileIO io()
TableOperationsFileIO to read and write table data and metadata files.io in interface TableOperationspublic EncryptionManager encryption()
TableOperationsEncryptionManager to encrypt and decrypt data
files.encryption in interface TableOperationspublic java.lang.String metadataFileLocation(java.lang.String fileName)
TableOperationsThe file may not exist yet, in which case the path should be returned as if it were to be
created by e.g. FileIO.newOutputFile(String).
metadataFileLocation in interface TableOperationspublic LocationProvider locationProvider()
TableOperationsLocationProvider that supplies locations for new new data files.locationProvider in interface TableOperationspublic long newSnapshotId()
TableOperationsnewSnapshotId in interface TableOperations