You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tupshin Harper (Created) (JIRA)" <ji...@apache.org> on 2012/03/15 01:34:40 UTC
[jira] [Created] (CASSANDRA-4052) Add way to force the
cassandra-cli to refresh it's schema
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
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
[jira] [Commented] (CASSANDRA-4052) Add way to force the
cassandra-cli to refresh it's schema
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252203#comment-13252203 ]
Jonathan Ellis commented on CASSANDRA-4052:
-------------------------------------------
Ah, I bet you're right.
> 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
>
> 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
[jira] [Updated] (CASSANDRA-4052) Add way to force the
cassandra-cli to refresh it's schema
Posted by "Jonathan Ellis (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-4052:
--------------------------------------
Reviewer: xedin
Fix Version/s: 1.1.1
Assignee: Dave Brosius
Labels: cli (was: )
bq. 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.
Nice!
> 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
> 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" 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
[jira] [Commented] (CASSANDRA-4052) Add way to force the
cassandra-cli to refresh it's schema
Posted by "Pavel Yaskevich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258953#comment-13258953 ]
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: https://issues.apache.org/jira/browse/CASSANDRA-4052
> 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" 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
[jira] [Commented] (CASSANDRA-4052) Add way to force the
cassandra-cli to refresh it's schema
Posted by "Dave Brosius (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258952#comment-13258952 ]
Dave Brosius commented on CASSANDRA-4052:
-----------------------------------------
Hmmm this applies directly, but it is against trunk.. Do you want me to apply it to some other branch?
> 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
> 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" 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
[jira] [Commented] (CASSANDRA-4052) Add way to force the
cassandra-cli to refresh it's schema
Posted by "Dave Brosius (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252196#comment-13252196 ]
Dave Brosius commented on CASSANDRA-4052:
-----------------------------------------
Is this schema cached to allow for the assumption of cf attributes?
ie, assume cf validator as utf8;
?
> 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
>
> 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
[jira] [Updated] (CASSANDRA-4052) Add way to force the
cassandra-cli to refresh it's schema
Posted by "Dave Brosius (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_1.1_branch.diff
4052_refresh_schema_1.1_branch.diff
patch applied to cassandra-1.1 branch
> 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
> Reporter: Tupshin Harper
> Assignee: Dave Brosius
> Priority: Minor
> Labels: cli
> Fix For: 1.1.1
>
> Attachments: 4052_refresh_schema.diff, 4052_refresh_schema_1.1_branch.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
[jira] [Commented] (CASSANDRA-4052) Add way to force the
cassandra-cli to refresh it's schema
Posted by "Pavel Yaskevich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258939#comment-13258939 ]
Pavel Yaskevich commented on CASSANDRA-4052:
--------------------------------------------
Can you please rebase?
> 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
> 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" 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
[jira] [Commented] (CASSANDRA-4052) Add way to force the
cassandra-cli to refresh it's schema
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230253#comment-13230253 ]
Jonathan Ellis commented on CASSANDRA-4052:
-------------------------------------------
Is schema querying so slow that we really need to cache it? Sounds to me like we may have overengineered this.
> 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
>
> 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
[jira] [Issue Comment Edited] (CASSANDRA-4052) Add way to force the
cassandra-cli to refresh it's schema
Posted by "Dave Brosius (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257259#comment-13257259 ]
Dave Brosius edited comment on CASSANDRA-4052 at 4/19/12 5:57 AM:
------------------------------------------------------------------
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.
patch against trunk
was (Author: dbrosius@apache.org):
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
[jira] [Commented] (CASSANDRA-4052) Add way to force the
cassandra-cli to refresh it's schema
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260880#comment-13260880 ]
Hudson commented on CASSANDRA-4052:
-----------------------------------
Integrated in Cassandra #1273 (See [https://builds.apache.org/job/Cassandra/1273/])
fix for situation when assumtions are read for CF that does not exist (CASSANDRA-4052) (Revision 189e133a586a5b4afb1021440def9c02d14d17bb)
Result = FAILURE
xedin :
Files :
* src/java/org/apache/cassandra/cli/CliClient.java
> 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
> Reporter: Tupshin Harper
> Assignee: Dave Brosius
> Priority: Minor
> Labels: cli
> Fix For: 1.1.1
>
> Attachments: 4052_refresh_schema.diff, 4052_refresh_schema_1.1_branch.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
[jira] [Updated] (CASSANDRA-4052) Add way to force the
cassandra-cli to refresh it's schema
Posted by "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