[
https://issues.apache.org/jira/browse/CASSANDRA-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847605#action_12847605
]
Eric Evans commented on CASSANDRA-859:
--------------------------------------
That was my thinking, that we'd have a command that could be used to switch the
current keyspace (it would simply do a new login() call against the node).
We should drop the keyspace specification from commands, (i.e.
ks.cf['something'] should become cf['something']), since that better
communicates that the keyspace is the upper-most namespace in an application,
and because it fits better with how the api will work after completing
CASSANDRA-714.
> update cassandra-cli for mandatory login()
> ------------------------------------------
>
> Key: CASSANDRA-859
> URL: https://issues.apache.org/jira/browse/CASSANDRA-859
> Project: Cassandra
> Issue Type: Task
> Components: Tools
> Affects Versions: 0.7
> Reporter: Eric Evans
> Priority: Minor
>
> With the completion of CASSANDRA-714, the cli will need to be updated
> accordingly.
> * Either the --keyspace command argument (or something equivalent entered
> interactively after startup), will need to be made required.
> * The record specifier should be changed from `keyspace.column_family['row']'
> to `column_family['row']'.
> * The keyspace name should be displayed in the prompt, instead of the fixed
> string "cassandra" as a reminder of the current working keyspace.
> Additionally, a get_string_property("cluster name") was recently added to
> force connection errors to occur early (the name is also displayed in the
> banner). Since this changeset will make a login() call mandatory, the
> get_string_property() call will be unneeded and can be removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
