THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Accurate text search
- Reuse code
- Scalability
- Performance, compare to RAMFSDirectory
User Input
- User needs to be able to provide the analyzer to be used with index and field type for each field. Note: A string can be Text or String in lucene. The two have different behavior
Index Persistence
Lucene context
...
Here search request is handled by Lucene and Lucene's Parser and aggregator is utilized. DistributedFSDirectory will provide a unified view to Lucene. Lucene will request DistributedFSDirectory to fetch index chunks. DistributedFSDirectory will aggregate the index chunks from the PR which hosts the data. This is similar to a Cache Client in behavior. Cache Client reaches different PRs and provides a unified data view to the user.
PlantUML |
---|
() User -> [Cache] : Search node cluster { database { () indexPR1 } [Cache] ..> [PR 1] [PR 1] --> [LucenePR1] [LucenePR1] --> [DistributedFSDirectory] [DistributedFSDirectory] -down-> [FSDirectoryPR1] [FSDirectoryPR1] -> indexPR1 database { () indexPR2 } [DistributedFSDirectory] -down-> [FSDirectoryPR2] [FSDirectoryPR2] -> indexPR2 } |
...