Hi folks, I'm working on a clean-up task for some bad data in a cassandra db. The bad data in this case are values with mixed case that will need to be lowercased. In some tables the value that needs to be changed is a primary key, in other cases it is not.
>From the reading I've done, the situations where I need to change a primary key column to lowercase will mean I need to perform an INSERT of the entire row using the new primary key values merged with the old non-primary-key values, followed by a DELETE of the old primary key row. My question is, on a table where I need to update a column that isn't primary key, should I perform a limited UPDATE in that situation like I would in SQL: UPDATE ks.table SET col1 = ? WHERE pk1 = ? AND pk2 = ? or will there be any downsides to that over an INSERT where I specify all columns? INSERT INTO ks.table (pk1, pk2, col1, col2, ...) VALUES (?,?,?,?, ...) In SQL I'd never question just using the update but my impression reading the blogosphere is that Cassandra has subtleties that I might not be grasping when it comes to UPDATE v. INSERT behavior... Jim --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
