cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4052) Add way to force the cassandra-cli to refresh it's schema
Date Sat, 21 Apr 2012 22:06:33 GMT


Pavel Yaskevich commented on CASSANDRA-4052:

Yeah,the ticket says that it's for 1.1.1 which is cassandra-1.1 branch.
> Add way to force the cassandra-cli to refresh it's schema
> ---------------------------------------------------------
>                 Key: CASSANDRA-4052
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Tupshin Harper
>            Assignee: Dave Brosius
>            Priority: Minor
>              Labels: cli
>             Fix For: 1.1.1
>         Attachments: 4052_refresh_schema.diff
> By design, the cassandra-cli caches the schema and doesn't refresh it when various commands
like "describe keyspaces" are run. This is reasonable, and it is easy enough to restart the
cli  if necessary. However, this does lead to confusion since a new user can reasonably assume
that describe keyspaces will always show an accurate current represention of the ring. We
should find a way to reduce the surprise (and lack of easy discoverability) of this behaviour.
> I propose any one of the following(#1 is probably the easiest and most likely):
> 1) Add a command (that would be documented in the cli's help) to explicitly refresh the
schema ("schema refresh", "refresh schema", or anything similar).
> 2) Always force a refresh of the schema when performing at least the "describe keyspaces"
> 3) Add a flag to cassandra-cli to explicitly enable schema caching. If that flag is not
passed, then schema caching will be disabled for that session. This suggestion assumes that
for simple deployments (few CFs, etc), schema caching isn't very important to the performance
of the cli.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message