Description
Currently the suggestor storage logic maintains a timestamp of when suggestor data was last updated in property lastUpdated in :suggesterStatus node. Actual suggest data is stored in a separate node :suggest-data.
/oak:index/lucene-suggest: { reindexCount = 1, name = lucene-suggest, compatVersion = 2, reindex = false, type = lucene, jcr:primaryType = oak:QueryIndexDefinition, :facet-config = { ... }, indexRules = { ... }, :data = { ... }, :status = { ... }, :suggest-data = { ... }, :suggesterStatus = { ... }}
It would be better if this property is stored in :suggest-data. This would simplify adding support for multiplexing as each dir node would be having complete info
+ :oak:mount-foo-suggest-data - lastUpdated + :suggest-data - lastUpdated
Attachments
Attachments
Issue Links
- blocks
-
OAK-4566 Multiplexing store support in Lucene Indexes
- Closed
patch for the same
catholicon Can you have a look. It does not check for backward compatibility so for upgraded system there would be a slight hit that first index post Oak version update would trigger suggestor index update. But that should be ok