|FieldSetting||For non package access see org.apache.lucene.index.IndexReader#getFieldNames(org.apache.lucene.index.IndexReader.FieldOption)||code | html|
|InstantiatedAllTermDocs||Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.||code | html|
|InstantiatedDocument||A document in the instantiated index object graph, optionally coupled to the vector space view.||code | html|
|InstantiatedIndex||Represented as a coupled graph of class instances, this all-in-memory index store implementation delivers search results up to a 100 times faster than the file-centric RAMDirectory at the cost of greater RAM consumption.||code | html|
|InstantiatedIndexReader||An InstantiatedIndexReader is not a snapshot in time, it is completely in
sync with the latest commit to the store!
Consider using InstantiatedIndex as if it was immutable.
|code | html|
|InstantiatedIndexReader.NormUpdate||code | html|
|InstantiatedIndexWriter||This class, similar to org.apache.lucene.index.IndexWriter , has no locking mechanism.||code | html|
|InstantiatedIndexWriter.FieldSetting||code | html|
|InstantiatedIndexWriter.TermDocumentInformationFactory||code | html|
|InstantiatedTerm||A term in the inverted index, coupled to the documents it occurs in.||code | html|
|InstantiatedTermDocs||A org.apache.lucene.index.TermDocs navigating an InstantiatedIndexReader .||code | html|
|InstantiatedTermDocumentInformation||There is one instance of this class per indexed term in a document and it contains the meta data about each occurrence of a term in a document.||code | html|
|InstantiatedTermEnum||A org.apache.lucene.index.TermEnum navigating an org.apache.lucene.store.instantiated.InstantiatedIndexReader .||code | html|
|InstantiatedTermFreqVector||Vector space view of a document in an InstantiatedIndexReader .||code | html|
|InstantiatedTermPositionVector||Extended vector space view of a document in an InstantiatedIndexReader .||code | html|
|InstantiatedTermPositions||A org.apache.lucene.index.TermPositions navigating an InstantiatedIndexReader .||code | html|
InstantiatedIndex, alternative RAM store for small corpora.
WARNING: This contrib is experimental and the APIs may change without warning.
Represented as a coupled graph of class instances, this all-in-memory index store implementation delivers search results up to a 100 times faster than the file-centric RAMDirectory at the cost of greater RAM consumption.
Just as the default store implementation, InstantiatedIndex comes with an IndexReader and IndexWriter. The latter share many method signatures with the file-centric IndexWriter.
It is also possible to load the content of another index by passing an IndexReader to the InstantiatedIndex constructor.
At a few thousand ~160 characters long documents InstantiatedIndex outperforms RAMDirectory some 50x, 15x at 100 documents of 2000 characters length, and is linear to RAMDirectory at 10,000 documents of 2000 characters length.
Mileage may vary depending on term saturation.
Populated with a single document InstantiatedIndex is almost, but not quite, as fast as MemoryIndex.
It takes more or less the same time to populate an InstantiatedIndex as it takes to populate a RAMDirectory. Hardly any effort has been put in to optimizing the InstantiatedIndexWriter, only minimizing the amount of time needed to write-lock the index has been considered.
Could replace any small index that could do with greater response time. spell check a priori index, the index of new documents exposed to user search agent queries, to compile classifiers in machine learning environments, etc.