[
https://issues.apache.org/jira/browse/CASSANDRA-11114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294120#comment-15294120
]
Alex Petrov commented on CASSANDRA-11114:
-----------------------------------------
Yes, I know it was there.. Just tried to reword it (actually took the other
wording from DataStax documentation on {{ALTER}} statement) to reflect the
current situation.
You're right about the validation of existing data part. I've changed it to:
bq. To change the type of any other column, the column must already exist in
type definition and its type should be compatible with the new type. No
validation of existing data is performed. The compatibility table is available
below.
|[trunk|https://github.com/ifesdjeen/cassandra/commits/11114-trunk]|[utest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-11114-trunk-testall/]|
CI has passed the added tests. So if you +1, we can move it to ready to commit
state.
> Document which type conversions are allowed
> -------------------------------------------
>
> Key: CASSANDRA-11114
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11114
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL, Documentation and Website
> Reporter: Sylvain Lebresne
> Assignee: Giampaolo
> Priority: Minor
> Labels: doc-impacting, lhf
> Attachments: cassandra-11114-trunk.patch
>
>
> We allow only some type conversion through {{ALTER TABLE}} and type casts,
> the ones that don't break stuff, but we don't currently document which ones
> those are. We should add it to
> http://cassandra.apache.org/doc/cql3/CQL-3.0.html.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
