Bug report posted @ https://issues.apache.org/jira/browse/CASSANDRA-9023
On Mon, Mar 23, 2015 at 11:21 PM, Robert Coli wrote:
> On Mon, Mar 23, 2015 at 7:27 AM, Brian Tarbox
> wrote:
>
> > My group is seeing the same thing and also can not figure out why its
> > happening.
> >
> > On Mon, Mar 2
On Mon, Mar 23, 2015 at 7:27 AM, Brian Tarbox wrote:
> My group is seeing the same thing and also can not figure out why its
> happening.
>
> On Mon, Mar 23, 2015 at 8:36 AM, Anishek Agarwal
> wrote:
>
>> Forgot to mention I am using Cassandra 2.0.13
>>
>
This seems like a rather significant bug
Forgot to mention I am using Cassandra 2.0.13
On Mon, Mar 23, 2015 at 5:59 PM, Anishek Agarwal wrote:
> Hello,
>
> I am using a single node server class machine with 16 CPUs with 32GB RAM
> with a single drive attached to it.
>
> my table structure is as below
>
> CREATE TABLE t1(id bigint, ts
Hello,
I am using a single node server class machine with 16 CPUs with 32GB RAM
with a single drive attached to it.
my table structure is as below
CREATE TABLE t1(id bigint, ts timestamp, cat1 set, cat2
set, lat float, lon float, a bigint, primary key (id, ts));
I am trying to insert 300 entri
