 |
Page History
...
Proposed Relational Implementation under Lucene 5.0.0
Lucene provides support for limited relational expression starting with Lucene 3.4. A single level parent/child relationship can be maintained as a one to many relationship between one document and several others. This support provides LexEVS with an opportunity to improve index search times and reduce index size.
| Code Block | ||||
|---|---|---|---|---|
| ||||
//This appears to be where a good part of the filtering on boundary docs takes place. A rethinking and reimplementing of all of these will be necessary. org.lexevs.dao.index.lucene.v2010.entity.SingleTemplateDisposableLuceneCommonEntityDao org.lexevs.dao.index.lucene.AbstractBaseLuceneIndexTemplateDao org.lexevs.dao.index.access.entity.CommonEntityDao //Deeply integrated with boundary doc position and scoring. Will need to be rethought and reimplemented against the new Collector class //in Lucene. This will also be moved from the Indexer into the DAO project. edu.mayo.informatics.indexer.lucene.hitcollector.AbstractBestScoreOfEntityHitCollector<T> //This companion to it doesn’t seem to have a code path that calls it and may be able to be disposed of edu.mayo.informatics.indexer.lucene.hitcollector.BitSetFilteringBestScoreOfEntityHitCollector //These classes will all need to be revised or replaced to implement //the BlockJoinQuery indexing support edu.mayo.informatics.indexer.api.generators.DocumentFromStringsGenerator org.lexevs.dao.index.indexer.LuceneLoaderCodeIndexer org.lexevs.dao.index.indexer.LuceneLoaderCode //While most code paths for indexing flow through this class access through a BaseLoader //a number of alternative paths include two special case loaders and the revision/authoring API org.lexevs.dao.index.indexer.EntityBatchingIndexCreator |
