public class LocalLogStore extends HadoopFileSystemLogStore
LogStore implementation (should be used for testing only!).
Production users should specify the appropriate LogStore implementation in Spark properties.
We assume the following from FileSystem implementations:
| Constructor and Description |
|---|
LocalLogStore(org.apache.hadoop.conf.Configuration hadoopConf) |
| Modifier and Type | Method and Description |
|---|---|
java.lang.Boolean |
isPartialWriteVisible(org.apache.hadoop.fs.Path path,
org.apache.hadoop.conf.Configuration hadoopConf)
:: DeveloperApi ::
Whether a partial write is visible for the underlying file system of `path`.
|
void |
write(org.apache.hadoop.fs.Path path,
java.util.Iterator<java.lang.String> actions,
java.lang.Boolean overwrite,
org.apache.hadoop.conf.Configuration hadoopConf)
This write implementation needs to wrap `writeWithRename` with `synchronized` as rename()
for
RawLocalFileSystem doesn't throw an exception when the target file
exists. |
createTempPath, listFrom, read, resolvePathOnPhysicalStorage, writeWithRenameinitHadoopConfpublic LocalLogStore(org.apache.hadoop.conf.Configuration hadoopConf)
public void write(org.apache.hadoop.fs.Path path,
java.util.Iterator<java.lang.String> actions,
java.lang.Boolean overwrite,
org.apache.hadoop.conf.Configuration hadoopConf)
throws java.io.IOException
RawLocalFileSystem doesn't throw an exception when the target file
exists. Hence, we must make sure `exists + rename` in `writeWithRename` is atomic in our tests.public java.lang.Boolean isPartialWriteVisible(org.apache.hadoop.fs.Path path,
org.apache.hadoop.conf.Configuration hadoopConf)
throws java.io.IOException
LogStoreisPartialWriteVisible in class LogStorejava.io.IOException - if there's an issue resolving the FileSystem