[
https://issues.apache.org/jira/browse/CASSANDRA-20365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17929856#comment-17929856
]
Brandon Williams commented on CASSANDRA-20365:
----------------------------------------------
The answer to my question is that DescribeStatementTest in its current form
tests describing materialized views, but does not test for materialized views
in the table describe.
Okay, with that out of the way, +1 from me if CI is happy.
> DESCRIBE TABLE does not list materialized views
> -----------------------------------------------
>
> Key: CASSANDRA-20365
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20365
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Legacy/Core, Legacy/CQL
> Reporter: Nadav Har'El
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I noticed that if I run DESCRIBE TABLE (the new server-side CQL command, not
> the old cqlsh command) on a table that has materialized views, I get back
> just {{CREATE TABLE}} command for the base table but no {{{}CREATE
> MATERIALIZED VIEW{}}}.
> I found this strange for several reasons:
> # Old cqlsh documentation such as
> [https://docs.datastax.com/en/cql/hcd/reference/cqlsh-commands/describe-table.html]
> suggested that DESCRIBE TABLE should return "executable CQL information for
> a single table, including materialized views that are based on the table".
> # Probably a user will want to recreate views when recreating a table.
> # On a table with secondary index, CREATE INDEX statements *are* included in
> the output of DESCRIBE TABLE. Why should indexes be listed and views not?
> Is any of this intentional? I couldn't find any CQL (not cqlsh) documentation
> explaining what DESCRIBE TABLE should return, or why.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
