[
https://issues.apache.org/jira/browse/OAK-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16658960#comment-16658960
]
Francesco Mari commented on OAK-7846:
-------------------------------------
[~mduerig], the format above is processable with a finite state machine using a
stack to track the current node. Maybe I should have been clearer in my
explanation. In any case, I agree on your comment about the poor interaction
between the format with the usual command line utilities. A better format for
this use case is a "flat" one, similar to the following:
{noformat}
/path/to/node/prop1 TYPE VALUE
/path/to/node/prop2 TYPE VALUE
/path/to/node/prop3 TYPE VALUE
{noformat}
It is possible to derive this format from the one I proposed above, and in fact
it can be done in streaming fashion. The "flattened" format is great for piping
it into conventional command line utilities, but I find it too verbose for any
other use case. If I had to write a program to import data back into a
repository, I would prefer the format I originally proposed instead of the
flattened one.
> Add a tool to export the tree pointed to by a node record
> ---------------------------------------------------------
>
> Key: OAK-7846
> URL: https://issues.apache.org/jira/browse/OAK-7846
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: segment-tar
> Affects Versions: 1.10
> Reporter: Francesco Mari
> Assignee: Francesco Mari
> Priority: Major
>
> oak-segment-tar should have a tool that allows exporting a tree pointed to by
> a node record. The tool must be written in a way that plays along with
> existing Oak tools (see OAK-7834) and conventional UNIX ones.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
