Class BaseTransaction.TransactionTableOperations
- All Implemented Interfaces:
- TableOperations
- Enclosing class:
- BaseTransaction
- 
Constructor SummaryConstructors
- 
Method SummaryModifier and TypeMethodDescriptionvoidcommit(TableMetadata underlyingBase, TableMetadata metadata) Replace the base table metadata with a new version.current()Return the currently loaded table metadata, without checking for updates.Returns aEncryptionManagerto encrypt and decrypt data files.io()Returns aFileIOto read and write table data and metadata files.Returns aLocationProviderthat supplies locations for new new data files.metadataFileLocation(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.longCreate a new ID for a Snapshotrefresh()Return the current table metadata after checking for updates.Methods inherited from class java.lang.Objectclone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface org.apache.iceberg.TableOperationsrequireStrictCleanup, temp
- 
Constructor Details- 
TransactionTableOperationspublic TransactionTableOperations()
 
- 
- 
Method Details- 
currentDescription copied from interface:TableOperationsReturn the currently loaded table metadata, without checking for updates.- Specified by:
- currentin interface- TableOperations
- Returns:
- table metadata
 
- 
refreshDescription copied from interface:TableOperationsReturn the current table metadata after checking for updates.- Specified by:
- refreshin interface- TableOperations
- Returns:
- table metadata
 
- 
commitDescription copied from interface:TableOperationsReplace the base table metadata with a new version.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 CommitStateUnknownExceptionin 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.- Specified by:
- commitin interface- TableOperations
- Parameters:
- underlyingBase- table metadata on which changes were based
- metadata- new table metadata with updates
 
- 
ioDescription copied from interface:TableOperationsReturns aFileIOto read and write table data and metadata files.- Specified by:
- ioin interface- TableOperations
 
- 
encryptionDescription copied from interface:TableOperationsReturns aEncryptionManagerto encrypt and decrypt data files.- Specified by:
- encryptionin interface- TableOperations
 
- 
metadataFileLocationDescription copied from interface:TableOperationsGiven the name of a metadata file, obtain the full path of that file using an appropriate base location of the implementation's choosing.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).- Specified by:
- metadataFileLocationin interface- TableOperations
 
- 
locationProviderDescription copied from interface:TableOperationsReturns aLocationProviderthat supplies locations for new new data files.- Specified by:
- locationProviderin interface- TableOperations
- Returns:
- a location provider configured for the current table state
 
- 
newSnapshotIdpublic long newSnapshotId()Description copied from interface:TableOperationsCreate a new ID for a Snapshot- Specified by:
- newSnapshotIdin interface- TableOperations
- Returns:
- a long snapshot ID
 
 
-