[
https://issues.apache.org/jira/browse/CASSANDRA-15271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-15271:
------------------------------------------
Fix Version/s: (was: 4.0)
4.0-alpha
Since Version: 4.0-alpha
Source Control Link:
[1f242c900bb087770a4cffeade6986ef19ba303d|https://github.com/apache/cassandra/commit/1f242c900bb087770a4cffeade6986ef19ba303d]
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed with some minor touch-ups and nomenclature correction (we don't have
clustering key or clustering key columns anymore, the preferred term is just
"clustering columns").
> CASSANDRA-13426 changed the behavior of "CLUSTERING ORDER" on "CREATE TABLE"
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-15271
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15271
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Syntax
> Reporter: Jeremiah Jordan
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.0-alpha
>
> Attachments: CASSANDRA-15271-testall.txt, CASSANDRA-15271.zip, Screen
> Shot 2020-02-26 at 11.25.29 AM.png
>
>
> CASSANDRA-13426 changed the behavior of "CLUSTERING ORDER" on "CREATE TABLE",
> it now complains if you don't specify all the columns.
> It was nice that previously you could just specify to make the first
> clustering DESC and leave the rest ASC without needing to specify them. Also
> it would be nice I think to avoid breaking changes to the CREATE TABLE syntax.
> We should either update NEWS.txt to call out the breaking change there, or
> update the new code to be able to default the columns which were not
> mentioned.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
