av9ash/GitBugs huggingface dataset:
Bug: Retry failed stage jobs in jenkins
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 26/May/22 11:44
Resolved: 19/Jun/22 14:47

To avoid failing pipeline builds on CI infrastructure faults (disks, network, etc), retry stage jobs three times before marking them as FAILURE.

Intention is not to retry on UNSTABLE (tests failing).

This has already been done (and tested) for devbranch pipeline (pre-commit) [here|https://github.com/apache/cassandra-builds/pull/72].
Bug: sstableloader not respecting conf-path flag
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 05/May/22 12:54
Resolved: 16/Jun/22 17:49

Hello,

sstableloader does not seem to respect the config file flag (-f) and the storage port flag.

 

We run our cluster on a different storage port with encryption. We construct a YAML with {{server_encryption_options}} and {{client_encryption_options}} and pass the storage port flag (both {{-sp}} and {{-ssp}}).

 

However, we noticed that both the storage port flag and encryption settings are getting picked from the default config file {{conf/cassandra.yaml}} and ends up connecting to 7000 port unencrypted. As a workaround, we have added the storage port configuration to the YAML and copy our configuration file and overwrite the {{conf/cassandra.yaml}} and it is working now.

 

Also to be noted that using the {{-f}} works in Cassandra 3.x. The bug seems to be present in 4.x versions only.
Bug: Test Failure: dtest-offheap.auth_test.TestAuth.test_system_auth_ks_is_alterable (from Cassandra dtests)
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 13/May/22 18:26
Resolved: 08/Jun/22 05:24

Flaked a couple times on 4.1

{code}
Error Message
cassandra.DriverException: Keyspace metadata was not refreshed. See log for details.
{code}

https://ci-cassandra.apache.org/job/Cassandra-4.1/14/testReport/dtest-offheap.auth_test/TestAuth/test_system_auth_ks_is_alterable/

Nightlies archive if above dropped: https://nightlies.apache.org/cassandra/ci-cassandra.apache.org/job/Cassandra-4.1/14/testReport/dtest-offheap.auth_test/TestAuth/test_system_auth_ks_is_alterable/
Bug: CQLSH unicode control character list is too liberal
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 10/May/22 02:35
Resolved: 14/Jun/22 05:04

It appears that the list of escaped unicode control characters [here|https://github.com/apache/cassandra/blob/53a67ff2c36d90d337aba1409498de29931d4279/pylib/cqlshlib/formatting.py#L32] is a bit too liberal. It seems to include characters such as '1' (0x31) and '0' (0x30) which do not need to be escaped. It seems that the actual range should be 0x00 - 0x1F and 0x7F+ as corroborated [by this page|https://en.wikipedia.org/wiki/Unicode_control_characters].

 

This causes unnecessary escaping and regex substitutions on the CQLSH end whenever common characters such as any punctuation or a 0 or a 1 appear in the text column of a table. One might notice that a table with a text column filled with 2's will take much less time to print than one with all 0's for this reason.
Bug: Add cqlsh SHOW REPLICAS by token command
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 23/Apr/22 16:22
Resolved: 27/May/22 15:59

It is often useful to know when a query fails or a query is slow which nodes the query was routed  too. For clusters with vnodes, determining this is not simple and requires an admin tool like 'nodetool getendpoints;. 

But, the Cassandra driver has cluster metadata which identifies which nodes are the replicas for a given token range.  It should be straightforward to support this in CQLSH.

Example with python driver:
{quote}from cassandra.cluster import Cluster

from cassandra.auth import PlainTextAuthProvider

import cassandra.metadata

from cassandra.metadata import Murmur3Token

 

auth_provider = PlainTextAuthProvider(username='cassandra', password='cassandra')

cluster = Cluster(['127.0.0.1'], auth_provider=auth_provider)

session = cluster.connect('tests')

cluster.metadata.token_map.get_replicas('tests',Murmur3Token(100))

{color:#4c9aff}>>> cluster.metadata.token_map.get_replicas('tests',Murmur3Token(100)){color}

{color:#4c9aff}[<Host: 127.0.0.1:9042 datacenter1>]{color}

 
{quote}
Users shouldn't require access to an admin tool like nodetool to access the cluster metadata.  This is especially true for Cassandra-as-a-service offerings like AWS keyspaces or Instaclustr's managed service.
Bug: Expired snapshots of dropped tables are not removed after node restart
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 10/May/22 15:22
Resolved: 29/May/22 19:45

Expired TTL snapshots from a dropped table are only removed if the node is not restarted after the table is dropped.

The reason for this is because {{SnapshotManager}} is using the old implementation of {{listsnapshots}} to load snapshots in memory during node startup, before CASSANDRA-16843 is fixed so it doesn't keep track of snapshots of dropped tables.

We should make {{SnapshotManager}} use the new implementation to load snapshots of dropped tables in memory, what ensures they will be removed when expired.
Bug: Fix flaky testOutboundConnectionsAreRejectedWhenAuthFails
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 21/Jun/22 22:56
Resolved: 18/Feb/23 01:39

testOutboundConnectionsAreRejectedWhenAuthFails was introduced in CASSANDRA-17661

It seems it was introduced flaky from the very beginning as per this run in a loop - [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=flaky-testOutboundConnectionsAreRejectedWhenAuthFails&filter=all]

CC [~janaki.manchala] , [~jonmeredith],  [~ycai]
Bug: Add in Circle CI an option to run in a loop tests for the new  j8_jvm_dtests_vnode job
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 10/May/22 01:30
Resolved: 27/May/22 10:45

Similar to the python dtests we need to be able to run in a loop with/without vnodes the in-jvm tests. Very convenient during debugging flaky tests
Bug: Flaky CompactStorageTest
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 30/May/22 09:28
Resolved: 07/Jun/22 07:29

CompactStorageTest has been showing flaky behavior mainly due to timeouts such as [here|https://ci-cassandra.apache.org/job/Cassandra-4.1/43/testReport/org.apache.cassandra.cql3.validation.operations/CompactStorageTest/testAlterWithCompactNonStaticFormat/]
Bug: Fix widening - mebibytes to bytes in IntMebibytesBound
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 27/Jun/22 15:35
Resolved: 28/Jun/22 18:51

Follow up on CASSANDRA-17650

We need to add toBytesInLong method in IntMebibytesBound to support widening for a few parameters identified in CASSANDRA-17650

CC [~adelapena]
Bug: nodetool clientstats - client_options to be exposed by adding a new flag
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 23/Jun/22 23:36
Resolved: 27/Jun/22 23:44

client_options column (CASSANDRA-16378) should appear when using a new flag (to be introduced) to expose client_options instead of being added at the back of the current output. This is needed to ensure backward compatibility of the output is preserved.
Bug: Test failure: org.apache.cassandra.distributed.upgrade.DropCompactStorageWithDeletesAndWritesTest
Status: Open
Priority: Normal
Created: 31/May/22 17:09

The Java upgrade dtest {{org.apache.cassandra.distributed.upgrade.DropCompactStorageWithDeletesAndWritesTest}} is ~8% flaky on CircleCI:

https://app.circleci.com/pipelines/github/adelapena/cassandra/1623/workflows/5b7fe4ca-740d-4d99-b130-017e17770401/jobs/17286

{code}
java.lang.RuntimeException: java.lang.RuntimeException: Error setting schema for test (query was: ALTER TABLE distributed_test_keyspace.clustering_and_value_with_deletes DROP COMPACT STORAGE)
	at org.apache.cassandra.distributed.impl.IsolatedExecutor.waitOn(IsolatedExecutor.java:218)
	at org.apache.cassandra.distributed.impl.IsolatedExecutor.lambda$sync$7(IsolatedExecutor.java:112)
	at org.apache.cassandra.distributed.impl.Instance.schemaChangeInternal(Instance.java:240)
	at org.apache.cassandra.distributed.impl.DelegatingInvokableInstance.schemaChangeInternal(DelegatingInvokableInstance.java:82)
	at org.apache.cassandra.distributed.impl.AbstractCluster.schemaChange(AbstractCluster.java:522)
	at org.apache.cassandra.distributed.upgrade.DropCompactStorageWithDeletesAndWritesTest.lambda$testDropCompactWithClusteringAndValueColumnWithDeletesAndWrites$3(DropCompactStorageWithDeletesAndWritesTest.java:72)
	at org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:222)
	at org.apache.cassandra.distributed.upgrade.DropCompactStorageWithDeletesAndWritesTest.testDropCompactWithClusteringAndValueColumnWithDeletesAndWrites(DropCompactStorageWithDeletesAndWritesTest.java:157)
Caused by: java.lang.RuntimeException: Error setting schema for test (query was: ALTER TABLE distributed_test_keyspace.clustering_and_value_with_deletes DROP COMPACT STORAGE)
	at org.apache.cassandra.distributed.impl.Instance.lambda$schemaChangeInternal$2(Instance.java:238)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:84)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.cassandra.exceptions.InvalidRequestException: Cannot DROP COMPACT STORAGE as some nodes in the cluster ([/127.0.0.1]) has some non-upgraded 2.x sstables. Please run `upgradesstables` on those nodes before retrying
	at org.apache.cassandra.cql3.statements.AlterTableStatement.validateCanDropCompactStorage(AlterTableStatement.java:435)
	at org.apache.cassandra.cql3.statements.AlterTableStatement.announceMigration(AlterTableStatement.java:310)
	at org.apache.cassandra.cql3.statements.SchemaAlteringStatement.executeInternal(SchemaAlteringStatement.java:150)
	at org.apache.cassandra.distributed.impl.Instance.lambda$schemaChangeInternal$2(Instance.java:234)
{code}

This was discovered during CASSANDRA-17213.
Bug: Create release branch cassandra-4.1
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 01/May/22 18:35
Resolved: 06/May/22 22:09

Figure out what needs to be done beyond the following…

1. Create release branch
{code}
git switch -c cassandra-4.1 trunk
git push --set-upstream origin cassandra-4.1
{code}

2. Bump trunk's version 
{code}
git switch trunk
# increment version to 4.2
edit build.xml debian/changelog CHANGES.txt NEWS.txt
{code}

2a. Update jvm-dtest supported upgrade paths
 - https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96 

3. Add `4.1.x` to jira versions
(no existing tickets will be changed - assignees need to change appropriate bugs from 4.x to 4.1.x)

4. Update docker images to include cassandra-4.1
(Docker images also need to be deployed)

5. Add pipeline to ci-cassandra
https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51

6. Add dtest version and upgrade paths
 - https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
 - https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
 - https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41

7. Update how_to_commit documentation
https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
Bug: Clients using JMX are unable to handle non-standard java types but we leak this into our Exceptions
Status: Open
Priority: Normal
Created: 25/Apr/22 17:43

This is an extension of CASSANDRA-17527.

When we throw in JMX the exception gets serialized and sent over the wire, and if the client doesn’t have the same class path it fails and the exception is lost and replaced with a ClassNotFoundException.  This is bad as the user has no idea what the issue is so unable to resolve it.
Bug: Local host-id may not be set when replaying commit log
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 05/Apr/22 20:38
Resolved: 12/Apr/23 16:10

The local host id is now used when replaying commit logs to prevent data loss when moving SSTables between nodes (CASSANDRA-16619).

The local host-id is assigned once on initial startup and persisted to the local.local table for use on subsequent startups - however it remains in the memtable/commitlog until the local table is eventually flushed.

If the node dies for any reason before the flush takes place, on the next restart a new host id will be allocated before the commit log is replayed and any sstables appearing in the commit log will be skipped incorrectly.
Bug: Fix flaky test - org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.testConditionalUpdate[0: clusterMinVersion=3.0]
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 23/May/22 11:06
Resolved: 11/Jul/22 07:52

{code}
junit.framework.AssertionFailedError
	at org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.lambda$data$0(InsertUpdateIfConditionTest.java:64)
	at org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.beforeSetup(InsertUpdateIfConditionTest.java:90)
	at org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.before(InsertUpdateIfConditionTest.java:84)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
{code}

https://ci-cassandra.apache.org/job/Cassandra-4.1/34/testReport/org.apache.cassandra.cql3.validation.operations/InsertUpdateIfConditionTest/testConditionalUpdate_0__clusterMinVersion_3_0__3/
Bug: Migrate track_warnings to more standard naming conventions and use latest configuration types rather than long
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 18/Apr/22 20:39
Resolved: 21/Apr/22 21:33

Track warnings currently is nested which is discouraged at the moment.  It also was before the config standards patch which moved storage typed longs to a new DataStorageSpec type, we should migrate the configs there.
Bug: Resolve additional pylint issues in pylib
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 12/Apr/22 01:38
Resolved: 13/Apr/22 12:17

Resolve minor pylint and PEP8 issues:
 * Lines too long
 * Unused args in functions
 * Exceptions defined too broadly
 * Redundant parenthesis
 * Unnecessary escapes in regex
 * Update select.error merged into OSError (python 3.3+, PEP 3151)
 * Variable names reused in inner scope
 * Obsolete EINTR handling (python 3.5+, PEP 475)
Bug: Fix replace_address_test.TestReplaceAddress.test_fail_when_seed
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 06/May/22 00:16
Resolved: 14/Mar/23 20:00

Seen [with|https://ci-cassandra.apache.org/job/Cassandra-3.11/349/testReport/dtest.replace_address_test/TestReplaceAddress/test_fail_when_seed/] and [without vnode|https://ci-cassandra.apache.org/job/Cassandra-3.11/348/testReport/dtest-novnode.replace_address_test/TestReplaceAddress/test_fail_when_seed/]:
{code:java}
Error Message
test teardown failure

Stacktrace
Unexpected error found in node logs (see stdout for full details). Errors: [ERROR [MessagingService-Incoming-/127.0.0.1] 2022-04-28 22:04:36,765 CassandraDaemon.java:244 - Exception in thread Thread[MessagingService-Incoming-/127.0.0.1,5,main] java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor has shut down at org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor$1.rejectedExecution(DebuggableThreadPoolExecutor.java:58) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379) at org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor.execute(DebuggableThreadPoolExecutor.java:148) at org.apache.cassandra.net.MessagingService.receive(MessagingService.java:1035) at org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:215) at org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:195) at org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:98), ERROR [MessagingService-Incoming-/127.0.0.1] 2022-04-28 22:04:36,765 CassandraDaemon.java:244 - Exception in thread Thread[MessagingService-Incoming-/127.0.0.1,5,main] java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor has shut down at org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor$1.rejectedExecution(DebuggableThreadPoolExecutor.java:58) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379) at org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor.execute(DebuggableThreadPoolExecutor.java:148) at org.apache.cassandra.net.MessagingService.receive(MessagingService.java:1035) at org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:215) at org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:195) at org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:98)]
{code}
Bug: Make GuardrailDiskUsageTest deterministic
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 22/Apr/22 21:33
Resolved: 23/Apr/22 19:32

