[
https://issues.apache.org/jira/browse/GEODE-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912579#comment-16912579
]
Darrel Schneider commented on GEODE-7025:
-----------------------------------------
It looks to me like the page is out of date about what gfsh does not support.
For example I see support for the following now on gfsh create region:
compressor, lru-memory-size (see --eviction-max-memory), and partition-resolver.
> 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)
