[
https://issues.apache.org/jira/browse/OAK-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542376#comment-15542376
]
Alex Parvulescu commented on OAK-2498:
--------------------------------------
fyi based on the latest changes on this issue, there's a size regression we
need to consider again (see [this for
reference|https://issues.apache.org/jira/browse/OAK-4844?focusedCommentId=15522577&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15522577]):
{noformat}
Total size:
21 GB in 87794 data segments
768 KB in 3 bulk segments
4 GB in maps (46450859 leaf and branch records)
1 GB in lists (55469092 list and bucket records)
3 GB in values (value and block records of 70765674 properties,
3429/378684/0/1214419 small/medium/long/external blobs, 46258452/1862224/159
small/medium/long strings)
194 MB in templates (16772712 template records)
3 GB in nodes (251591739 node records)
{noformat}
> 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)
