[jira] [Updated] (CASSANDRA-4052) Add way to force the cassandra-cli to refresh it's schema

["Dave Brosius (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Brosius updated CASSANDRA-4052:
------------------------------------

    Attachment: 4052_refresh_schema.diff

Add flushing of cached schema in cli on updatekeyspace, use and describe. To retain assume commands that have been applied, hold assumptions in a separate class that holds a map of these assumptions. Since we now have that, save these assumptions across separate invocations of cli by storing in a ~/.cassandra-cli directory file.
                
> Add way to force the cassandra-cli to refresh it's schema
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-4052
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4052
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions: 1.0.8
>            Reporter: Tupshin Harper
>            Priority: Minor
>         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" command.
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira