[
https://issues.apache.org/jira/browse/OAK-9449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Gupta resolved OAK-9449.
------------------------------
Fix Version/s: 1.42.0
Resolution: Fixed
> Any new (elastic) index def added after Out of the band reindexing will
> trigger reindexing when the async cycle will run the first index update
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OAK-9449
> URL: https://issues.apache.org/jira/browse/OAK-9449
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Nitin Gupta
> Assignee: Nitin Gupta
> Priority: Major
> Fix For: 1.42.0
>
>
> When we will do an Out of band indexing for any elastic index , it will
> create the remote elastic index.
> And then we need to apply the index def to the node store in a separate step.
>
> However, once the oak process will observe this new change, it will trigger a
> reindex on this newly added index because of logic at [0]. This is wrong,
> since this reindex in not needed.
> In case of a newly added lucene index, there are hidden nodes such as :data
> which according to the logic at [0] prevents it from getting reindexed.
>
> However any newly added elastic index from Out Of the Band indexer does not
> have any such hidden nodes (because it doesn't store the indexed data locally
> like lucene), so it leads to reindexing.
>
>
> [0]:
> [https://github.com/oak-indexing/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/IndexUpdate.java#L235#L251]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
