Index inconsistency detection
-----------------------------
Key: QI-211
URL: http://issues.ops4j.org/browse/QI-211
Project: Qi4j
Issue Type: Improvement
Components: Indexing
Reporter: Niclas Hedhman
Assignee: Rickard Öberg
Currently it is possible for the EntityStore to have been updated, and right
after the system fails, leaving that update not indexed. It is not detected
that this has occurred nor is there any way to recover from the failure. The
re-index need (QI-192) does not fully cover this, as it is extremely expensive
to re-index the entire stores.
One possible solution would be that the entity IDs are recorded/persisted by
the Indexer upon 'entry' of the EntityStore, and that the Indexer goes straight
to the ES to retrieve those data never index upon start-up.
There are possible complications in the new way that we might do
EntityStoreUnitOfWork.apply() which is where the Indexer need to hook itself
into and not the ES itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
