[
https://issues.apache.org/jira/browse/OAK-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442242#comment-16442242
]
Michael Dürig commented on OAK-7416:
------------------------------------
[~frm], I just went to the proposed changes. This looks very good to me and I'd
be +1 to applying this in trunk.
* See [https://github.com/francescomari/jackrabbit-oak/pull/18/files] for some
proposed changes to clean up a few bits.
* The classes in {{org.apache.jackrabbit.oak.segment.file.proc}} generally
lack Javadoc. No blocker for trunk, but let's add some class level comments re.
what the structure of what the individual classes as long as our memories are
still fresh.
> Contribute a 'proc' subtree for the Segment Node Store
> ------------------------------------------------------
>
> Key: OAK-7416
> URL: https://issues.apache.org/jira/browse/OAK-7416
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Reporter: Francesco Mari
> Assignee: Francesco Mari
> Priority: Major
> Labels: tooling
> Fix For: 1.10
>
>
> With guidance from [~mduerig], I recently developed a way to expose Segment
> Node Store's internal information through the NodeState API.
> The concept is similar in spirit to the proc file system in Linux: the proc
> subtree exposes internal information in a straightforward manner, enabling
> consumers to rely on a well-understood API to access the data. This proc
> subtree shelters tooling from variations of the internal APIs of the Segment
> Store. As long as the data exported through the proc subtree is stable, the
> same tools are going to work across different versions of the Segment Store
> with minimal to no modifications.
> The proc subtree has been developed in [this branch on
> GitHub|https://github.com/francescomari/jackrabbit-oak/tree/proc]. I created
> this issue in order to review the work done so far, and to track the
> contribution of the proc subtree in Oak.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
