All Classes and Interfaces
Class
Description
Interface for objects that represents the base information for a commit.
Interface for metadata actions in Delta.
Interface for protocol actions in Delta.
LogStore implementation for Azure.
:: DeveloperApi ::
An iterator that may contain resources which should be released after use.
Representation of a commit file
The CommitCoordinatorClient is responsible for communicating with the commit coordinator
and backfilling commits.
Helper for misc functions relating to file names for delta commits.
The
LogStore implementation for GCS, which uses gcs-connector to
provide the necessary atomic and durability guarantees:
Atomic Visibility: Read/read-after-metadata-update/delete are strongly
consistent for GCS.
Consistent Listing: GCS guarantees strong consistency for both object and
bucket listing operations.Response container for
CommitCoordinatorClient.getCommits(TableDescriptor, Long, Long).Default implementation of
LogStore for Hadoop FileSystem implementations.The
LogStore implementation for HDFS, which uses Hadoop FileContext API's to
provide the necessary atomic and durability guarantees:
Atomic visibility of files: `FileContext.rename` is used write files which is atomic for
HDFS.
Consistent file listing: HDFS file listing is consistent.
Turn a
Reader to CloseableIterator which can be read on demand.Default
LogStore implementation (should be used for testing only!).:: DeveloperApi ::
A lock that provides per-file-path `acquire` and `release` semantics.
Static utility methods for the S3SingleDriverLogStore.
Single JVM LogStore implementation for S3.
Container for all the info to uniquely identify the table
Identifier for a table.
A container class to inform the CommitCoordinatorClient about any changes in Protocol/Metadata