[
https://issues.apache.org/jira/browse/CASSANDRA-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543680#comment-13543680
]
Sylvain Lebresne commented on CASSANDRA-5101:
---------------------------------------------
For the record, I think I'd prefer fixing cqlsh to be less fragile and to
handle both null and [] the same way (it should probably do that for
column_aliases too btw). Adding code at startup to rewrite nulls to [] feels
highly overkill here, especially since having no key_aliases column is no wrong
per se.
I note that the fact we have 2 way to mean "no key aliases" is unfortunate but
just a downside of using a json-encoded list internally and that'll be fix once
we switch to true lists.
> 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
