[
https://issues.apache.org/jira/browse/CASSANDRA-18837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17947375#comment-17947375
]
Brad Schoening edited comment on CASSANDRA-18837 at 4/25/25 4:56 PM:
---------------------------------------------------------------------
Currently, most if not all of the auto-complete is done with static content.
One example where dynamic content with PostgreSQL doesn't work with
auto-complete and the reasons why was discussed in [Autocomplete is not working
in
postgreesql|https://serverfault.com/questions/638237/autocomplete-is-not-working-in-postgreesql-8-4]
[~pranavchaurasia] the PR performs a select from system.local and system.peers.
The driver querying the system tables for metadata doesn't seem right. Not
sure if there are other instances where this is done, but among other problems,
if it's cached, it would not be up-to-date with any new data centers added.
Also not sure all users have read access to system tables.
The DC meta-data issue be might worth discussing on the #cassandra-drivers
Slack channel. If the driver doesn't have the metadata about DCs, then this
might be a barrier to making the driver aware of DCs and keeping it up-to-date
just for auto-complete.
[~pranavchaurasia] we always appreciate new contributors, I could suggest a few
other Jiras involving CQLSH or python which might be more straightforward.
was (Author: bschoeni):
Currently, most if not all of the auto-complete is done with static content.
One example where dynamic content with PostgreSQL doesn't work with
auto-complete and the reasons why was discussed in [Autocomplete is not working
in
postgreesql|https://serverfault.com/questions/638237/autocomplete-is-not-working-in-postgreesql-8-4]
[~pranavchaurasia] the PR performs a select from system.local and system.peers.
The driver querying the system tables for metadata doesn't seem right. Not
sure if there are other instances where this is done, but among other problems,
if it's cached, it would not be up-to-date with any new data centers added.
Also not sure all users have read access to system tables.
The DC meta-data issue might worth discussing on the #cassandra-drivers Slack
channel. If the driver doesn't have the metadata about DCs, then this might be
a barrier to making the driver aware of DCs and keeping it up-to-date just for
auto-complete.
[~pranavchaurasia] we always appreciate new contributors, I could suggest a few
other Jiras involving CQLSH or python which might be more straightforward.
> Tab complete datacenter values in cqlsh
> ---------------------------------------
>
> Key: CASSANDRA-18837
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18837
> Project: Apache Cassandra
> Issue Type: Task
> Components: CQL/Interpreter
> Reporter: Jeremy Hanna
> Priority: Normal
> Fix For: 5.x
>
>
> cqlsh has a number of great tab completions. For example, when creating a
> keyspace it will tab complete the syntax for options and give you options for
> the replication strategy. It doesn't show options for the data centers,
> which would be nice to have. The server has access to the list of data
> centers in the cluster. So there shouldn't be a reason why that couldn't tab
> complete.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
