Re: [VOTE] Release Apache Cassandra 1.1.8

+1 On Dec 17, 2012 8:57 AM, "Brandon Williams" wrote: > +1 > > On Mon, Dec 17, 2012 at 3:28 AM, Sylvain Lebresne > wrote: > > We've fixed a few annoying issue since 1.1.7 so I propose the following > > artifacts for release as 1.1.8. > > > > sha1: 4885bfccf1841def0c86b46302133cf2924d7acd > > Git

Re: [VOTE] Release Apache Cassandra 1.1.8

+1 On Mon, Dec 17, 2012 at 10:56 AM, Brandon Williams wrote: > +1 > > On Mon, Dec 17, 2012 at 3:28 AM, Sylvain Lebresne > wrote: >> We've fixed a few annoying issue since 1.1.7 so I propose the following >> artifacts for release as 1.1.8. >> >> sha1: 4885bfccf1841def0c86b46302133cf2924d7acd >>

Re: [VOTE] Release Apache Cassandra 1.1.8

+1 On Mon, Dec 17, 2012 at 3:28 AM, Sylvain Lebresne wrote: > We've fixed a few annoying issue since 1.1.7 so I propose the following > artifacts for release as 1.1.8. > > sha1: 4885bfccf1841def0c86b46302133cf2924d7acd > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=r

Re: Compund/Composite column names

Will do. --- Brian O'Neill Lead Architect, Software Development Health Market Science The Science of Better Results 2700 Horizon Drive € King of Prussia, PA € 19406 M: 215.588.6024 € @boneill42 € healthmarketscience.com This information transmitted in this

Re: Compund/Composite column names

You are confusing client-side and server-side validation. The server should validate thrift inserts against cql3 table to prevent egregiously malformed data, per the discussion on [1]. (Of course even on the server we're limited to "this bunch of bytes here could probably be an int" but that shou

Re: Compund/Composite column names

Feel free to open a ticket with steps to reproduce. We can certainly throw a more meaningful exception. On Mon, Dec 17, 2012 at 4:11 PM, Edward Capriolo wrote: > This was discussed in one of the tickets. The problem is that CQL3's sparse > tables is it has different metadata that has NOT been ad

Re: Compund/Composite column names

This was discussed in one of the tickets. The problem is that CQL3's sparse tables is it has different metadata that has NOT been added to thrift's CFMetaData. Thus thrift is unaware of exactly how to verify the insert. Originally it was made impossible for thrift to see a sparse table (but that r

Re: Compund/Composite column names

Looks like Thrift API is not working as expected? -Vivek From: Brian O'Neill To: dev@cassandra.apache.org Cc: Vivek Mishra Sent: Monday, December 17, 2012 8:12 PM Subject: Re: Compund/Composite column names FYI -- I'm still seeing this on 1.2-beta1. If

Re: Compund/Composite column names

FYI -- I'm still seeing this on 1.2-beta1. If you create a table via CQL, then insert into it (via Java API) with an incorrect number of components. The insert works, but select * from CQL results in a TSocket read error. I showed this in the webinar last week, just in case people ran into it.

Re: [VOTE] Release Apache Cassandra 1.1.8

+1 On Dec 17, 2012 3:28 AM, "Sylvain Lebresne" wrote: > We've fixed a few annoying issue since 1.1.7 so I propose the following > artifacts for release as 1.1.8. > > sha1: 4885bfccf1841def0c86b46302133cf2924d7acd > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/

Re: [VOTE] Release Apache Cassandra 1.1.8

+1 On Monday, December 17, 2012, Sylvain Lebresne wrote: > We've fixed a few annoying issue since 1.1.7 so I propose the following > artifacts for release as 1.1.8. > > sha1: 4885bfccf1841def0c86b46302133cf2924d7acd > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=re

[VOTE] Release Apache Cassandra 1.1.8

We've fixed a few annoying issue since 1.1.7 so I propose the following artifacts for release as 1.1.8. sha1: 4885bfccf1841def0c86b46302133cf2924d7acd Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.1.8-tentative Artifacts: https://repository.apache.org/content