cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lohfink (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8834) Top partitions reporting wrong cardinality
Date Tue, 03 Mar 2015 15:40:05 GMT


Chris Lohfink commented on CASSANDRA-8834:

So I cant seem to reproduce it but I when testing after upgrading to 2.1.3 (along with stress
tool upgrade that happened there) I was getting that exception from there, which I can neither
explain or have happen again...  Something involving the change in schema when going from
old pure thrift table to what cqlstress creates now I assumed.

> Top partitions reporting wrong cardinality
> ------------------------------------------
>                 Key: CASSANDRA-8834
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Chris Lohfink
>            Assignee: Chris Lohfink
>             Fix For: 2.1.4
>         Attachments: cardinality.patch
> It always reports a cardinality of 1.  Patch also includes a try/catch around the conversion
of partition keys that isn't always handled well in thrift cfs.

This message was sent by Atlassian JIRA

View raw message