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=refs/tags/1.1.8-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-037/org/apache/cassandra/apache-cassandra/1.1.8/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-037/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). [1]: http://goo.gl/vkaZt (CHANGES.txt) [2]: http://goo.gl/H3E61 (NEWS.txt)
Re: [VOTE] Release Apache Cassandra 1.1.8
+1 On Dec 17, 2012 3:28 AM, Sylvain Lebresne sylv...@datastax.com 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/tags/1.1.8-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-037/org/apache/cassandra/apache-cassandra/1.1.8/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-037/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). [1]: http://goo.gl/vkaZt (CHANGES.txt) [2]: http://goo.gl/H3E61 (NEWS.txt)
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. It would be great to translate the ArrayIndexOutofBoundsException
from the server side into something meaningful in cqlsh to help people
diagnose the problem. (a regular user probably doesn't have access to
the server-side logs)
You can see it at minute 41 in the video from the webinar:
http://www.youtube.com/watch?v=AdfugJxfd0ofeature=youtu.be
-brian
On Tue, Oct 9, 2012 at 9:39 AM, Jonathan Ellis jbel...@gmail.com wrote:
Sounds like you're running into the keyspace drop bug. It's mostly fixed
in 1.1.5 but you might need the latest from 1.1 branch. 1.1.6 will be
released soon with the final fix.
On Oct 9, 2012 1:58 AM, Vivek Mishra vivek.mis...@yahoo.com wrote:
Ok. I am able to understand the problem now. Issue is:
If i create a column family altercations as:
**8
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at,ships_destroyed)
);
/
INSERT INTO altercations (instigator, started_at, ships_destroyed,
energy_used, alliance_involvement)
VALUES ('Jayne Cobb', '2012-07-23', 2, 4.6, 'false');
*
It works!
But if i create a column family with compound primary key with 2 composite
column as:
*
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at)
);
*
and Then drop this column family:
*
drop columnfamily altercations;
*
and then try to create same one with primary compound key with 3 composite
column:
*
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at,ships_destroyed)
);
*
it gives me error: TSocket read 0 bytes
Rest, as no column family is created, so nothing onwards will work.
Is this an issue?
-Vivek
From: Jonathan Ellis jbel...@gmail.com
To: dev@cassandra.apache.org; Vivek Mishra vivek.mis...@yahoo.com
Sent: Tuesday, October 9, 2012 9:08 AM
Subject: Re: Compund/Composite column names
Works for me on latest 1.1 in cql3 mode. cql2 mode gives a parse error.
On Mon, Oct 8, 2012 at 9:18 PM, Vivek Mishra vivek.mis...@yahoo.com
wrote:
Hi All,
I am trying to use compound primary key column name and i am referring
to:
http://www.datastax.com/dev/blog/whats-new-in-cql-3-0
As mentioned on this example, i tried to create a column family
containing compound primary key (one or more) as:
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at,ships_destroyed)
);
And i am getting:
**
TSocket read 0 bytes
cqlsh:testcomp
**
Then followed by insert and select statements giving me following errors:
cqlsh:testcompINSERT INTO altercations (instigator, started_at,
ships_destroyed,
... energy_used,
alliance_involvement)
... VALUES ('Jayne Cobb', '2012-07-23',
2, 4.6, 'false');
TSocket read 0
Re: Compund/Composite column names
Looks like Thrift API is not working as expected?
-Vivek
From: Brian O'Neill b...@alumni.brown.edu
To: dev@cassandra.apache.org
Cc: Vivek Mishra vivek.mis...@yahoo.com
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 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. It would be great to translate the ArrayIndexOutofBoundsException
from the server side into something meaningful in cqlsh to help people
diagnose the problem. (a regular user probably doesn't have access to
the server-side logs)
You can see it at minute 41 in the video from the webinar:
http://www.youtube.com/watch?v=AdfugJxfd0ofeature=youtu.be
-brian
On Tue, Oct 9, 2012 at 9:39 AM, Jonathan Ellis jbel...@gmail.com wrote:
Sounds like you're running into the keyspace drop bug. It's mostly fixed
in 1.1.5 but you might need the latest from 1.1 branch. 1.1.6 will be
released soon with the final fix.
On Oct 9, 2012 1:58 AM, Vivek Mishra vivek.mis...@yahoo.com wrote:
Ok. I am able to understand the problem now. Issue is:
If i create a column family altercations as:
**8
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at,ships_destroyed)
);
/
INSERT INTO altercations (instigator, started_at, ships_destroyed,
energy_used, alliance_involvement)
VALUES ('Jayne Cobb', '2012-07-23', 2, 4.6, 'false');
*
It works!
But if i create a column family with compound primary key with 2 composite
column as:
*
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at)
);
*
and Then drop this column family:
*
drop columnfamily altercations;
*
and then try to create same one with primary compound key with 3 composite
column:
*
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at,ships_destroyed)
);
*
it gives me error: TSocket read 0 bytes
Rest, as no column family is created, so nothing onwards will work.
Is this an issue?
-Vivek
From: Jonathan Ellis jbel...@gmail.com
To: dev@cassandra.apache.org; Vivek Mishra vivek.mis...@yahoo.com
Sent: Tuesday, October 9, 2012 9:08 AM
Subject: Re: Compund/Composite column names
Works for me on latest 1.1 in cql3 mode. cql2 mode gives a parse error.
On Mon, Oct 8, 2012 at 9:18 PM, Vivek Mishra vivek.mis...@yahoo.com
wrote:
Hi All,
I am trying to use compound primary key column name and i am referring
to:
http://www.datastax.com/dev/blog/whats-new-in-cql-3-0
As mentioned on this example, i tried to create a column family
containing compound primary key (one or more) as:
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at,ships_destroyed)
);
And i am getting:
**
TSocket read 0 bytes
cqlsh:testcomp
**
Then followed by insert and select statements giving me following errors:
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 restriction has been lifted) it seems. It is probably a bad idea to
thrift insert into a sparse table until Cassandra does not have two
distinct sources of meta information.
On Mon, Dec 17, 2012 at 9:52 AM, Vivek Mishra vivek.mis...@yahoo.comwrote:
Looks like Thrift API is not working as expected?
-Vivek
From: Brian O'Neill b...@alumni.brown.edu
To: dev@cassandra.apache.org
Cc: Vivek Mishra vivek.mis...@yahoo.com
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 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. It would be great to translate the ArrayIndexOutofBoundsException
from the server side into something meaningful in cqlsh to help people
diagnose the problem. (a regular user probably doesn't have access to
the server-side logs)
You can see it at minute 41 in the video from the webinar:
http://www.youtube.com/watch?v=AdfugJxfd0ofeature=youtu.be
-brian
On Tue, Oct 9, 2012 at 9:39 AM, Jonathan Ellis jbel...@gmail.com wrote:
Sounds like you're running into the keyspace drop bug. It's mostly
fixed
in 1.1.5 but you might need the latest from 1.1 branch. 1.1.6 will be
released soon with the final fix.
On Oct 9, 2012 1:58 AM, Vivek Mishra vivek.mis...@yahoo.com wrote:
Ok. I am able to understand the problem now. Issue is:
If i create a column family altercations as:
**8
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at,ships_destroyed)
);
/
INSERT INTO altercations (instigator, started_at, ships_destroyed,
energy_used, alliance_involvement)
VALUES ('Jayne Cobb', '2012-07-23', 2, 4.6,
'false');
*
It works!
But if i create a column family with compound primary key with 2
composite
column as:
*
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at)
);
*
and Then drop this column family:
*
drop columnfamily altercations;
*
and then try to create same one with primary compound key with 3
composite
column:
*
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at,ships_destroyed)
);
*
it gives me error: TSocket read 0 bytes
Rest, as no column family is created, so nothing onwards will work.
Is this an issue?
-Vivek
From: Jonathan Ellis jbel...@gmail.com
To: dev@cassandra.apache.org; Vivek Mishra vivek.mis...@yahoo.com
Sent: Tuesday, October 9, 2012 9:08 AM
Subject: Re: Compund/Composite column names
Works for me on latest 1.1 in cql3 mode. cql2 mode gives a parse error.
On Mon, Oct 8, 2012 at 9:18 PM, Vivek Mishra vivek.mis...@yahoo.com
wrote:
Hi All,
I am trying to use compound primary key column name and i am referring
to:
http://www.datastax.com/dev/blog/whats-new-in-cql-3-0
As mentioned on this example, i tried to create a column family
containing compound primary key (one or more) as:
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 edlinuxg...@gmail.comwrote:
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 restriction has been lifted) it seems. It is probably a bad idea to
thrift insert into a sparse table until Cassandra does not have two
distinct sources of meta information.
On Mon, Dec 17, 2012 at 9:52 AM, Vivek Mishra vivek.mis...@yahoo.com
wrote:
Looks like Thrift API is not working as expected?
-Vivek
From: Brian O'Neill b...@alumni.brown.edu
To: dev@cassandra.apache.org
Cc: Vivek Mishra vivek.mis...@yahoo.com
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 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. It would be great to translate the ArrayIndexOutofBoundsException
from the server side into something meaningful in cqlsh to help people
diagnose the problem. (a regular user probably doesn't have access to
the server-side logs)
You can see it at minute 41 in the video from the webinar:
http://www.youtube.com/watch?v=AdfugJxfd0ofeature=youtu.be
-brian
On Tue, Oct 9, 2012 at 9:39 AM, Jonathan Ellis jbel...@gmail.com
wrote:
Sounds like you're running into the keyspace drop bug. It's mostly
fixed
in 1.1.5 but you might need the latest from 1.1 branch. 1.1.6 will be
released soon with the final fix.
On Oct 9, 2012 1:58 AM, Vivek Mishra vivek.mis...@yahoo.com wrote:
Ok. I am able to understand the problem now. Issue is:
If i create a column family altercations as:
**8
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at,ships_destroyed)
);
/
INSERT INTO altercations (instigator, started_at, ships_destroyed,
energy_used, alliance_involvement)
VALUES ('Jayne Cobb', '2012-07-23', 2, 4.6,
'false');
*
It works!
But if i create a column family with compound primary key with 2
composite
column as:
*
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at)
);
*
and Then drop this column family:
*
drop columnfamily altercations;
*
and then try to create same one with primary compound key with 3
composite
column:
*
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at,ships_destroyed)
);
*
it gives me error: TSocket read 0 bytes
Rest, as no column family is created, so nothing onwards will work.
Is this an issue?
-Vivek
From: Jonathan Ellis jbel...@gmail.com
To: dev@cassandra.apache.org; Vivek Mishra vivek.mis...@yahoo.com
Sent: Tuesday, October 9, 2012 9:08 AM
Subject: Re: Compund/Composite column names
Works for me on latest 1.1 in cql3 mode. cql2 mode gives a parse
error.
On Mon, Oct 8,
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 should be enough to prevent AIOBE.)
So if rc1 has validation problems, we should be able to fix that. (An
example with the cli would be easiest to address.)
[1]
https://issues.apache.org/jira/browse/CASSANDRA-4377?focusedCommentId=13446499page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13446499
On Mon, Dec 17, 2012 at 9:11 AM, Edward Capriolo edlinuxg...@gmail.com 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 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 restriction has been lifted) it seems. It is probably a bad idea to
thrift insert into a sparse table until Cassandra does not have two
distinct sources of meta information.
On Mon, Dec 17, 2012 at 9:52 AM, Vivek Mishra vivek.mis...@yahoo.comwrote:
Looks like Thrift API is not working as expected?
-Vivek
From: Brian O'Neill b...@alumni.brown.edu
To: dev@cassandra.apache.org
Cc: Vivek Mishra vivek.mis...@yahoo.com
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 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. It would be great to translate the ArrayIndexOutofBoundsException
from the server side into something meaningful in cqlsh to help people
diagnose the problem. (a regular user probably doesn't have access to
the server-side logs)
You can see it at minute 41 in the video from the webinar:
http://www.youtube.com/watch?v=AdfugJxfd0ofeature=youtu.be
-brian
On Tue, Oct 9, 2012 at 9:39 AM, Jonathan Ellis jbel...@gmail.com wrote:
Sounds like you're running into the keyspace drop bug. It's mostly
fixed
in 1.1.5 but you might need the latest from 1.1 branch. 1.1.6 will be
released soon with the final fix.
On Oct 9, 2012 1:58 AM, Vivek Mishra vivek.mis...@yahoo.com wrote:
Ok. I am able to understand the problem now. Issue is:
If i create a column family altercations as:
**8
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at,ships_destroyed)
);
/
INSERT INTO altercations (instigator, started_at, ships_destroyed,
energy_used, alliance_involvement)
VALUES ('Jayne Cobb', '2012-07-23', 2, 4.6,
'false');
*
It works!
But if i create a column family with compound primary key with 2
composite
column as:
*
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at)
);
*
and Then drop this column family:
*
drop columnfamily altercations;
*
and then try to create same one with primary compound key with 3
composite
column:
*
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at,ships_destroyed)
);
*
it gives me error: TSocket read 0 bytes
Rest, as no column family is created, so nothing onwards will
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 http://www.twitter.com/boneill42
healthmarketscience.com
This information transmitted in this email message is for the intended
recipient only and may contain confidential and/or privileged material. If
you received this email in error and are not the intended recipient, or the
person responsible to deliver it to the intended recipient, please contact
the sender at the email above and delete this email and any attachments and
destroy any copies thereof. Any review, retransmission, dissemination,
copying or other use of, or taking any action in reliance upon, this
information by persons or entities other than the intended recipient is
strictly prohibited.
From: Sylvain Lebresne sylv...@datastax.com
Date: Monday, December 17, 2012 10:35 AM
To: dev@cassandra.apache.org
Cc: Vivek Mishra vivek.mis...@yahoo.com, Brian O'Neill
b...@alumni.brown.edu
Subject: 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 edlinuxg...@gmail.com
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 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 restriction has been lifted) it seems. It is probably a bad idea to
thrift insert into a sparse table until Cassandra does not have two
distinct sources of meta information.
On Mon, Dec 17, 2012 at 9:52 AM, Vivek Mishra vivek.mis...@yahoo.comwrote:
Looks like Thrift API is not working as expected?
-Vivek
From: Brian O'Neill b...@alumni.brown.edu
To: dev@cassandra.apache.org
Cc: Vivek Mishra vivek.mis...@yahoo.com
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 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. It would be great to translate the ArrayIndexOutofBoundsException
from the server side into something meaningful in cqlsh to help people
diagnose the problem. (a regular user probably doesn't have access to
the server-side logs)
You can see it at minute 41 in the video from the webinar:
http://www.youtube.com/watch?v=AdfugJxfd0ofeature=youtu.be
-brian
On Tue, Oct 9, 2012 at 9:39 AM, Jonathan Ellis jbel...@gmail.com wrote:
Sounds like you're running into the keyspace drop bug. It's mostly
fixed
in 1.1.5 but you might need the latest from 1.1 branch. 1.1.6 will be
released soon with the final fix.
On Oct 9, 2012 1:58 AM, Vivek Mishra vivek.mis...@yahoo.com wrote:
Ok. I am able to understand the problem now. Issue is:
If i create a column family altercations as:
*
*8
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at,ships_destroyed)
);
/
INSERT INTO altercations (instigator, started_at, ships_destroyed,
energy_used, alliance_involvement)
VALUES ('Jayne Cobb', '2012-07-23', 2, 4.6,
'false');
*
It works!
But if i create a column family with compound primary key with 2
composite
column as:
*
CREATE TABLE altercations (
instigator text,
started_at timestamp,
ships_destroyed int,
energy_used float,
alliance_involvement boolean,
PRIMARY KEY (instigator,started_at)
);
*
and Then drop this column family:
*
drop columnfamily altercations;
*
Re: [VOTE] Release Apache Cassandra 1.1.8
+1 On Mon, Dec 17, 2012 at 3:28 AM, Sylvain Lebresne sylv...@datastax.com 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/tags/1.1.8-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-037/org/apache/cassandra/apache-cassandra/1.1.8/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-037/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). [1]: http://goo.gl/vkaZt (CHANGES.txt) [2]: http://goo.gl/H3E61 (NEWS.txt)
Re: [VOTE] Release Apache Cassandra 1.1.8
+1 On Dec 17, 2012 8:57 AM, Brandon Williams dri...@gmail.com wrote: +1 On Mon, Dec 17, 2012 at 3:28 AM, Sylvain Lebresne sylv...@datastax.com 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/tags/1.1.8-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-037/org/apache/cassandra/apache-cassandra/1.1.8/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-037/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). [1]: http://goo.gl/vkaZt (CHANGES.txt) [2]: http://goo.gl/H3E61 (NEWS.txt)
