rsion of the
> schema on a new node? Is there a reason to apply the migrations?
>
> - Mike
>
> From: aaron morton [mailto:aa...@thelastpickle.com]
> Sent: Tuesday, March 06, 2012 4:14 AM
> To: user@cassandra.apache.org
> Subject: Re: Secondary indexes don't go away afte
on of the schema on a
new node? Is there a reason to apply the migrations?
- Mike
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: Tuesday, March 06, 2012 4:14 AM
To: user@cassandra.apache.org
Subject: Re: Secondary indexes don't go away after metadata change
When the new node co
elastpickle.com]
> Sent: Monday, March 05, 2012 3:58 AM
> To: user@cassandra.apache.org
> Subject: Re: Secondary indexes don't go away after metadata change
>
> The secondary index CF's are marked as no longer required / marked as
> compacted. under 1.x they would then be delet
2012 3:58 AM
To: user@cassandra.apache.org
Subject: Re: Secondary indexes don't go away after metadata change
The secondary index CF's are marked as no longer required / marked as
compacted. under 1.x they would then be deleted reasonably quickly, and
definitely deleted after a restart
The secondary index CF's are marked as no longer required / marked as
compacted. under 1.x they would then be deleted reasonably quickly, and
definitely deleted after a restart.
Is there a zero length .Compacted file there ?
> Also, when adding a new node to the ring the new node will build i