Jenkins is low on space so we should mock the amount of available disk space when testing the disk usage guardrails as otherwise the tests fail.

The issue was not seen before commit as CircleCI doesn't have storage problems.

[https://ci-cassandra.apache.org/job/Cassandra-trunk/1095/]

Cc [~adelapena]
Bug: Fix NPE in SimpleBuilders.ParititionUpdateBulder.RTBuilder.build
Status: Resolved
Priority: Normal
Resolution: Won't Fix
Created: 04/May/22 06:42
Resolved: 10/Jun/22 23:15

These two arrays are not initialised (1) which means that if I do not set start nor end, when ClusteringBound.create is called, it will be null, but it will fail here (2) as values will be null.

The fix consists of check if values are null and if they are, we build that bound immediately.

(1) https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/SimpleBuilders.java#L257-L258
(2) https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/ClusteringBound.java#L128
Bug: Add additional new JMX methods for the old Config migrated to the new types
Status: Open
Priority: Normal
Created: 19/Apr/22 19:16

In CASSANDRA-15234 we migrated config parameters to new types. The old JMX methods which use primitives are still working as expected. We need to add also new JMX methods for the new types, the getters/setters will get/set String until write mode is added to the Settings virtual table.
Bug: In-jvm framework to plugin yaml config per version
Status: Open
Priority: Normal
Created: 12/Apr/22 21:58

Remove Constants.KEY_DTEST_API_CONFIG_CHECK which currently is set to false for in-jvm upgrade tests which means we don't do the regular checks for invalid yaml that Cassandra does on startup for those tests. 
We need to be able to acknowledge new config parameters added to newer versions. Those should be ignored in the old Cassandra versions during upgrade tests instead of ignoring the checks for the whole configuration file on all Cassandra versions.
Bug: Fix org.apache.cassandra.db.commitlog.BatchCommitLogTest.testOutOfOrderFlushRecovery[3]-cdc
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 05/May/22 23:09
Resolved: 25/May/22 08:26

[https://ci-cassandra.apache.org/job/Cassandra-trunk/1130/testReport/org.apache.cassandra.db.commitlog/BatchCommitLogTest/testOutOfOrderFlushRecovery_3__cdc/]

 
h3.  
{code:java}
Stacktrace
java.io.UncheckedIOException at org.apache.cassandra.io.util.PathUtils.propagateUnchecked(PathUtils.java:768) at org.apache.cassandra.io.util.PathUtils.propagateUnchecked(PathUtils.java:753) at org.apache.cassandra.io.util.PathUtils.delete(PathUtils.java:255) at org.apache.cassandra.io.util.PathUtils.delete(PathUtils.java:297) at org.apache.cassandra.io.util.PathUtils.delete(PathUtils.java:304) at org.apache.cassandra.io.util.File.delete(File.java:158) at org.apache.cassandra.io.util.File.delete(File.java:167) at org.apache.cassandra.io.util.FileUtils.deleteWithConfirm(FileUtils.java:691) at org.apache.cassandra.db.commitlog.CommitLogSegment.discard(CommitLogSegment.java:449) at org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager.discardAvailableSegment(AbstractCommitLogSegmentManager.java:519) at org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager.shutdown(AbstractCommitLogSegmentManager.java:506) at org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDC.shutdown(CommitLogSegmentManagerCDC.java:157) at org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager.stopUnsafe(AbstractCommitLogSegmentManager.java:452) at org.apache.cassandra.db.commitlog.CommitLog.stopUnsafe(CommitLog.java:504) at org.apache.cassandra.db.commitlog.CommitLog.resetUnsafe(CommitLog.java:470) at org.apache.cassandra.db.commitlog.CommitLogTest.testOutOfOrderFlushRecovery(CommitLogTest.java:991) at org.apache.cassandra.db.commitlog.CommitLogTest.testOutOfOrderFlushRecovery(CommitLogTest.java:1057) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) Caused by: java.nio.file.NoSuchFileException: build/test/cassandra/commitlog/CommitLog-7-1651753848882.log at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116) at java.base/sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:249) at java.base/sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:105) at java.base/java.nio.file.Files.delete(Files.java:1142) at org.apache.cassandra.io.util.PathUtils.delete(PathUtils.java:250)
{code}
Bug: FQLTool Replay should support full set of login options (ssl, auth provider etc)
Status: Open
Priority: Normal
Created: 18/Apr/22 19:16

While the FQLTool is great, It would appear that the connection options for the FQLTool are limited to user name and password as the only mechanisms for logging in.  There are a few things that I noticed in playing around with the tool...
 # user name and login are possible through the target connection string, but this is not documented in the help.
 # it also appears that the password is put in the log as plain text while executing.
 # we should have the ability to use ssl (such as an ssl option).
 # we should have the ability to specify different auth providers, so that those which run on Kerberos etc, can be used.
Bug: NPE in RangeTombstoneTest.overlappingRangeTest-compression
Status: Resolved
Priority: Normal
Resolution: Cannot Reproduce
Created: 13/Apr/22 15:13
Resolved: 30/Jun/22 10:18

The trace looks something like this on trunk:

{noformat}
java.lang.NullPointerException
	at org.apache.cassandra.db.RangeTombstoneTest.overlappingRangeTest(RangeTombstoneTest.java:437)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
{noformat}

See https://ci-cassandra.apache.org/job/Cassandra-trunk/1078/testReport/org.apache.cassandra.db/RangeTombstoneTest/overlappingRangeTest_compression/