av9ash/GitBugs huggingface dataset:
Bug: Gossip NPE due to shutdown event corrupting empty statuses
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 06/Oct/23 22:30
Resolved: 10/Oct/23 21:23

When an instance either disables gossip or shuts down we send a gossip shutdown message, peers ignore it if the endpoint isn’t known, else it mutates its local copy of the state to mark shutdown…
When an instance restarts it populates gossip with the endpoints found in peers, but the state is empty (not null)

So, there is a fun timing bug…

* stop node1
* start node1; at this point all known endpoints before exist in gossip but are empty
* node2 shutdown (gossip shutdown or node, doesn’t matter)
* node1 sees the shutdown before gossip messages, and gets corruptted
* node3 tries to join the cluster, fails due to node1 being corrupted

There are 2 different patterns the NPE can happen with, in this example node1 and node3 will have different stack traces

{code}
org.apache.cassandra.distributed.shared.ShutdownException: Uncaught exceptions were thrown during test
	Suppressed: java.lang.NullPointerException: Unable to get HOST_ID; HOST_ID is not defined, given EndpointState: HeartBeatState = HeartBeat: generation = 0, version = 2147483647, AppStateMap = {STATUS=Value(shutdown,true,37), RPC_READY=Value(false,38), STATUS_WITH_PORT=Value(shutdown,true,36)}
		at org.apache.cassandra.gms.Gossiper.getHostId(Gossiper.java:1218)
		at org.apache.cassandra.gms.Gossiper.getHostId(Gossiper.java:1208)
		at org.apache.cassandra.service.StorageService.handleStateNormal(StorageService.java:3279)
		at org.apache.cassandra.service.StorageService.onChange(StorageService.java:2756)
		at org.apache.cassandra.gms.Gossiper.markAsShutdown(Gossiper.java:611)
		at org.apache.cassandra.gms.GossipShutdownVerbHandler.doVerb(GossipShutdownVerbHandler.java:39)
		at org.apache.cassandra.net.InboundSink.lambda$new$0(InboundSink.java:78)
	Suppressed: java.lang.NullPointerException: Unable to get HOST_ID; HOST_ID is not defined, given EndpointState: HeartBeatState = HeartBeat: generation = 0, version = 2147483647, AppStateMap = {STATUS=Value(shutdown,true,37), RPC_READY=Value(false,38), STATUS_WITH_PORT=Value(shutdown,true,36)}
		at org.apache.cassandra.gms.Gossiper.getHostId(Gossiper.java:1218)
		at org.apache.cassandra.gms.Gossiper.getHostId(Gossiper.java:1208)
		at org.apache.cassandra.service.StorageService.handleStateNormal(StorageService.java:3279)
		at org.apache.cassandra.service.StorageService.onChange(StorageService.java:2756)
		at org.apache.cassandra.gms.Gossiper.doOnChangeNotifications(Gossiper.java:1762)
		at org.apache.cassandra.service.StorageService.onJoin(StorageService.java:3793)
		at org.apache.cassandra.gms.Gossiper.handleMajorStateChange(Gossiper.java:1465)
		at org.apache.cassandra.gms.Gossiper.applyStateLocally(Gossiper.java:1678)
		at org.apache.cassandra.gms.GossipDigestAck2VerbHandler.doVerb(GossipDigestAck2VerbHandler.java:50)
		at org.apache.cassandra.net.InboundSink.lambda$new$0(InboundSink.java:78)

{code}
Bug: Avoid bad serializedSize when sending GOSSIP_SHUTDOWN message
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 29/Nov/23 16:32
Resolved: 30/Nov/23 07:35

In CASSANDRA-18913 we started sending EndpointState with the GOSSIP_SHUTDOWN message - but there is no guard that EndpointState doesn't change between calls to {{serializedSize}} and {{serialize}}
Bug: Fix CQLSH Capture to save query results only and not trace details when Tracing is on
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 27/Nov/23 20:26
Resolved: 20/Nov/24 21:02

When using *Tracing* in CQLSH, it's sometimes helpful to use *Capture* to avoid paging through output when you want to see the trace results.  However, the trace results are also incorrectly captured to the output file.

According to *Help Capture* (below), only the query result should be saved. The correct behavior should display the trace results and only capture the query results.

        {_}Help capture message{_}:  Only query result output is captured. Errors and output from cqlsh-only commands will still be shown in the cqlsh session.

