You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Francesco Mari (JIRA)" <ji...@apache.org> on 2016/10/03 09:12:20 UTC

[jira] [Commented] (OAK-2498) Root record references provide too little context for parsing a segment

    [ https://issues.apache.org/jira/browse/OAK-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541936#comment-15541936 ] 

Francesco Mari commented on OAK-2498:
-------------------------------------

In r1763136 I removed the root record table from the segments. Every record is now considered a root record. I also added a new method in Segment to iterate over every record contained in that segment. This method allows to iterate over the records without exposing the way records are stored in the segment.

> 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.14
>
>
> 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)