Re: Using writetime in CAS Lightweight transactions

2016-05-11 Thread Bhuvan Rawal 
Hi Tyler/Doan,

If we have already reached till the cell level and put the LWT condition on
it im sure from a design standpoint it shouldnt be really difficult to get
the cell write time and verify the same, maybe to be considered in a future
release. In this case it looks cleaner and if performance doesnt degrade
then im sure it can be used in multiple use cases. (fetch a row, do some
processing save it if its not been updated, if it has been updated then
repeat). In other words:  If updated time has not changed then do a write.

Best Regards,
Bhuvan

On Wed, May 11, 2016 at 9:32 PM, Tyler Hobbs  wrote:

> On Wed, May 11, 2016 at 10:22 AM, DuyHai Doan 
> wrote:
>
> > It is not (yet) possible to use functions in LWT predicates. LWT only
> > supports = and != plus IF (NOT) EXISTS right now
> >
>
> You're correct about functions not being supported, but we do actually
> support >, >=, <, <=, and IN operators (see
> https://issues.apache.org/jira/browse/CASSANDRA-6839).
>
> --
> Tyler Hobbs
> DataStax 
>

Re: [VOTE] Release Apache Cassandra 3.0.6

2016-05-11 Thread Josh McKenzie 
+1

On Tue, May 10, 2016 at 9:54 PM, Jake Luciani  wrote:

> I propose the following artifacts for release as 3.0.6.
>
> sha1: 52447873a361647a5e80c547adea9cf5ee85254a
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.6-tentative
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1110/org/apache/cassandra/apache-cassandra/3.0.6/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1110/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/IiNyVb (CHANGES.txt)
> [2]: http://goo.gl/ZAr03L (NEWS.txt)
> [3]: https://goo.gl/2jPtss (DataStax QA Report)
>

Re: [VOTE] Release Apache Cassandra 3.6

2016-05-11 Thread Josh McKenzie 
+1

On Tue, May 10, 2016 at 9:54 PM, Jake Luciani  wrote:

> I propose the following artifacts for release as 3.6.
>
> sha1: c17cbe1875a974a00822ffbfad716abde363c8da
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.6-tentative
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1112/org/apache/cassandra/apache-cassandra/3.6/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1112/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/Yv15Qz (CHANGES.txt)
> [2]: http://goo.gl/VyR9EG (NEWS.txt)
> [3]: https://goo.gl/raz8ok (DataStax QA Report)
>

Re: Using writetime in CAS Lightweight transactions

2016-05-11 Thread Tyler Hobbs 
On Wed, May 11, 2016 at 10:22 AM, DuyHai Doan  wrote:

> It is not (yet) possible to use functions in LWT predicates. LWT only
> supports = and != plus IF (NOT) EXISTS right now
>

You're correct about functions not being supported, but we do actually
support >, >=, <, <=, and IN operators (see
https://issues.apache.org/jira/browse/CASSANDRA-6839).

-- 
Tyler Hobbs
DataStax

Re: [VOTE] Release Apache Cassandra 3.0.6

2016-05-11 Thread Tyler Hobbs 
+1

On Tue, May 10, 2016 at 8:54 PM, Jake Luciani  wrote:

> I propose the following artifacts for release as 3.0.6.
>
> sha1: 52447873a361647a5e80c547adea9cf5ee85254a
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.6-tentative
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1110/org/apache/cassandra/apache-cassandra/3.0.6/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1110/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/IiNyVb (CHANGES.txt)
> [2]: http://goo.gl/ZAr03L (NEWS.txt)
> [3]: https://goo.gl/2jPtss (DataStax QA Report)
>



-- 
Tyler Hobbs
DataStax

Re: [VOTE] Release Apache Cassandra 3.6

2016-05-11 Thread Tyler Hobbs 
+1

On Tue, May 10, 2016 at 8:54 PM, Jake Luciani  wrote:

> I propose the following artifacts for release as 3.6.
>
> sha1: c17cbe1875a974a00822ffbfad716abde363c8da
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.6-tentative
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1112/org/apache/cassandra/apache-cassandra/3.6/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1112/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/Yv15Qz (CHANGES.txt)
> [2]: http://goo.gl/VyR9EG (NEWS.txt)
> [3]: https://goo.gl/raz8ok (DataStax QA Report)
>



-- 
Tyler Hobbs
DataStax

Re: Using writetime in CAS Lightweight transactions

2016-05-11 Thread DuyHai Doan 
It is not (yet) possible to use functions in LWT predicates. LWT only
supports = and != plus IF (NOT) EXISTS right now
Le 11 mai 2016 16:50, "Bhuvan Rawal"  a écrit :

> Hi,
>
> I was working on maintaining counters in cassandra, I read that it is not
> 100% accurate, I have tested them to be extremely accurate with 3.0.5 but
> going by docs there may be slight in accuracy.
>
> Thinking about this I thought there may be 2 approaches to resolve this:
> 1. Read the existing count and write the new count if table count is the
> count earlier fetched using LWT transaction.
> 2. Read the existing writetime(count) and write the new count if
> writetime(count) is the writetime count earlier fetched using lightweight
> transaction.-
>
> For me approach1 is working, but approach 2 doesnt. Please Find below the
> same:
>
> superuser@cqlsh:test_keyspace> CREATE TABLE test_keyspace.test (
> ... part_k int,
> ... clust_k text,
> ... count int,
> ... PRIMARY KEY (part_k, clust_k)
> ... );
> superuser@cqlsh:test_keyspace> insert into test(part_k , clust_k , count )
> values (2390, 'Test Ck Value', 007);
> superuser@cqlsh:test_keyspace> select * from test;
>
>  part_k | clust_k   | count
> +---+---
>2390 | Test Ck Value | 7
>
> superuser@cqlsh:test_keyspace> update test set count=8 where part_k=2390
> and clust_k='Test Ck Value' if count=7;
> # Works perfectly
>
> superuser@cqlsh:test_keyspace> select
> writetime(count),part_k,clust_k,count
> from test;
>
>  writetime(count) | part_k | clust_k   | count
> --++---+---
>  1462974475292000 |   2390 | Test Ck Value | 8
>
> # Now try to use the write time in LWT
> superuser@cqlsh:test_keyspace> update test set count=8 where part_k=2390
> and clust_k='Test Ck Value' if writetime(count)=1462974475292000;
> SyntaxException:  message="line 1:82 no viable alternative at input '(' (... and
> clust_k='Test Ck Value' if writetime[(]...)">
>
> Best Regards,
> Bhuvan Rawal
>

Using writetime in CAS Lightweight transactions

2016-05-11 Thread Bhuvan Rawal 
Hi,

I was working on maintaining counters in cassandra, I read that it is not
100% accurate, I have tested them to be extremely accurate with 3.0.5 but
going by docs there may be slight in accuracy.

Thinking about this I thought there may be 2 approaches to resolve this:
1. Read the existing count and write the new count if table count is the
count earlier fetched using LWT transaction.
2. Read the existing writetime(count) and write the new count if
writetime(count) is the writetime count earlier fetched using lightweight
transaction.-

For me approach1 is working, but approach 2 doesnt. Please Find below the
same:

superuser@cqlsh:test_keyspace> CREATE TABLE test_keyspace.test (
... part_k int,
... clust_k text,
... count int,
... PRIMARY KEY (part_k, clust_k)
... );
superuser@cqlsh:test_keyspace> insert into test(part_k , clust_k , count )
values (2390, 'Test Ck Value', 007);
superuser@cqlsh:test_keyspace> select * from test;

 part_k | clust_k   | count
+---+---
   2390 | Test Ck Value | 7

superuser@cqlsh:test_keyspace> update test set count=8 where part_k=2390
and clust_k='Test Ck Value' if count=7;
# Works perfectly

superuser@cqlsh:test_keyspace> select writetime(count),part_k,clust_k,count
from test;

 writetime(count) | part_k | clust_k   | count
--++---+---
 1462974475292000 |   2390 | Test Ck Value | 8

# Now try to use the write time in LWT
superuser@cqlsh:test_keyspace> update test set count=8 where part_k=2390
and clust_k='Test Ck Value' if writetime(count)=1462974475292000;
SyntaxException: 

Best Regards,
Bhuvan Rawal

Re: Cassandra 2.0.x OOM during startsup - schema version inconsistency after reboot

2016-05-11 Thread Alain RODRIGUEZ 
Hi Michaels :-),

My guess is this ticket will be closed with a "Won't Fix" resolution.

Cassandra 2.0 is no longer supported and I have seen tickets being rejected
like CASSANDRA-10510 
.

Would you like to upgrade to 2.1.last and see if you still have the issue?

About your issue, do you stop your node using a command like the following
one?

nodetool disablethrift && nodetool disablebinary && sleep 5 && nodetool
disablegossip && sleep 10 && nodetool drain && sleep 10 && sudo service
cassandra stop

or even flushing:

nodetool disablethrift && nodetool disablebinary && sleep 5 && nodetool
disablegossip && sleep 10 && nodetool flush && nodetool drain && sleep 10
&& sudo service cassandra stop

Are commitlogs empty when you start cassandra?

C*heers,

---
Alain Rodriguez - al...@thelastpickle.com
France

The Last Pickle - Apache Cassandra Consulting
http://www.thelastpickle.com

2016-05-11 5:35 GMT+02:00 Michael Fong :

> Hi,
>
> Thanks for your recommendation.
> I also opened a ticket to keep track @
> https://issues.apache.org/jira/browse/CASSANDRA-11748
> Hope this could brought someone's attention to take a look. Thanks.
>
> Sincerely,
>
> Michael Fong
>
> -Original Message-
> From: Michael Kjellman [mailto:mkjell...@internalcircle.com]
> Sent: Monday, May 09, 2016 11:57 AM
> To: dev@cassandra.apache.org
> Cc: u...@cassandra.apache.org
> Subject: Re: Cassandra 2.0.x OOM during startsup - schema version
> inconsistency after reboot
>
> I'd recommend you create a JIRA! That way you can get some traction on the
> issue. Obviously an OOM is never correct, even if your process is wrong in
> some way!
>
> Best,
> kjellman
>
> Sent from my iPhone
>
> > On May 8, 2016, at 8:48 PM, Michael Fong <
> michael.f...@ruckuswireless.com> wrote:
> >
> > Hi, all,
> >
> >
> > Haven't heard any responses so far, and this isue has troubled us for
> quite some time. Here is another update:
> >
> > We have noticed several times that The schema version may change after
> migration and reboot:
> >
> > Here is the scenario:
> >
> > 1.   Two node cluster (1 & 2).
> >
> > 2.   There are some schema changes, i.e. create a few new
> columnfamily. The cluster will wait until both nodes have schema version in
> sync (describe cluster) before moving on.
> >
> > 3.   Right before node2 is rebooted, the schema version is
> consistent; however, after ndoe2 reboots and starts servicing, the
> MigrationManager would gossip different schema version.
> >
> > 4.   Afterwards, both nodes starts exchanging schema  message
> indefinitely until one of the node dies.
> >
> > We currently suspect the change of schema is due to replying the old
> entry in commit log. We wish to continue dig further, but need experts help
> on this.
> >
> > I don't know if anyone has seen this before, or if there is anything
> wrong with our migration flow though..
> >
> > Thanks in advance.
> >
> > Best regards,
> >
> >
> > Michael Fong
> >
> > From: Michael Fong [mailto:michael.f...@ruckuswireless.com]
> > Sent: Thursday, April 21, 2016 6:41 PM
> > To: u...@cassandra.apache.org; dev@cassandra.apache.org
> > Subject: RE: Cassandra 2.0.x OOM during bootstrap
> >
> > Hi, all,
> >
> > Here is some more information on before the OOM happened on the rebooted
> node in a 2-node test cluster:
> >
> >
> > 1.   It seems the schema version has changed on the rebooted node
> after reboot, i.e.
> > Before reboot,
> > Node 1: DEBUG [MigrationStage:1] 2016-04-19 11:09:42,326
> > MigrationManager.java (line 328) Gossiping my schema version
> > 4cb463f8-5376-3baf-8e88-a5cc6a94f58f
> > Node 2: DEBUG [MigrationStage:1] 2016-04-19 11:09:42,122
> > MigrationManager.java (line 328) Gossiping my schema version
> > 4cb463f8-5376-3baf-8e88-a5cc6a94f58f
> >
> > After rebooting node 2,
> > Node 2: DEBUG [main] 2016-04-19 11:18:18,016 MigrationManager.java
> > (line 328) Gossiping my schema version
> > f5270873-ba1f-39c7-ab2e-a86db868b09b
> >
> >
> >
> > 2.   After reboot, both nods repeatedly send MigrationTask to each
> other - we suspect it is related to the schema version (Digest) mismatch
> after Node 2 rebooted:
> > The node2  keeps submitting the migration task over 100+ times to the
> other node.
> > INFO [GossipStage:1] 2016-04-19 11:18:18,261 Gossiper.java (line 1011)
> > Node /192.168.88.33 has restarted, now UP INFO [GossipStage:1]
> > 2016-04-19 11:18:18,262 TokenMetadata.java (line 414) Updating
> > topology for /192.168.88.33 INFO [GossipStage:1] 2016-04-19
> > 11:18:18,263 StorageService.java (line 1544) Node /192.168.88.33 state
> > jump to normal INFO [GossipStage:1] 2016-04-19 11:18:18,264
> > TokenMetadata.java (line 414) Updating topology for /192.168.88.33
> DEBUG [GossipStage:1] 2016-04-19 11:18:18,265 MigrationManager.java (line
> 102) Submitting migration task for /192.168.88.33 DEBUG [GossipStage:1]
> 2016-04-19 11:18:18,265 MigrationManager.java (line 102) Subm

Re: [VOTE] Release Apache Cassandra 3.0.6

2016-05-11 Thread Benjamin Lerer 
+1

On Wed, May 11, 2016 at 9:44 AM, Sylvain Lebresne 
wrote:

> +1
>
> On Wed, May 11, 2016 at 6:23 AM, Jonathan Ellis  wrote:
>
> > +1
> >
> > On Tue, May 10, 2016 at 8:54 PM, Jake Luciani  wrote:
> >
> > > I propose the following artifacts for release as 3.0.6.
> > >
> > > sha1: 52447873a361647a5e80c547adea9cf5ee85254a
> > > Git:
> > >
> > >
> >
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.6-tentative
> > > Artifacts:
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1110/org/apache/cassandra/apache-cassandra/3.0.6/
> > > Staging repository:
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1110/
> > >
> > > The artifacts as well as the debian package are also available here:
> > > http://people.apache.org/~jake
> > >
> > > The vote will be open for 72 hours (longer if needed).
> > >
> > > [1]: http://goo.gl/IiNyVb (CHANGES.txt)
> > > [2]: http://goo.gl/ZAr03L (NEWS.txt)
> > > [3]: https://goo.gl/2jPtss (DataStax QA Report)
> > >
> >
> >
> >
> > --
> > Jonathan Ellis
> > Project Chair, Apache Cassandra
> > co-founder, http://www.datastax.com
> > @spyced
> >
>

Re: [VOTE] Release Apache Cassandra 3.6

2016-05-11 Thread Benjamin Lerer 
+1

On Wed, May 11, 2016 at 11:15 AM, Sam Tunnicliffe  wrote:

> +1
>
> On Wed, May 11, 2016 at 9:51 AM, Aleksey Yeschenko 
> wrote:
>
> > +1
> >
> > --
> > AY
> >
> > On 11 May 2016 at 02:55:10, Jake Luciani (j...@apache.org) wrote:
> >
> > I propose the following artifacts for release as 3.6.
> >
> > sha1: c17cbe1875a974a00822ffbfad716abde363c8da
> > Git:
> >
> >
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.6-tentative
> > Artifacts:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1112/org/apache/cassandra/apache-cassandra/3.6/
> > Staging repository:
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1112/
> >
> > The artifacts as well as the debian package are also available here:
> > http://people.apache.org/~jake
> >
> > The vote will be open for 72 hours (longer if needed).
> >
> > [1]: http://goo.gl/Yv15Qz (CHANGES.txt)
> > [2]: http://goo.gl/VyR9EG (NEWS.txt)
> > [3]: https://goo.gl/raz8ok (DataStax QA Report)
> >
>

Re: [VOTE] Release Apache Cassandra 3.6

2016-05-11 Thread Sam Tunnicliffe 
+1

On Wed, May 11, 2016 at 9:51 AM, Aleksey Yeschenko 
wrote:

> +1
>
> --
> AY
>
> On 11 May 2016 at 02:55:10, Jake Luciani (j...@apache.org) wrote:
>
> I propose the following artifacts for release as 3.6.
>
> sha1: c17cbe1875a974a00822ffbfad716abde363c8da
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.6-tentative
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1112/org/apache/cassandra/apache-cassandra/3.6/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1112/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/Yv15Qz (CHANGES.txt)
> [2]: http://goo.gl/VyR9EG (NEWS.txt)
> [3]: https://goo.gl/raz8ok (DataStax QA Report)
>

Re: [VOTE] Release Apache Cassandra 3.0.6

2016-05-11 Thread Sam Tunnicliffe 
+1

On Wed, May 11, 2016 at 9:51 AM, Aleksey Yeschenko 
wrote:

> +1
>
> --
> AY
>
> On 11 May 2016 at 02:55:11, Jake Luciani (j...@apache.org) wrote:
>
> I propose the following artifacts for release as 3.0.6.
>
> sha1: 52447873a361647a5e80c547adea9cf5ee85254a
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.6-tentative
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1110/org/apache/cassandra/apache-cassandra/3.0.6/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1110/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/IiNyVb (CHANGES.txt)
> [2]: http://goo.gl/ZAr03L (NEWS.txt)
> [3]: https://goo.gl/2jPtss (DataStax QA Report)
>

Re: [VOTE] Release Apache Cassandra 3.0.6

2016-05-11 Thread Aleksey Yeschenko 
+1

-- 
AY

On 11 May 2016 at 02:55:11, Jake Luciani (j...@apache.org) wrote:

I propose the following artifacts for release as 3.0.6.  

sha1: 52447873a361647a5e80c547adea9cf5ee85254a  
Git:  
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.6-tentative
  
Artifacts:  
https://repository.apache.org/content/repositories/orgapachecassandra-1110/org/apache/cassandra/apache-cassandra/3.0.6/
  
Staging repository:  
https://repository.apache.org/content/repositories/orgapachecassandra-1110/  

The artifacts as well as the debian package are also available here:  
http://people.apache.org/~jake  

The vote will be open for 72 hours (longer if needed).  

[1]: http://goo.gl/IiNyVb (CHANGES.txt)  
[2]: http://goo.gl/ZAr03L (NEWS.txt)  
[3]: https://goo.gl/2jPtss (DataStax QA Report)

Re: [VOTE] Release Apache Cassandra 3.6

2016-05-11 Thread Aleksey Yeschenko 
+1

-- 
AY

On 11 May 2016 at 02:55:10, Jake Luciani (j...@apache.org) wrote:

I propose the following artifacts for release as 3.6.  

sha1: c17cbe1875a974a00822ffbfad716abde363c8da  
Git:  
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.6-tentative
  
Artifacts:  
https://repository.apache.org/content/repositories/orgapachecassandra-1112/org/apache/cassandra/apache-cassandra/3.6/
  
Staging repository:  
https://repository.apache.org/content/repositories/orgapachecassandra-1112/  

The artifacts as well as the debian package are also available here:  
http://people.apache.org/~jake  

The vote will be open for 72 hours (longer if needed).  

[1]: http://goo.gl/Yv15Qz (CHANGES.txt)  
[2]: http://goo.gl/VyR9EG (NEWS.txt)  
[3]: https://goo.gl/raz8ok (DataStax QA Report)

Re: [VOTE] Release Apache Cassandra 3.6

2016-05-11 Thread Sylvain Lebresne 
+1

On Wed, May 11, 2016 at 6:23 AM, Jonathan Ellis  wrote:

> +1
>
> On Tue, May 10, 2016 at 8:54 PM, Jake Luciani  wrote:
>
> > I propose the following artifacts for release as 3.6.
> >
> > sha1: c17cbe1875a974a00822ffbfad716abde363c8da
> > Git:
> >
> >
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.6-tentative
> > Artifacts:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1112/org/apache/cassandra/apache-cassandra/3.6/
> > Staging repository:
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1112/
> >
> > The artifacts as well as the debian package are also available here:
> > http://people.apache.org/~jake
> >
> > The vote will be open for 72 hours (longer if needed).
> >
> > [1]: http://goo.gl/Yv15Qz (CHANGES.txt)
> > [2]: http://goo.gl/VyR9EG (NEWS.txt)
> > [3]: https://goo.gl/raz8ok (DataStax QA Report)
> >
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder, http://www.datastax.com
> @spyced
>

Re: [VOTE] Release Apache Cassandra 3.0.6

2016-05-11 Thread Sylvain Lebresne 
+1

On Wed, May 11, 2016 at 6:23 AM, Jonathan Ellis  wrote:

> +1
>
> On Tue, May 10, 2016 at 8:54 PM, Jake Luciani  wrote:
>
> > I propose the following artifacts for release as 3.0.6.
> >
> > sha1: 52447873a361647a5e80c547adea9cf5ee85254a
> > Git:
> >
> >
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.6-tentative
> > Artifacts:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1110/org/apache/cassandra/apache-cassandra/3.0.6/
> > Staging repository:
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1110/
> >
> > The artifacts as well as the debian package are also available here:
> > http://people.apache.org/~jake
> >
> > The vote will be open for 72 hours (longer if needed).
> >
> > [1]: http://goo.gl/IiNyVb (CHANGES.txt)
> > [2]: http://goo.gl/ZAr03L (NEWS.txt)
> > [3]: https://goo.gl/2jPtss (DataStax QA Report)
> >
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder, http://www.datastax.com
> @spyced
>