[
https://issues.apache.org/jira/browse/CASSANDRA-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543869#comment-13543869
]
Aleksey Yeschenko commented on CASSANDRA-5101:
----------------------------------------------
I'm checking now, but it seems like there is another issue with key aliases for
upgraded 1.1 instances - if they have a key alias, it's going to be in the
key_alias column, which we are no longer using.
That would make key aliases even less consistent (need to look at key_alias
column, need to check key_aliases for null). I think pushing this complexity to
the clients is a bad thing (cqlsh is not the only consumer of system.shema_*
tables) - the better way would be to convert non-null key_alias to key_aliases
singleton list and null key_alias to an empty list on startup, once.
I'm not a fat of either solution, but there is no third one, and I slightly
prefer dealing with this in C* and not pushing the complexity to all the
clients.
> describe commands fail in cql3 when previously created with cql2
> ----------------------------------------------------------------
>
> Key: CASSANDRA-5101
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5101
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Michael Kjellman
> Assignee: Aleksey Yeschenko
> Priority: Minor
> Fix For: 1.2.1
>
> Attachments: 5101.txt
>
>
> column families and keyspaces created with cassandra-cli/cql2 cannot be
> described with cql3
> describe table cfname fails with: "expected string or buffer"
> describe schema fails with "expected string or buffer" as well
--
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
