You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jens Deppe (JIRA)" <ji...@apache.org> on 2019/03/29 14:29:00 UTC

[jira] [Commented] (GEODE-6336) gfsh create region does not support multiple configurations for the same region name

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

Jens Deppe commented on GEODE-6336:
-----------------------------------

[~dschneider] is there still an issue here? If so, please could you add some more details or close this ticket if you're OK with the current status quo.

> gfsh create region does not support multiple configurations for the same region name
> ------------------------------------------------------------------------------------
>
>                 Key: GEODE-6336
>                 URL: https://issues.apache.org/jira/browse/GEODE-6336
>             Project: Geode
>          Issue Type: Bug
>          Components: gfsh
>            Reporter: Darrel Schneider
>            Priority: Major
>
> gfsh create region has group support but it does not allow the same region name to be created with different configurations in different groups.
> Geode has support for different configurations for the same region name in the same cluster.
> For example you can have some members define a PartitionedRegion as an accessor (it stores no data) and others that define it as a store (it actually stores data for the region).
> For replicas you can have some members be persistent, others non-persistent, and others be empty proxies.
> Cluster config does have group support so the way this was supposed to work was that each group could define the region in its own way and would not fail saying it was already created in another group. If a member decides to join multiple groups then it is an error if the same name is defined in more than one group. 
> As it is, you currently can not use gfsh to create regions in supported configurations. You would need to disable cluster config and instead define you regions with your own xml files or using apis each time.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)