[
https://issues.apache.org/jira/browse/OAK-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541820#comment-15541820
]
Michael Dürig commented on OAK-4872:
------------------------------------
With this change segment references are not loaded lazily on an as need basis
any more. Instead they are loaded eagerly in the {{Segment}} constructor. This
*might* have adverse effects in scenarios where many segments need to be
loaded, so let's keep an eye on this. If required it should still be possible
to regain lazy loading by coming up with a respective implementation of
{{SegmentReferences}}.
> Don't write the referenced segment IDs in the segment buffer
> ------------------------------------------------------------
>
> Key: OAK-4872
> URL: https://issues.apache.org/jira/browse/OAK-4872
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
> Reporter: Francesco Mari
> Assignee: Francesco Mari
> Fix For: Segment Tar 0.0.14
>
>
> The work done for OAK-4844 restores the capability of a Segment to
> efficiently maintain a list of referenced segment IDs. The referenced segment
> IDs are marshalled to the underlying buffer by the SegmentBufferWriter and
> unmarshalled by the current Segment as needed. While this solution works, it
> would be beneficial to encapsulate this concern in a separate set of classes,
> especially when considering future development directions (e.g. OAK-4582).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
