CQL Export for Thrift Tables

Description

Need to revisit CQL export for thrift tables.

https://datastax-oss.atlassian.net/browse/PYTHON-192 for background.

We settled for commenting out types we couldn't handle, but that will not be adequate for when CLI is deprecated.

Any 'custom' types, including DCT, should be quoted verbatim as the column type. Presently DCT is recognized as a Composite type.

Getting indexes correct on these may not work in 2.1. May require https://issues.apache.org/jira/browse/CASSANDRA-8099

Environment

None

Pull Requests

None

Activity

Show:
Adam Holmberg
August 3, 2016, 9:18 PM

if you're still willing to take a look at this, I've created a gist showing some CLI schema and current CQL output (created CLI in 2.1 then upgraded -> 2.2 -> 3.0).

Adam Holmberg
August 3, 2016, 2:45 PM

It appears that we still can't quite represent the inode table in CQL. There is no way to model tables with non-UTF8 comparators, in the presence of static columns. We will still need an update to detect this configuration as non-cql-compatible. Presently the absence of `flags` causes the table meta to disregard the clustering column in this table.

Aleksey also noted that we'll need to follow up on https://issues.apache.org/jira/browse/CASSANDRA-7190, and possibly create a separate ticket to allow full compatibility.

Adam Holmberg
August 2, 2016, 5:56 PM

There have been numerous refactors and improvements in schema parsing. That, and the tickets Tyler mentioned above are complete. I'm resuming this now to see where we are and hopefully button it up.

One note from Aleksey: we should also exclude super column tables from output (comment when not is_cql_compatible).

Adam Holmberg
December 11, 2015, 3:16 PM

Removing from progress until blockers are removed.

Tyler Hobbs
April 30, 2015, 5:41 PM

We're not going to be able to support this schema server-side in Cassandra 2.1. In 3.0 we should be able to support it by treating the defined columns as static columns. CASSANDRA-8178 (already completed) should enable the handling of column names like b@706172656e745f70617468. We will also need to make sure CASSANDRA-8103 gets implemented for 3.0 to support the indexes.

Fixed

Assignee

Unassigned

Reporter

Adam Holmberg

Fix versions