Re: [VOTE] Release Apache Cassandra 1.0.7 (Strike 2)

2012-01-13 Thread Jonathan Ellis
+1 On Fri, Jan 13, 2012 at 3:44 AM, Sylvain Lebresne wrote: > With the fix for CASSANDRA-3733 and CASSANDRA-3625 added on top of the > artifacts of Strike 1, I propose the following artifacts for release as 1.0.7 > > Sha1: 6a1ed6205cad8d019eb6eda326d7796a8a0dd67b > Git: > http://git-wip-us.apach

Re: Prepared Statement support (CASSANDRA-2475)

2012-01-13 Thread Jonathan Ellis
To throw out a real-world example: I'm working on CASSANDRA-2878 ("Allow CQL-based map/reduce") and it simplifies things to have the "output" from a query (CqlRow/Column, which are binary) the same as the input parameters [for the resultset KEY > X paging]. Otherwise I have to convert it to string

Re: Prepared Statement support (CASSANDRA-2475)

2012-01-13 Thread Jonathan Ellis
You can always use hex in classic string-based, non-prepared-statements CQL. On Fri, Jan 13, 2012 at 10:53 AM, Jake Luciani wrote: > Not to mention in the case of CFS we deal only in binary blobs. > > I'd rather see us add a hex hack for JS and PHP rather then cater to them. > > -Jake > > On Fri,

Re: Prepared Statement support (CASSANDRA-2475)

2012-01-13 Thread Jake Luciani
Not to mention in the case of CFS we deal only in binary blobs. I'd rather see us add a hex hack for JS and PHP rather then cater to them. -Jake On Fri, Jan 13, 2012 at 11:42 AM, Sylvain Lebresne wrote: > I think CQL has a problem, it doesn't deal with binary correctly. > I have very successful

Re: Prepared Statement support (CASSANDRA-2475)

2012-01-13 Thread Sylvain Lebresne
I think CQL has a problem, it doesn't deal with binary correctly. I have very successfully used C* to store big amounts of small pictures and CQL just cannot handle that efficiently. I've looked quickly but I didn't see anywhere in the tests on CASSANDRA-3634 biggish column values tested (say in t

Re: Prepared Statement support (CASSANDRA-2475)

2012-01-13 Thread Jonathan Ellis
On Fri, Jan 13, 2012 at 9:45 AM, Tyler Hobbs wrote: > On Fri, Jan 13, 2012 at 8:11 AM, Gary Dusbabek wrote: > >> >> Not all languages Javascript make it easy to do binary. > > > PHP also goes in this boat, which leads me to agree with Gary. I don't get it. Don't you already have the binary enco

Re: Prepared Statement support (CASSANDRA-2475)

2012-01-13 Thread Tyler Hobbs
On Fri, Jan 13, 2012 at 8:11 AM, Gary Dusbabek wrote: > > Not all languages Javascript make it easy to do binary. PHP also goes in this boat, which leads me to agree with Gary. -- Tyler Hobbs DataStax

Re: Prepared Statement support (CASSANDRA-2475)

2012-01-13 Thread Gary Dusbabek
I'd like to see the clients stay as simple as possible, keeping the bind parameters as strings. Not all languages Javascript make it easy to do binary. Gary. On Wed, Jan 11, 2012 at 15:14, Eric Evans wrote: > On Wed, Dec 14, 2011 at 5:49 PM, Eric Evans wrote: >> Thanks to the hard work of Ric

[VOTE] Release Apache Cassandra 1.0.7 (Strike 2)

2012-01-13 Thread Sylvain Lebresne
With the fix for CASSANDRA-3733 and CASSANDRA-3625 added on top of the artifacts of Strike 1, I propose the following artifacts for release as 1.0.7 Sha1: 6a1ed6205cad8d019eb6eda326d7796a8a0dd67b Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.0.7-tentative Ar