If you've been dropping and recreating tables with the same name, you might
be seeing this: https://issues.apache.org/jira/browse/CASSANDRA-6525
On Tue, Jun 10, 2014 at 12:19 PM, Robert Coli wrote:
> On Tue, Jun 10, 2014 at 7:31 AM, Jeremy Jongsma
> wrote:
>
>> I'm in the process of migrating
On Tue, Jun 10, 2014 at 7:31 AM, Jeremy Jongsma wrote:
> I'm in the process of migrating data over to cassandra for several of our
> apps, and a few of the schemas use secondary indexes. Four times in the
> last couple months I've run into a corrupted sstable belonging to a
> secondary index, but
I'm in the process of migrating data over to cassandra for several of our
apps, and a few of the schemas use secondary indexes. Four times in the
last couple months I've run into a corrupted sstable belonging to a
secondary index, but have never seen this on any other sstables. When it
happens, any
