subject:"\[GitHub\] cassandra pull request #\:"

[GitHub] cassandra pull request #89: fix typo in the clustering columns section

2017-03-24 Thread IDUnderCover

Github user IDUnderCover closed the pull request at:

https://github.com/apache/cassandra/pull/89


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #:

2017-03-21 Thread Baddaboo

Github user Baddaboo commented on the pull request:


https://github.com/apache/cassandra/commit/5b8b1ce26cd073a44ddf7c7a6750da409a343eba#commitcomment-21412404
  
Maybe @belliottsmith was just writing this printout in 
[Italian](https://translate.google.com/#eo/en/datata), referring to a 
Tinder-like dating server ð 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #97: Fix typo

2017-03-20 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/cassandra/pull/97


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #98: Fix cassandra 13246

2017-03-20 Thread MikkelTAndersen

Github user MikkelTAndersen closed the pull request at:

https://github.com/apache/cassandra/pull/98


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #100: clean up

2017-03-20 Thread aertoria

GitHub user aertoria opened a pull request:

https://github.com/apache/cassandra/pull/100

clean up



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/aertoria/cassandra trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/100.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #100


commit 5e2df663dc9d6cd2d4fdedc98dc43a51fe00206d
Author: aertoria 
Date:   2017-03-20T07:01:38Z

clean up




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #99: Fix typo: Pptions -> Options

2017-03-18 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/cassandra/pull/99


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #99: Fix typo: Pptions -> Options

2017-03-18 Thread Garciat

GitHub user Garciat opened a pull request:

https://github.com/apache/cassandra/pull/99

Fix typo: Pptions -> Options



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Garciat/cassandra patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/99.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #99


commit f37cefa9517ab99f37c52552f112661f62a618ff
Author: Gabriel Garcia 
Date:   2017-03-18T16:05:51Z

Fix typo: Pptions -> Options




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #98: Fix cassandra 13246

2017-03-13 Thread MikkelTAndersen

GitHub user MikkelTAndersen opened a pull request:

https://github.com/apache/cassandra/pull/98

Fix cassandra 13246

This should fix null pointer if the content of the column is null.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MikkelTAndersen/cassandra fix_CASSANDRA-13246

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/98.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #98


commit dac39d0268ba82b6be033e0c63ebd653ae0517cc
Author: Mikkel Andersen 
Date:   2017-03-13T09:21:27Z

added null check - see CASSANDRA-13246

commit 145087e3b5d748ce25e8792f91c249d2a05de3e5
Author: Mikkel Andersen 
Date:   2017-03-13T09:22:53Z

fixed formatting




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #96: Fix cqlsh automatic protocol downgrade regressio...

2017-03-08 Thread Jollyplum

GitHub user Jollyplum opened a pull request:

https://github.com/apache/cassandra/pull/96

Fix cqlsh automatic protocol downgrade regression CASSANDRA-13307

Patch by Matt Byrd for CASSANDRA-13307

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Jollyplum/cassandra 13307

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/96.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #96


commit b52b27810bf0d3bb9caafe21fde6120cf53c7382
Author: Matt Byrd 
Date:   2017-03-08T21:55:01Z

Fix cqlsh automatic protocol downgrade regression
Patch by Matt Byrd for CASSANDRA-13307




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #88: added encoding param to non-debug printmsg funct...

2017-03-01 Thread sparkida

Github user sparkida closed the pull request at:

https://github.com/apache/cassandra/pull/88


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #95: Expire messages by a single Thread

2017-03-01 Thread christian-esken

GitHub user christian-esken opened a pull request:

https://github.com/apache/cassandra/pull/95

Expire messages by a single Thread

When queue expiration is done, one single Thread is elected to do the
work. Previously, all Threads would go in and do the same work,
producing high lock contention. The Thread reading from the Queue could
even be starved by not be able to acquire the read lock. CASSANDRA-13265

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/christian-esken/cassandra 13265b-3.0

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/95.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #95


commit 448d7a9c1430d9f23bd819895fc618bb227ca833
Author: Christian Esken 
Date:   2017-03-01T14:56:36Z

Expire messages by a single Thread

When queue expiration is done, one single Thread is elected to do the
work. Previously, all Threads would go in and do the same work,
producing high lock contention. The Thread reading from the Queue could
even be starved by not be able to acquire the read lock. CASSANDRA-13265




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #94: CASSANDRA-10726: Read repair inserts should use ...

2017-02-17 Thread xiaolong302

GitHub user xiaolong302 opened a pull request:

https://github.com/apache/cassandra/pull/94

CASSANDRA-10726: Read repair inserts should use speculative retry

1. do an extra read repair retry to only guarantee âmonotonic quorum
readâ. Here âquorumâ means majority of nodes among replicas
2. only block what is needed for resolving the digest mismatch no
matter whether itâs speculative retry or read repair chance.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/xiaolong302/cassandra CASSANDRA-10726

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/94.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #94


commit a587c20e82ffc4aa7c4a3cb1468551b255fc7f71
Author: Xiaolong Jiang 
Date:   2017-01-17T05:31:06Z

Cass: CASSANDRA-10726: Read repair inserts should use speculative retry

1. do an extra read repair retry to only guarantee âmonotonic quorum
readâ. Here âquorumâ means majority of nodes among replicas
2. only block what is needed for resolving the digest mismatch no
matter whether itâs speculative retry or read repair chance.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #93: CASSANDRA-9384 bump version of jbcrypt to 0.4

2017-02-13 Thread dysmento

GitHub user dysmento opened a pull request:

https://github.com/apache/cassandra/pull/93

CASSANDRA-9384 bump version of jbcrypt to 0.4

org.mindrot:jbcrypt:0.4 just landed in Maven Central. Here's a version bump 
for Cassandra.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dysmento/cassandra trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/93.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #93






---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #92: Fix failing COPY ... TO STDOUT

2017-02-07 Thread salomvary

GitHub user salomvary opened a pull request:

https://github.com/apache/cassandra/pull/92

Fix failing COPY ... TO STDOUT

Fixes 
[CASSANDRA-12497](https://issues.apache.org/jira/browse/CASSANDRA-12497).

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/salomvary/cassandra fix-copy-to-stdout

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/92.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #92


commit 43b46a9cf2a4a190ce0e3b69b1b21ddf1a10
Author: MÃ¡rton SalomvÃ¡ry 
Date:   2017-02-07T14:15:34Z

Fix failing COPY ... TO STDOUT

Fixed CASSANDRA-12497




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #91: Fix broken SASI diagrams from PR #90

2017-01-27 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/cassandra/pull/91


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #91: Fix broken SASI diagrams from PR #90

2017-01-27 Thread joaquincasares

GitHub user joaquincasares opened a pull request:

https://github.com/apache/cassandra/pull/91

Fix broken SASI diagrams from PR #90

Addressing the regressions on #90.

I was modifying in Github's view and didn't realize the text was correct 
and Github's view does not use a monospaced font.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/joaquincasares/cassandra Fix-PR-90

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/91.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #91


commit 34cb35f001d9b9cb32e1116ca09bc5d9bb42f45f
Author: Joaquin Casares 
Date:   2017-01-28T00:24:12Z

Fix broken SASI diagrams from PR #90




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #85: sasi: AND optimizations

2016-12-28 Thread iksaif

Github user iksaif closed the pull request at:

https://github.com/apache/cassandra/pull/85


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #90: Update SASI.md

2016-12-22 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/cassandra/pull/90


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #90: Update SASI.md

2016-12-22 Thread joaquincasares

GitHub user joaquincasares opened a pull request:

https://github.com/apache/cassandra/pull/90

Update SASI.md

Minor grammatical fixes to improve readability.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/joaquincasares/cassandra patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/90.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #90


commit df33c3a426b8443a41af94463052e98a8f1a6589
Author: Joaquin Casares 
Date:   2016-12-23T02:02:43Z

Update SASI.md

Minor grammatical fixes to improve readability.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #89: fix typo in the clustering columns section

2016-12-21 Thread IDUnderCover

GitHub user IDUnderCover opened a pull request:

https://github.com/apache/cassandra/pull/89

fix typo in the clustering columns section

clustering column should be 'b' , not 'c' and 'd'

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/IDUnderCover/cassandra trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/89.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #89


commit 13315fef1fe968840176ad09f06010a1249b4702
Author: Razaura <469792...@qq.com>
Date:   2016-12-22T07:29:37Z

Update ddl.rst

clustering column should be 'b' , not 'c' and 'd'




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #59: CASSANDRA-10855: Use Caffeine for on-heap caches

2016-12-19 Thread ben-manes

Github user ben-manes closed the pull request at:

https://github.com/apache/cassandra/pull/59


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #88: added encoding param to non-debug printmsg funct...

2016-12-12 Thread sparkida

GitHub user sparkida opened a pull request:

https://github.com/apache/cassandra/pull/88

added encoding param to non-debug printmsg function

`cqlsh> copy test.image3d_impressions to STDOUT;`
Running this ^ without `--debug` produces:
`() got an unexpected keyword argument 'encoding'`

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sparkida/cassandra import-export-fix

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/88.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #88


commit c0a57ee2afaf4781ebc87b77249ad32617c37e64
Author: Nick Riley 
Date:   2016-12-13T01:09:54Z

added encoding to non-debug printmsg




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #87: 12979 fix check disk space

2016-12-07 Thread rustyrazorblade

Github user rustyrazorblade closed the pull request at:

https://github.com/apache/cassandra/pull/87


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #87: 12979 fix check disk space

2016-12-06 Thread rustyrazorblade

GitHub user rustyrazorblade opened a pull request:

https://github.com/apache/cassandra/pull/87

12979 fix check disk space



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rustyrazorblade/cassandra 
12979_fix_check_disk_space

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/87.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #87


commit 5bc53b2787e2e37eefd22a81e5ce57bdcd9229ba
Author: Jon Haddad 
Date:   2016-12-06T18:36:39Z

calculating disk space before checking if we have enough available.

commit d353858f60170bc102be1558afe83c9cb5fdeb59
Author: Jon Haddad 
Date:   2016-12-06T19:11:03Z

fixed extra newlines




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #86: pull

2016-11-24 Thread quemilk

GitHub user quemilk opened a pull request:

https://github.com/apache/cassandra/pull/86

pull

aa

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/quemilk/cassandra trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/86.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #86


commit 1a11d5239e3e26ff5e5110f9d4198a1bbe28a514
Author: Robert Stupp 
Date:   2015-04-29T16:53:30Z

Merge branch 'cassandra-2.1' into trunk

commit 1f3ab81099199457fb3bb8cea2ca29e2c136b412
Author: T Jake Luciani 
Date:   2015-04-29T18:30:14Z

Merge branch 'cassandra-2.1' into trunk

commit 33f37f86f64a570d63c7102b11ea455ff4a4806d
Author: Ariel Weisberg 
Date:   2015-04-29T19:14:08Z

Disable memory mapping of hsperfdata files for JVM statistics

Patch by Ariel Weisberg; reviewed by jmckenzie for CASSANDRA-9242

commit c57984216e3c962455895f4a6df83ac1a79c6486
Author: Brandon Williams 
Date:   2015-04-29T21:06:14Z

Merge branch 'cassandra-2.1' into trunk

commit cdfa9ed7e94aee9ff641152118fc1276d35299fe
Author: Ariel Weisberg 
Date:   2015-04-29T21:48:16Z

Merge branch 'cassandra-2.1' into trunk

commit 3c09adec72dbdc6d27479ca7f681ee2406e21e64
Author: Dave Brosius 
Date:   2015-04-30T02:24:52Z

don't mask(shadow) superclass fields

commit 16a7fcfb78556b23bf8b9b6dae5bb9a6756b83c9
Author: Dave Brosius 
Date:   2015-04-30T02:39:39Z

remove dead field

commit 01880a470c31c6c27bb82d73727623fe253eef9f
Author: Dave Brosius 
Date:   2015-04-30T03:25:24Z

simplify duplicate catch blocks

commit f85df37416db31c0b61acbeedfddbdedafc04634
Author: Marcus Eriksson 
Date:   2015-04-30T10:59:48Z

Merge branch 'cassandra-2.1' into trunk

commit 0656924fc5feb736f219fdf2dba2138a7a209dcd
Author: Marcus Eriksson 
Date:   2015-04-30T11:06:39Z

Merge branch 'cassandra-2.1' into trunk

commit 90476352a56568fc47418905dd31a16eb00a7981
Author: Aleksey Yeschenko 
Date:   2015-04-30T16:04:35Z

Merge branch 'cassandra-2.1' into trunk

commit 774bd0bc56abd97a122c563852210cf54bbc
Author: Josh McKenzie 
Date:   2015-04-30T16:13:23Z

Follow-up #2 for 9104. Fix SchemaLoader + EmbeddedCassandraServer recover 
case

Patch by jmckenzie; reviewed by branimir for CASSANDRA-9104

commit 3bfe4b6ae849add1c3388db3874bbdfd27443822
Author: T Jake Luciani 
Date:   2015-04-30T16:42:10Z

Merge branch 'cassandra-2.1' into trunk

commit 49b089893b5407ba42dad389804ff21d535a8537
Author: Tyler Hobbs 
Date:   2015-04-30T18:15:57Z

Merge branch 'cassandra-2.1' into trunk

commit 527c12a0115629ad0fa7ec95a24c55fc115739a1
Author: Benedict Elliott Smith 
Date:   2015-05-01T10:33:52Z

Merge branch 'cassandra-2.1' into trunk

commit 97d9a6b730eaf77c90dbe0b743b025a2f875f4f0
Author: Benedict Elliott Smith 
Date:   2015-05-01T10:38:42Z

Merge branch 'cassandra-2.1' into trunk

commit 184f5b3ad470862b6f624cd17d6f379cd2cb24fe
Author: Benedict Elliott Smith 
Date:   2015-05-01T12:59:03Z

revert CASSANDRA-9084

commit c799a98f0a454010cb3a63c874c404d1d2c79048
Author: Aleksey Yeschenko 
Date:   2015-05-01T16:21:04Z

Merge branch 'cassandra-2.1' into trunk

commit 6404e015ffe916fe24bacb3772b388e633af1261
Author: Aleksey Yeschenko 
Date:   2015-05-01T16:50:06Z

Merge branch 'cassandra-2.1' into trunk

commit d305ce42fc727c6251fc682fcc2168e410e33e99
Author: Yuki Morishita 
Date:   2015-05-01T19:49:01Z

Merge branch 'cassandra-2.1' into trunk

commit be6295edeec7dd78f5911f6dea02ce6544d0f6e7
Author: Yuki Morishita 
Date:   2015-05-01T20:59:59Z

Merge branch 'cassandra-2.1' into trunk

commit bbc796dfd092e01c8c42e1885819f6ba193260f9
Author: Yuki Morishita 
Date:   2015-05-01T21:56:37Z

Merge branch 'cassandra-2.1' into trunk

commit 00cd9b9fff711a678c37b1f93ecd8417f22c256e
Author: Jim Witschey 
Date:   2015-05-01T22:45:11Z

Add tests for cqlsh's CQL parser

Patch by Jim Witschey; reviewed by Tyler Hobbs for CASSANDRA-9248

commit 253ce00a64a59210b5a6bffc4999ce23921d73c5
Author: Dave Brosius 
Date:   2015-05-02T23:47:36Z

simplify throws clauses

commit 6f1e38cc2d037017b1fdfdca0fbcfc63f830577c
Author: Dave Brosius 
Date:   2015-05-03T01:02:40Z

move field to local

commit

[GitHub] cassandra pull request #85: sasi: AND optimizations

2016-11-22 Thread iksaif

GitHub user iksaif opened a pull request:

https://github.com/apache/cassandra/pull/85

sasi: AND optimizations

when op is AND:
- do not use indexes that return way more results that the others
- do not use more indexes if one of them returns no results
- try to use something smarter to get the primary index (which is
  important because it limits the searches done on other indexes)

Cosmetic changes such as changing logger.debug() to logger.trace() will be 
done later, I'd like a first opinion on the concept.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/iksaif/cassandra cassandra-3.X

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/85.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #85


commit bc54f7ae176e9314190c49d1780fb87e26b62728
Author: Corentin Chary 
Date:   2016-11-21T16:04:42Z

sasi: AND optimizations

when op is AND:
- do not use indexes that return way more results that the others
- do not use more indexes if one of them returns no results
- try to use something smarter to get the primary index (which is
  important because it limits the searches done on other indexes)




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #84: removed local bind for outbound connections

2016-11-15 Thread mmajercik

Github user mmajercik closed the pull request at:

https://github.com/apache/cassandra/pull/84


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #83: 12796 2.2

2016-11-10 Thread mmajercik

GitHub user mmajercik opened a pull request:

https://github.com/apache/cassandra/pull/83

12796 2.2

This is a proposed patch for CASSANDRA-12796

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mmajercik/cassandra 12796-2.2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/83.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #83


commit de57fc5ddc3fffdd6a1eed2dee53a638d5053fab
Author: mmajercik 
Date:   2016-10-14T13:54:02Z

Changed operation group granularity to page rathen than partition when 
rebuilding secondary index

commit f5d4f1cfb8dbaf550bb1685408279cd6935d3cbf
Author: mmajercik 
Date:   2016-11-10T08:22:24Z

replaced tabs with spaces




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #82: 12796 2.2

2016-11-10 Thread mmajercik

Github user mmajercik closed the pull request at:

https://github.com/apache/cassandra/pull/82


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #82: 12796 2.2

2016-11-10 Thread mmajercik

GitHub user mmajercik opened a pull request:

https://github.com/apache/cassandra/pull/82

12796 2.2

This is a proposed fix for CASSANDRA-12796

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mmajercik/cassandra 12796-2.2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/82.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #82


commit caaa9fc82cd51b7321da4dad0715ebc561d180dd
Author: Josh McKenzie 
Date:   2016-04-01T15:46:15Z

Merge branch 'cassandra-2.1' into cassandra-2.2

commit c662259fe9e1e25e10e58eb1146de80c53e69867
Author: Yuki Morishita 
Date:   2016-02-16T18:45:36Z

Use canonical path for directory in SSTable descriptor

patch by yukim; reviewed by Paulo Motta for CASSANDRA-10587

commit 0ac2072bb2cc6d8e069e07f5cbcdf2e83cdc5b5c
Author: Andrzej Ludwikowski 
Date:   2016-03-07T18:27:54Z

DatabaseDescriptor should log stacktrace in case of Eception during seed 
provider creation

patch by Andrzej Ludwikowski; reviewed by jasobrown for CASSANDRA-11312

commit ea9b42e7d7bf9003dd6ed911035d3a85a2d99bac
Author: Benjamin Lerer 
Date:   2016-04-02T15:55:04Z

Fix paging for COMPACT tables without clustering columns

patch by Benjamin Lerer; reviewed by Tyler Hobbs for CASSANDRA-11467

commit 2ed855592ab77399e061f03f73a943aefbd44eaf
Author: Benjamin Lerer 
Date:   2016-04-02T15:59:37Z

Merge branch cassandra-2.1 into cassandra-2.2

commit 1ff9df75c46edb02bf1f994e7ecc651e29b277fb
Author: Marcus Olsson 
Date:   2016-03-24T14:06:23Z

Remove duplicate logging of sending MerkleTree request

Patch by Marcus Olsson; reviewed by marcuse for CASSANDRA-11486

commit a33038be23e4114f5b6f0736887d35656b0aa40f
Author: Ryan Magnusson 
Date:   2016-04-04T12:09:54Z

IncomingStreamingConnection version check message wrong

patch by Ryan Magnusson reviewed by Robert Stupp for CASSANDRA-11462

commit 96c53e0a5e73046acb77e2ac2a3aa9d9ef64fc65
Author: Josh McKenzie 
Date:   2016-04-06T22:37:08Z

Fix launch with whitespace in path on Windows

Patch by jmckenzie; reviewed by pmotta for CASSANDRA-11515

commit 2dd244b439049baa1a9f175237acf802e1946d74
Author: Benjamin Lerer 
Date:   2016-04-11T07:41:44Z

Ninja: fix typo in CommitLog error message

commit e22faeb8c5463a34b630aff8e265aefbe950b58d
Author: Benjamin Lerer 
Date:   2016-04-11T07:43:56Z

Merge branch cassandra-2.1 into cassandra-2.2

commit 3557d2e05c8d1059562de2a91c1b33b4fcfcc6eb
Author: Paulo Motta 
Date:   2016-04-05T19:58:06Z

Make deprecated repair methods backward-compatible with previous 
notification service

patch by Paulo Motta; reviewed by Yuki Morishita for CASSANDRA-11430

commit c1b1d3bccf30a7ee1deb633d2bc2dfbd7b9c542f
Author: Stefania Alborghetti 
Date:   2016-04-08T03:52:17Z

Checking if an unlogged batch is local is inefficient

patch by Stefania Alborghetti; reviewed by Paulo Motta for CASSANDRA-11529

commit ab2b8a60c4b6d27081d632fefa0e19ee13816e2c
Author: Aleksey Yeschenko 
Date:   2016-04-11T18:14:41Z

Merge branch 'cassandra-2.1' into cassandra-2.2

commit 19b4b637ac79b5d53b9384bd95bed8e08b43f111
Author: Jacek Lewandowski 
Date:   2016-04-08T15:31:00Z

CqlConfigHelper no longer requires both a keystore and truststore to work.

patch by Jacek Lewandowski; reviewed by Jeremiah Jordan for CASSANDRA-11532

commit 69edeaa46b78bb168f7e9d0b1c991c07b90f41ca
Author: Alex Petrov 
Date:   2016-04-14T10:26:52Z

Allow only DISTINCT queries with partition keys restrictions

patch by Alex Petrov; reviewed by Benjamin Lerer for CASSANDRA-11339

commit 220e4f62db7fe14c4d6c0e499c52059f7ebc5a53
Author: T Jake Luciani 
Date:   2016-04-15T14:00:04Z

2.2.6 version bump

commit 5c5c5b44c6d952d4d6f8170fa4ef239060275b76
Author: T Jake Luciani 
Date:   2016-04-15T14:30:21Z

2.1.14 version bump

commit 37f63ecc5d3b36fc115fd7ae98e4fc1f4bc2d1d6
Author: T Jake Luciani 
Date:   2016-04-15T14:34:48Z

Merge branch 'cassandra-2.1' into cassandra-2.2

commit 77ab77328e7e263a8e93ff24ff9b5d4be33e7c27
Author: Artem Aliev 
Date:   2016-04-18T14:24:12Z

Always close cluster with connection in CqlRecordWriter

patch by Artem Aliev; reviewed by Aleksey Yeschenko for CASSANDRA-11553

commit d200d137823d5b250406bccb35473a8fc2f14faf
Author: Ruoran Wang

[GitHub] cassandra pull request #79: Correct Spelling Errors in JavaDoc for IEndPoint...

2016-11-07 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/cassandra/pull/79


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #79: Correct Spelling Errors in JavaDoc for IEndPoint...

2016-11-06 Thread michaelsembwever

Github user michaelsembwever commented on a diff in the pull request:

https://github.com/apache/cassandra/pull/79#discussion_r86710443
  
--- Diff: src/java/org/apache/cassandra/locator/IEndpointSnitch.java ---
@@ -30,12 +30,12 @@
 public interface IEndpointSnitch
 {
 /**
- * returns a String repesenting the rack this endpoint belongs to
+ * returns a String representing the rack this endpoint belongs to
  */
 public String getRack(InetAddress endpoint);
 
 /**
- * returns a String representing the datacenter this endpoint belongs 
to
+ * returns a String representing the data center this endpoint belongs 
to
--- End diff --

I don't think this is warranted.
 `datacenter` is the more popular term within the repository than `data 
center`

```
cassandra-git (trunk) $ find . -type f -exec grep -l "datacenter" {} \; | 
wc -l
98
cassandra-git (trunk) $ find . -type f -exec grep -l "data center" {} \; | 
wc -l
56
```



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #79: Correct Spelling Errors in JavaDoc for IEndPoint...

2016-11-06 Thread michaelsembwever

Github user michaelsembwever commented on a diff in the pull request:

https://github.com/apache/cassandra/pull/79#discussion_r86710377
  
--- Diff: src/java/org/apache/cassandra/locator/IEndpointSnitch.java ---
@@ -30,12 +30,12 @@
 public interface IEndpointSnitch
 {
 /**
- * returns a String repesenting the rack this endpoint belongs to
+ * returns a String representing the rack this endpoint belongs to
--- End diff --

Thanks for spotting and patching this!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #80: CASSANDRA-12869: Don't load mx4j beans twice

2016-11-03 Thread nastra

Github user nastra closed the pull request at:

https://github.com/apache/cassandra/pull/80


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #81: 12869 trunk

2016-11-03 Thread nastra

Github user nastra closed the pull request at:

https://github.com/apache/cassandra/pull/81


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #81: 12869 trunk

2016-11-02 Thread nastra

GitHub user nastra opened a pull request:

https://github.com/apache/cassandra/pull/81

12869 trunk



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nastra/cassandra 12869-trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/81.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #81


commit cb989c427e401eb2375aa9226551573ac3ff9a37
Author: Eduard Tudenhoefner 
Date:   2016-11-02T08:31:30Z

CASSANDRA-12869: Don't load mx4j beans twice

commit 12145583dc355f97524c5e271bb918be62652401
Author: Eduard Tudenhoefner 
Date:   2016-11-02T08:36:51Z

Merge branch '12869-3.X' into 12869-trunk




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #80: CASSANDRA-12869: Don't load mx4j beans twice

2016-11-02 Thread nastra

GitHub user nastra opened a pull request:

https://github.com/apache/cassandra/pull/80

CASSANDRA-12869: Don't load mx4j beans twice



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nastra/cassandra 12869-3.X

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/80.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #80


commit cb989c427e401eb2375aa9226551573ac3ff9a37
Author: Eduard Tudenhoefner 
Date:   2016-11-02T08:31:30Z

CASSANDRA-12869: Don't load mx4j beans twice




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #79: Correct Spelling Errors in JavaDoc for IEndPoint...

2016-10-28 Thread cmlicata

GitHub user cmlicata opened a pull request:

https://github.com/apache/cassandra/pull/79

Correct Spelling Errors in JavaDoc for IEndPointSnitch

Addresses issue 
[CASSANDRA-12855](https://issues.apache.org/jira/browse/CASSANDRA-12855).

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cmlicata/cassandra 12855-trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/79.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #79


commit fcc1df484d00ffad19b280f4cef9d07f2dd6b70d
Author: Christopher Licata (xle012) 
Date:   2016-10-28T13:02:23Z

correct JavaDoc in IEndPointSnitch




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #78: Fix flapping test in 2.0.17. Looks like an event...

2016-10-21 Thread earlye

Github user earlye closed the pull request at:

https://github.com/apache/cassandra/pull/78


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #78: Fix flapping test in 2.0.17. Looks like an event...

2016-10-21 Thread earlye

GitHub user earlye opened a pull request:

https://github.com/apache/cassandra/pull/78

Fix flapping test in 2.0.17. Looks like an eventual consistency issue.

Not the best fix - would prefer to have a way to have the test wait until 
it knows the 6 INSERTs ahead of checking the results had completed instead.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/keenlabs/cassandra 
earlye-fix-cass2.0.17-flapping-test

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/78.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #78


commit 88b77fe54cd895a8f15815dc4b813b2041acaaae
Author: Early Ehlinger 
Date:   2016-10-21T14:41:39Z

Fix flapping test in 2.0.17. Looks like an eventual consistency issue.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #77: Remove legacy docs

2016-10-19 Thread eprothro

Github user eprothro closed the pull request at:

https://github.com/apache/cassandra/pull/77


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #77: 12804 3.x

2016-10-19 Thread eprothro

GitHub user eprothro opened a pull request:

https://github.com/apache/cassandra/pull/77

12804 3.x



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/eprothro/cassandra 12804-3.X

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/77.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #77


commit 41c90d85fdb691639a7259f8510f1b2053f50d30
Author: Evan Prothro 
Date:   2016-10-19T18:25:12Z

Add clarity to process of building the docs

commit cedda54fdbe3c6e19498d2e2af75ce1de9a25167
Author: Evan Prothro 
Date:   2016-10-19T19:57:27Z

Remove legacy cql textile/html doc in favor of new sphinx docs




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #76: CASSANDRA-12541, CASSANDRA-12542, CASSANDRA-1254...

2016-10-19 Thread deshpamit

Github user deshpamit closed the pull request at:

https://github.com/apache/cassandra/pull/76


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #76: CASSANDRA-12541, CASSANDRA-12542, CASSANDRA-1254...

2016-10-15 Thread deshpamit

GitHub user deshpamit opened a pull request:

https://github.com/apache/cassandra/pull/76

CASSANDRA-12541, CASSANDRA-12542, CASSANDRA-12543 and CASSANDRA-12545



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/deshpamit/cassandra trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/76.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #76


commit cb47a3937bab99980d4fec481bfb2b163535a2f0
Author: Amit Deshpande 
Date:   2016-10-15T16:23:50Z

CASSANDRA-12541, CASSANDRA-12542, CASSANDRA-12543 and CASSANDRA-12545




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #75: Fix windows available ports checking

2016-10-02 Thread ptemplier

GitHub user ptemplier opened a pull request:

https://github.com/apache/cassandra/pull/75

Fix windows available ports checking

Check only for listening source TCP ports. Previous check was also checking 
for destination ports wrongly reporting the port as unavailable.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptemplier/cassandra patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/75.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #75


commit c26632cbc4f28a2851aceb2ea183171cef2f3b98
Author: Pierre Templier 
Date:   2016-10-02T08:08:34Z

Fix windows available ports checking

Check only for listening source TCP ports. Previous check was also checking 
for destination ports wrongly reporting the port as unavailable.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #74: fixed typo in select example

2016-09-27 Thread rustyrazorblade

GitHub user rustyrazorblade opened a pull request:

https://github.com/apache/cassandra/pull/74

fixed typo in select example



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rustyrazorblade/cassandra CASSANDRA-12718

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/74.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #74


commit 0f9386be94ca57d45b7b8532b753d11b078e14d7
Author: Jon Haddad 
Date:   2016-09-28T03:25:34Z

fixed typo in select example




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #73: Follow up commit 028f539eaa7f5ebcda42495145686dc...

2016-08-12 Thread YoshikiHigo

GitHub user YoshikiHigo opened a pull request:

https://github.com/apache/cassandra/pull/73

Follow up commit 028f539eaa7f5ebcda42495145686dc1fa40acd9

We replaced an if-statement and a return-statement with another 
return-statement with a ternary operator because the same change was conducted 
in a past commit.


https://github.com/apache/cassandra/commit/028f539eaa7f5ebcda42495145686dc1fa40acd9#diff-75ebe654dcf6c8c474f787abaf47bb68

Yoshiki, Shinpei, Hideaki, and Mei

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/YoshikiHigo/cassandra bugfix01

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/73.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #73


commit e57a601296912019859ac9853a78ba624af7
Author: Yoshiki Higo 
Date:   2016-08-12T10:49:55Z

Follow up commit 028f539eaa7f5ebcda42495145686dc1fa40acd9




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #72: 11182 trunk v2

2016-07-13 Thread ifesdjeen

Github user ifesdjeen closed the pull request at:

https://github.com/apache/cassandra/pull/72


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #71: Intruduce the fix for FixforCASSANDRA-11272

2016-06-20 Thread zhiyanshao

Github user zhiyanshao closed the pull request at:

https://github.com/apache/cassandra/pull/71


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #71: Intruduce the fix for FixforCASSANDRA-11272

2016-06-20 Thread zhiyanshao

GitHub user zhiyanshao opened a pull request:

https://github.com/apache/cassandra/pull/71

Intruduce the fix for FixforCASSANDRA-11272



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/zhiyanshao/cassandra 
2.2.5PlusFixforCASSANDRA-11272

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/71.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #71


commit 1151249919e2eece40d3c2b51f13cf8803b45498
Author: Zhiyan Shao 
Date:   2016-06-20T17:53:01Z

Intruduce the fix for FixforCASSANDRA-11272




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: adding bound variables of the parsed state...

2016-05-16 Thread mm-binary

GitHub user mm-binary opened a pull request:

https://github.com/apache/cassandra/pull/70

adding bound variables of the parsed statement to tracing output



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mm-binary/cassandra 11719-2.1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/70.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #70


commit f9d8e710db6fcb6827f747f69ba22186e272bbc3
Author: Mahdi Mohammadi 
Date:   2016-05-16T22:35:01Z

adding bound variables of the parsed statement to tracing output




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request:

2016-05-10 Thread nwparker

Github user nwparker commented on the pull request:


https://github.com/apache/cassandra/commit/cd4a1e6acc51b0f708127a50d37dd7832bbe8dfa#commitcomment-17428934
  
Thanks, I'll try to open one there once I have time !


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request:

2016-05-10 Thread jeffjirsa

Github user jeffjirsa commented on the pull request:


https://github.com/apache/cassandra/commit/cd4a1e6acc51b0f708127a50d37dd7832bbe8dfa#commitcomment-17412038
  
The project does not officially use Github to track bugs, issues or pull 
requests for Apache Cassandra. Genearlly, it's best to open a JIRA 
(https://issues.apache.org/jira/browse/CASSANDRA).



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request:

2016-05-10 Thread nwparker

Github user nwparker commented on the pull request:


https://github.com/apache/cassandra/commit/cd4a1e6acc51b0f708127a50d37dd7832bbe8dfa#commitcomment-17411980
  
Hey, this actually has a bug.

You forgot to remove the old "withPartitioner"

Best,


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request:

2016-05-10 Thread nwparker

Github user nwparker commented on the pull request:


https://github.com/apache/cassandra/commit/cd4a1e6acc51b0f708127a50d37dd7832bbe8dfa#commitcomment-17411978
  
In src/java/org/apache/cassandra/hadoop/cql3/CqlBulkRecordWriter.java:
In src/java/org/apache/cassandra/hadoop/cql3/CqlBulkRecordWriter.java on 
line 154:
Remove this


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request:

2016-05-04 Thread thobbs

Github user thobbs commented on the pull request:


https://github.com/apache/cassandra/commit/55f7a53e44b5d9af767464872b74a721717ba216#commitcomment-17355570
  
In src/java/org/apache/cassandra/cql3/Maps.java:
In src/java/org/apache/cassandra/cql3/Maps.java on line 470:
Same comment as above about slice deletions within collections


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request:

2016-05-04 Thread thobbs

Github user thobbs commented on the pull request:


https://github.com/apache/cassandra/commit/55f7a53e44b5d9af767464872b74a721717ba216#commitcomment-17355539
  
In src/java/org/apache/cassandra/cql3/Maps.java:
In src/java/org/apache/cassandra/cql3/Maps.java on line 399:
Setting on an arbitrary level shouldn't fundamentally require a read before 
write.  However, it occurred to me that in the 3.x storage format, we don't 
have a tombstone that can delete a slice of cells within a collection -- 
ComplexColumnDeletions can only cover a full column.  This may be something 
that we need to implement for good nested collection support, but would have to 
wait until 4.0 for the storage format change.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Setup travis ci

2016-04-30 Thread jasonstack

Github user jasonstack commented on the pull request:

https://github.com/apache/cassandra/pull/69#issuecomment-215976562
  
sorry.. wrong repo


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Setup travis ci

2016-04-30 Thread jasonstack

Github user jasonstack closed the pull request at:

https://github.com/apache/cassandra/pull/69


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Setup travis ci

2016-04-30 Thread jasonstack

GitHub user jasonstack opened a pull request:

https://github.com/apache/cassandra/pull/69

Setup travis ci



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jasonstack/cassandra setup-travis-ci

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/69.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #69


commit b4b4a535dc7923767014654f4ac974623d59533f
Author: jasonstack 
Date:   2015-03-06T10:48:36Z

Update and rename README.asc to README.md

commit 5f493ca3293f9ba3134f337fa4e71a2bd3d35150
Author: zhao_yang 
Date:   2015-03-06T10:51:13Z

Hello

commit 79f5b48dcaa9bff624c623fc2eb160a361e036c8
Author: jasonstack 
Date:   2015-03-31T03:08:28Z

Merge pull request #1 from apache/trunk

merge from origin

commit 5169a977d24e2a79aa0879bf22bacffe203db2f3
Author: jasonstack 
Date:   2015-03-06T10:48:36Z

Update and rename README.asc to README.md

commit 6a0ef1f8f40fe4f6b7a7c1f1d8b43f73c81fbac4
Author: zhao_yang 
Date:   2015-03-06T10:51:13Z

Hello

commit 28fa8c6924dd83783d461d129b08f5415f13ab49
Author: jasonstack 
Date:   2016-04-10T13:39:51Z

Merge branch 'trunk' of https://github.com/jasonstack/cassandra into trunk

commit 0ba6750d2b26f6eb2701090c4dbb6374852fe37d
Author: jasonstack 
Date:   2016-04-30T16:19:49Z

add travis ci




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: CASSANDRA-11683: Code refactor for Storage...

2016-04-29 Thread peoplehlj

Github user peoplehlj closed the pull request at:

https://github.com/apache/cassandra/pull/68


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: CASSANDRA-11683: Code refactor for Storage...

2016-04-29 Thread peoplehlj

Github user peoplehlj commented on the pull request:

https://github.com/apache/cassandra/pull/68#issuecomment-215919791
  
2.1 has reached end of development and only accepting critical bug fixes at 
this stage.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: CASSANDRA-11683: Code refactor for Storage...

2016-04-29 Thread peoplehlj

GitHub user peoplehlj opened a pull request:

https://github.com/apache/cassandra/pull/68

CASSANDRA-11683: Code refactor for StorageServiceMBean.forceRepair* methods

This patch is for https://issues.apache.org/jira/browse/CASSANDRA-11683 
For the class StorageServiceMBean, it has below methods, 

```
public int forceRepairAsync(String keyspace, boolean isSequential, 
Collection dataCenters, Collection hosts,  boolean 
primaryRange, boolean repairedAt, String... columnFamilies) throws IOException;

public int forceRepairRangeAsync(String beginToken, String endToken, String 
keyspaceName, boolean isSequential, Collection dataCenters, 
Collection hosts, boolean repairedAt, String... columnFamilies) throws 
IOException;

public int forceRepairRangeAsync(String beginToken, String endToken, String 
keyspaceName, boolean isSequential, boolean isLocal, boolean repairedAt, 
String... columnFamilies);
```

But in the implementation, the arguments are different from this MBean, 
please notice the last second argument, from *repairedAt* to *fullRepair*, and 
actually *fullRepair* is more clear for this API.

```
public int forceRepairAsync(String keyspace, boolean isSequential, 
Collection dataCenters, Collection hosts, boolean primaryRange, 
boolean fullRepair, String... columnFamilies) throws IOException{}

public int forceRepairRangeAsync(String beginToken, String endToken, String 
keyspaceName, boolean isSequential, Collection dataCenters, 
Collection hosts, boolean fullRepair, String... columnFamilies) throws 
IOException{}

public int forceRepairRangeAsync(String beginToken, String endToken, String 
keyspaceName, boolean isSequential, Collection dataCenters, 
Collection hosts, boolean fullRepair, String... columnFamilies) throws 
IOException{}
```

This will make developers confused, for example I met an issue that we 
didn't want to do a "full" repair but from the MBean I didn't know how to pass 
the argument.

Please help to merge it if we want to fix this issue, thanks in advance.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/peoplehlj/cassandra CASSANDRA-11683

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/68.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #68


commit 4c8b75bc664371c19e118f8497f9777831721084
Author: Huang, Lijun 
Date:   2016-04-29T09:11:17Z

CASSANDRA-11683: Code refactor for StorageServiceMBean.forceRepair* methods




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: fixed help text in sstabledump

2016-04-20 Thread rustyrazorblade

GitHub user rustyrazorblade opened a pull request:

https://github.com/apache/cassandra/pull/67

fixed help text in sstabledump



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rustyrazorblade/cassandra trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/67.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #67


commit d8174bdaee088735bc676fde91962a757703a925
Author: Jon Haddad 
Date:   2016-04-20T14:44:26Z

fixed help text in sstabledump




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request:

2016-04-12 Thread mambocab

Github user mambocab commented on the pull request:


https://github.com/apache/cassandra/commit/82179ffe3df89cbe5d5b7997a318d77e8727e5f1#commitcomment-17068346
  
In test/unit/org/apache/cassandra/cql3/CDCStatementTest.java:
In test/unit/org/apache/cassandra/cql3/CDCStatementTest.java on line 53:
These tests don't assert that the error is thrown, only that the message is 
correct if it's thrown.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Added TenantAwared Compaction Strategy wit...

2016-03-27 Thread jasonstack

Github user jasonstack closed the pull request at:

https://github.com/apache/cassandra/pull/66


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Fix bug for running on ppc64

2016-03-23 Thread mlpesant

Github user mlpesant commented on the pull request:

https://github.com/apache/cassandra/pull/65#issuecomment-200555378
  
Moved this request to JIRA   
https://issues.apache.org/jira/browse/THRIFT-3754


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Fix bug for running on ppc64

2016-03-23 Thread mlpesant

Github user mlpesant closed the pull request at:

https://github.com/apache/cassandra/pull/65


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Fix bug for running on ppc64

2016-03-23 Thread verma7

Github user verma7 commented on the pull request:

https://github.com/apache/cassandra/pull/65#issuecomment-200539241
  
Hi @mlpesant, please see the steps on how to contribute to Cassandra are 
available on the wiki (https://wiki.apache.org/cassandra/HowToContribute).

Notably, we don't use pull requests. It would be great if you could close 
your pull request on GitHub. Please create a new JIRA ticket and patch and 
somebody should be able to review and merge it.

Disclaimer: I am also new to the Cassandra dev community.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Change token validation of Murmur3Partitio...

2016-03-22 Thread verma7

Github user verma7 closed the pull request at:

https://github.com/apache/cassandra/pull/64


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Change token validation of Murmur3Partitio...

2016-03-22 Thread verma7

GitHub user verma7 opened a pull request:

https://github.com/apache/cassandra/pull/64

Change token validation of Murmur3Partitioner to display a helpful erâ¦

â¦ror message if the token is invalid

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/verma7/cassandra 9348-trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/64.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #64


commit 11c52b904bc284dd0738181ff9b208671f7f5522
Author: Abhishek Verma 
Date:   2016-03-22T21:18:28Z

Change token validation of Murmur3Partitioner to display a helpful error 
message if the token is invalid




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Cass: Implement ...

2016-03-11 Thread vkasar

Github user vkasar closed the pull request at:

https://github.com/apache/cassandra/pull/63


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Cass: Implement ...

2016-03-11 Thread jasobrown

Github user jasobrown commented on the pull request:

https://github.com/apache/cassandra/pull/63#issuecomment-195602892
  
I thought this was an internal repo, hence my comments. We don't accept PRs 
for the Apache Cassandra project, so please upload a patch to the JIRA ticket 
or add a link to your guthub branch in the ticket 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Cass: Implement ...

2016-03-11 Thread vkasar

Github user vkasar commented on the pull request:

https://github.com/apache/cassandra/pull/63#issuecomment-195597797
  
This is based on OSS c* trunk. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Cass: Implement ...

2016-03-11 Thread jasobrown

Github user jasobrown commented on the pull request:

https://github.com/apache/cassandra/pull/63#issuecomment-195596203
  
What version of c* are you targeting? Looks like you've based it on 
whatever our current trunk is. For the OSS c*, you are probably best targeting 
> 2.2, and the back port to our internal versions probably won't be too hard.

I have further questions, as well, but waiting on this first piece of info.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Cass: Implement ...

2016-03-11 Thread vkasar

GitHub user vkasar opened a pull request:

https://github.com/apache/cassandra/pull/63

 Cass: Implement compaction for a specific tâ¦

â¦oken range

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/vkasar/cassandra trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/63.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #63


commit ff4f668ba81fcc6cea3078dcc1310130209981ca
Author: Vishy Kasar 
Date:   2016-03-11T22:11:20Z

 Cass: Implement compaction for a specific token 
range




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: remove duplicated control for flush mesage...

2016-02-08 Thread jiafu1115

Github user jiafu1115 closed the pull request at:

https://github.com/apache/cassandra/pull/62


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request:

2016-02-05 Thread yukim

Github user yukim commented on the pull request:


https://github.com/apache/cassandra/commit/2384bfb026ef9fb6756a3100ae9653a52b68e43e#commitcomment-15924257
  
In src/java/org/apache/cassandra/io/sstable/SSTableSimpleIterator.java:
In src/java/org/apache/cassandra/io/sstable/SSTableSimpleIterator.java on 
line 117:
You can remove comments here



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Update lib/snappy-java-1.0.5.jar with snap...

2016-02-02 Thread iheanyi

Github user iheanyi closed the pull request at:

https://github.com/apache/cassandra/pull/37


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: remove duplicated control for flush mesage...

2016-01-26 Thread blerer

Github user blerer commented on the pull request:

https://github.com/apache/cassandra/pull/62#issuecomment-174888193
  
Hi,

This repository is just a mirror and does not accept pull requests.
Could you open a JIRA ticket and attach your patch to it?

Thanks


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: remove duplicated control for flush mesage...

2016-01-26 Thread jiafu1115

Github user jiafu1115 commented on the pull request:

https://github.com/apache/cassandra/pull/62#issuecomment-174888659
  
@blerer  I had request in 
https://issues.apache.org/jira/browse/CASSANDRA-11070, can you take a look? 3ks


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: remove duplicated control for flush mesage...

2016-01-26 Thread jiafu1115

Github user jiafu1115 commented on the pull request:

https://github.com/apache/cassandra/pull/62#issuecomment-175311128
  
 

![issue](https://cloud.githubusercontent.com/assets/5654180/12599801/c7464b3a-c4cf-11e5-8004-9e2957360cb7.jpg)

 
 




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: remove duplicated control for flush mesage...

2016-01-26 Thread jiafu1115

Github user jiafu1115 commented on the pull request:

https://github.com/apache/cassandra/pull/62#issuecomment-175313210
  

![issue](https://cloud.githubusercontent.com/assets/5654180/12599934/c8fc8060-c4d0-11e5-8d12-d4399dde8a2d.jpg)



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: remove duplicated control for flush mesage...

2016-01-26 Thread jiafu1115

Github user jiafu1115 commented on the pull request:

https://github.com/apache/cassandra/pull/62#issuecomment-175313381
  

![ss](https://cloud.githubusercontent.com/assets/5654180/12599960/ede28bcc-c4d0-11e5-9a2a-5ebd68ced78b.jpg)



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: remove duplicated control for flush mesage...

2016-01-25 Thread jiafu1115

GitHub user jiafu1115 opened a pull request:

https://github.com/apache/cassandra/pull/62

remove duplicated control for flush mesage control

Motivation:

the !doneWork's control is duplicated and confused with runsSinceFlush > 2

if on the first run:the queue size is 20
donework will be set to true and not do flush due to the size<50 and 
runsSinceFlush<2.

if on the second run. the queue size is 0,
donework will be reset to false and not set to true due to no new items in 
queue, but the flush will be triggered due to:
  if (!doneWork || runsSinceFlush > 2 || flushed.size() > 50)
now the runsSinceFlush is 2. so in actual, its function is similar with 
runsSinceFlush>1.
so it is no need to keep it so that the code is confused and duplicated.
  

Modifications:

remove it

Result:

after remove it, it will more clear and no confused.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jiafu1115/cassandra trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/62.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #62


commit 5279884e6a392d36b4adc5e29f9ca5d0666cb275
Author: fu.jian 
Date:   2016-01-26T01:20:05Z

remove duplicated control for flush mesage control

Motivation:

the !doneWork's control is duplicated and confused with runsSinceFlush > 2

if on the first run:the queue size is 20
donework will be set to true and not do flush due to the size<50 and 
runsSinceFlush<2.

if on the second run. the queue size is 0,
donework will be reset to false and not set to true due to no new items in 
queue, but the flush will be triggered due to:
  if (!doneWork || runsSinceFlush > 2 || flushed.size() > 50)
now the runsSinceFlush is 2. so in actual, its function is similar with 
runsSinceFlush>1.
so it is no need to keep it so that the code is confused and duplicated.
  

Modifications:

remove it

Result:

after remove it, it will more clear and no confused.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Added support for IBM zSystems architectur...

2016-01-20 Thread pauloricardomg

Github user pauloricardomg commented on the pull request:

https://github.com/apache/cassandra/pull/61#issuecomment-173235917
  
Cassandra project does not take pull requests via github, you must create 
an issue and submit a patch via 
https://issues.apache.org/jira/browse/cassandra/. Please see guidelines here: 
https://wiki.apache.org/cassandra/HowToContribute


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Added support for IBM zSystems architectur...

2016-01-20 Thread meerabo-IBM

GitHub user meerabo-IBM opened a pull request:

https://github.com/apache/cassandra/pull/61

Added support for IBM zSystems architecture (s390x)

Added support for IBM zSystems architecture (s390x). These code changes are 
required to make few test cases 'pass' for zSystems.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/linux-on-ibm-z/cassandra trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/61.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #61


commit ccdc0ce64cb492b354068053884cc471dcc44f41
Author: root 
Date:   2016-01-08T10:27:39Z

Unaligned memory acces is supported in s390 architecture,so added s390x 
architecture to the list of architectures supporting unaligned memory access




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: CASSANDRA-9556: Add newer data types to ca...

2015-12-16 Thread jasonstack

Github user jasonstack closed the pull request at:

https://github.com/apache/cassandra/pull/58


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: CASSANDRA-9556: Add newer data types to ca...

2015-12-16 Thread blerer

Github user blerer commented on the pull request:

https://github.com/apache/cassandra/pull/58#issuecomment-165125795
  
We cannot merge the PR because this repository is only a mirror from:  
git://git.apache.org/cassandra.git
I have committed your patch. Could you close your pull request?



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: CASSANDRA-9556: Add newer data types to ca...

2015-12-16 Thread mshuler

Github user mshuler commented on the pull request:

https://github.com/apache/cassandra/pull/58#issuecomment-165142570
  
The Cassandra JIRA is public, so for future reference, public patches 
posted to a public JIRA should probably suffice :)
http://wiki.apache.org/cassandra/HowToContribute


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: CASSANDRA-10855: Use Caffeine for on-heap ...

2015-12-13 Thread ben-manes

GitHub user ben-manes opened a pull request:

https://github.com/apache/cassandra/pull/59

CASSANDRA-10855: Use Caffeine for on-heap caches

[Caffeine](https://github.com/ben-manes/caffeine) is a Java 8 cache by the 
author of ConcurrentLinkedHashMap and Guava's cache, which is what was 
previously used. For the key and counter caches, the CLHM-based cache remains 
as a fallback if needed, but is deprecated and scheduled for removal.

CLHM and Guava uses the LRU policy due to its simplicity, decent hit rate, 
and known characteristics. Caffeine uses a near optimal policy, 
[W-TinyLFU](http://arxiv.org/pdf/1512.00727.pdf), which has a significantly 
[higher hit rate](https://github.com/ben-manes/caffeine/wiki/Efficiency). In 
particular the hit rate in the paper shows a substantial gain on database and 
search workloads.

The performance between CLHM and Caffeine caches should be similar, with 
some possible gains in write throughput. Significant gains may be observed from 
Guava, due to it never porting over some optimizations that improve read 
throughput and avoid creating garbage as a side effect.

For a brief overview, see this 
[article](https://www.voxxed.com/blog/2015/12/add-a-boost-of-caffeine-to-your-java).
 This pull request is being tracked in 
[CASSANDRA-10855](https://issues.apache.org/jira/browse/CASSANDRA-10855).

@jbellis @snazy 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ben-manes/cassandra caffeine

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/59.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #59


commit 3435a5a2b6eee30210350d5dfe1f76203d9d0f35
Author: Ben Manes 
Date:   2015-12-14T06:22:04Z

Use Caffeine for key and counter on-heap caches

Caffeine is a Java 8 cache by the author of ConcurrentLinkedHashMap,
which is what was previously used. That cache remains as a fallback
if needed, but is deprecated and scheduled for removal.

CLHM uses the LRU policy due to its simplicity, decent hit rate, and
known characteristics. Caffeine uses a near optimal policy, W-TinyLFU,
which has a significantly higher hit rate. In particular the hit rate
in the paper shows a substantial gain on database and search workloads.

The performance between the two caches should be similar, with some
possible gains in write throughput.

Caffeine: https://github.com/ben-manes/caffeine
W-TinyLFU: http://arxiv.org/pdf/1512.00727.pdf
Overview: 
https://www.voxxed.com/blog/2015/12/add-a-boost-of-caffeine-to-your-java

commit 91ac1fbf6e38704597befce9c280c516d61fb07a
Author: Ben Manes 
Date:   2015-12-14T06:44:17Z

Switch usage of Guava caches to Caffeine




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: CASSANDRA-9556: Add newer data types to ca...

2015-12-10 Thread jasonstack

GitHub user jasonstack opened a pull request:

https://github.com/apache/cassandra/pull/58

CASSANDRA-9556: Add newer data types to cassandra stress

eg. TinyInt, Time, Date, SmallInt
Protocol upgrades to NEWEST_SUPPORTED

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/WorksApplications/cassandra CASSANDRA-9556

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/58.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #58


commit 0de36aeb8ed0ed876eb55019464fda2f90a253dc
Author: Zhao Yang 
Date:   2015-12-09T06:42:19Z

CASSANDRA-9556: Add newer data types to cassandra stress (e.g. decimal, 
dates, UDTs)




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Tombstone max

2015-12-08 Thread jivemonkey

Github user jivemonkey closed the pull request at:

https://github.com/apache/cassandra/pull/57


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Tombstone max

2015-12-04 Thread jivemonkey

GitHub user jivemonkey opened a pull request:

https://github.com/apache/cassandra/pull/57

Tombstone max

Adding TSWC and the ability to give high tombstone ratio sstables 
compaction precedence @wulczer @relistan and @jfernandez

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/newrelic-forks/cassandra jking/tws_updates

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/57.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #57


commit 83cb68dc3458f11ac758c70f766eb08638d21bfd
Author: James King 
Date:   2015-12-04T23:57:34Z

Adding the ability to give high tombstone ratio sstages compaction precdence




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: CASSANDRA-10598:Let same index name can be...

2015-10-28 Thread allenyeh79

GitHub user allenyeh79 opened a pull request:

https://github.com/apache/cassandra/pull/56

CASSANDRA-10598:Let same index name can be used in different keyspaces

Let same index name can be used in different keyspaces.

JIRA link:
https://issues.apache.org/jira/browse/CASSANDRA-10598

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/bitus-dt/cassandra cassandra-1.2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/56.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #56


commit 85487ad55c253ac43d4980cf30b9cfeac256af0f
Author: allen.yeh 
Date:   2015-10-28T09:36:22Z

CASSANDRA-10598:The same index name can be used in different keyspaces
without conflict




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Fix typo in Java doc for pending compactio...

2015-10-12 Thread indigo423

GitHub user indigo423 opened a pull request:

https://github.com/apache/cassandra/pull/55

Fix typo in Java doc for pending compactions



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/indigo423/cassandra patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/55.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #55


commit 267aad35ba246b13cf5904f0a3113e1d6b86a457
Author: Ronny Trommer 
Date:   2015-10-12T08:37:47Z

Fix typo in Java doc for pending compactions




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Disable auto snapshot on selected tables (...

2015-09-28 Thread tommystendahl

GitHub user tommystendahl opened a pull request:

https://github.com/apache/cassandra/pull/54

Disable auto snapshot on selected tables (CASSANDRA-10383)



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tommystendahl/cassandra cassandra-10383

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/54.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #54


commit c647b57abedda8e2c578cc0bab14d79ca0722b71
Author: tommy stendahl 
Date:   2015-09-28T08:24:18Z

Disable auto snapshot on selected tables (CASSANDRA-10383)




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Disable auto snapshot on selected tables (...

2015-09-28 Thread tommystendahl

Github user tommystendahl closed the pull request at:

https://github.com/apache/cassandra/pull/54


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Cassandra 6246 trunk

2015-06-04 Thread bdeggleston

GitHub user bdeggleston opened a pull request:

https://github.com/apache/cassandra/pull/52

Cassandra 6246 trunk



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/bdeggleston/cassandra CASSANDRA-6246-trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/52.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #52


commit bd0b1cbf37d66f5fefb8cbc4b5acb7c3327b9e8e
Author: Blake Eggleston bdeggles...@gmail.com
Date:   2014-10-07T00:49:07Z

adding epaxos implementation

commit 27078ecd1087ba16882fca6d7396d8d5f1696b9e
Author: Blake Eggleston bdeggles...@gmail.com
Date:   2015-05-30T23:08:04Z

adding paxos - epaxos upgrade support




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: Cassandra 6246 trunk

2015-06-04 Thread bdeggleston

Github user bdeggleston closed the pull request at:

https://github.com/apache/cassandra/pull/52


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

1 2 >

1 - 100 of 124 matches

Mail list logo