You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Darrel Schneider (JIRA)" <ji...@apache.org> on 2016/05/11 22:32:13 UTC

[jira] [Resolved] (GEODE-1224) AttributesMutator.setCloningEnabled does not modify PR bucket regions

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

Darrel Schneider resolved GEODE-1224.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0-incubating.M3

Fixed in revision: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/123ddb7c

> 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
>             Fix For: 1.0.0-incubating.M3
>
>
> 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)