[
https://issues.apache.org/jira/browse/OAK-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574132#comment-14574132
]
Francesco Mari commented on OAK-2960:
-------------------------------------
[~amitjain], configuration can change at any time for any properties. A
component should handle modification to all of its properties, and act
accordingly if some property has a deeper impact than others.
The solution developed for OAK-2016 forces a user to unbind the configuration,
modify properties (if one of the properties to modify is not
{{blobGcMaxAgeInSecs}}), and bind the configuration again. This behaviour,
other than being cumbersome, is different from the one that the
{{DocumentNodeStoreService}} used to have.
> 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
>
> Attachments: OAK-2960-01.patch
>
>
> 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)