Example:
{quote}> TRACING ON;

> select * from system_schema.columns LIMIT 1;

> CAPTURE 'foo'
{quote}
this should display only the tracing information
{quote}> CAPTURE OFF
{quote}
displays results and then the tracing
{quote}> TRACING OFF
{quote}
displays only the results
Bug: jvm-dtests crash on java 17
Status: In Progress
Priority: Normal
Created: 22/Dec/23 10:30

This is a similar problem to the one mentioned in https://issues.apache.org/jira/browse/CASSANDRA-15981

I'm filling it because I've noticed the same problem on JDK17, perhaps we should also disable unloading classes with CMS for JDK17. 

However, I'm in favour of moving tests to G1 instead.
Bug: WEBSITE - Add Cassandra Catalyst page and blog
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 23/Nov/23 00:03
Resolved: 30/Nov/23 23:20

This ticket is to capture the work associated with creating a new page for the Cassandra Catalyst program and it's associated blog.

 

Preferably, the blog and page are live as of *November 27.* Please contact me, suggest changes, or correct the date when possible in the pull request for the appropriate time that the blog will go live (on both the blog.adoc and the blog post's file).
Bug: Nodetool gcstats correctly displays Direct Memory usage and supports printing in table format
Status: Open
Priority: Normal
Created: 13/Nov/23 20:43

If {{io.netty.maxDirectMemory}} is not specified, Netty defaults the limit to the max heap size.  Thus, direct memory in use can be significant.

However, trying this on two different platform and the result returned in gcstats is always -1:
{noformat}
Interval (ms) Max GC Elapsed (ms)Total GC Elapsed (ms)Stdev GC Elapsed (ms)   GC Reclaimed (MB)         Collections      Direct Memory Bytes
2792770717                 274              665186                  54      41276288089024                6120                       -1{noformat}
Bug: Debian packaging broken by quilt?
Status: Resolved
Priority: Normal
Resolution: Cannot Reproduce
Created: 04/Oct/23 16:57
Resolved: 09/Oct/23 13:09

Something has changed in the docker image that is breaking the debian packaging in all versions, similar to this:

{quote}
dpkg-buildpackage: info: source package cassandra
dpkg-buildpackage: info: source version 4.1.4-20231004git486acc68f1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by build <build@1518e06a5507>
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --tar-ignore=.git --before-build .
 fakeroot debian/rules clean
QUILT_PATCHES=debian/patches \
        quilt --quiltrc /dev/null pop -a -R || test $? = 1
No patch removed
make: *** [/usr/share/quilt/quilt.make:23: unpatch] Error 1
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2
{quote}
Bug: Test failure: secondary_indexes_test.TestPreJoinCallback.test_resume
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 10/Oct/23 16:43
Resolved: 10/Oct/23 19:51

As seen here: https://ci-cassandra.apache.org/job/Cassandra-5.0/60/testReport/dtest-novnode.secondary_indexes_test/TestPreJoinCallback/test_resume/

{quote}
failed on teardown with "Failed: Unexpected error found in node logs (see stdout for full details). Errors: [[node2] 'ERROR [Stream-Deserializer-/127.0.0.1:7000-ffd39504] 2023-10-09 16:12:59,153 StreamSession.java:702 - [Stream #b69e6f80-66be-11ee-b813-3bca425f16a7] Socket closed before session completion, peer 127.0.0.1:7000 is probably down.\njava.nio.channels.ClosedChannelException: null\n\tat org.apache.cassandra.net.AsyncStreamingInputPlus.reBuffer(AsyncStreamingInputPlus.java:119)\n\tat org.apache.cassandra.io.util.RebufferingInputStream.readByte(RebufferingInputStream.java:178)\n\tat org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:49)\n\tat org.apache.cassandra.streaming.StreamDeserializingTask.run(StreamDeserializingTask.java:59)\n\tat io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat java.base/java.lang.Thread.run(Thread.java:833)']"
{quote}
Bug: Add j17|j11_dtests_repeat and j17|j11_dtests_vnode_repeat among circle jobs
Status: Resolved
Priority: Normal
Resolution: Invalid
Created: 28/Nov/23 15:37
Resolved: 28/Nov/23 15:52

j17_dtests_repeat and j17_dtests_vnode_repeat do exist in circleci but they are not referenced in workflows. I basically can not run multiplexer on dtests in circle.

Same happens for their j11 counterparts.

Same applies for 3.0 where j8_dtests_repeat is, again, not referenced in workflows. I guess it will be same for all branches we have.
Bug: Support max SSTable size in sorted CQLSSTableWriter
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 18/Oct/23 23:31
Resolved: 30/Nov/23 09:52

The CQLSSTableWriter can produce a series of SSTables with a bounded size in the unsorted mode. The functionality is missing in the sorted CQLSSTableWriter.

It will be great to bringing the parity to the sorted mode, so that it is able to produce a series of size-bounded SSTable, instead of a single but giant one.

Unlike the unsorted CQLSSTableWriter, the max SSTable size in the sorted writer does not require buffering.
Bug: cassandra-driver-core-3.11.5 vulnerability: CVE-2023-4586
Status: Resolved
Priority: Normal
Resolution: Invalid
Created: 11/Oct/23 10:32
Resolved: 05/Dec/23 15:25

This is failing OWASP: https://nvd.nist.gov/vuln/detail/CVE-2023-4586

but appears to be a false positive.
Bug: CEP-15: (C*/Accord)  Schema based fast path reconfiguration
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 07/Nov/23 23:10
Resolved: 21/Dec/23 20:29

This adds availability aware accord fast path reconfiguration, as well as user configurable fast path settings, which are set at the keyspace level and (optionally) at the table level for increased granularity.

The major parts are:

*Add availability information to cluster metadata*

Accord topology in C* is not stored in cluster metadata, but is meant to calculated deterministically from cluster metadata state at a given epoch. This adds the availability data, as well as the failure detector / gossip listener and state change deduplication to CMS.

*Move C* accord keys/topology from keyspace prefixes to tableid prefixes*

To support per-table fast path settings, topologies and keys need to include the table id. Since accord topologies could begin to consume a lot of memory in clusters with a lot of nodes and tables, topology generation has been updated to reuse previously allocated shards / shard parts where possible, which will only increase heap sizes when things actually change.

*Make fast path settings configurable via schema*

There are 2.5 strategies: Simple, Parameterized, and InheritKeyspaceSettings. Simple will use as many available nodes as possible for the fast path electorate, this is the default for the keyspace fast path strategy. Parameterized allows you to set a target size, and preferred datacenters for the FP electorate. InheritKeyspace tells topology generation to just use the keyspace fast path settings, and is the default for the table fast path strategy.
Bug: "Query start time" in native transport request threads should be the task enqueue time
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 20/Dec/23 22:29
Resolved: 31/May/24 09:38

Recently, our Cassandra 4.0.6 cluster experienced an outage due to a surge in expensive traffic from the application side. This surge involved a large volume of costly read queries, which took a considerable amount of time to process on the server side. The client had timeout settings; if a request timed out, it might trigger the sending of new requests. Since the server nodes were overloaded, numerous nodes had hundreds of thousands of tasks queued in the Native-Transport-Request pending queue. I expected that once the application ceased sending requests, the server node would quickly return to normal, as most requests in the queue were over half an hour old and should have timed out rapidly, clearing the queue. However, it actually took an hour to clear the native transport's pending queue, even with native transport disabled. Upon examining the code, I noticed that for read/write requests, the [queryStartNanoTime|https://github.com/apache/cassandra/blob/cassandra-4.0/src/java/org/apache/cassandra/transport/Dispatcher.java#L78], which determines if a request has timed out, only begins when the task starts processing. This means that no matter how long a request has been pending, it doesn't contribute to the timeout. I believe this is incorrect. The timer should start when the Cassandra server receives the request or when it enqueues the task, not when the request/task begins processing. This way, an overloaded node with many pending tasks can quickly discard timed-out requests and recover from an outage once new requests stop.
Bug: Test Failure: org.apache.cassandra.db.DiskBoundaryManagerTest.alterKeyspaceTest-cdc_jdk17_x86_64 
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 05/Dec/23 00:29
Resolved: 07/Dec/23 15:37

[https://ci-cassandra.apache.org/job/Cassandra-trunk/1801/testReport/org.apache.cassandra.db/DiskBoundaryManagerTest/alterKeyspaceTest_cdc_jdk17_x86_64/]
{code:java}

Error Message
expected not same

Stacktrace
junit.framework.AssertionFailedError: expected not same at org.apache.cassandra.db.DiskBoundaryManagerTest.alterKeyspaceTest(DiskBoundaryManagerTest.java:140) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
{code}
Bug: Test Failure: org.apache.cassandra.distributed.test.ReadRepairTest#readRepairRTRangeMovementTest
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 27/Nov/23 11:37
Resolved: 07/Dec/23 17:17

{noformat}
java.lang.AssertionError: Expected a different error message, but got Operation failed - received 2 responses and 1 failures: INVALID_ROUTING from /127.0.0.2:7012

	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.apache.cassandra.distributed.test.ReadRepairTest.readRepairRTRangeMovementTest(ReadRepairTest.java:424)
	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)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
	at com.intellij.rt.junit.IdeaTestRunner$Repeater$1.execute(IdeaTestRunner.java:38)
	at com.intellij.rt.execution.junit.TestsRepeater.repeat(TestsRepeater.java:11)
	at com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:35)
	at com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:232)
	at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:55)
{noformat}

