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

Anilkumar Gingade commented on GEODE-7025:
------------------------------------------

There are good list of configurations that are not supported with gfsh 
(cluster-configuration); till geode supports configuration in mixed mode; we 
need to make sure; either we are throwing a right exception or document the 
behavior.
E.g.: If region is configured through cache.xml and gfsh command is used to 
create an index on it; either we need to throw exception saying the region is 
not found in cluster config or create an index on the region (from cache.xml) 
and not store in cluster config; but document the behavior.

> Document not mixing cache.xml and cluster configuration in gfsh
> ---------------------------------------------------------------
>
>                 Key: GEODE-7025
>                 URL: https://issues.apache.org/jira/browse/GEODE-7025
>             Project: Geode
>          Issue Type: Bug
>          Components: docs
>            Reporter: Mario Kevo
>            Assignee: Dave Barnes
>            Priority: Major
>              Labels: ClusterConfig
>
> It's generally acknowledged that if you mixed cache.xml with cluster 
> configuration in gfsh, there are bound to be some weird behaviors that are 
> undocumented. 
> Including new changes, more commands failed if you mixed cache.xml and 
> cluster configuration.
> For example,
> Changes for _alter region_ are included in 1.9.0. Now if we create region and 
> indexes with cache.xml and after creating region want to add gateway sender 
> with _alter region_ this will failed. This works for 1.8.0. 
> So this should be documented somewhere to avoid this situations.
> There are two proposals:
> 1. Add this note to documentation to not mix cache.xml and cluster 
> configuration in gfsh.
> 2. Exclude using cache.xml for all properties which has other way to execute.
> In the second proposal we should remove cache.xml examples for all commands 
> that can be executed in the other way.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to