[
https://issues.apache.org/jira/browse/GEODE-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247067#comment-15247067
]
Edin Zulich commented on GEODE-1223:
------------------------------------
To clarify regarding the comment, ??It is not clear that changing these items
on an existing PR is a feature that is needed.??:
It might be needed if we decide to extend the hot deploy support to callbacks
(so that callbacks can be set or replaced at runtime). This is something that
has been brought up before.
> AttributesMutator on partitioned region allows inconsistent region
> configuration
> --------------------------------------------------------------------------------
>
> Key: GEODE-1223
> URL: https://issues.apache.org/jira/browse/GEODE-1223
> Project: Geode
> Issue Type: Bug
> Components: regions
> Reporter: Darrel Schneider
>
> When a partitioned region is created it makes sure that the following items
> on the PR being created are consistent with them for the same PR in existing
> members:
> 1. CacheLoader
> 2. CacheWriter
> 3. Expiration attributes
> The code that does this validation is: PartitionRegionConfigValidator
> validateCacheLoaderWriterBetweenDataStores and validateExpirationAttributes.
> But if you get an AttributesMutator for the PR it allows you to change these
> items on just one member leaving them inconsistent across the distributed
> members.
> It is not clear that changing these items on an existing PR is a feature that
> is needed. It would be safer to just configure them when the region is
> created. So these methods on AttributesMutator should be changed to throw
> UnsupportedOperationException on PRs:
> 1. setCacheLoader
> 2. setCacheWriter
> 3. setRegionTimeToLive
> 4. setRegionIdleTimeout
> 5. setEntryTimeToLive
> 6. setCustomEntryTimeToLive
> 7. setEntryIdleTimeout
> 8. setCustomEntryIdleTimeout
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
