[
https://issues.apache.org/jira/browse/CASSANDRA-15576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039285#comment-17039285
]
David Capwell commented on CASSANDRA-15576:
-------------------------------------------
In testing it looks like this isn't enough
{code}
$ ./bin/cqlsh
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 4.0-alpha4-SNAPSHOT | CQL spec 3.4.5 | Native protocol
v4]
Use HELP for help.
cqlsh> describe keyspace;
Not in any keyspace.
cqlsh> describe keyspaces;
system_traces system_auth system_distributed system_views
system_schema system system_virtual_schema
cqlsh> use system_views;
cqlsh:system_views> describe keyspace;
'NoneType' object has no attribute 'export_for_schema'
{code}
This looks like the other jira CASSANDRA-14872. Now, looking at that JIRA the
TODO implies that upgrading would actually fix the issue.
[~djoshi] is the intent that this is to unblock trunk until CASSANDRA-14872
happens? Kinda feel it would be best to have one JIRA which makes sure vtables
work with cqlsh.
> CQLSH missing virtual keyspaces on DESCRIBE call
> ------------------------------------------------
>
> Key: CASSANDRA-15576
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15576
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
> Reporter: Dinesh Joshi
> Assignee: Dinesh Joshi
> Priority: Normal
> Fix For: 4.0-alpha
>
>
> cqlsh is missing virtual keyspaces. This patch fixes it. It also adds a dtest
> to avoid future regressions.
> [Branch|https://github.com/dineshjoshi/cassandra/tree/fix-missing-keyspace-issue-cqlsh],
>
> [DTests|https://github.com/dineshjoshi/cassandra-dtest-1/tree/fix-missing-keyspace-issue-cqlsh]
> and
> [CI|https://circleci.com/workflow-run/b978fe37-98a8-482b-89bf-f7b6c8c41a40].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
