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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2016/06/07 07:51:21 UTC

[jira] [Commented] (OAK-4283) Align GCMonitor API with implementation

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

Michael Dürig commented on OAK-4283:
------------------------------------

At http://svn.apache.org/viewvc?rev=1747157&view=rev I did some initial refactoring on duplicated functionality: the {{LoggingGCMonitor}} is now a top level class. Delegation has been removed as it should be used in conjunction with {{DelegatingGCMonitor}} if delegating is necessary. 

> Align GCMonitor API with implementation 
> ----------------------------------------
>
>                 Key: OAK-4283
>                 URL: https://issues.apache.org/jira/browse/OAK-4283
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: segment-tar
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: api-change, compaction, gc
>             Fix For: 1.6
>
>
> The argument taken by {{GCMonitor.compacted}} related to parameters of the compaction map. The latter has gone with OAK-3348. We need to come up with a way to adjust this API accordingly. Also it might make sense to broaden the scope of {{GCMonitor}} from its initial intent (logging) to a more general one as this is how it is already used e.g. by the {{RefreshOnGC}} implementation and for OAK-4096. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)