[jira] [Commented] (OAK-3987) Indexer dry run mode
[
https://issues.apache.org/jira/browse/OAK-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092869#comment-16092869
]
Davide Giannella commented on OAK-3987:
---
Go ahead [~chetanm]
> Indexer dry run mode
>
>
> Key: OAK-3987
> URL: https://issues.apache.org/jira/browse/OAK-3987
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Alex Deparvu
>Assignee: Davide Giannella
> Fix For: 1.8
>
>
> Based on a discussion on the dev list, it would be interesting to provide a
> {{dry run}} mode for the indexer which would give an indication of an average
> indexing time.
> Input could be:
> * path to index definition (mandatory)
> * path to the content (mandatory, default could be {{/}})
> * max number of nodes (optional, but I'd still cap this value so indexing
> doesn't take over the entire aem instance)
> Also, we could do this on a separate (dedicated) thread so it doesn't
> interfere with existing indexers.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-3987) Indexer dry run mode
[
https://issues.apache.org/jira/browse/OAK-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092576#comment-16092576
]
Chetan Mehrotra commented on OAK-3987:
--
[~edivad] oak-run tool now supports out-of-band indexing where no changes are
done to NodeStore [1]. This meets the dry run requirements.
If this looks fine to you then I would like to resolve this issue as done
[1]
https://jackrabbit.apache.org/oak/docs/query/oak-run-indexing.html#out-of-band-indexing
> Indexer dry run mode
>
>
> Key: OAK-3987
> URL: https://issues.apache.org/jira/browse/OAK-3987
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Alex Deparvu
>Assignee: Davide Giannella
>
> Based on a discussion on the dev list, it would be interesting to provide a
> {{dry run}} mode for the indexer which would give an indication of an average
> indexing time.
> Input could be:
> * path to index definition (mandatory)
> * path to the content (mandatory, default could be {{/}})
> * max number of nodes (optional, but I'd still cap this value so indexing
> doesn't take over the entire aem instance)
> Also, we could do this on a separate (dedicated) thread so it doesn't
> interfere with existing indexers.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
