You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dave Barnes (JIRA)" <ji...@apache.org> on 2017/10/05 21:46:00 UTC

[jira] [Commented] (GEODE-3762) User Guide: Clarify cluster config docs around gfsh limitations

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

Dave Barnes commented on GEODE-3762:
------------------------------------

Config via gfsh is preferred because changes are saved and propagated via the cluster configuration service. 
There are still some cases that can be handled only by other means, such as XML files or the Java API.
These need to be specified clearly in the docs, with the understanding that the number of such cases is steadily shrinking as gfsh gains additional capabilities.
This ticket is aimed at updating the docs to match the gfsh/cluster config service implementation as of of Geode 1.3.

> User Guide: Clarify cluster config docs around gfsh limitations
> ---------------------------------------------------------------
>
>                 Key: GEODE-3762
>                 URL: https://issues.apache.org/jira/browse/GEODE-3762
>             Project: Geode
>          Issue Type: Improvement
>          Components: docs
>            Reporter: Dave Barnes
>            Assignee: Dave Barnes
>
> Incomplete gfsh help "worries customers," who think they can't "do anything with functions/loaders/writers." Also that they "didn't know they could use a combination of xml + java api + gfsh. Which is partially on them but could possibly be more called out in the docs."



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)