cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-4696) improve ALTER TABLE
Date Fri, 21 Sep 2012 13:17:07 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-4696.
---------------------------------------

    Resolution: Won't Fix

doing a seq scan across potentially TB of data is not an option.  if you change it to something
incompatible by mistake, you can always change it back.
                
> improve ALTER TABLE
> -------------------
>
>                 Key: CASSANDRA-4696
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4696
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 1.1.5
>            Reporter: Michael Krumpholz
>              Labels: alter, cql, datatype
>
> Please improve the ALTER TABLE statement so that it automatically checks the data in
the table against the new data type to change to. I know that it's in the docs that this is
the current state and not checked. It may be the easiest and fastest way for implementation
for now but it should be improved in the future.
> docs on ALTER:
> {noformat}
> The column must already have a type in the column family metadata. The column may or
may not already exist 
> in current rows (no validation of existing data occurs). The bytes stored in values for
that column remain 
> unchanged, and if existing data is not deserializable according to the new type, your
CQL driver or 
> interface might report errors.
> {noformat}

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

Mime
View raw message