av9ash/GitBugs huggingface dataset:
Bug: CircleCI Unit Tests issue on latest trunk - java.lang.OutOfMemoryError: Java heap space 
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 24/Jul/20 18:07
Resolved: 24/Jul/20 18:11

We persistently see on the latest CircleCI trunk the following error:

 
{code:java}
BUILD FAILED
/tmp/cassandra/build.xml:1982: The following error occurred while executing this line:
/tmp/cassandra/build.xml:1866: java.lang.OutOfMemoryError: Java heap space
 at java.lang.AbstractStringBuilder.<init>(AbstractStringBuilder.java:68)
 at java.lang.StringBuffer.<init>(StringBuffer.java:128)
 at com.sun.org.apache.xml.internal.utils.FastStringBuffer.getString(FastStringBuffer.java:872)
 at com.sun.org.apache.xml.internal.dtm.ref.sax2dtm.SAX2DTM2.getStringValueX(SAX2DTM2.java:2937)
 at com.sun.org.apache.xalan.internal.xsltc.dom.DOMAdapter.getStringValueX(DOMAdapter.java:284)
 at junit_frames.template$dot$5()
 at junit_frames.applyTemplates5()
 at junit_frames.package()
 at junit_frames.template$dot$0()
 at junit_frames.applyTemplates()
 at junit_frames.applyTemplates()
 at junit_frames.transform()
 at com.sun.org.apache.xalan.internal.xsltc.runtime.AbstractTranslet.transform(AbstractTranslet.java:620)
 at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:730)
 at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:343)
 at org.apache.tools.ant.taskdefs.optional.TraXLiaison.transform(TraXLiaison.java:201)
 at org.apache.tools.ant.taskdefs.XSLTProcess.process(XSLTProcess.java:870)
 at org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:408)
 at org.apache.tools.ant.taskdefs.optional.junit.AggregateTransformer.transform(AggregateTransformer.java:281)
 at org.apache.tools.ant.taskdefs.optional.junit.XMLResultAggregator.execute(XMLResultAggregator.java:157)
 at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
 at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
 at org.apache.tools.ant.Task.perform(Task.java:350)
 at org.apache.tools.ant.taskdefs.Sequential$$Lambda$149/1543351283.accept(Unknown Source)
 at java.util.Vector.forEach(Vector.java:1275)
 at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:67)
 at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
 at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Total time: 2 minutes 52 seconds
Exited with code exit status 1
CircleCI received exit code 1
{code}
 

*Example:* https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/285/workflows/f2722016-2353-4c38-9fd2-8614f6609f55/jobs/1648/parallel-runs/16?filterBy=FAILED
Bug: Nodetool unit test coverage
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 04/Aug/20 09:18
Resolved: 03/Aug/21 19:41

Nowadays the majority of nodetool testing happens outside the main java unit testing effort. A lot is done as separate dtests under python, some commands don't have dedicated tests, some only get tested as a side effect of some other test, etc.

The purpose of this ticket is to improve unit test coverage as much as possible now that CASSANDRA-15583 allows us to perform java unit tests for the tool.
Bug: Fix flaky python dtest test_simple_rebuild - rebuild_test.TestRebuild
Status: Resolved
Priority: Normal
Resolution: Auto Closed
Created: 29/Jul/20 00:11
Resolved: 13/Sep/21 17:12

https://app.circleci.com/pipelines/github/dcapwell/cassandra/360/workflows/8e93a655-b66e-4bf2-8866-5f9a46487763/jobs/1847

{code}
>       assert self.rebuild_errors == 1, \
            'rebuild errors should be 1, but found {}. Concurrent rebuild should not be allowed, but one rebuild command should have succeeded.'.format(self.rebuild_errors)
E       AssertionError: rebuild errors should be 1, but found 0. Concurrent rebuild should not be allowed, but one rebuild command should have succeeded.
E       assert 0 == 1
E        +  where 0 = <rebuild_test.TestRebuild object at 0x7f29fe243518>.rebuild_errors
{code}
Bug: Digest for some queries is different depending whether the data are retrieved from sstable or memtable
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 20/Jul/20 13:19
Resolved: 25/Jan/21 10:50

Not sure into which category should I assign this ticket.

 

Basically when reading using certain column filters, the digest is different depending whether we read from sstable and memtable. This happens on {{trunk}} and {{cassandra-3.11}} branches. However it works properly on {{cassandra-3.0}} branch.

 

I'm attaching a simple test for trunk to demonstrate what I mean. 

 