Manual testing in IntelliJ / trunk. Detected during investigation of test failures of CASSANDRA-18464
Bug: Test Failure: org.apache.cassandra.locator.PropertyFileSnitchTest.configContainsRemoteConfig-cdc_jdk17_x86_64
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 05/Dec/23 22:34
Resolved: 07/Dec/23 17:16

h3.  
{code:java}
Error Message
Multiple entries with same key: 127.0.0.1:7012=OTHER_DC1:OTHER_RAC1 and 127.0.0.1:7012=DC1:RAC1

Stacktrace
java.lang.IllegalArgumentException: Multiple entries with same key: 127.0.0.1:7012=OTHER_DC1:OTHER_RAC1 and 127.0.0.1:7012=DC1:RAC1 at com.google.common.collect.ImmutableMap.conflictException(ImmutableMap.java:378) at com.google.common.collect.ImmutableMap.checkNoConflict(ImmutableMap.java:372) at com.google.common.collect.RegularImmutableMap.checkNoConflictInKeyBucket(RegularImmutableMap.java:246) at com.google.common.collect.RegularImmutableMap.fromEntryArrayCheckingBucketOverflow(RegularImmutableMap.java:133) at com.google.common.collect.RegularImmutableMap.fromEntryArray(RegularImmutableMap.java:95) at com.google.common.collect.RegularImmutableMap.fromEntries(RegularImmutableMap.java:78) at com.google.common.collect.ImmutableMap.of(ImmutableMap.java:139) at org.apache.cassandra.locator.PropertyFileSnitchTest.configContainsRemoteConfig(PropertyFileSnitchTest.java:121) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
{code}
Bug: Test failure: org.apache.cassandra.distributed.test.ring.DecommissionTest.testDecomDirectoryMinMaxVersions
Status: Triage Needed
Priority: Normal
Created: 22/Dec/23 07:51

