[
https://issues.apache.org/jira/browse/CASSANDRA-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485254#comment-14485254
]
Carl Yeksigian commented on CASSANDRA-7212:
-------------------------------------------
{quote}
But when we login to cqlsh using ./cqlsh -u <username > -p <password> at that
time also the command is saved in history.So is it really needed?If yes then do
we need to disable echoing the charecters on screen when user enters the
password?
{quote}
We also allow {{./cqlsh -u username}} which will prompt for the password, which
I think we should have for this as well.
> Allow to switch user within CQLSH session
> -----------------------------------------
>
> Key: CASSANDRA-7212
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7212
> Project: Cassandra
> Issue Type: Improvement
> Components: API
> Environment: [cqlsh 4.1.1 | Cassandra 2.0.7.31 | CQL spec 3.1.1 |
> Thrift protocol 19.39.0]
> Reporter: Jose Martinez Poblete
> Labels: cqlsh
> Attachments: 7212_1.patch
>
>
> Once a user is logged into CQLSH, it is not possible to switch to another
> user without exiting and relaunch
> This is a feature offered in postgres and probably other databases:
> http://secure.encivasolutions.com/knowledgebase.php?action=displayarticle&id=1126
>
> Perhaps this could be implemented on CQLSH as part of the "USE" directive:
> USE <Keyspace> [USER] [password]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
