Re: Possible bug in Cassandra MapReduce

2010-06-18 Thread Jonathan Ellis
Looks like the end of June. On Fri, Jun 18, 2010 at 8:38 PM, Corey Hulen wrote: > Awesome...thanks. > I just downloaded the patch and applied it and verified it fixes our > problems. > what's the ETA on 0.6.3?  (debating on weather to tolerate it or maintain > our own 0.6.2+patch). > -Corey > > O

Re: Possible bug in Cassandra MapReduce

2010-06-18 Thread Corey Hulen
Awesome...thanks. I just downloaded the patch and applied it and verified it fixes our problems. what's the ETA on 0.6.3? (debating on weather to tolerate it or maintain our own 0.6.2+patch). -Corey On Fri, Jun 18, 2010 at 8:21 PM, Jonathan Ellis wrote: > Fixed for 0.6.3: https://issues.apac

Re: Possible bug in Cassandra MapReduce

2010-06-18 Thread Jonathan Ellis
Fixed for 0.6.3: https://issues.apache.org/jira/browse/CASSANDRA-1042 On Fri, Jun 18, 2010 at 2:49 PM, Corey Hulen wrote: > > We are using MapReduce to periodical verify and rebuild our secondary > indexes along with counting total records.  We started to noticed double > counting of unique keys

Re: Possible bug in Cassandra MapReduce

2010-06-18 Thread Corey Hulen
OK...I just verified on a clean EC2 small single instance box using apache-cassandra-0.6.2-src. I'm pertty sure the Cassandra MapReduce functionality is broken. If your MapReduce jobs are idempotent then you are OK, but if you are doing things like word count (as in the supplied example) or key c

Re: Possible bug in Cassandra MapReduce

2010-06-18 Thread Corey Hulen
I thought the same thing, but using the supplied contrib example I just delete the /var/lib/data dirs and commit log. -Corey On Fri, Jun 18, 2010 at 3:11 PM, Phil Stanhope wrote: > "blow all the data away" ... how do you do that? What is the timestamp > precision that you are using when creat

Re: Possible bug in Cassandra MapReduce

2010-06-18 Thread Phil Stanhope
"blow all the data away" ... how do you do that? What is the timestamp precision that you are using when creating key/col or key/supercol/col items? I have seen a fail to write a key when the timestamp is identical to the previous timestamp of a deleted key/col. While I didn't examine the source

Possible bug in Cassandra MapReduce

2010-06-18 Thread Corey Hulen
We are using MapReduce to periodical verify and rebuild our secondary indexes along with counting total records. We started to noticed double counting of unique keys on single machine standalone tests. We were finally able to reproduce the problem using the apache-cassandra-0.6.2-src/contrib/word_