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

Dave Barnes reassigned GEODE-2976:
----------------------------------

    Assignee: Dave Barnes

> gfsh 'export cluster-config' behavior does not match online help
> ----------------------------------------------------------------
>
>                 Key: GEODE-2976
>                 URL: https://issues.apache.org/jira/browse/GEODE-2976
>             Project: Geode
>          Issue Type: Bug
>          Components: docs, gfsh
>            Reporter: Dave Barnes
>            Assignee: Dave Barnes
>
> [Geode v1.1]
> Online help and userman docs for gfsh 'export cluster-config' specify two 
> options that work together, --zip-file-name and --dir (shown below). In 
> practice, I found that --dir is ignored and --zip-file-name must be a 
> fully-qualified path.
> FWIW, the manual shows one example of each (cluster tutorial vs gfsh 
> reference).
> Unsuccessful command:
> gfsh>export cluster-configuration --zip-file-name=myClusterConfig.zip 
> --dir=/Users/dbarnes
> Could not process command due to GemFire error. Error while processing 
> command <export cluster-configuration --zip-file-name=myClusterConfig.zip 
> --dir=/Users/dbarnes> Reason : null
> Successful command:
> gfsh>export cluster-configuration 
> --zip-file-name=/Users/dbarnes/myClusterConfig.zip
> Downloading cluster configuration : /Users/dbarnes/myClusterConfig.zip
> Online help:
> gfsh>help export cluster-configuration
> NAME
>     export cluster-configuration
> IS AVAILABLE
>     true
> SYNOPSIS
>     Exports the cluster configuration artifacts as a zip file.
> SYNTAX
>     export cluster-configuration --zip-file-name=value [--dir=value]
> PARAMETERS
>     zip-file-name
>         Name of the zip file containing the exported cluster configuration 
> artifacts
>         Required: true
>     dir
>         The directory in which the exported cluster configuration artifacts 
> will be saved
>         Required: false



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

Reply via email to