jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-1160) Generic interfaces for operation tasks
Date Fri, 14 Mar 2014 21:10:44 GMT

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

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

At http://svn.apache.org/r1577705 I committed a generalised and clarified version of the first
draft from above, which takes Jukka's and Tom's comments into considerations. I removed all
parameters from all methods. The idea here is that parametrisation and configuration of the
tasks should be provided by other means. E.g. OSGi configurations or more specific MBeans
exposed by the respective implementations. I further clarified how tasks that are not available
and their respective status should be handled by this interface.

> Generic interfaces for operation tasks
> --------------------------------------
>
>                 Key: OAK-1160
>                 URL: https://issues.apache.org/jira/browse/OAK-1160
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: core, mk
>            Reporter: Michael Marth
>            Assignee: Michael Dürig
>             Fix For: 0.19
>
>
> Could we add generic (i.e. MK independent) interfaces that can be used by higher levels
to trigger certain ops tasks? The the application could decide when would be a good time to
run them.
> I am thinking especially about backup/restore (OAK-1158), MVCC revision cleanup (OAK-1158)
and DSGC (OAK-377)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message