[
https://issues.apache.org/jira/browse/OAK-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15750336#comment-15750336
]
Chetan Mehrotra commented on OAK-5309:
--------------------------------------
[~mduerig] Any thoughts on possible solution approach
For now I think of
# Add a new method Whiteboard#track(Class, Map filterAttrs) where the map
represents attributes which can be used for filtering. The prop here would
those which are passed in {{Whiteboard#register}}. Or it can be directly
represented as a string filter (See #2)
# Modify OSGi whiteboard impl to convert the map to
[Filter|https://osgi.org/javadoc/r4v43/core/org/osgi/framework/Filter.html]
# Have default method pass map expressing that look for impls where {{role}} is
null
And have role variants specify the role
> Supporting roles in RepositoryManager execution of maintenance tasks
> --------------------------------------------------------------------
>
> Key: OAK-5309
> URL: https://issues.apache.org/jira/browse/OAK-5309
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: 1.8
>
>
> With recent support for maintenance task MBeans exposed for secondary stores
> via OAK-4978 its now possible to have multiple implementations of
> RevisionGCMBean present in same setup.
> However o.a.j.o.management.RepositoryManager implementation only supports
> single implementation by design. This needs to be updated to support
> # Looking up RevisionGCMBean which does not have {{role}} OSGi property
> defined
> # Expose a management op like startRevisionGCForRole
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
