[
https://issues.apache.org/jira/browse/OAK-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542073#comment-15542073
]
Michael Dürig commented on OAK-2498:
------------------------------------
At http://svn.apache.org/viewvc?rev=1763148&view=rev I also included the type
of the records in {{Segment.toString()}}:
{code}
VALUE record 00000000: 0003ffd0
BUCKET record 00000001: 0003f7d8
BUCKET record 00000002: 0003efe0
BUCKET record 00000003: 0003e7e8
BUCKET record 00000004: 0003dff0
BUCKET record 00000005: 0003d7f8
BUCKET record 00000006: 0003d7d0
BUCKET record 00000007: 0003d7a0
VALUE record 00000008: 0003d790
VALUE record 00000009: 0003d788
VALUE record 0000000a: 0003d780
TEMPLATE record 0000000b: 0003d768
NODE record 0000000c: 0003d748
NODE record 0000000d: 0003d730
{code}
> 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)
