You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/10/03 21:23:00 UTC

[jira] [Commented] (GEODE-5727) Export cluster-configuration does not work filename only

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

ASF subversion and git services commented on GEODE-5727:
--------------------------------------------------------

Commit c3494e037122df8b9d1f42531f10242bff1575ea in geode's branch refs/heads/master from jinmeiliao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c3494e0 ]

GEODE-5727: rework how ResultModel deal with file contents. (#2460)

* file saving should be handled by the command's postExecutor to save to appropriate places
* after saving file content to a directory, the ResultModel turned the FileResultModel into InfoResultModel.
* gfsh should not be the place to save files in ModelCommandResult.


> Export cluster-configuration does not work filename only
> --------------------------------------------------------
>
>                 Key: GEODE-5727
>                 URL: https://issues.apache.org/jira/browse/GEODE-5727
>             Project: Geode
>          Issue Type: Bug
>          Components: gfsh
>            Reporter: Bradford D. Boyle
>            Assignee: Jinmei Liao
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.7.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Using the latest Geode snapshot (aaac1e5cefe6ad7ca533a7ca87eef9dd779912e4), exporting cluster config with only a filename (no path) results in an error:
> {code}
> gfsh> start locator
> gfsh> start server
> gfsh> create region --name=test --type=PARTITION
> gfsh> export cluster-configuration --zip-file-name=cluster-config.zip
> Could not process command due to error. null
> {code}
> It does (sort of) work if you use a path:
> {code}
> gfsh> start locator
> gfsh> start server
> gfsh> create region --name=test --type=PARTITION
> gfsh> export cluster-configuration --zip-file-name=./cluster-config.zip
> {code}
> However, it appears that the cluster config file is written to both the specified path and the current working directory.
> {code}
> gfsh > export cluster-configuration --zip-file-name=/tmp/cluster-config.zip
> {code}
> {code}
> $ md5 /tmp/cluster-config.zip cluster-config.zip
> MD5 (/tmp/cluster-config.zip) = 50022493fa54f54da700adfc1a8f709c
> MD5 (cluster-config.zip) = 50022493fa54f54da700adfc1a8f709c
> {code}



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