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 "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2016/09/21 11:20:20 UTC

[jira] [Updated] (OAK-4834) Make the role configurable for the SegmentNodeStore

     [ https://issues.apache.org/jira/browse/OAK-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomek Rękawek updated OAK-4834:
-------------------------------
    Description: 
Right now the SegmentNodeStoreService can be configured with the secondary boolean property. It'll be then registered as NodeStoreProvider with {{role=secondary}}.

Maybe we can make it more flexible and allow to configure any role, using {{nsProvider.role}} property?

  was:
Right now the SegmentNodeStoreService can be configured with the secondary boolean property. It'll be then registered as NodeStoreProvider with {{role=secondary}}.

Maybe we can make it more flexible and allow to configure any role, using nsProvider.role property?


> Make the role configurable for the SegmentNodeStore
> ---------------------------------------------------
>
>                 Key: OAK-4834
>                 URL: https://issues.apache.org/jira/browse/OAK-4834
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-tar, segmentmk
>            Reporter: Tomek Rękawek
>            Priority: Minor
>             Fix For: 1.6
>
>
> Right now the SegmentNodeStoreService can be configured with the secondary boolean property. It'll be then registered as NodeStoreProvider with {{role=secondary}}.
> Maybe we can make it more flexible and allow to configure any role, using {{nsProvider.role}} property?



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