[ https://issues.apache.org/jira/browse/OAK-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099882#comment-16099882 ]
Chetan Mehrotra edited comment on OAK-6471 at 7/26/17 5:27 AM: --------------------------------------------------------------- Pending TODOs # Edit :childOrder property on parent node if present while adding new index : 1803017 (/) # Ensure that nodetype index on QueryIndexDefinition do get updated when new index is introduced : 1803018 (/) was (Author: chetanm): Pending TODOs # Edit :childOrder property on parent node if present while adding new index # Ensure that nodetype index on QueryIndexDefinition do get updated when new index is introduced > Support adding or updating index definitions via oak-run > -------------------------------------------------------- > > Key: OAK-6471 > URL: https://issues.apache.org/jira/browse/OAK-6471 > Project: Jackrabbit Oak > Issue Type: New Feature > Components: indexing, run > Reporter: Chetan Mehrotra > Assignee: Chetan Mehrotra > Fix For: 1.8 > > > Currently oak-run can be used to reindex an existing index present in > NodeStore. I would like to extend this feature set to support adding or > updating the index definition and then reindexing them. The end user story > would be like below > Development team updates or introduces a new index definition and gives it to > system admin. Then admin can use oak-run and give it reference to the index > definition and then tooling takes care of indexing (with read only mode) and > then importing the updated index definition back into the repository. > To start with the index definitions would be provided as a json file with a > single json file containing index definitions which needs to be reindexed. > The file format would be similar to one we used for dumping index definition > (OAK-6224). -- This message was sent by Atlassian JIRA (v6.4.14#64029)