[
https://issues.apache.org/jira/browse/OAK-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653870#comment-16653870
]
Axel Hanikel edited comment on OAK-7846 at 10/17/18 5:12 PM:
-------------------------------------------------------------
[~frm] I will gladly follow up on the contribution request :) As discussed I
think url-encoding all names and values is the easiest way to avoid problems
with unexpected character codes. '/' and ':' (and perhaps others?) could be
left unchanged for readability. For the blobs we could just use the hex value
of each byte in sequence. That's not very space efficient but easy to handle,
and the whole stream could still be gzipped on the fly, if needed.
Perhaps it would be useful if 'b' had the segment id + record offset as
arguments.
was (Author: ahanikel):
[~frm] I will gladly follow up on the contribution request :) As discussed I
think url-encoding all names and values is the easiest way to avoid problems
with unexpected character codes. '/' and ':' (and perhaps others?) could be
left unchanged for readability. For the blobs we could just use the hex value
of each byte in sequence. That's not very space efficient but easy to handle,
and the whole stream could still be gzipped on the fly, if needed.
> 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)
