public interface TableOperations
Modifier and Type | Method and Description |
---|---|
void |
commit(TableMetadata base,
TableMetadata metadata)
Replace the base table metadata with a new version.
|
TableMetadata |
current()
Return the currently loaded table metadata, without checking for updates.
|
default 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.
|
default long |
newSnapshotId()
Create a new ID for a Snapshot
|
TableMetadata |
refresh()
Return the current table metadata after checking for updates.
|
default boolean |
requireStrictCleanup()
Whether to clean up uncommitted metadata files only when a commit fails with a
CleanableFailure exception. |
default TableOperations |
temp(TableMetadata uncommittedMetadata)
Return a temporary
TableOperations instance that uses configuration from uncommitted
metadata. |
TableMetadata current()
TableMetadata refresh()
void commit(TableMetadata base, TableMetadata metadata)
This 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.
base
- table metadata on which changes were basedmetadata
- new table metadata with updatesdefault EncryptionManager encryption()
EncryptionManager
to encrypt and decrypt data
files.java.lang.String metadataFileLocation(java.lang.String fileName)
The 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)
.
LocationProvider locationProvider()
LocationProvider
that supplies locations for new new data files.default TableOperations temp(TableMetadata uncommittedMetadata)
TableOperations
instance that uses configuration from uncommitted
metadata.
This is called by transactions when uncommitted table metadata should be used; for example, to create a metadata file location based on metadata in the transaction that has not been committed.
Transactions will not call refresh()
or commit(TableMetadata,
TableMetadata)
.
uncommittedMetadata
- uncommitted table metadatadefault long newSnapshotId()
default boolean requireStrictCleanup()
CleanableFailure
exception.
This defaults to true: cleanup will only occur for exceptions marked as CleanableFailure