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 "Francesco Mari (JIRA)" <ji...@apache.org> on 2015/06/04 16:23:37 UTC

[jira] [Commented] (OAK-2960) SegmentNodeStoreService should correctly handle modifications in the configuration

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

Francesco Mari commented on OAK-2960:
-------------------------------------

The {{@Modified}} method was introduced as part of the resolution of OAK-2016. [~amitjain], can you have a look at this issue?

> SegmentNodeStoreService should correctly handle modifications in the configuration
> ----------------------------------------------------------------------------------
>
>                 Key: OAK-2960
>                 URL: https://issues.apache.org/jira/browse/OAK-2960
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segmentmk
>            Reporter: Francesco Mari
>            Priority: Critical
>             Fix For: 1.3.0
>
>
> The {{SegmentNodeStoreService} component recently introduced an {{@Modified}} method that picks up changes in just one configuration property and ignores the rest.
> Some configuration properties, like {{customBlobStore}}, have a huge impact on the dynamic behaviour of the component. If the component fails to pick up these changes, its behaviour is just wrong.
> The {{@Modified}} method should be removed. It is safer to go through a complete deactivation and activation process.



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