All Classes and Interfaces

Class	Description
AzureLogStore	LogStore implementation for Azure.
CloseableIterator<T>	:: DeveloperApi :: An iterator that may contain resources which should be released after use.
FileNameUtils	Helper for misc functions relating to file names for delta commits.
GCSLogStore	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.
HadoopFileSystemLogStore	Default implementation of LogStore for Hadoop FileSystem implementations.
HDFSLogStore	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.
LineCloseableIterator	Turn a Reader to CloseableIterator which can be read on demand.
LocalLogStore	Default LogStore implementation (should be used for testing only!).
LogStore	:: DeveloperApi ::
LogStoreErrors
PathLock	A lock that provides per-file-path `acquire` and `release` semantics.
S3LogStoreUtil	Static utility methods for the S3SingleDriverLogStore.
S3SingleDriverLogStore	Single Spark-driver/JVM LogStore implementation for S3.
ThreadUtils