https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/1252/workflows/234ccc92-65f2-4adb-a68a-a5505398f4d0/jobs/63795/tests

{noformat}
java.lang.RuntimeException: java.util.concurrent.TimeoutException
	at org.apache.cassandra.utils.Throwables.maybeFail(Throwables.java:79)
	at org.apache.cassandra.utils.FBUtilities.waitOnFutures(FBUtilities.java:547)
	at org.apache.cassandra.distributed.impl.AbstractCluster.close(AbstractCluster.java:1098)
	at org.apache.cassandra.distributed.test.ring.DecommissionTest.testDecomDirectoryMinMaxVersions(DecommissionTest.java:130)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Caused by: java.util.concurrent.TimeoutException
	at org.apache.cassandra.utils.concurrent.AbstractFuture.get(AbstractFuture.java:253)
	at org.apache.cassandra.utils.FBUtilities.waitOnFutures(FBUtilities.java:539)
{noformat}
Bug: Test failure: write_failures_test.TestWriteFailures.test_mutation_any
Status: Triage Needed
Priority: Normal
Created: 22/Dec/23 07:53

https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/1252/workflows/a10c9859-3ded-42eb-804b-97dad97bbd2f/jobs/63753/tests

{noformat}
failed on teardown with "Failed: Unexpected error found in node logs (see stdout for full details). Errors: [[node3] 'ERROR [GossipStage:1] 2023-12-21 16:51:00,081 MessagingService.java:488 - Cannot send the message (from:/127.0.0.3:7000, type:GOSSIP verb:GOSSIP_DIGEST_ACK2) to /127.0.0.2:7000, as messaging service is shutting down']"
Unexpected error found in node logs (see stdout for full details). Errors: [[node3] 'ERROR [GossipStage:1] 2023-12-21 16:51:00,081 MessagingService.java:488 - Cannot send the message (from:/127.0.0.3:7000, type:GOSSIP verb:GOSSIP_DIGEST_ACK2) to /127.0.0.2:7000, as messaging service is shutting down']
{noformat}
Bug: SAI post-filtering reads don't update local table latency metrics
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 18/Oct/23 21:39
Resolved: 26/Feb/24 21:35

