You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Jens Deppe (JIRA)" <ji...@apache.org> on 2019/03/29 15:00:00 UTC

[jira] [Resolved] (GEODE-6027) Separate ConfigObject from the ResultModel for configuration persistence

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

Jens Deppe resolved GEODE-6027.
-------------------------------
    Resolution: Won't Fix

> Separate ConfigObject from the ResultModel for configuration persistence
> ------------------------------------------------------------------------
>
>                 Key: GEODE-6027
>                 URL: https://issues.apache.org/jira/browse/GEODE-6027
>             Project: Geode
>          Issue Type: Improvement
>          Components: gfsh
>            Reporter: Kenneth Howe
>            Assignee: Kenneth Howe
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Evolving the {{CommandExector}} class/workflow; as we're refactoring more classes, making the following changes seems appropriate:
> - Have {{updateClusterConfig}} return a boolean value indicating whether a change was made or not
> - Have {{updateClusterConfig}} receive the {{ResultModel}} as input



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