[
https://issues.apache.org/jira/browse/OAK-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15584812#comment-15584812
]
Michael Dürig commented on OAK-2498:
------------------------------------
Patch LGTM AFAICS. I didn't follow through all the details on how those types
are passed along though.
As you suggest, let's start with the part of the patch that unblocks us on
OAK-4740. For the other types I think any implementation should come along with
a POC of the tooling that would profit from them.
> 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: Francesco Mari
> Labels: tools
> Fix For: Segment Tar 0.0.16
>
> Attachments: OAK-2498-01.patch
>
>
> 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)
