Thomas Mueller created OAK-10399:
------------------------------------
Summary: Automatically pick a merged index over multiple levels
Key: OAK-10399
URL: https://issues.apache.org/jira/browse/OAK-10399
Project: Jackrabbit Oak
Issue Type: Improvement
Components: query
Reporter: Thomas Mueller
When using the composite node store for blue-green deployments, multiple
versions of a index can exist at the same time, for a short period of time
(while both blue and green are running at the same time). In OAK-9301 we
support merged indexes.
What we don't support currently is merged indexes over multiple levels. Example:
* /oak:index/index-1 (first version of the index)
* /oak:index/index-1-custom-1 (customization of that index)
* /oak:index/index-2 (new base version)
* /oak:index/index-2-custom-1 (auto-merged index)
* /oak:index/index-3 (the second new base version)
* /oak:index/index-3-custom-1 (auto-merged index)
In this case, index-3 is used for queries, instead of index-3-custom-1.
The reason is the following: whenever we auto-merge, we set the merges property
to the previous base version, and the previous customization. This works well
for index-2-custom-1, but doesn't work for index-3-custom-1.
We need to change the index picking algorithm, such that only one level of base
indexes is checked: only the existence of index-3. The existence of index-2
must not be checked.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