Please verify my test and my conclusions
Bug: SEP.shutdownAndWait does not wait for termination and SEPExecutor.awaitTermination may hang
Status: Review In Progress
Priority: Normal
Created: 24/Jul/20 00:45

SharedExecutorPool.shutdownAndWait calls shutdownNow on the executors it owns, which has the side effect of removing the executor from the list, then uses the same emptied list to try and wait for them to complete shutting down, which completes immediately.
 
Once fixed by copying the list in SEP.shutdownAndWait, the SEPExecutorTest suite fails with a timeout due to a startup race in SEPWorker.
 
If a SEPExecutor is shutdown immediately after maybeSchedule creates a new SEPWorker,
but before it is able to execute the first task then it exits immediately on entering the work loop with a work and task permit reserved for it, which invalidates the work/task permit accounting and prevents calling the shutdown SimpleCondition.signalAll when the last SEPWorker exits.
Bug: sstablerepairedset unit test hardening
Status: Open
Priority: Normal
Created: 04/Aug/20 08:57

During CASSANDRA-15883 / CASSANDRA-15991 it was detected unit test coverage for this tool is minimal. There is a unit test to enhance upon under {{test/unit/org/apache/cassandra/tools}}. Aso args parsing is brittle and it would benefit from migrating to some args parsing framework.
Bug: sstableverify unit test hardening and docs improvement
Status: In Progress
Priority: Normal
Created: 04/Aug/20 08:48

During CASSANDRA-15883 / CASSANDRA-15991 it was detected unit test coverage for this tool is minimal. There is a unit test to enhance upon under {{test/unit/org/apache/cassandra/tools}}. Also docs need to be updated with any missing options and the {{token_range}} option needs to be fixed as it appears broken.
Bug: Fix flaky test testIndexMemtableSwitching - org.apache.cassandra.index.sasi.SASIIndexTest
Status: Resolved
Priority: Normal
Resolution: Auto Closed
Created: 29/Jul/20 00:13
Resolved: 13/Sep/21 17:12

https://app.circleci.com/pipelines/github/dcapwell/cassandra/361/workflows/3a42fa45-1f60-4c95-86a4-15a6773e384e/jobs/1855

{code}
junit.framework.AssertionFailedError: expected:<0> but was:<1>
	at org.apache.cassandra.index.sasi.SASIIndexTest.testIndexMemtableSwitching(SASIIndexTest.java:2379)
{code}
Bug: dtest.cql_tracing_test.TestCqlTracing.test_tracing_default_impl  fails
Status: Resolved
Priority: Normal
Resolution: Auto Closed
Created: 11/Aug/20 23:37
Resolved: 13/Sep/21 17:12

dtest.cql_tracing_test.TestCqlTracing.test_tracing_default_impl fails on trunk:

 https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-dtest/10/label=cassandra,split=25/testReport/junit/dtest.cql_tracing_test/TestCqlTracing/test_tracing_default_impl/
Bug: python dtest TestCqlsh added enable_scripted_user_defined_functions which breaks on 2.2
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 26/Jul/20 19:19
Resolved: 21/Jul/21 21:07

{code}
ERROR [main] 2020-07-26 03:03:14,108 CassandraDaemon.java:744 - Exception encountered during startup
org.apache.cassandra.exceptions.ConfigurationException: Invalid yaml. Please remove properties [enable_scripted_user_defined_functions] from your cassandra.yaml
	at org.apache.cassandra.config.YamlConfigurationLoader$MissingPropertiesChecker.check(YamlConfigurationLoader.java:146) ~[main/:na]
	at org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:113) ~[main/:na]
	at org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:85) ~[main/:na]
	at org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:151) ~[main/:na]
	at org.apache.cassandra.config.DatabaseDescriptor.<clinit>(DatabaseDescriptor.java:133) ~[main/:na]
	at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:604) [main/:na]
	at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:731) [main/:na]]
{code}

This test doesn’t put a version limit, so all tests fail on 2.2 since the property was added to all clusters.
Bug: rpc server gets wrongly initialized with rpc_enabled:false
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 01/Sep/20 10:53
Resolved: 20/Oct/20 19:05

After upgrading to Cassandra 3.11.8, Cassandra no longer starts. An exception is thrown:
{code:java}
 java.lang.RuntimeException: Client SSL is not supported for non-blocking sockets (hsha). Please remove client ssl from the configuration.
	at org.apache.cassandra.thrift.THsHaDisruptorServer$Factory.buildTServer(THsHaDisruptorServer.java:74)
	at org.apache.cassandra.thrift.TServerCustomFactory.buildTServer(TServerCustomFactory.java:55)
	at org.apache.cassandra.thrift.ThriftServer$ThriftServerThread.<init>(ThriftServer.java:128)
	at org.apache.cassandra.thrift.ThriftServer.start(ThriftServer.java:55)
	at org.apache.cassandra.service.CassandraDaemon.startNativeTransport(CassandraDaemon.java:713)
	at org.apache.cassandra.service.CassandraDaemon.start(CassandraDaemon.java:538)
	at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:643)
	at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:768)
{code}
No configuration changed between 3.11.7 and 3.11.8. rpc_enabled is false in both versions.

