cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Branson (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3568) cassandra-cli and nodetool should connect to localhost by default
Date Fri, 09 Dec 2011 00:07:40 GMT

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

Rick Branson commented on CASSANDRA-3568:
-----------------------------------------

As of current trunk, if a -h is specified and it cannot connect, it dumps back out to the
shell. The patch attached remains consistent with that, along the lines of the most minimally
invasive behavior. Just to be clear -- are you proposing that any connection failure of any
kind to continue to the CLI and allow a "connect" command to be issued later to attempt a
retry?
                
> cassandra-cli and nodetool should connect to localhost by default
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-3568
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3568
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Rick Branson
>            Assignee: Rick Branson
>            Priority: Minor
>         Attachments: 3568.txt
>
>
> The command line tools (cassandra-cli and noetool) should connect by default to localhost.
This behavior is a bit more user-friendly and reflects somewhat of a convention among command-line
database tools for popular open source databases such as MySQL and PostgreSQL.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message