[jira] [Commented] (CASSANDRA-15500) only partition key push down when multiple cluster keys restricted in where clause

[ https://issues.apache.org/jira/browse/CASSANDRA-15500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17014072#comment-17014072 ] Vincent White commented on CASSANDRA-15500: --- That's correct, it does appear to just be an

[jira] [Commented] (CASSANDRA-15293) Static columns not include in mutation size calculation

[ https://issues.apache.org/jira/browse/CASSANDRA-15293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17012404#comment-17012404 ] Vincent White commented on CASSANDRA-15293: --- ||Branch|| |[Trunk unit

[jira] [Updated] (CASSANDRA-14099) LCS ordering of sstables by timestamp is inverted

[ https://issues.apache.org/jira/browse/CASSANDRA-14099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14099: -- Fix Version/s: (was: 3.11.x) (was: 4.x)

[jira] [Updated] (CASSANDRA-14099) LCS ordering of sstables by timestamp is inverted

[ https://issues.apache.org/jira/browse/CASSANDRA-14099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14099: -- Resolution: Fixed Status: Resolved (was: Open) > LCS ordering of

[jira] [Updated] (CASSANDRA-14099) LCS ordering of sstables by timestamp is inverted

[ https://issues.apache.org/jira/browse/CASSANDRA-14099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14099: -- Status: Open (was: Patch Available) > LCS ordering of sstables by timestamp is

[jira] [Assigned] (CASSANDRA-15353) Documentation Preview - Cassandra 4.0

[ https://issues.apache.org/jira/browse/CASSANDRA-15353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White reassigned CASSANDRA-15353: - Assignee: Vincent White > Documentation Preview - Cassandra 4.0 >

[jira] [Assigned] (CASSANDRA-15353) Documentation Preview - Cassandra 4.0

[ https://issues.apache.org/jira/browse/CASSANDRA-15353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White reassigned CASSANDRA-15353: - Assignee: (was: Vincent White) > Documentation Preview - Cassandra 4.0

[jira] [Updated] (CASSANDRA-15293) Static columns not include in mutation size calculation

[ https://issues.apache.org/jira/browse/CASSANDRA-15293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15293: -- Bug Category: Parent values: Correctness(12982) Complexity: Low Hanging

[jira] [Updated] (CASSANDRA-15293) Static columns not include in mutation size calculation

[ https://issues.apache.org/jira/browse/CASSANDRA-15293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15293: -- Description: Patch to include any updates to static columns in the data size

[jira] [Updated] (CASSANDRA-15293) Static columns not include in mutation size calculation

[ https://issues.apache.org/jira/browse/CASSANDRA-15293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15293: -- Description: Patch to include any updates to static columns in the data size

[jira] [Created] (CASSANDRA-15293) Static columns not include in mutation size calculation

Vincent White created CASSANDRA-15293: - Summary: Static columns not include in mutation size calculation Key: CASSANDRA-15293 URL: https://issues.apache.org/jira/browse/CASSANDRA-15293 Project:

[jira] [Updated] (CASSANDRA-15292) Point-in-time recovery ignoring timestamp of static column updates

[ https://issues.apache.org/jira/browse/CASSANDRA-15292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15292: -- Description: During point-in-time recovery

[jira] [Updated] (CASSANDRA-15292) Point-in-time recovery ignoring timestamp of static column updates

[ https://issues.apache.org/jira/browse/CASSANDRA-15292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15292: -- Bug Category: Parent values: Correctness(12982) Complexity: Normal

[jira] [Updated] (CASSANDRA-15292) Point-in-time recovery ignoring timestamp of static column updates

[ https://issues.apache.org/jira/browse/CASSANDRA-15292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15292: -- Description: During point-in-time recovery

[jira] [Created] (CASSANDRA-15292) Point-in-time recovery ignoring timestamp of static column updates

Vincent White created CASSANDRA-15292: - Summary: Point-in-time recovery ignoring timestamp of static column updates Key: CASSANDRA-15292 URL: https://issues.apache.org/jira/browse/CASSANDRA-15292

[jira] [Updated] (CASSANDRA-15191) stop_paranoid disk failure policy race condition on startup

[ https://issues.apache.org/jira/browse/CASSANDRA-15191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15191: -- Discovered By: Adhoc Test Since Version: 3.0 alpha 1 > stop_paranoid disk

[jira] [Created] (CASSANDRA-15191) stop_paranoid disk failure policy race condition on startup

Vincent White created CASSANDRA-15191: - Summary: stop_paranoid disk failure policy race condition on startup Key: CASSANDRA-15191 URL: https://issues.apache.org/jira/browse/CASSANDRA-15191

[jira] [Updated] (CASSANDRA-15158) Wait for schema agreement rather then in flight schema requests when bootstrapping

[ https://issues.apache.org/jira/browse/CASSANDRA-15158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15158: -- Description: Currently when a node is bootstrapping we use a set of latches

[jira] [Updated] (CASSANDRA-15158) Wait for schema agreement rather then in flight schema requests when bootstrapping

[ https://issues.apache.org/jira/browse/CASSANDRA-15158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15158: -- Description: Currently when a node is bootstrapping we use a set of latches

[jira] [Updated] (CASSANDRA-15158) Wait for schema agreement rather then in flight schema requests when bootstrapping

[ https://issues.apache.org/jira/browse/CASSANDRA-15158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15158: -- Severity: Normal Discovered By: User Report Bug Category: Parent

[jira] [Created] (CASSANDRA-15158) Wait for schema agreement rather then in flight schema requests when bootstrapping

Vincent White created CASSANDRA-15158: - Summary: Wait for schema agreement rather then in flight schema requests when bootstrapping Key: CASSANDRA-15158 URL:

[jira] [Updated] (CASSANDRA-15136) Incorrect error message in legacy reader

[ https://issues.apache.org/jira/browse/CASSANDRA-15136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15136: -- Description: Just fixes the order in the exception message. ||3.0.x||3.11.x||

[jira] [Updated] (CASSANDRA-15136) Incorrect error message in legacy reader

[ https://issues.apache.org/jira/browse/CASSANDRA-15136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15136: -- Description: Just fixes the order in the exception message. ||3.0.x||3.11||

[jira] [Updated] (CASSANDRA-15136) Incorrect error message in legacy reader

[ https://issues.apache.org/jira/browse/CASSANDRA-15136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15136: -- Description: Just fixes the order in the exception message.   ||3.0.x|3.11||

[jira] [Commented] (CASSANDRA-15136) Incorrect error message in legacy reader

[ https://issues.apache.org/jira/browse/CASSANDRA-15136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846376#comment-16846376 ] Vincent White commented on CASSANDRA-15136: --- Thanks, should be sorted now. > Incorrect

[jira] [Updated] (CASSANDRA-15136) Incorrect error message in legacy reader

[ https://issues.apache.org/jira/browse/CASSANDRA-15136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15136: -- Description: Just fixes the order in the exception message.   ||3.11||

[jira] [Updated] (CASSANDRA-15136) Incorrect error message in legacy reader

[ https://issues.apache.org/jira/browse/CASSANDRA-15136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15136: -- Complexity: Low Hanging Fruit Discovered By: User Report Since Version:

[jira] [Created] (CASSANDRA-15136) Incorrect error message in legacy reader

Vincent White created CASSANDRA-15136: - Summary: Incorrect error message in legacy reader Key: CASSANDRA-15136 URL: https://issues.apache.org/jira/browse/CASSANDRA-15136 Project: Cassandra

[jira] [Updated] (CASSANDRA-15135) SASI tokenizer options not validated before being added to schema

[ https://issues.apache.org/jira/browse/CASSANDRA-15135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15135: -- Discovered By: Adhoc Test Since Version: 3.4 > SASI tokenizer options not

[jira] [Created] (CASSANDRA-15135) SASI tokenizer options not validated before being added to schema

Vincent White created CASSANDRA-15135: - Summary: SASI tokenizer options not validated before being added to schema Key: CASSANDRA-15135 URL: https://issues.apache.org/jira/browse/CASSANDRA-15135

[jira] [Updated] (CASSANDRA-15134) SASI index files not included in snapshots

[ https://issues.apache.org/jira/browse/CASSANDRA-15134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15134: -- Severity: Normal (was: Low) > SASI index files not included in snapshots >

[jira] [Updated] (CASSANDRA-15134) SASI index files not included in snapshots

[ https://issues.apache.org/jira/browse/CASSANDRA-15134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15134: -- Severity: Low Discovered By: Adhoc Test Since Version: 3.4 > SASI

[jira] [Updated] (CASSANDRA-15134) SASI index files not included in snapshots

[ https://issues.apache.org/jira/browse/CASSANDRA-15134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-15134: -- Description: Newly written SASI index files are not being included in snapshots.

[jira] [Created] (CASSANDRA-15134) SASI index files not included in snapshots

Vincent White created CASSANDRA-15134: - Summary: SASI index files not included in snapshots Key: CASSANDRA-15134 URL: https://issues.apache.org/jira/browse/CASSANDRA-15134 Project: Cassandra

[jira] [Comment Edited] (CASSANDRA-14957) Rolling Restart Of Nodes Causes Dataloss Due To Schema Collision

[ https://issues.apache.org/jira/browse/CASSANDRA-14957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741791#comment-16741791 ] Vincent White edited comment on CASSANDRA-14957 at 1/16/19 10:38 AM:

[jira] [Commented] (CASSANDRA-14957) Rolling Restart Of Nodes Causes Dataloss Due To Schema Collision

[ https://issues.apache.org/jira/browse/CASSANDRA-14957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743600#comment-16743600 ] Vincent White commented on CASSANDRA-14957: ---   This doesn't require a new CREATE TABLE

[jira] [Comment Edited] (CASSANDRA-14957) Rolling Restart Of Nodes Causes Dataloss Due To Schema Collision

[ https://issues.apache.org/jira/browse/CASSANDRA-14957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741791#comment-16741791 ] Vincent White edited comment on CASSANDRA-14957 at 1/16/19 4:14 AM:

[jira] [Updated] (CASSANDRA-14957) Rolling Restart Of Nodes Causes Dataloss Due To Schema Collision

[ https://issues.apache.org/jira/browse/CASSANDRA-14957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14957: -- Reproduced In: 3.0.10, 3.11.x (was: 3.0.10) > Rolling Restart Of Nodes Causes

[jira] [Commented] (CASSANDRA-14957) Rolling Restart Of Nodes Causes Dataloss Due To Schema Collision

[ https://issues.apache.org/jira/browse/CASSANDRA-14957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741791#comment-16741791 ] Vincent White commented on CASSANDRA-14957: --- I believe this can happen due a race

[jira] [Updated] (CASSANDRA-14365) Commit log replay failure for static columns with collections in clustering keys

[ https://issues.apache.org/jira/browse/CASSANDRA-14365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14365: -- Description: In the old storage engine, static cells with a collection as part of

[jira] [Updated] (CASSANDRA-14365) Commit log replay failure for static columns with collections in clustering keys

[ https://issues.apache.org/jira/browse/CASSANDRA-14365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14365: -- Description: In the old storage engine, static cells with a collection as part of

[jira] [Updated] (CASSANDRA-14948) Backport dropped column checks to 3.11

[ https://issues.apache.org/jira/browse/CASSANDRA-14948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14948: -- Fix Version/s: 3.11.x Status: Patch Available (was: Open) > Backport

[jira] [Created] (CASSANDRA-14948) Backport dropped column checks to 3.11

Vincent White created CASSANDRA-14948: - Summary: Backport dropped column checks to 3.11 Key: CASSANDRA-14948 URL: https://issues.apache.org/jira/browse/CASSANDRA-14948 Project: Cassandra

[jira] [Updated] (CASSANDRA-14564) issue while adding a column in a table with compact storage

[ https://issues.apache.org/jira/browse/CASSANDRA-14564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14564: -- Assignee: Vincent White Fix Version/s: 3.11.x Status: Patch

[jira] [Commented] (CASSANDRA-14564) issue while adding a column in a table with compact storage

[ https://issues.apache.org/jira/browse/CASSANDRA-14564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732694#comment-16732694 ] Vincent White commented on CASSANDRA-14564: --- Looks like the behaviour your seeing is

[jira] [Comment Edited] (CASSANDRA-14192) netstats information mismatch between senders and receivers

[ https://issues.apache.org/jira/browse/CASSANDRA-14192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16344515#comment-16344515 ] Vincent White edited comment on CASSANDRA-14192 at 12/3/18 4:58 AM:

[jira] [Created] (CASSANDRA-14559) Check for endpoint collision with hibernating nodes

Vincent White created CASSANDRA-14559: - Summary: Check for endpoint collision with hibernating nodes Key: CASSANDRA-14559 URL: https://issues.apache.org/jira/browse/CASSANDRA-14559 Project:

[jira] [Resolved] (CASSANDRA-9652) Nodetool cleanup does not work for nodes taken out of replication

[ https://issues.apache.org/jira/browse/CASSANDRA-9652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White resolved CASSANDRA-9652. -- Resolution: Fixed > Nodetool cleanup does not work for nodes taken out of

[jira] [Updated] (CASSANDRA-14477) The check of num_tokens against the length of inital_token in the yaml triggers unexpectedly

[ https://issues.apache.org/jira/browse/CASSANDRA-14477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14477: -- Status: Patch Available (was: Open) > The check of num_tokens against the length

[jira] [Created] (CASSANDRA-14477) The check of num_tokens against the length of inital_token in the yaml triggers unexpectedly

Vincent White created CASSANDRA-14477: - Summary: The check of num_tokens against the length of inital_token in the yaml triggers unexpectedly Key: CASSANDRA-14477 URL:

[jira] [Assigned] (CASSANDRA-14477) The check of num_tokens against the length of inital_token in the yaml triggers unexpectedly

[ https://issues.apache.org/jira/browse/CASSANDRA-14477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White reassigned CASSANDRA-14477: - Assignee: Vincent White > The check of num_tokens against the length of

[jira] [Comment Edited] (CASSANDRA-14073) Prevent replacement nodes from skipping bootstrapping without allow_unsafe_replace:true

[ https://issues.apache.org/jira/browse/CASSANDRA-14073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486779#comment-16486779 ] Vincent White edited comment on CASSANDRA-14073 at 5/23/18 6:31 AM:

[jira] [Comment Edited] (CASSANDRA-14073) Prevent replacement nodes from skipping bootstrapping without allow_unsafe_replace:true

[ https://issues.apache.org/jira/browse/CASSANDRA-14073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486779#comment-16486779 ] Vincent White edited comment on CASSANDRA-14073 at 5/23/18 6:29 AM:

[jira] [Updated] (CASSANDRA-14073) Prevent replacement nodes from skipping bootstrapping without allow_unsafe_replace:true

[ https://issues.apache.org/jira/browse/CASSANDRA-14073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14073: -- Resolution: Incomplete Fix Version/s: (was: 3.11.x) Status:

[jira] [Updated] (CASSANDRA-14463) Prevent the generation of new tokens when using replace_address flag

[ https://issues.apache.org/jira/browse/CASSANDRA-14463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14463: -- Description: This is a follow up to/replacement of CASSANDRA-14073. The behaviour

[jira] [Commented] (CASSANDRA-14073) Prevent replacement nodes from skipping bootstrapping without allow_unsafe_replace:true

[ https://issues.apache.org/jira/browse/CASSANDRA-14073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486779#comment-16486779 ] Vincent White commented on CASSANDRA-14073: --- I've realised I overlooked an issue with the

[jira] [Created] (CASSANDRA-14463) Prevent the generation of new tokens when using replace_address flag

Vincent White created CASSANDRA-14463: - Summary: Prevent the generation of new tokens when using replace_address flag Key: CASSANDRA-14463 URL: https://issues.apache.org/jira/browse/CASSANDRA-14463

[jira] [Created] (CASSANDRA-14365) Commit log replay failure for static columns with collections in clustering keys

Vincent White created CASSANDRA-14365: - Summary: Commit log replay failure for static columns with collections in clustering keys Key: CASSANDRA-14365 URL:

[jira] [Commented] (CASSANDRA-13797) RepairJob blocks on syncTasks

[ https://issues.apache.org/jira/browse/CASSANDRA-13797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383119#comment-16383119 ] Vincent White commented on CASSANDRA-13797: --- After upgrading an ~18 node, vnode multi-DC

[jira] [Commented] (CASSANDRA-13797) RepairJob blocks on syncTasks

[ https://issues.apache.org/jira/browse/CASSANDRA-13797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16382839#comment-16382839 ] Vincent White commented on CASSANDRA-13797: --- Now that we don't wait for the validations of

[jira] [Updated] (CASSANDRA-14204) Nodetool garbagecollect AssertionError

[ https://issues.apache.org/jira/browse/CASSANDRA-14204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14204: -- Status: Patch Available (was: Open) > Nodetool garbagecollect AssertionError >

[jira] [Created] (CASSANDRA-14204) Nodetool garbagecollect AssertionError

Vincent White created CASSANDRA-14204: - Summary: Nodetool garbagecollect AssertionError Key: CASSANDRA-14204 URL: https://issues.apache.org/jira/browse/CASSANDRA-14204 Project: Cassandra

[jira] [Commented] (CASSANDRA-14192) netstats information mismatch between senders and receivers

[ https://issues.apache.org/jira/browse/CASSANDRA-14192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16344515#comment-16344515 ] Vincent White commented on CASSANDRA-14192: --- This is because we now use

[jira] [Commented] (CASSANDRA-14092) Max ttl of 20 years will overflow localDeletionTime

[ https://issues.apache.org/jira/browse/CASSANDRA-14092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343619#comment-16343619 ] Vincent White commented on CASSANDRA-14092: --- I haven't had a chance to completely catch up

[jira] [Commented] (CASSANDRA-14169) Trivial intellij junit run fix

[ https://issues.apache.org/jira/browse/CASSANDRA-14169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326733#comment-16326733 ] Vincent White commented on CASSANDRA-14169: --- I wonder if we should include the rest of the

[jira] [Updated] (CASSANDRA-14132) sstablemetadata incorrect date string for "EncodingStats minLocalDeletionTime:"

[ https://issues.apache.org/jira/browse/CASSANDRA-14132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14132: -- Fix Version/s: 4.x Status: Patch Available (was: Open) >

[jira] [Created] (CASSANDRA-14132) sstablemetadata incorrect date string for "EncodingStats minLocalDeletionTime:"

Vincent White created CASSANDRA-14132: - Summary: sstablemetadata incorrect date string for "EncodingStats minLocalDeletionTime:" Key: CASSANDRA-14132 URL: https://issues.apache.org/jira/browse/CASSANDRA-14132

[jira] [Updated] (CASSANDRA-14099) LCS ordering of sstables by timestamp is inverted

[ https://issues.apache.org/jira/browse/CASSANDRA-14099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14099: -- Status: Patch Available (was: Open) I've created a patch that splits in this

[jira] [Commented] (CASSANDRA-14027) consistent_range_movement_false_with_rf1_should_succeed_test - bootstrap_test.TestBootstrap

[ https://issues.apache.org/jira/browse/CASSANDRA-14027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279587#comment-16279587 ] Vincent White commented on CASSANDRA-14027: --- I had this test running against trunk for a

[jira] [Commented] (CASSANDRA-14013) Data loss in snapshots keyspace after service restart

[ https://issues.apache.org/jira/browse/CASSANDRA-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273709#comment-16273709 ] Vincent White commented on CASSANDRA-14013: --- I've create a patch for 3.0.x and trunk using

[jira] [Updated] (CASSANDRA-14047) test_simple_strategy_each_quorum_users - consistency_test.TestAccuracy fails: Missing: ['127.0.0.3.* now UP']:

[ https://issues.apache.org/jira/browse/CASSANDRA-14047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14047: -- Attachment: trunk-patch_passes_test-debug.log 3_11-debug.log

[jira] [Updated] (CASSANDRA-14013) Data loss in snapshots keyspace after service restart

[ https://issues.apache.org/jira/browse/CASSANDRA-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14013: -- Status: Awaiting Feedback (was: In Progress) > Data loss in snapshots keyspace

[jira] [Commented] (CASSANDRA-14047) test_simple_strategy_each_quorum_users - consistency_test.TestAccuracy fails: Missing: ['127.0.0.3.* now UP']:

[ https://issues.apache.org/jira/browse/CASSANDRA-14047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16268714#comment-16268714 ] Vincent White commented on CASSANDRA-14047: --- While looking into this the only error I came

[jira] [Updated] (CASSANDRA-14073) Prevent replacement nodes from skipping bootstrapping without allow_unsafe_replace:true

[ https://issues.apache.org/jira/browse/CASSANDRA-14073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14073: -- Fix Version/s: 3.11.2 Status: Patch Available (was: Open) > Prevent

[jira] [Updated] (CASSANDRA-14073) Prevent replacement nodes from skipping bootstrapping without allow_unsafe_replace:true

[ https://issues.apache.org/jira/browse/CASSANDRA-14073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14073: -- Since Version: (was: 2.1.0) > Prevent replacement nodes from skipping

[jira] [Created] (CASSANDRA-14073) Prevent replacement nodes from skipping bootstrapping without allow_unsafe_replace:true

Vincent White created CASSANDRA-14073: - Summary: Prevent replacement nodes from skipping bootstrapping without allow_unsafe_replace:true Key: CASSANDRA-14073 URL:

[jira] [Created] (CASSANDRA-14063) Cassandra will start listening for clients without initialising system_auth after a failed bootstrap

Vincent White created CASSANDRA-14063: - Summary: Cassandra will start listening for clients without initialising system_auth after a failed bootstrap Key: CASSANDRA-14063 URL:

[jira] [Commented] (CASSANDRA-14010) NullPointerException when creating keyspace

[ https://issues.apache.org/jira/browse/CASSANDRA-14010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256229#comment-16256229 ] Vincent White commented on CASSANDRA-14010: --- I had a look at this and assumed that

[jira] [Commented] (CASSANDRA-14013) Data loss in snapshots keyspace after service restart

[ https://issues.apache.org/jira/browse/CASSANDRA-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251160#comment-16251160 ] Vincent White commented on CASSANDRA-14013: --- I took a look at this today and found the

[jira] [Commented] (CASSANDRA-13127) Materialized Views: View row expires too soon

[ https://issues.apache.org/jira/browse/CASSANDRA-13127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837348#comment-15837348 ] Vincent White commented on CASSANDRA-13127: --- I think I pretty much understand what's