Re: implementation choice with regard to multiple range slice query filters

2012-04-03 Thread David Alves
cool, thanks. -david On Apr 4, 2012, at 1:01 AM, Jonathan Ellis wrote: > You need more than column_index_size_in_kb worth of column data for it > to generate row header index entries. We have a cassandra.yaml in > test/conf that sets that extra low, to 4, to make that easier. "ant > test" sets

Re: implementation choice with regard to multiple range slice query filters

2012-04-03 Thread Jonathan Ellis
You need more than column_index_size_in_kb worth of column data for it to generate row header index entries. We have a cassandra.yaml in test/conf that sets that extra low, to 4, to make that easier. "ant test" sets up the environment to point to that yaml, but if you're running it from your IDE

Re: implementation choice with regard to multiple range slice query filters

2012-04-03 Thread David Alves
Hi Jonathan: Thanks for the tip. Although the first option I proposed would not incur in that penalty it would not take advantage of the columns index for the middle ranges. On a related matter, I'm struggling to test the IndexedBlockFetcher implementation (SimpleBlockF

Re: [VOTE] Release Apache Cassandra 1.0.9 (strike 2)

2012-04-03 Thread Pavel Yaskevich
+1 3 apr 2012 kl. 22:38 skrev Jonathan Ellis : > +1 > > On Tue, Apr 3, 2012 at 10:21 AM, Sylvain Lebresne > wrote: >> The first attempt was closed to include the fix for CASSANDRA-4112. After >> have >> committed said fix, I'm proposing the following artifacts for release as >> 1.0.9. >> >> s

Re: [VOTE] Release Apache Cassandra 1.0.9 (strike 2)

2012-04-03 Thread Jonathan Ellis
+1 On Tue, Apr 3, 2012 at 10:21 AM, Sylvain Lebresne wrote: > The first attempt was closed to include the fix for CASSANDRA-4112. After have > committed said fix, I'm proposing the following artifacts for release as > 1.0.9. > > sha1: 3fd0fb6aa0038f0c8aaf34f98f2ceed2f308a501 > Git: > http://git

[VOTE] Release Apache Cassandra 1.0.9 (strike 2)

2012-04-03 Thread Sylvain Lebresne
The first attempt was closed to include the fix for CASSANDRA-4112. After have committed said fix, I'm proposing the following artifacts for release as 1.0.9. sha1: 3fd0fb6aa0038f0c8aaf34f98f2ceed2f308a501 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.0.9-te

[VOTE CLOSED] Release Apache Cassandra 1.0.9

2012-04-03 Thread Sylvain Lebresne
https://issues.apache.org/jira/browse/CASSANDRA-4112 showed up. It's an easy fix but an annoying bug, so I think it's worth rerolling this one to include it. I'm thus closing this vote and I will start a new one very soon that will include the fix for CASSANDRA-4112 -- Sylvain On Mon, Apr 2, 2012