[
https://issues.apache.org/jira/browse/OAK-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033493#comment-14033493
]
Chetan Mehrotra commented on OAK-1893:
--------------------------------------
bq. -0 I'm not too excited about a remotely accessible feature that can be used
to write to an arbitrary location in the local file system.
FWIW Oracle JDK already exposes a method to dump the heap content via JMX [1]
to arbitrary path. So the method exposed here is on same pattern
bq. In general I think a low-level feature like this would be better
implemented as a debugging tool in oak-run, for example as a new console
command.
That would also be a good place in addition to JMX. Just that we need to sort
out packaging of Lucene 4.x binaries with oak-run (OAK-1896). However I would
still prefer to retain the JMX option due to ease of use
[1]
http://docs.oracle.com/javase/6/docs/jre/api/management/extension/com/sun/management/HotSpotDiagnosticMXBean.html#dumpHeap%28java.lang.String,%20boolean%29
> MBean to dump Lucene Index content and related stats
> ----------------------------------------------------
>
> Key: OAK-1893
> URL: https://issues.apache.org/jira/browse/OAK-1893
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: oak-lucene
> Affects Versions: 1.0
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.1
>
>
> Currently the Lucene index is stored within NodeStore as a content. To enable
> debugging and better understanding of Lucene index content it would be
> helpful to provide a JMX Bean which can dump the index content to filesystem
--
This message was sent by Atlassian JIRA
(v6.2#6252)