I created this Jira issue because clearly something changed between 3.11.7 and 3.11.8. Maybe intentional, maybe not. Changing `rpc_server_type` (which is not clearly documented to be about Thrift only) from `hsha` to `sync` does resolve the issue, as expected, but this does seem like a regression, hence the Jira issue.
Bug: Node state incorrectly set to NORMAL after nodetool disablegossip and enablegossip during bootstrap
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 28/Sep/20 17:23
Resolved: 30/Oct/20 19:41

At high level, {{StorageService#setGossipTokens}} set the gossip state to {{NORMAL}} blindly. Therefore, re-enabling gossip (stop and start gossip) overrides the actual gossip state.
  
It could happen in the below scenario.
# Bootstrap failed. The gossip state remains in {{BOOT}} / {{JOINING}} and code execution exits StorageService#initServer.
# Operator runs nodetool to stop and re-start gossip. The gossip state gets flipped to {{NORMAL}}
Bug: New Cassandra website design, content and layout to work with Antora
Status: Resolved
Priority: Normal
Resolution: Done
Created: 08/Sep/20 23:27
Resolved: 24/Jun/21 22:29

This task is related to CASSANDRA-16066 (Update and rework the cassandra-website material to work with Antora). The goal is to update the front-end of the C* website (design, IA and content) to work with Antora to help modernize the website as discussed on the [mailing list|https://www.mail-archive.com/dev@cassandra.apache.org/msg15537.html].

*Design Concepts:* A minimum of two homepage design concepts will be created and shared for input, which will help standardize a brand palette for C* and a design language for the site. This may include custom iconography and graphics. The chosen design language will be used to develop the remaining templates. 

*Template Design*: It's estimated that 7 template designs will be needed including the creation of several new pages: 
 * Homepage template
 * Toplevel template - e.g. Community.
 * General template - Mostly textual with some images, e.g. Intro, Quickstart 
 * “Library” template - A library of assets (links, downloads, logos etc) that are sortable by metadata, e.g Resources, or Kafka's Powered By page).
 * Blog landing template 
 * Blog single template
 * Docs template 

*Website Content:* Along with new design will be a need for new or updated content to fit the new page layouts. The intention is to use as much as possible from existing content, and augment with new content where needed.

*Template Development:* This includes the frontend development, such as any HTML markup to achieve designs. HTML would be crafted so as to preserve any backend/API calls, such that content is pulled in as designed. The majority of the frontend work would come in the form of crafting CSS to bring the designs to life, plus any minor Javascript to add subtle delights to key pages.

*Style Guide*: Once all is complete, a Style Guide be added to GitHub for contributors.

The [cassandra-website|https://github.com/apache/cassandra-website] repository would need to be modified. Specific changes to be determined.
Bug: Cqlsh unit testing and coverage improvements
Status: Open
Priority: Normal
Created: 04/Aug/20 09:17

Nowadays the majority of cqlsh testing happens outside the main java unit testing effort. A lot is done as separate cqlsh tests, dtests, python, etc.

The purpose of this ticket is to improve unit test coverage as much as possible now that CASSANDRA-15583 allows us to perform java unit tests for the tool.
Bug: sstabledump unit test hardening
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 04/Aug/20 09:06
Resolved: 05/Aug/20 12:52

During CASSANDRA-15883 / CASSANDRA-15991 it was detected unit test coverage for this tool is minimal. There is a unit test to enhance upon under {{test/unit/org/apache/cassandra/tools}}.
Bug: Failure in ViewTest#testNullInClusteringColumns on FreeBSD
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 27/Jul/20 16:17
Resolved: 29/Apr/21 14:34

 

Failure occurs on FreeBSD 12.1-RELEASE-p5 amd64, OpenJDK 64-Bit Server VM (build 11.0.8+10-1, mixed mode),  4.0-beta1.
{noformat}
[junit-timeout] Testsuite: org.apache.cassandra.cql3.ViewTest Tests run: 41, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 110.152 sec
[junit-timeout]
[junit-timeout] Testcase: testNullInClusteringColumns(org.apache.cassandra.cql3.ViewTest):      FAILED
[junit-timeout] Invalid value for row 0 column 2 (v1 of type varchar), expected <NULL> (-1 bytes) but got <'foo'> (3 bytes) (using protocol version 4/v4)
[junit-timeout] junit.framework.AssertionFailedError: Invalid value for row 0 column 2 (v1 of type varchar), expected <NULL> (-1 bytes) but got <'foo'> (3 bytes) (using protocol version 4/v4)
[junit-timeout]         at org.apache.cassandra.cql3.CQLTester.assertRowsNet(CQLTester.java:1034)
[junit-timeout]         at org.apache.cassandra.cql3.ViewTest.testNullInClusteringColumns(ViewTest.java:1262)
[junit-timeout]         at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit-timeout]         at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[junit-timeout]         at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[junit-timeout]
[junit-timeout]
[junit-timeout] Test org.apache.cassandra.cql3.ViewTest FAILED{noformat}
Bug: Jenkins: dsl for website build, logging repo SHAs, and using nightlies.a.o instead of archiving
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 15/Sep/20 10:23
Resolved: 30/Sep/20 20:43

Jenkins improvements

1. Add the cassandra-website job into cassandra_job_dsl.seed.groovy (so we don't lose it next time the Jenkins master is corrupted)

2. Print the SHAs of the different git repos used during the build process. Also store them in the .head files (so the pipeline can print them out too).

3. Instead of archiving artefacts, ssh them to https://nightlies.apache.org/cassandra/
(Disk usage on agents is largely under control, but disk usage on master was the new problem. The suspicion here is the Cassandra-*-artifact's artefacts was the disk usage culprit, though we have to evidence to support it.)
Bug: BLOG - Post about Cassandra & Kubernetes - SIG Update
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 12/Aug/20 23:09
Resolved: 17/Aug/20 15:39

We're getting a blog post out before/coinciding with Kubecon 2020. Content code is mostly ready 

 

 

[https://github.com/Anant/cassandra-website/blob/master/src/_posts/2020-08-17-cassandra-and-kubernetes-sig-update.markdown]
Bug: materialized view rebuild automatically after drop multiple views
Status: Open
Priority: Normal
Created: 02/Jul/20 12:44

Background:

Cassandra version: 3.0.12

Our cassandra cluster has 9 host for DC1 and 3 host for DC2,

each host :
||node||memory||disk||
|DC1 1|256 GB|5*788GB|
|DC1 2|256 GB|5*788GB|
|DC1 3|256 GB|5*788GB|
|DC1 4|256 GB|5*788GB|
|DC1 5|256 GB|5*788GB|
|DC1 6|256 GB|5*788GB|
|DC1 7|512 GB|5 TB|
|DC1 8|512 GB|5 TB|
|DC1 9|512 GB|5 TB|
|DC2 1|256 GB|8*788GB|
|DC2 2|256 GB|8*788GB|
|DC2 3|256 GB|8*788GB|

by using nodetool status, node load in DC1 is about 1.5 TB, node load in DC2 is about 4 TB

QPS: 270

-------------------------------------

Problem we met:

In DC1 1 node, enter the cql command line and execute command like following in sametime:

"drop materialized view if exists view1; 

drop materialized view if exists view2;

drop materialized view if exists view3;

drop materialized view if exists view4;"

after a while, command line display warning like "schema version mismatch detected..." (sorry we cannot find the exact output for that time)

After that we find view files in node: "DC1 7" hasn't be deleted yet.

at this moment, we find performance of cluster drop sharp, the cluster almost stop response to any request.

by runing:  select * from system.views_builds_in_progress;

we can see several views were building.

then we execte:

1,   nodetool stop VIEW_BUILD  in each node

2, in cql: delete from system.views_builds_in_progress where view_name=XXXX

3, rolling restart cassandra nodes

 

about an hours later, performance increase to normal.

--------------------------------------------------------------

Why this happen?

How to avoid this problem?

Any better way to deal with this problem?
Bug: sstableofflinerelevel unit test hardening
Status: Open
Priority: Normal
Created: 04/Aug/20 08:59

During CASSANDRA-15883 / CASSANDRA-15991 it was detected unit test coverage for this tool is minimal. There is a unit test to enhance upon under {{test/unit/org/apache/cassandra/tools}}. Also the tools parsing of args seems brittle and it would benefit from using some cmd parsing framework.
Bug: sstableloader unit testing, docs and args parsing
Status: Open
Priority: Normal
Created: 04/Aug/20 09:04

During CASSANDRA-15883 / CASSANDRA-15991 it was detected unit test coverage for this tool is minimal. A unit test under {{test/unit/org/apache/cassandra/tools}} is needed, docs improvements to reflect all options making sure cmd args parsing is done through some framework rather than being a simple brittle custom code.
Bug: bin/cassandra may fail to execute in certain environments due to unhandled output pipe
Status: Open
Priority: Normal
Created: 05/Aug/20 03:09

While developing Docker images for C* 3.11.6 I noticed bin/cassandra failed to start when executed with nohup in a container based Red Hat Universal Base Image on Kubernetes. Curiously this issue could not be reproduced when simply running the container on Docker. Instead it had to be scheduled within a k8s pod.

 

Running an strace indicates the following:
{code:java}
[pid 3666026] write(2, "OpenJDK 64-Bit Server VM warning: ", 34) = -1 EPIPE (Broken pipe) {code}
 

The issue occurs before the system.log file is created. After further digging in to the command being run it was determined the bin/cassandra file was not redirecting all output pipes. In this particular environment this leads to the process going defunct and no Cassandra running.

 

The 4 lines starting with 
{code:java}
exec $NUMACTL {code}
are not handling one of the outputs (stderr or stdout). As a workaround suffixing each line with 
{code:java}
> /var/log/cassandra/stdout.log 2> /var/log/cassandra/stderr.log
{code}
{{resolves the issue and Cassandra starts without any issues.}}

 

{{Rather than bake this into our containers the fix should make its way upstream.}}
Bug: FQL replay should have options to ignore DDL statements
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 07/Aug/20 21:21
Resolved: 19/Aug/20 07:43

FQL logs will contain DDL statements made on the host, and the replay tool will attempt to replay them; this can be unsafe in general so should have an option to filter them out.

Thinking about it, since DDL replay isn’t obvious, we should most likely default to false and have a flag to allow DDL replay as well.
Bug: Provide easy copypasta config formatting for nodetool get commands
Status: Triage Needed
Priority: Normal
Created: 27/Jul/20 20:06

Allow all nodetool commands which print out the state of the node or cluster to do so in a way that makes it easy to re-use or paste on other nodes or config files.

For example, the command getcompactionthroughput formats its output like this:
{noformat}
[jshook@cass4 bin]$ ./nodetool getcompactionthroughput      
Current compaction throughput: 64 MB/s
{noformat}
But with an --as-yaml option, it could do this instead:
{noformat}
[jshook@cass4 bin]$ ./nodetool getcompactionthroughput --as-yaml
compaction_throughput_mb_per_sec: 64{noformat}
and with an --as-cli option, it could do this:
{noformat}
[jshook@cass4 bin]$ ./nodetool getcompactionthroughput --as-cli
./nodetool setcompactionthroughput 64{noformat}
Any other nodetool standard options should simply be carried along to the --as-cli form, with the exception of -pw.

Any -pw options should be elided with a warning in comments, but -pwf options should be allowed. This would allow users using -pw to append a password at their discretion, but would allow -pwf to work as usual.

In the absence of either of the options above (--as-yaml or --as-cli) the formatting should not be changed to avoid breaking extant tool integrations.
Bug: Performance regression for queries accessing multiple rows
Status: Resolved
Priority: Normal
Resolution: Cannot Reproduce
Created: 27/Aug/20 18:28
Resolved: 27/Jan/21 17:19

This is spin off from CASSANDRA-16036.

In testing 4.0 relative to 3.0* I found that queries which accessed multiple rows to have a noticeable performance decrease; two queries were used in the test (more may be impacted, others might not): query partition (table has clustering keys) with LIMIT, and query clustering keys using IN clause.

In the below graphs the green line is 3.0 and the other lines are 4.0 (with and without chunk cache)


Partition with LIMIT

!https://issues.apache.org/jira/secure/attachment/13009751/clustering-slice_latency_selects_baseline.png!
!https://issues.apache.org/jira/secure/attachment/13009750/clustering-slice_latency_under90_selects_baseline.png!

Cluster with IN clause

!https://issues.apache.org/jira/secure/attachment/13009749/clustering-in-clause_latency_selects_baseline.png!
!https://issues.apache.org/jira/secure/attachment/13009748/clustering-in-clause_latency_under90_selects_baseline.png!
Bug: sstablescrub unit test hardening and docs improvements
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 04/Aug/20 08:56
Resolved: 17/Nov/20 20:04

During CASSANDRA-15883 / CASSANDRA-15991 it was detected unit test coverage for this tool is minimal. There is a unit test to enhance upon under {{test/unit/org/apache/cassandra/tools}}. Also docs need updating to reflect the latest options available.