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 "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2017/10/12 18:09:00 UTC

[jira] [Updated] (OAK-6823) oak-run tooling to compare two (json) index definition

     [ https://issues.apache.org/jira/browse/OAK-6823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vikas Saurabh updated OAK-6823:
-------------------------------
    Summary: oak-run tooling to compare two (json) index definition  (was: oak-run tooling to comparetwo (json) index definition)

> oak-run tooling to compare two (json) index definition
> ------------------------------------------------------
>
>                 Key: OAK-6823
>                 URL: https://issues.apache.org/jira/browse/OAK-6823
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene
>            Reporter: Vikas Saurabh
>            Assignee: Vikas Saurabh
>            Priority: Minor
>
> We should provide a way to compare 2 (sets of) index definitions and give suggestions to merge it.
> Such a utility would be useful when index defs are customized but we'd also want to utilize some improved defs by upgrades.
> While aggregates and non-regex-property index rules would be simple to merge (they don't step on each other's foot).
> But, we need to be careful with how we order regex properties. I think for such cases, we need to elaborate on which rules are potentially conflicting - but, we should not attempt to fix/provide-merges for such cases at least to begin with.
> /cc [~chetanm], [~tmueller]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)