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 "Paul Chibulcuteanu (JIRA)" <ji...@apache.org> on 2017/05/19 11:56:04 UTC

[jira] [Comment Edited] (OAK-6117) Enable lucene indexing via oak-run

    [ https://issues.apache.org/jira/browse/OAK-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017287#comment-16017287 ] 

Paul Chibulcuteanu edited comment on OAK-6117 at 5/19/17 11:56 AM:
-------------------------------------------------------------------

[~chetanm], in the current form, does this mean that the repository needs to be offline for both mongo and tar?

Later edit: In OAK-6081 it is mentioned that for Documentstore 
{quote}
DocumentNodeStore setup it would be possible to connect oak-run to a live cluster and it would take care of indexing
{quote}


was (Author: chibulcu):
[~chetanm], in the current form, does this mean that the repository needs to be offline for both mongo and tar?

> Enable lucene indexing via oak-run
> ----------------------------------
>
>                 Key: OAK-6117
>                 URL: https://issues.apache.org/jira/browse/OAK-6117
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: lucene, run
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.8, 1.7.1
>
>
> This is first step of OAK-6081 where we need to enable performing Lucene indexing via oak-run. The indexing approach would be very close to what we already have with minimal changes done.
> Once this is done it should be possible to connect oak-run against an existing setup and let it reindexing specific set of indexes



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)