You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2013/06/25 19:25:27 UTC
[jira] [Updated] (CASSANDRA-5489) Fix 2.0 key and column aliases
serialization and cqlsh DESC SCHEMA
[ https://issues.apache.org/jira/browse/CASSANDRA-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne updated CASSANDRA-5489:
----------------------------------------
Attachment: 5489.txt
I had forgotten this. Anyway, attaching simple patch for trunk that 1) add a sanity check to validate that we do have either all or no aliases and that 2) write an empty json list in the case we have none.
> Fix 2.0 key and column aliases serialization and cqlsh DESC SCHEMA
> ------------------------------------------------------------------
>
> Key: CASSANDRA-5489
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5489
> Project: Cassandra
> Issue Type: Bug
> Components: Core, Tools
> Affects Versions: 2.0 beta 1
> Reporter: Aleksey Yeschenko
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 2.0 beta 1
>
> Attachments: 5489-1.2.txt, 5489.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 table.
> 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: http://www.atlassian.com/software/jira