public abstract class FSDirectory extends BaseDirectory
SimpleFSDirectory is a straightforward
implementation using Files.newByteChannel.
However, it has poor concurrent performance
(multiple threads will bottleneck) as it
synchronizes when multiple threads read from the
same file.
NIOFSDirectory uses java.nio's
FileChannel's positional io when reading to avoid
synchronization when reading from the same file.
Unfortunately, due to a Windows-only Sun
JRE bug this is a poor choice for Windows, but
on all other platforms this is the preferred
choice. Applications using Thread.interrupt() or
Future.cancel(boolean) should use
RAFDirectory instead. See NIOFSDirectory java doc
for details.
MMapDirectory uses memory-mapped IO when
reading. This is a good choice if you have plenty
of virtual memory relative to your index size, eg
if you are running on a 64 bit JRE, or you are
running on a 32 bit JRE but your index sizes are
small enough to fit into the virtual memory space.
Java has currently the limitation of not being able to
unmap files from user code. The files are unmapped, when GC
releases the byte buffers. Due to
this bug in Sun's JRE, MMapDirectory's IndexInput.close()
is unable to close the underlying OS file handle. Only when
GC finally collects the underlying objects, which could be
quite some time later, will the file handle be closed.
This will consume additional transient disk usage: on Windows,
attempts to delete or overwrite the files will result in an
exception; on other platforms, which typically have a "delete on
last close" semantics, while such operations will succeed, the bytes
are still consuming space on disk. For many applications this
limitation is not a problem (e.g. if you have plenty of disk space,
and you don't rely on overwriting files on Windows) but it's still
an important limitation to be aware of. This class supplies a
(possibly dangerous) workaround mentioned in the bug report,
which may fail on non-Sun JVMs.
Unfortunately, because of system peculiarities, there is
no single overall best implementation. Therefore, we've
added the open(java.nio.file.Path) method, to allow Lucene to choose
the best FSDirectory implementation given your
environment, and the known limitations of each
implementation. For users who have no reason to prefer a
specific implementation, it's best to simply use open(java.nio.file.Path). For all others, you should instantiate the
desired implementation directly.
NOTE: Accessing one of the above subclasses either directly or
indirectly from a thread while it's interrupted can close the
underlying channel immediately if at the same time the thread is
blocked on IO. The channel will remain closed and subsequent access
to the index will throw a ClosedChannelException.
Applications using Thread.interrupt() or
Future.cancel(boolean) should use the slower legacy
RAFDirectory from the misc Lucene module instead.
The locking implementation is by default NativeFSLockFactory, but can be changed by
passing in a custom LockFactory instance.
Directory| Modifier and Type | Field and Description |
|---|---|
protected Path |
directory |
isOpen, lockFactory| Modifier | Constructor and Description |
|---|---|
protected |
FSDirectory(Path path,
LockFactory lockFactory)
Create a new FSDirectory for the named location (ctor for subclasses).
|
| Modifier and Type | Method and Description |
|---|---|
void |
close()
Closes the store to future operations.
|
IndexOutput |
createOutput(String name,
IOContext context)
Creates an IndexOutput for the file with the given name.
|
void |
deleteFile(String name)
Removes an existing file in the directory.
|
protected void |
ensureCanWrite(String name) |
long |
fileLength(String name)
Returns the length in bytes of a file in the directory.
|
protected void |
fsync(String name) |
Path |
getDirectory() |
String[] |
listAll()
Returns an array of strings, one for each entry in the directory.
|
static String[] |
listAll(Path dir)
Lists all files (including subdirectories) in the
directory.
|
static FSDirectory |
open(Path path)
Creates an FSDirectory instance, trying to pick the
best implementation given the current environment.
|
static FSDirectory |
open(Path path,
LockFactory lockFactory)
Just like
open(Path), but allows you to
also specify a custom LockFactory. |
void |
renameFile(String source,
String dest)
Renames
source to dest as an atomic operation,
where dest does not yet exist in the directory. |
void |
sync(Collection<String> names)
Ensure that any writes to these files are moved to
stable storage.
|
String |
toString()
For debug output.
|
ensureOpen, makeLockcopyFrom, openChecksumInput, openInputprotected final Path directory
protected FSDirectory(Path path, LockFactory lockFactory) throws IOException
path - the path of the directorylockFactory - the lock factory to use, or null for the default
(NativeFSLockFactory);IOException - if there is a low-level I/O errorpublic static FSDirectory open(Path path) throws IOException
NativeFSLockFactory.
The directory is created at the named location if it does not yet exist.
Currently this returns MMapDirectory for Linux, MacOSX, Solaris,
and Windows 64-bit JREs, NIOFSDirectory for other
non-Windows JREs, and SimpleFSDirectory for other
JREs on Windows. It is highly recommended that you consult the
implementation's documentation for your platform before
using this method.
NOTE: this method may suddenly change which
implementation is returned from release to release, in
the event that higher performance defaults become
possible; if the precise implementation is important to
your application, please instantiate it directly,
instead. For optimal performance you should consider using
MMapDirectory on 64 bit JVMs.
See above
IOExceptionpublic static FSDirectory open(Path path, LockFactory lockFactory) throws IOException
open(Path), but allows you to
also specify a custom LockFactory.IOExceptionpublic static String[] listAll(Path dir) throws IOException
IOException - if there was an I/O error during listingpublic String[] listAll() throws IOException
DirectorylistAll in class DirectoryIOException - in case of IO errorpublic long fileLength(String name) throws IOException
fileLength in class Directoryname - the name of the file for which to return the length.IOException - if there was an IO error while retrieving the file's
length.public void deleteFile(String name) throws IOException
deleteFile in class DirectoryIOExceptionpublic IndexOutput createOutput(String name, IOContext context) throws IOException
createOutput in class DirectoryIOExceptionprotected void ensureCanWrite(String name) throws IOException
IOExceptionpublic void sync(Collection<String> names) throws IOException
Directorysync in class DirectoryIOExceptionpublic void renameFile(String source, String dest) throws IOException
Directorysource to dest as an atomic operation,
where dest does not yet exist in the directory.
Notes: This method is used by IndexWriter to publish commits.
It is ok if this operation is not truly atomic, for example
both source and dest can be visible temporarily.
It is just important that the contents of dest appear
atomically, or an exception is thrown.
renameFile in class DirectoryIOExceptionpublic void close()
public Path getDirectory()
public String toString()
toString in class BaseDirectoryprotected void fsync(String name) throws IOException
IOExceptionCopyright © 2000-2015 Apache Software Foundation. All Rights Reserved.