You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Thomas Mueller (Jira)" <ji...@apache.org> on 2021/02/25 08:54:00 UTC
[jira] [Resolved] (OAK-9341) Composite node store: Unversioned
index is getting used even if it doesn't have mutable content index data
[ https://issues.apache.org/jira/browse/OAK-9341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Mueller resolved OAK-9341.
---------------------------------
Resolution: Won't Fix
Changing the behavior would not be backward-compatible, so the only option I see is to keep it as is.
> Composite node store: Unversioned index is getting used even if it doesn't have mutable content index data
> ----------------------------------------------------------------------------------------------------------
>
> Key: OAK-9341
> URL: https://issues.apache.org/jira/browse/OAK-9341
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: indexing
> Reporter: Amrit Verma
> Assignee: Thomas Mueller
> Priority: Major
>
> While using a composite node store, if an index doesn't specify a version in its name e.g. {{/oak:index/lucene}} it gets considered for use in a query even if it doesn't have the oak mount index data.
> This the probably due to the reason that `isIndexActive` check is only performed for the versioned indices here - https://github.com/apache/jackrabbit-oak/blob/08c7b20e0676739d9c445b5249c3f71004b6b894/oak-search/src/main/java/org/apache/jackrabbit/oak/plugins/index/search/spi/query/IndexName.java#L208-L215
--
This message was sent by Atlassian Jira
(v8.3.4#803005)