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

ASF GitHub Bot commented on IGNITE-9253:
----------------------------------------

GitHub user shroman opened a pull request:

    https://github.com/apache/ignite/pull/4525

    IGNITE-9253: Rename activation/deactivation commands for REST API.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shroman/ignite IGNITE-9253

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4525.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4525
    
----
commit 0283d984643f6ea705907d5695ac2066654b02db
Author: shroman <rshtykh@...>
Date:   2018-08-13T09:11:24Z

    IGNITE-9253: Rename activation/deactivation commands for REST API.

----


> Rename activation/deactivation commands for REST API
> ----------------------------------------------------
>
>                 Key: IGNITE-9253
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9253
>             Project: Ignite
>          Issue Type: Task
>          Components: rest
>            Reporter: Roman Shtykh
>            Assignee: Roman Shtykh
>            Priority: Minor
>
> "Active/inactive" don't sound like commands. I propose to rename to 
> "activate/deactivate."
> It will also bring consistency with the cluster control tool commands 
> (control.sh)
> "response":null can be changed to "activate started"/"deactivate started."



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

Reply via email to