cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Petrov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-11114) Document which type conversions are allowed
Date Fri, 20 May 2016 18:32:13 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293927#comment-15293927
] 

Alex Petrov edited comment on CASSANDRA-11114 at 5/20/16 6:31 PM:
------------------------------------------------------------------

I've also changed the wording a bit:

bq.  Other columns are free from those restrictions (no validation of existing data is performed),
but it is usually a bad idea to change the type to a non-compatible one, unless no data have
been inserted for that column yet, as this could confuse CQL drivers/tools.

is now:

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. The compatibility table is available
below.

As previously it sounded as if the {{ALTER TABLE}} statement would actually succeed for those
types. Although since it's going to succeed only in case when types are compatible (or same),
the reference to the compatibility table is added.

I've triggered a CI just to make sure that the newly written tests are working:

|[trunk|https://github.com/ifesdjeen/cassandra/commits/11114-trunk]|[utest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-11114-trunk-testall/]|


was (Author: ifesdjeen):
I've also changed the wording a bit:

bq.  Other columns are free from those restrictions (no validation of existing data is performed),
but it is usually a bad idea to change the type to a non-compatible one, unless no data have
been inserted for that column yet, as this could confuse CQL drivers/tools.

is now:

bq. To change the type of a column, the column must already exist in type definition and its
type should be compatible with the new type. The compatibility table is available below.

As previously it sounded as if the {{ALTER TABLE}} statement would actually succeed for those
types. Although since it's going to succeed only in case when types are compatible (or same),
the reference to the compatibility table is added.

I've triggered a CI just to make sure that the newly written tests are working:

|[trunk|https://github.com/ifesdjeen/cassandra/commits/11114-trunk]|[utest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-11114-trunk-testall/]|

> 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)

Mime
View raw message