-
-
Notifications
You must be signed in to change notification settings - Fork 489
201311solr
Jesse Eichar edited this page Mar 19, 2015
·
13 revisions
Use SOLR indexes instead of the current Lucene implementation.
Benefits:
- Scalability
- Native Spatial search support instead of using GeoTools
- Possibly the OR queries of alphanumeric & spatial search criteria can be resolved (required for CSW compliancy)
Challenges:
- Multilingual indexing and search
- Spatial operators support. Verify if all spatial operators provided by GeoTools are also available in SOLR.
References:
- Apache SOLR
- Multilingual Indexing and Search
- SOLR Spatial query parameters
- Under development
- Spatial extension
Interest Lars, Bernhard, Paul H, Maria, Jesse, Jeroen
- Solr rough solr based spatial query then Java filter with our implementation
- Multilingual support
- We will have 1 doc per md doc and multiple field per language.
- dynamic field based search to search across all languages
- Search Suggestions
- Hierarchical Faceting
- Error detection
- flag any MD that failed indexing or had problems during the process
- Search response must be very fast if faceting slows it down then do a second faceting search
- Statistics
- camel routing for putting into another solr instance for stats
- or AnalyticsQuery API
- Must be FAST
- in memory maybe use metrics?
- periodic snapshots in storage? SOLR, database?
If you have some comments, start a discussion, raise an issue or use one of our other communication channels to talk to us.