cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Bannister (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7814) enable describe on indices
Date Wed, 20 Jun 2018 00:29:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517653#comment-16517653
] 

Patrick Bannister commented on CASSANDRA-7814:
----------------------------------------------

Is it a requirement that the output of DESCRIBE should sort things lexicographically? For
example, if keyspace test has tables test and users, do we require that the output of DESCRIBE
KEYSPACE test should show the test table before the users table?

I ask because the dtest for this ticket is very flaky and fails frequently. It's written to
expect a specific sort order in the tables and indexes for the output of DESCRIBE KEYSPACE.
The root cause is in the cassandra Python driver in cassandra.metadata, because of the implementation
of export_as_string() in the KeyspaceMetadata and TableMetadata classes. They visit their
child objects in the order returned by the Python dict values() function, which is arbitrary
and unsorted.

If lexicographic sorting is a requirement, a modification to the Python driver will be needed.
If lexicographic sorting is not a requirement, then I could modify the test_describe() dtest
to stop caring about the order of objects in the DESCRIBE output.

This is coming up in CASSANDRA-10190 (adding Python 3 compatibility to cqlsh).

> enable describe on indices
> --------------------------
>
>                 Key: CASSANDRA-7814
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7814
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: radha
>            Assignee: Stefania
>            Priority: Minor
>              Labels: doc-impacting
>             Fix For: 2.1.8, 2.2.0 rc2, 3.0 alpha 1
>
>
> Describe index should be supported, right now, the only way is to export the schema and
find what it really is before updating/dropping the index.
> verified in 
> [cqlsh 3.1.8 | Cassandra 1.2.18.1 | CQL spec 3.0.0 | Thrift protocol 19.36.2]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message