Mailing-List: contact client-dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: client-dev@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of robertj@promedicalinc.com
 designates 97.66.157.146 as permitted sender)
Subject: Re: Ruby cassandra client: unit tests no longer pass 100%
References: <874nztb1he.fsf@lambda.ihatejava.org>
Content-Transfer-Encoding: quoted-printable
From: Robert Jackson <robertj@promedicalinc.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: <874nztb1he.fsf@lambda.ihatejava.org>
Message-Id: <45E25DD8-E664-486F-B94B-CCF9640BCDCA@promedicalinc.com>
Date: Sat, 01 Oct 2011 07:46:44 -0400 (EDT)
To: "client-dev@cassandra.apache.org" <client-dev@cassandra.apache.org>
Cc: "client-dev@cassandra.apache.org" <client-dev@cassandra.apache.org>
MIME-Version: 1.0

Sorry, but I have not had a chance to take a look at your pull request.=20

I'll try to look into it this weekend, and either merge it in or give some s=
uggestions on any changes needed.=20

Robert Jackson

Sent from my iPhone

On Oct 1, 2011, at 3:45 AM, shyamal <shyamal@member.fsf.org> wrote:

>=20
> Hi,
>=20
> The unit tests for the fauna cassandra ruby client
> (https://github.com/fauna/cassandra/) consistently fail for me:
>=20
> $ ruby ./test/cassandra_test.rb -n test_each
> ....
> 1) Failure:
> test_each(CassandraTest) [./test/cassandra_test.rb:354]:
> each limits to specified count.
> <7> expected but was
> <10>.
>=20
> As far as I can tell this is because get_range_batch was modified to
> discard rows when a block is provided as a way to reduce memory
> footprint. This broke support for a :key_count.
>=20
> I submitted a request to what I think is "upstream" for this project at
> https://github.com/fauna/cassandra/pull/122. Since I've got no feedback
> I'd appreciate some confirmation that this was the right place to
> discuss the library (and, of course, any feedback on the failure case
> itself is welcome!).
>=20
> Cheers!
> Shyamal
>=20
> PS: Sorry if you see duplicate messages, I seemed to have had trouble
> posting to this list earlier today.