[
https://issues.apache.org/jira/browse/OAK-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated OAK-4406:
---------------------------------
Description:
Currently only the console within {{oak-run}} can be used to remove search
index files.
But for that you have to know where the index definition is stored (because the
actual index is stored below those nodes). and you have to use low-level
commands to manually modify the repository.
It would be really nice if there would be dedicated commands in oak-run which
would allow to
# list all existing search indices
# remove specific indices
# verify them for validity (not sure if that is possible though)
In addition those commands probably need to consider the copy on the local
filesystem of indices
(http://jackrabbit.apache.org/oak/docs/query/lucene.html#CopyOnRead).
was:
Currently only {{oak-run}} can be used to remove search index files.
But for that you have to know where the index definition is stored (because the
actual index is stored below those nodes). and you have to use low-level
commands to manually modify the repository.
It would be really nice if there would be dedicated commands in oak-run which
would allow to
# list all existing search indices
# remove specific indices
# verify them for validity (not sure if that is possible though)
In addition those commands probably need to consider the copy on the local
filesystem of indices
(http://jackrabbit.apache.org/oak/docs/query/lucene.html#CopyOnRead).
> Add easy to use commands to maintain search indices (for Property, Lucene and
> Solr)
> ------------------------------------------------------------------------------------
>
> Key: OAK-4406
> URL: https://issues.apache.org/jira/browse/OAK-4406
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run
> Reporter: Konrad Windszus
>
> Currently only the console within {{oak-run}} can be used to remove search
> index files.
> But for that you have to know where the index definition is stored (because
> the actual index is stored below those nodes). and you have to use low-level
> commands to manually modify the repository.
> It would be really nice if there would be dedicated commands in oak-run which
> would allow to
> # list all existing search indices
> # remove specific indices
> # verify them for validity (not sure if that is possible though)
> In addition those commands probably need to consider the copy on the local
> filesystem of indices
> (http://jackrabbit.apache.org/oak/docs/query/lucene.html#CopyOnRead).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
