geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darrel Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-1224) AttributesMutator.setCloningEnabled does not modify PR bucket regions
Date Wed, 04 May 2016 20:57:12 GMT

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

Darrel Schneider commented on GEODE-1224:
-----------------------------------------

It is now clear that if you use AttributesMutator.setCloningEnabled on a partitioned region
that already has had entries added to it then the setCloningEnabled call will have no effect.


> AttributesMutator.setCloningEnabled does not modify PR bucket regions
> ---------------------------------------------------------------------
>
>                 Key: GEODE-1224
>                 URL: https://issues.apache.org/jira/browse/GEODE-1224
>             Project: Geode
>          Issue Type: Bug
>          Components: regions
>            Reporter: Darrel Schneider
>            Assignee: Scott Jewell
>
> PartitionedRegions are implemented with multiple BucketRegion. When the PR creates a
bucket region it sets cloningEnabled on the bucket. But when AttributesMutator.setCloningEnabled
is called it only changes the flag on the top level PR region and not on any of the buckets.
> It is not clear if the BucketRegion cloningEnabled flag is ever used but since we do
set it at bucket creation we should make it consistent when it is changed by the mutator.
> To fix this it might make more sense to just change BucketRegion.getCloningEnabled to
always call this.partitionedRegion.getCloningEnabled().



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

Mime
View raw message