cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5489) Fix 2.0 key and column aliases serialization and cqlsh DESC SCHEMA
Date Wed, 01 May 2013 12:36:16 GMT


Aleksey Yeschenko commented on CASSANDRA-5489:

Agreed then.

Though on that part, shouldn't we handle the case where the schema don't have a 'type' column
(since 'type' is only there in trunk)? 

Ahead of you here - v1 patch handles that already (in "c.get('type', 'regular')" 'regular'
is the default value to use if 'type' attribute is absent).

> Fix 2.0 key and column aliases serialization and cqlsh DESC SCHEMA
> ------------------------------------------------------------------
>                 Key: CASSANDRA-5489
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core, Tools
>    Affects Versions: 2.0
>            Reporter: Aleksey Yeschenko
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 2.0
>         Attachments: 5489-1.2.txt, 5489.txt
> CASSANDRA-5125 made a slight change to how key_aliases and column_aliases are serialized
in schema. Prior to that we never kept nulls in the the json pseudo-lists. This does break
cqlsh and probably breaks 1.2 nodes receiving such migrations as well. The patch reverts this
behavior and also slightly modifies cqlsh itself to ignore non-regular columns from system.schema_columns
> This patch breaks nothing, since 2.0 already handles 1.2 non-null padded alias lists.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message