[
https://issues.apache.org/jira/browse/OAK-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426104#comment-15426104
]
Michael Dürig commented on OAK-2498:
------------------------------------
While we introduce new record types, we should also think of adding a type
{{RecordType.ROOT_NODE}} marking the roots of the content trees. This could be
helpful for implementing OAK-4103 (mind the
[disclaimer|https://issues.apache.org/jira/browse/OAK-4103?focusedCommentId=15426101&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15426101]
though). Furthermore it could simplify {{oak-run tarmkrecovery}} and at the
same time make it more reliable (see OAK-3804).
/cc [~alex.parvulescu] re. OAK-3804.
> Root record references provide too little context for parsing a segment
> -----------------------------------------------------------------------
>
> Key: OAK-2498
> URL: https://issues.apache.org/jira/browse/OAK-2498
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
> Reporter: Michael Dürig
> Assignee: Andrei Dulceanu
> Labels: tools
> Fix For: Segment Tar 0.0.12
>
>
> According to the [documentation |
> http://jackrabbit.apache.org/oak/docs/nodestore/segmentmk.html] the root
> record references in a segment header provide enough context for parsing all
> records within this segment without any external information.
> Turns out this is not true: if a root record reference turns e.g. to a list
> record. The items in that list are record ids of unknown type. So even though
> those records might live in the same segment, we can't parse them as we don't
> know their type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
