[
https://issues.apache.org/jira/browse/CASSANDRA-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543886#comment-13543886
]
Sylvain Lebresne commented on CASSANDRA-5101:
---------------------------------------------
Converting things at startup is not as easy as it sound, because the schema is
distributed. Typically, removing key_alias on startup on newly upgraded node
would potentially propagate and screw up old, not-yet upgraded nodes (and/or
new nodes would pull back the "key_alias" from older nodes after startup).
I hear you about not pushing the complexity to the clients, but at the same
time we have to be extra careful with the schema table, as screwing things
there is the one way to screw up a full cluster, and so making those tables
convenient to read for clients is not a top priority (which is not saying we
should make it hard on purpose but ...).
Also, converting the information from the schema table to a CQL3 definition is
already far from trivial and I'm not sure that little details like the one on
this issue really make much quantitative difference here. Don't get me wrong,
this already existing complexity is not a good thing, and maybe exposing the
system tables directly is not the best way to expose the schema for CQL3
clients. But my point is, as far as this ticket is concerned, I'd still rather
avoid messing with schema at startup, especially to save a very small amount of
complexity to clients library. But I'm all for discussing how we could fix the
more general issue that the information exposed in the system schema is hard to
make sense of for a CQL3 client.
> 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
