org.apache.lucene.store |
Binary i/o API, used for all index data.
|
Java Source File Name | Type | Comment |
AlreadyClosedException.java | Class | This exception is thrown when there is an attempt to
access something that has already been closed. |
BufferedIndexInput.java | Class | Base implementation class for buffered
IndexInput . |
BufferedIndexOutput.java | Class | Base implementation class for buffered
IndexOutput . |
Directory.java | Class | A Directory is a flat list of files. |
FSDirectory.java | Class | Straightforward implementation of
Directory as a directory of files.
Locking implementation is by default the
SimpleFSLockFactory , but
can be changed either by passing in a
LockFactory instance to
getDirectory , or specifying the LockFactory class by setting
org.apache.lucene.store.FSDirectoryLockFactoryClass Java system
property, or by calling
FSDirectory.setLockFactory after creating
the Directory.
Directories are cached, so that, for a given canonical
path, the same FSDirectory instance will always be
returned by getDirectory . |
GCJDirectory.java | Class | Native file-based
Directory implementation, using GCJ. |
GCJIndexInput.java | Class | Native file-based
IndexInput implementation, using GCJ. |
IndexInput.java | Class | Abstract base class for input from a file in a
Directory . |
IndexOutput.java | Class | Abstract base class for output to a file in a Directory. |
Lock.java | Class | An interprocess mutex lock.
Typical use might look like:
new Lock.With(directory.makeLock("my.lock")) {
public Object doBody() {
... |
LockFactory.java | Class | Base class for Locking implementation. |
LockObtainFailedException.java | Class | This exception is thrown when the write.lock
could not be acquired. |
LockReleaseFailedException.java | Class | This exception is thrown when the write.lock
could not be released. |
LockStressTest.java | Class | Simple standalone tool that forever acquires & releases a
lock using a specific LockFactory. |
LockVerifyServer.java | Class | Simple standalone server that must be running when you
use
VerifyingLockFactory . |
MMapDirectory.java | Class | File-based
Directory implementation that uses mmap for input.
To use this, invoke Java with the System property
org.apache.lucene.FSDirectory.class set to
org.apache.lucene.store.MMapDirectory. |
MockRAMDirectory.java | Class | This is a subclass of RAMDirectory that adds methods
intented to be used only by unit tests. |
MockRAMInputStream.java | Class | Used by MockRAMDirectory to create an input stream that
keeps track of when it's been closed. |
MockRAMOutputStream.java | Class | Used by MockRAMDirectory to create an output stream that
will throw an IOException on fake disk full, track max
disk space actually used, and maybe throw random
IOExceptions. |
NativeFSLockFactory.java | Class | Implements
LockFactory using native OS file
locks. |
NoLockFactory.java | Class | Use this
LockFactory to disable locking entirely.
This LockFactory is used when you call
FSDirectory.setDisableLocks .
Only one instance of this lock is created. |
RAMDirectory.java | Class | A memory-resident
Directory implementation. |
RAMFile.java | Class | |
RAMInputStream.java | Class | A memory-resident
IndexInput implementation. |
RAMOutputStream.java | Class | A memory-resident
IndexOutput implementation. |
SimpleFSLockFactory.java | Class | Implements
LockFactory using
File.createNewFile . |
SingleInstanceLockFactory.java | Class | Implements
LockFactory for a single in-process instance,
meaning all locking will take place through this one instance.
Only use this
LockFactory when you are certain all
IndexReaders and IndexWriters for a given index are running
against a single shared in-process Directory instance. |
TestBufferedIndexInput.java | Class | |
TestHugeRamFile.java | Class | Test huge RAMFile with more than Integer.MAX_VALUE bytes. |
TestLock.java | Class | |
TestLockFactory.java | Class | |
TestMMapDirectory.java | Class | |
TestWindowsMMap.java | Class | |
VerifyingLockFactory.java | Class | A
LockFactory that wraps another
LockFactory and verifies that each lock obtain/release
is "correct" (never results in two processes holding the
lock at the same time). |
_TestHelper.java | Class | This class provides access to package-level features defined in the
store package. |