[
https://issues.apache.org/jira/browse/CASSANDRA-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859677#action_12859677
]
Todd Blose commented on CASSANDRA-859:
--------------------------------------
1. The original completer added every ks.cf upon successful connection.
Obviously, we wouldn't want cmd <tab> to return every CF of every keyspace,
only those associated with the active one. I updated the code to modify the
completor strings whenever the keyspace changes. Whenever there is no active
keyspace, cmd <tab> returns nothing.
2-4. Fixed.
> 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
> Reporter: Eric Evans
> Assignee: Todd Blose
> Priority: Minor
> Fix For: 0.7
>
> Attachments:
> 0001-CASSANDRA-859.-update-cassandra-cli-for-mandatory-lo.patch,
> CASSANDRA-859-04-21.patch, CASSANDRA-859.patch, example_session.txt
>
>
> 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.