Once an SAI index finds matches (primary keys), it reads the associated rows and post-filters them to incorporate partial writes, tombstones, etc. However, those reads are not currently updating the local table latency metrics. It should be simple enough to attach a metrics recording transformation to the iterator produced by querying local storage.
Bug: Test failure: CQLVectorTest fails with heap_buffers
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 05/Dec/23 08:17
Resolved: 30/Jan/24 22:20

When {{memtable_allocation_type}} is set to {{heap_buffers}}, the {{udf}} test fails with
{code}
org.apache.cassandra.cql3.functions.types.exceptions.InvalidTypeException: Invalid 32-bits integer value, expecting 4 bytes but got 6
	at org.apache.cassandra.cql3.functions.types.TypeCodec$IntCodec.deserializeNoBoxing(TypeCodec.java:1695)
	at org.apache.cassandra.cql3.functions.types.TypeCodec$PrimitiveIntCodec.deserialize(TypeCodec.java:842)
	at org.apache.cassandra.cql3.functions.types.TypeCodec$PrimitiveIntCodec.deserialize(TypeCodec.java:819)
	at org.apache.cassandra.cql3.functions.types.VectorCodec$FixedLength.deserialize(VectorCodec.java:135)
	at org.apache.cassandra.cql3.functions.types.VectorCodec$FixedLength.deserialize(VectorCodec.java:83)
	at org.apache.cassandra.cql3.functions.types.TypeCodec$AbstractCollectionCodec.deserialize(TypeCodec.java:2141)
	at org.apache.cassandra.cql3.functions.types.TypeCodec$AbstractCollectionCodec.deserialize(TypeCodec.java:2082)
	at org.apache.cassandra.cql3.functions.UDFDataType.compose(UDFDataType.java:180)
	at org.apache.cassandra.cql3.functions.FunctionArguments.set(FunctionArguments.java:142)
	at org.apache.cassandra.cql3.selection.AbstractFunctionSelector.setArg(AbstractFunctionSelector.java:277)
	at org.apache.cassandra.cql3.selection.ScalarFunctionSelector.getOutput(ScalarFunctionSelector.java:58)
	at org.apache.cassandra.cql3.selection.Selection$SelectionWithProcessing$1.getOutputRow(Selection.java:605)
	at org.apache.cassandra.cql3.selection.ResultSetBuilder.getOutputRow(ResultSetBuilder.java:175)
	at org.apache.cassandra.cql3.selection.ResultSetBuilder.build(ResultSetBuilder.java:162)
	at org.apache.cassandra.cql3.statements.SelectStatement.process(SelectStatement.java:999)
	at org.apache.cassandra.cql3.statements.SelectStatement.processResults(SelectStatement.java:564)
	at org.apache.cassandra.cql3.statements.SelectStatement.executeInternal(SelectStatement.java:600)
	at org.apache.cassandra.cql3.statements.SelectStatement.executeLocally(SelectStatement.java:570)
	at org.apache.cassandra.cql3.statements.SelectStatement.executeLocally(SelectStatement.java:108)
	at org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:445)
	at org.apache.cassandra.cql3.CQLTester.executeFormattedQuery(CQLTester.java:1597)
	at org.apache.cassandra.cql3.CQLTester.execute(CQLTester.java:1576)
	at org.apache.cassandra.cql3.validation.operations.CQLVectorTest.udf(CQLVectorTest.java:427)
{code}