[CASSANDRA-10857] Allow dropping COMPACT STORAGE flag from tables in 3.X - ASF JIRA

Agile Board

Attach files

Attach Screenshot

Bulk Copy Attachments

Bulk Move Attachments

Voters

Watch issue

Watchers

Create sub-task

Convert to sub-task

Move

Link

Clone

Labels

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Resolved
Priority: Urgent
Resolution: Fixed
Fix Version/s: 3.0.16, 3.11.2
Component/s: Legacy/CQL, Legacy/Distributed Metadata
Labels:
None

Impacts:

Clients

Description

Thrift allows users to define flexible mixed column families - where certain columns would have explicitly pre-defined names, potentially non-default validation types, and be indexed.

Example:

create column family foo
    and default_validation_class = UTF8Type
    and column_metadata = [
        {column_name: bar, validation_class: Int32Type, index_type: KEYS},
        {column_name: baz, validation_class: UUIDType, index_type: KEYS}
    ];

Columns named bar and baz will be validated as Int32Type and UUIDType, respectively, and be indexed. Columns with any other name will be validated by UTF8Type and will not be indexed.

With ~~CASSANDRA-8099~~, bar and baz would be mapped to static columns internally. However, being WITH COMPACT STORAGE, the table will only expose bar and baz columns. Accessing any dynamic columns (any column not named bar and baz) right now requires going through Thrift.

This is blocking Thrift -> CQL migration for users who have mixed dynamic/static column families. That said, it shouldn't be hard to allow users to drop the compact flag to expose the table as it is internally now, and be able to access all columns.