[1/3] cassandra git commit: Remove old driver version from merge of CASSANDRA-12847

Repository: cassandra Updated Branches: refs/heads/cassandra-3.11 c0941cf78 -> 28f8fcb04 refs/heads/trunk 36b63ef51 -> 66e5cc0d1 Remove old driver version from merge of CASSANDRA-12847 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[3/3] cassandra git commit: Merge branch 'cassandra-3.11' into trunk

Merge branch 'cassandra-3.11' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/66e5cc0d Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/66e5cc0d Diff:

[2/3] cassandra git commit: Remove old driver version from merge of CASSANDRA-12847

Remove old driver version from merge of CASSANDRA-12847 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/28f8fcb0 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/28f8fcb0 Diff:

[jira] [Commented] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted

[ https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007507#comment-16007507 ] Paulo Motta commented on CASSANDRA-10130: - Good call [~sbtourist]! I thought setting the

[jira] [Commented] (CASSANDRA-13526) nodetool cleanup on KS with no replicas should remove old data, not silently complete

[ https://issues.apache.org/jira/browse/CASSANDRA-13526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007319#comment-16007319 ] Jai Bheemsen Rao Dhanwada commented on CASSANDRA-13526: --- The issue I am seeing

[jira] [Updated] (CASSANDRA-13518) sstableloader doesn't support non default storage_port and ssl_storage_port.

[ https://issues.apache.org/jira/browse/CASSANDRA-13518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuki Morishita updated CASSANDRA-13518: --- Status: Ready to Commit (was: Patch Available) > sstableloader doesn't support

[jira] [Commented] (CASSANDRA-13518) sstableloader doesn't support non default storage_port and ssl_storage_port.

[ https://issues.apache.org/jira/browse/CASSANDRA-13518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007356#comment-16007356 ] Yuki Morishita commented on CASSANDRA-13518: Thanks for the patch! Patch looks good to

[jira] [Commented] (CASSANDRA-13478) SASIndex has a time to live issue in Cassandra

[ https://issues.apache.org/jira/browse/CASSANDRA-13478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007666#comment-16007666 ] jack chen commented on CASSANDRA-13478: --- When I insert a large amount of data, i use

[jira] [Updated] (CASSANDRA-13218) Duration validation error is unclear in case of overflow.

[ https://issues.apache.org/jira/browse/CASSANDRA-13218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-13218: --- Fix Version/s: (was: 3.11.x) 4.0 3.11.0

[jira] [Updated] (CASSANDRA-13218) Duration validation error is unclear in case of overflow.

[ https://issues.apache.org/jira/browse/CASSANDRA-13218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-13218: --- Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed

[jira] [Commented] (CASSANDRA-12996) update slf4j dependency to 1.7.21

[ https://issues.apache.org/jira/browse/CASSANDRA-12996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006036#comment-16006036 ] Stefan Podkowinski commented on CASSANDRA-12996: If having Cassandra as "close as

[jira] [Created] (CASSANDRA-13522) AbstractTracingAwareExecutorService - Uncaught exception on thread - leads to JVM exit

Matthew O'Riordan created CASSANDRA-13522: - Summary: AbstractTracingAwareExecutorService - Uncaught exception on thread - leads to JVM exit Key: CASSANDRA-13522 URL:

[jira] [Commented] (CASSANDRA-12996) update slf4j dependency to 1.7.21

[ https://issues.apache.org/jira/browse/CASSANDRA-12996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006064#comment-16006064 ] Tomas Repik commented on CASSANDRA-12996: - Let's assume we've integrated your official RPM

[3/3] cassandra git commit: Merge branch cassandra-3.11 into trunk

Merge branch cassandra-3.11 into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/6deafff5 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/6deafff5 Diff:

[jira] [Created] (CASSANDRA-13523) StreamReceiveTask: java.lang.OutOfMemoryError: Map failed

Matthew O'Riordan created CASSANDRA-13523: - Summary: StreamReceiveTask: java.lang.OutOfMemoryError: Map failed Key: CASSANDRA-13523 URL: https://issues.apache.org/jira/browse/CASSANDRA-13523

[jira] [Updated] (CASSANDRA-13522) AbstractTracingAwareExecutorService - Uncaught exception on thread - leads to JVM exit

[ https://issues.apache.org/jira/browse/CASSANDRA-13522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew O'Riordan updated CASSANDRA-13522: -- Description: Initially saw the following exception numerous times: {code}

[jira] [Created] (CASSANDRA-13524) cassandra core connector - Guava incompatibility: Detected incompatible version of Guava in the classpath. You need 16.0.1 or higher

Michael Hornung created CASSANDRA-13524: --- Summary: cassandra core connector - Guava incompatibility: Detected incompatible version of Guava in the classpath. You need 16.0.1 or higher Key: CASSANDRA-13524

[jira] [Commented] (CASSANDRA-13218) Duration validation error is unclear in case of overflow.

[ https://issues.apache.org/jira/browse/CASSANDRA-13218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006103#comment-16006103 ] Benjamin Lerer commented on CASSANDRA-13218: Thanks for the review. > Duration

[1/3] cassandra git commit: Fix duration type validation to prevent overflow

Repository: cassandra Updated Branches: refs/heads/cassandra-3.11 f33cdcb8a -> 869335710 refs/heads/trunk 122bf06e4 -> 6deafff5a Fix duration type validation to prevent overflow patch by Benjamin Lerer; reviewed by Andrés de la Peña for CASSANDRA-13218 Project:

[2/3] cassandra git commit: Fix duration type validation to prevent overflow

Fix duration type validation to prevent overflow patch by Benjamin Lerer; reviewed by Andrés de la Peña for CASSANDRA-13218 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/86933571 Tree:

[jira] [Commented] (CASSANDRA-13525) ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade

[ https://issues.apache.org/jira/browse/CASSANDRA-13525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006512#comment-16006512 ] Sam Tunnicliffe commented on CASSANDRA-13525: - Fixed the 3.0 -> 3.11 merge issue, so both

[jira] [Commented] (CASSANDRA-13426) Make all DDL statements idempotent and not dependent on global state

[ https://issues.apache.org/jira/browse/CASSANDRA-13426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006594#comment-16006594 ] Aleksey Yeschenko commented on CASSANDRA-13426: --- Pushed WIP branch

[jira] [Comment Edited] (CASSANDRA-13441) Schema version changes for each upgraded node in a rolling upgrade, causing migration storms

[ https://issues.apache.org/jira/browse/CASSANDRA-13441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006613#comment-16006613 ] Julius Žaromskis edited comment on CASSANDRA-13441 at 5/11/17 3:22 PM:

[jira] [Comment Edited] (CASSANDRA-13441) Schema version changes for each upgraded node in a rolling upgrade, causing migration storms

[ https://issues.apache.org/jira/browse/CASSANDRA-13441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006613#comment-16006613 ] Julius Žaromskis edited comment on CASSANDRA-13441 at 5/11/17 3:22 PM:

[5/5] cassandra git commit: Merge branch 'cassandra-3.11' into trunk

Merge branch 'cassandra-3.11' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/c43371bf Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/c43371bf Diff:

[2/5] cassandra git commit: Fix 2ndary indexes on primary key columns to don't create expiring entries (CASSANDRA-13412)

Fix 2ndary indexes on primary key columns to don't create expiring entries (CASSANDRA-13412) Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/263740da Tree:

[3/5] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.11

Merge branch 'cassandra-3.0' into cassandra-3.11 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/3a064332 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/3a064332 Diff:

[4/5] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.11

Merge branch 'cassandra-3.0' into cassandra-3.11 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/3a064332 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/3a064332 Diff:

[1/5] cassandra git commit: Fix 2ndary indexes on primary key columns to don't create expiring entries (CASSANDRA-13412)

Repository: cassandra Updated Branches: refs/heads/cassandra-3.11 869335710 -> 3a0643329 refs/heads/trunk 6deafff5a -> c43371bf8 Fix 2ndary indexes on primary key columns to don't create expiring entries (CASSANDRA-13412) Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo

[jira] [Commented] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted

[ https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006528#comment-16006528 ] Paulo Motta commented on CASSANDRA-10130: - The approach looks mostly good, great job! I was

[jira] [Updated] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted

[ https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paulo Motta updated CASSANDRA-10130: Status: Open (was: Patch Available) > Node failure during 2i update after streaming

[jira] [Comment Edited] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted

[ https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006528#comment-16006528 ] Paulo Motta edited comment on CASSANDRA-10130 at 5/11/17 2:44 PM: --

[jira] [Commented] (CASSANDRA-13523) StreamReceiveTask: java.lang.OutOfMemoryError: Map failed

[ https://issues.apache.org/jira/browse/CASSANDRA-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006620#comment-16006620 ] Chris Lohfink commented on CASSANDRA-13523: --- This isnt really a bug so much as an

[jira] [Commented] (CASSANDRA-13441) Schema version changes for each upgraded node in a rolling upgrade, causing migration storms

[ https://issues.apache.org/jira/browse/CASSANDRA-13441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006613#comment-16006613 ] Julius Žaromskis commented on CASSANDRA-13441: -- Hi, any workaround for this issue? I've

[jira] [Comment Edited] (CASSANDRA-13441) Schema version changes for each upgraded node in a rolling upgrade, causing migration storms

[ https://issues.apache.org/jira/browse/CASSANDRA-13441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006613#comment-16006613 ] Julius Žaromskis edited comment on CASSANDRA-13441 at 5/11/17 3:24 PM:

[jira] [Commented] (CASSANDRA-8272) 2ndary indexes can return stale data

[ https://issues.apache.org/jira/browse/CASSANDRA-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006545#comment-16006545 ] Sergio Bossa commented on CASSANDRA-8272: - bq. my main point is that on principle we should be

[jira] [Commented] (CASSANDRA-13523) StreamReceiveTask: java.lang.OutOfMemoryError: Map failed

[ https://issues.apache.org/jira/browse/CASSANDRA-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006236#comment-16006236 ] Matthew O'Riordan commented on CASSANDRA-13523: --- Note: rerunning the same repair caused

[jira] [Commented] (CASSANDRA-8272) 2ndary indexes can return stale data

[ https://issues.apache.org/jira/browse/CASSANDRA-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006428#comment-16006428 ] Sylvain Lebresne commented on CASSANDRA-8272: - bq. 1) Stick with the current approach!

[jira] [Assigned] (CASSANDRA-13507) dtest failure in paging_test.TestPagingWithDeletions.test_ttl_deletions

[ https://issues.apache.org/jira/browse/CASSANDRA-13507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Brown reassigned CASSANDRA-13507: --- Assignee: Jason Brown > dtest failure in

[jira] [Commented] (CASSANDRA-13516) Message error for Duration types is confusing

[ https://issues.apache.org/jira/browse/CASSANDRA-13516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006796#comment-16006796 ] Jaume M commented on CASSANDRA-13516: - Looks like this is a duplicate of CASSANDRA-13218. Closing

[jira] [Resolved] (CASSANDRA-13516) Message error for Duration types is confusing

[ https://issues.apache.org/jira/browse/CASSANDRA-13516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaume M resolved CASSANDRA-13516. - Resolution: Duplicate > Message error for Duration types is confusing >

[jira] [Commented] (CASSANDRA-13523) StreamReceiveTask: java.lang.OutOfMemoryError: Map failed

[ https://issues.apache.org/jira/browse/CASSANDRA-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006700#comment-16006700 ] Matthew O'Riordan commented on CASSANDRA-13523: --- > Should check your limits ({{ulimit

[jira] [Commented] (CASSANDRA-13441) Schema version changes for each upgraded node in a rolling upgrade, causing migration storms

[ https://issues.apache.org/jira/browse/CASSANDRA-13441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006733#comment-16006733 ] Julius Žaromskis commented on CASSANDRA-13441: -- Here's a apiece of debug log, maybe this

[jira] [Commented] (CASSANDRA-10726) Read repair inserts should not be blocking

[ https://issues.apache.org/jira/browse/CASSANDRA-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006701#comment-16006701 ] Xiaolong Jiang commented on CASSANDRA-10726: regarding the response snapshot count:

[jira] [Commented] (CASSANDRA-10726) Read repair inserts should not be blocking

[ https://issues.apache.org/jira/browse/CASSANDRA-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006704#comment-16006704 ] Xiaolong Jiang commented on CASSANDRA-10726: regarding distinctHostNum: /** *

[jira] [Commented] (CASSANDRA-13441) Schema version changes for each upgraded node in a rolling upgrade, causing migration storms

[ https://issues.apache.org/jira/browse/CASSANDRA-13441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006683#comment-16006683 ] Jeff Jirsa commented on CASSANDRA-13441: Hi [~juliuszaromskis] - if you're upgrading from

[jira] [Assigned] (CASSANDRA-13517) dtest failure in paxos_tests.TestPaxos.contention_test_many_threads

[ https://issues.apache.org/jira/browse/CASSANDRA-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Brown reassigned CASSANDRA-13517: --- Assignee: Jason Brown > dtest failure in

[jira] [Updated] (CASSANDRA-13525) ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade

[ https://issues.apache.org/jira/browse/CASSANDRA-13525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-13525: Reproduced In: 3.10, 3.0.13 (was: 3.0.13, 3.10) Status: Patch

[jira] [Resolved] (CASSANDRA-13524) cassandra core connector - Guava incompatibility: Detected incompatible version of Guava in the classpath. You need 16.0.1 or higher

[ https://issues.apache.org/jira/browse/CASSANDRA-13524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Hornung resolved CASSANDRA-13524. - Resolution: Fixed > cassandra core connector - Guava incompatibility:

[jira] [Created] (CASSANDRA-13525) ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade

Sam Tunnicliffe created CASSANDRA-13525: --- Summary: ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade Key: CASSANDRA-13525 URL: https://issues.apache.org/jira/browse/CASSANDRA-13525

[jira] [Commented] (CASSANDRA-8272) 2ndary indexes can return stale data

[ https://issues.apache.org/jira/browse/CASSANDRA-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006297#comment-16006297 ] Sergio Bossa commented on CASSANDRA-8272: - One more thing I'm realizing we should fix is

[jira] [Commented] (CASSANDRA-8272) 2ndary indexes can return stale data

[ https://issues.apache.org/jira/browse/CASSANDRA-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006245#comment-16006245 ] Sergio Bossa commented on CASSANDRA-8272: - [~adelapena], I gave a first review pass and the

[jira] [Commented] (CASSANDRA-13521) Add configurable upper bound for validation executor threads

[ https://issues.apache.org/jira/browse/CASSANDRA-13521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007139#comment-16007139 ] Jeff Jirsa commented on CASSANDRA-13521: {code} +# Number of simultaneous repair validations

[jira] [Updated] (CASSANDRA-13521) Add configurable upper bound for validation executor threads

[ https://issues.apache.org/jira/browse/CASSANDRA-13521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Jirsa updated CASSANDRA-13521: --- Reviewer: Jeff Jirsa > Add configurable upper bound for validation executor threads >

[jira] [Comment Edited] (CASSANDRA-13521) Add configurable upper bound for validation executor threads

[ https://issues.apache.org/jira/browse/CASSANDRA-13521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007139#comment-16007139 ] Jeff Jirsa edited comment on CASSANDRA-13521 at 5/11/17 8:38 PM: -

[jira] [Updated] (CASSANDRA-13526) nodetool cleanup on KS with no replicas should remove old data, not silently complete

[ https://issues.apache.org/jira/browse/CASSANDRA-13526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Jirsa updated CASSANDRA-13526: --- Description: >From the user list:

[jira] [Commented] (CASSANDRA-13521) Add configurable upper bound for validation executor threads

[ https://issues.apache.org/jira/browse/CASSANDRA-13521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007158#comment-16007158 ] Blake Eggleston commented on CASSANDRA-13521: - [~jjirsa] fixed > Add configurable upper

[jira] [Commented] (CASSANDRA-13521) Add configurable upper bound for validation executor threads

[ https://issues.apache.org/jira/browse/CASSANDRA-13521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007173#comment-16007173 ] Jeff Jirsa commented on CASSANDRA-13521: +1. Looks good to me. > Add configurable upper

[jira] [Updated] (CASSANDRA-13521) Add configurable upper bound for validation executor threads

[ https://issues.apache.org/jira/browse/CASSANDRA-13521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Jirsa updated CASSANDRA-13521: --- Status: Ready to Commit (was: Patch Available) > Add configurable upper bound for

[jira] [Comment Edited] (CASSANDRA-13521) Add configurable upper bound for validation executor threads

[ https://issues.apache.org/jira/browse/CASSANDRA-13521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007139#comment-16007139 ] Jeff Jirsa edited comment on CASSANDRA-13521 at 5/11/17 8:34 PM: -

[jira] [Commented] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted

[ https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006895#comment-16006895 ] Sergio Bossa commented on CASSANDRA-10130: -- I had a quick look at this one and I think we

[jira] [Commented] (CASSANDRA-8272) 2ndary indexes can return stale data

[ https://issues.apache.org/jira/browse/CASSANDRA-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006896#comment-16006896 ] Andrés de la Peña commented on CASSANDRA-8272: -- Indeed, both returning entries that were

[jira] [Updated] (CASSANDRA-12847) cqlsh DESCRIBE output doesn't properly quote index names

[ https://issues.apache.org/jira/browse/CASSANDRA-12847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-12847: Resolution: Fixed Fix Version/s: (was: 3.11.x)

[5/6] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.11

Merge branch 'cassandra-3.0' into cassandra-3.11 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/c0941cf7 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/c0941cf7 Diff:

[3/6] cassandra git commit: Cqlsh DESCRIBE output handles quoted index names incorrectly

Cqlsh DESCRIBE output handles quoted index names incorrectly Patch by Sam Tunnicliffe; reviewed by Adam Holmberg and Alex Petrov for CASSANDRA-12847 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/33344fae Tree:

[1/6] cassandra git commit: Cqlsh DESCRIBE output handles quoted index names incorrectly

Repository: cassandra Updated Branches: refs/heads/cassandra-3.0 263740daa -> 33344fae6 refs/heads/cassandra-3.11 3a0643329 -> c0941cf78 refs/heads/trunk c43371bf8 -> 36b63ef51 Cqlsh DESCRIBE output handles quoted index names incorrectly Patch by Sam Tunnicliffe; reviewed by Adam Holmberg

[6/6] cassandra git commit: Merge branch 'cassandra-3.11' into trunk

Merge branch 'cassandra-3.11' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/36b63ef5 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/36b63ef5 Diff:

[4/6] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.11

Merge branch 'cassandra-3.0' into cassandra-3.11 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/c0941cf7 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/c0941cf7 Diff:

[2/6] cassandra git commit: Cqlsh DESCRIBE output handles quoted index names incorrectly

Cqlsh DESCRIBE output handles quoted index names incorrectly Patch by Sam Tunnicliffe; reviewed by Adam Holmberg and Alex Petrov for CASSANDRA-12847 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/33344fae Tree:

[jira] [Updated] (CASSANDRA-13486) Upstream Power arch specific code

[ https://issues.apache.org/jira/browse/CASSANDRA-13486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Stupp updated CASSANDRA-13486: - Reviewer: (was: Robert Stupp) Sorry, not available for a review. > Upstream Power

[jira] [Created] (CASSANDRA-13526) nodetool cleanup on KS with no replicas should remove old data, not fail

Jeff Jirsa created CASSANDRA-13526: -- Summary: nodetool cleanup on KS with no replicas should remove old data, not fail Key: CASSANDRA-13526 URL: https://issues.apache.org/jira/browse/CASSANDRA-13526

[jira] [Comment Edited] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted

[ https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007042#comment-16007042 ] Andrés de la Peña edited comment on CASSANDRA-10130 at 5/11/17 7:27 PM:

[jira] [Commented] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted

[ https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007042#comment-16007042 ] Andrés de la Peña commented on CASSANDRA-10130: --- [~sbtourist], I think you are right,

[jira] [Comment Edited] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted

[ https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007042#comment-16007042 ] Andrés de la Peña edited comment on CASSANDRA-10130 at 5/11/17 7:40 PM:

[jira] [Updated] (CASSANDRA-13521) Add configurable upper bound for validation executor threads

[ https://issues.apache.org/jira/browse/CASSANDRA-13521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-13521: Status: Patch Available (was: Open)

[jira] [Updated] (CASSANDRA-13526) nodetool cleanup on KS with no replicas should remove old data, not silently complete

[ https://issues.apache.org/jira/browse/CASSANDRA-13526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Jirsa updated CASSANDRA-13526: --- Summary: nodetool cleanup on KS with no replicas should remove old data, not silently

[jira] [Resolved] (CASSANDRA-13372) dtest failure in repair_tests.incremental_repair_test.TestIncRepair.sstable_marking_test

[ https://issues.apache.org/jira/browse/CASSANDRA-13372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston resolved CASSANDRA-13372. - Resolution: Fixed This hasn't failed since March, and CASSANDRA-13454 would