You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2018/10/19 07:17:00 UTC
[jira] [Commented] (IGNITE-6064) Rework control.sh script
[ https://issues.apache.org/jira/browse/IGNITE-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656359#comment-16656359 ]
Alexey Kuznetsov commented on IGNITE-6064:
------------------------------------------
I also have a couple of suggestions:
# Move this utility to separate module (for example ignite-tools? ignite-cli?)
# Add support for --output-format TEXT|JSON|XML ...
> Rework control.sh script
> ------------------------
>
> Key: IGNITE-6064
> URL: https://issues.apache.org/jira/browse/IGNITE-6064
> Project: Ignite
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.0, 2.1
> Reporter: Dmitriy Govorukhin
> Priority: Blocker
> Labels: usability
>
> Current behavior control.sh is not clear.
> 1. control.sh is a confusing name, need more suitable name.
> 2. Print help description if incorrect command was entered
> 3. Do not print stacktrace if connection fail, add more informative message.
> 4. Print information about connection, like "Connecting to [ip-address]:[port] etc."
> 5. Document the usage on a special page. Ping Denis Magda when it's time to do that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)