[
https://issues.apache.org/jira/browse/OAK-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282697#comment-14282697
]
Michael Dürig commented on OAK-2408:
------------------------------------
At
https://github.com/mduerig/jackrabbit-oak/commit/f38e906a34e9de679b558db2f1638a18fd917d7b
I refactored the various {{Record}} implementations to 'has-a' {{Record}}. In
a next step we should give each of them an additional "proxy segment" field,
which could be used to re-link them when the underlying persisted record is
rewritten. We need to be careful here to keep the implementations of
{{hashCode}} and {{equals}} correct (and immutable).
> Investigate ways to make revision gc more precise
> --------------------------------------------------
>
> Key: OAK-2408
> URL: https://issues.apache.org/jira/browse/OAK-2408
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: segmentmk
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Labels: gc
>
> Current approaches to revision garbage collection tend to be too conservative
> (too little space reclaimed, e.g. OAK-2045) or too aggressive (removing
> segments still being used, e.g. OAK-2384).
> This issue is to explore ways to make revision gc on TarMk more precise.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
