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 2019/03/18 00:40:00 UTC

[jira] [Updated] (OAK-8137) Oak run tooling to run a RepositoryInitializer on top a list index definitions

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

Vikas Saurabh updated OAK-8137:
-------------------------------
    Labels: doc-impacting  (was: )

> Oak run tooling to run a RepositoryInitializer on top a list index definitions
> ------------------------------------------------------------------------------
>
>                 Key: OAK-8137
>                 URL: https://issues.apache.org/jira/browse/OAK-8137
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: run
>            Reporter: Vikas Saurabh
>            Assignee: Vikas Saurabh
>            Priority: Major
>              Labels: doc-impacting
>
> Product index definitions are delivered using {{RepositoryInitializer}} (e.g. AEM and oak itself).
> Oak run has tooling to dump index definitions as a json and also ability to create lucene indexes as defined by an index definition json.
> That leaves a gap in tooling where we can dump current set of index definitions and prepare an index definition description to prepare of upgrades (thus saving time "during" upgrade). This step is currently done manually and hence is error prone. It'd be nice to have some automated tooling to assist in such a flow.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)