Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
We currently have 4 indexing subsystems and all are at different levels of completeness and none supports all features available in the API.
I think that we need a whole new attack on indexing/query, redesign APIs if needed. Instead of trying to fix the broken system we have, I think a brand new, parallel I/Q design should be developed and where it will be much easier to develop subsystems for it, in a similar fashion as MapEntityStore simplifies Key/Value capable entity stores.
Attachments
Issue Links
- is related to
-
POLYGENE-132 Improve Indexing/Query Semantics
- Open
-
POLYGENE-45 Investigate all @Ignore on tests.
- Closed
- supercedes
-
POLYGENE-222 Remove Indexing-SQL from 3.0
- Closed