Type: New Feature
Resolution: Won't Fix
Affects Version/s: 2.3.1
Fix Version/s: None
The problem the tag index solves is slow field cache loading and range queries, and reindexing an entire document to update fields that are not tokenized.
The tag index holds untokenized terms with a docfreq of 1 in a term dictionary like index file. The file also stores the docs per term, similar to
LUCENE-1278. The index also has a transaction log and in memory index for realtime updates to the tags. The transaction log is periodically merged into the existing tag term dictionary index file.
The TagIndexReader extends IndexReader and is unified with a regular index by ParallelReader. There is a doc id to terms skip pointer file for the IndexReader.document method. This file contains a pointer for looking up the terms for a document.
There is a higher level class that encapsulates writing a document with tag fields to IndexWriter and TagIndexWriter. This requires a hook into IndexWriter to coordinate doc ids and flushing segments to disk.
The writer class could be as simple as:
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|978d 7h 9m||1||Jason Rutherglen||24/Jan/11 21:16|
|Workflow||Default workflow, editable Closed status [ 12562262 ]||jira [ 12584736 ]|
|Workflow||jira [ 12431534 ]||Default workflow, editable Closed status [ 12562262 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Resolution||Won't Fix [ 2 ]|
|Field||Original Value||New Value|
[ Tag in the sense you described. In Lucene, an untokenized field. Yes, a
separate index that is dynamic while the main one is static except deletes.
The main problem, though not impossible, is syncing the segments. The tag
index needs the new segment docmap and a callback for each merge in
SegmentMerger. The write to the tag index needs the doc id for each
IndexWriter.addDocument call and a callback for each subsequent flush to
These event listeners can be used for other customized indexes.
On Thu, May 22, 2008 at 6:09 PM, Otis Gospodnetic (JIRA) <firstname.lastname@example.org>