Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.3.8
-
None
-
None
Description
Placeholder issue for the moment. Require more investigations and a
test case.
It seems that if an index definition has reindex=true but no index
provider is able to serve the index type, the re-indexing process will
retry endlessly.
Possible way to reproduce
- create an initial content with an index definition of type lucene
and reindex=true - start the repository without the lucene IndexProvider or having it
disabled. - see in the logs that the reindex will always re-index from scratch
as there are no checkpoints.
Should the reindex fail and stop after some attempts?
Attachments
Issue Links
- relates to
-
OAK-3533 Make it possible to disable LuceneIndexProviderService via OSGi configuration
-
- Closed
-