That's a good approach. You could also migrate in-place if you're confident
your migration algorithm is correct, but for more safety having another CF
is better.
If you have a huge volume of data to be migrated (millions of rows or
more), I'd suggest you to use Hadoop to perform these migrations
Hello,
Let's say we have a simple CQL3 table
CREATE TABLE example (
id UUID PRIMARY KEY,
timestamp TIMESTAMP,
data ASCII
);
And I need to mutate (for example encrypt) column values in the data column
for all rows.
What's the recommended approach to perform such migration
I would do something like you are suggesting. I would not do the delete
until all the rows are moved. Since writes in cassandra are idempotent you
can even run the migration process multiple times without harm.
On Sat, Sep 7, 2013 at 5:31 PM, Renat Gilfanov gren...@mail.ru wrote:
Hello,
