[jira] [Commented] (CASSANDRA-18969) Pre-release required legal changes for cassandra-java-driver
[ https://issues.apache.org/jira/browse/CASSANDRA-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782408#comment-17782408 ] Justin Mclean commented on CASSANDRA-18969: --- Thanks, Henry, for answering my question (originally asked on the incubator general list) that these are indeed optional. Regarding dependencies, A Category X build dependency may output content that is under a license not compatible with the Apache license or if it's under a "community license", even if the license seems compatible, it may impose further restrictions that are not compatible with the Apache license e.g non-commercial use, so it always best to double-check. > Pre-release required legal changes for cassandra-java-driver > > > Key: CASSANDRA-18969 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18969 > Project: Cassandra > Issue Type: Sub-task > Components: Build >Reporter: Michael Semb Wever >Priority: Urgent > Time Spent: 2h 40m > Remaining Estimate: 0h > > TODO > * there is still code copyrighted to others that isn't mentioned in > NOTICE.txt (e.g. ci/install-jdk.sh ) > * "© DataStax" still appears in the README > * spotbugs is LGPL, in 4.x, and not correctly made provided scope > * add any BSD/MIT deps to LICENCE > * ensure copyright headers are on all files, use rat plugin > These things must be done before a release. > Cat X deps we included as build tool by using scope provided we should put a > test in to ensure they work at runtime without the dep doesn't regress in the > future. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra-website) branch asf-staging updated (e37a649c7 -> 04f026975)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard e37a649c7 generate docs for f996c739 new 04f026975 generate docs for f996c739 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (e37a649c7) \ N -- N -- N refs/heads/asf-staging (04f026975) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4881412 -> 4881412 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18949) Test failure: org.apache.cassandra.tools.nodetool.ClearSnapshotTest.testClearSnapshot_RemoveByName-.jdk11.arch=x86_64.python2.7
[
https://issues.apache.org/jira/browse/CASSANDRA-18949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782378#comment-17782378
]
Ekaterina Dimitrova edited comment on CASSANDRA-18949 at 11/3/23 2:31 AM:
--
There is no more in the logs of nightlies than the error reported here.
I tried to reproduce the reported failure on a commit before the fix of
CASSANDRA-18747 unsuccessfully - both locally and in CI -
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18949-5.0]
One observation is that this test does not create keyspace_04, that one is
created by calling _prepareData,_ which is called by the other two test methods
in the same class but not the one that was reported -
testClearSnapshotWithOlderThanFlag and
testClearSnapshotWithOlderThanTimestampFlag.
So at the end I managed to reproduce by changing the Schema#unload method and
then running the whole test class (if I run the testClearSnapshot_RemoveByName
separately, it passes):
{code:java}
private synchronized void unload(KeyspaceMetadata ksm)
{
distributedKeyspaces = distributedKeyspaces.without(ksm.name);
if(!ksm.name.equals("keyspace_04"))
distributedAndLocalKeyspaces =
distributedAndLocalKeyspaces.without(ksm.name);
this.tableMetadataRefCache = tableMetadataRefCache.withRemovedRefs(ksm);
SchemaDiagnostics.metadataRemoved(this, ksm);
}{code}
I suspect after the fix in CASSANDRA-18747 we can close this one. [~blerer] ,
do you agree with this analysis?
was (Author: e.dimitrova):
I tried to reproduce this one on a commit before the fix of CASSANDRA-18747
unsuccessfully - both locally and in CI -
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18949-5.0
One observation is that this test does not create keyspace_04, that one is
created by calling _prepareData,_ which is called by the other two test methods
in the same class but not the one that was reported -
testClearSnapshotWithOlderThanFlag and
testClearSnapshotWithOlderThanTimestampFlag.
So at the end I managed to reproduce by changing the Schema#unload method and
then running the whole test class (if I run the testClearSnapshot_RemoveByName
separately, it passes):
{code:java}
private synchronized void unload(KeyspaceMetadata ksm)
{
distributedKeyspaces = distributedKeyspaces.without(ksm.name);
if(!ksm.name.equals("keyspace_04"))
distributedAndLocalKeyspaces =
distributedAndLocalKeyspaces.without(ksm.name);
this.tableMetadataRefCache = tableMetadataRefCache.withRemovedRefs(ksm);
SchemaDiagnostics.metadataRemoved(this, ksm);
}{code}
I suspect after the fix in CASSANDRA-18747 we can close this one. [~blerer] ,
do you agree with this analysis?
> Test failure:
> org.apache.cassandra.tools.nodetool.ClearSnapshotTest.testClearSnapshot_RemoveByName-.jdk11.arch=x86_64.python2.7
> ---
>
> Key: CASSANDRA-18949
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18949
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0-rc
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1747/testReport/org.apache.cassandra.tools.nodetool/ClearSnapshotTest/testClearSnapshot_RemoveByName__jdk11_arch_x86_64_python2_7/]
> h3.
> {code:java}
> Error Message
> [bin/nodetool, -p, 36753, -h, 127.0.0.1, snapshot, -t, some-name] exited with
> code 2 stderr: error: Unknown keyspace keyspace_04 -- StackTrace --
> java.lang.AssertionError: Unknown keyspace keyspace_04 at
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324) at
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162) at
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)
> at
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)
> at org.apache.cassandra.db.Keyspace.open(Keyspace.java:162) at
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151) at
> com.google.common.collect.Iterators$6.transform(Iterators.java:828) at
> com.google.common.collect.TransformedIterator.next(TransformedIterator.java:52)
> at
> org.apache.cassandra.service.StorageService.takeSnapshot(StorageService.java:4356)
> at
> org.apache.cassandra.service.StorageService.takeSnapshot(StorageService.java:4221)
> 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
>
[jira] [Comment Edited] (CASSANDRA-18949) Test failure: org.apache.cassandra.tools.nodetool.ClearSnapshotTest.testClearSnapshot_RemoveByName-.jdk11.arch=x86_64.python2.7
[
https://issues.apache.org/jira/browse/CASSANDRA-18949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782378#comment-17782378
]
Ekaterina Dimitrova edited comment on CASSANDRA-18949 at 11/3/23 2:31 AM:
--
There is no more in the
[logs|https://nightlies.apache.org/cassandra/trunk/Cassandra-trunk-test/1814/Cassandra-trunk-test/jdk=jdk_11_latest,label=cassandra,split=1/]
of nightlies than the error reported here.
I tried to reproduce the reported failure on a commit before the fix of
CASSANDRA-18747 unsuccessfully - both locally and in CI -
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18949-5.0]
One observation is that this test does not create keyspace_04, that one is
created by calling _prepareData,_ which is called by the other two test methods
in the same class but not the one that was reported -
testClearSnapshotWithOlderThanFlag and
testClearSnapshotWithOlderThanTimestampFlag.
So at the end I managed to reproduce by changing the Schema#unload method and
then running the whole test class (if I run the testClearSnapshot_RemoveByName
separately, it passes):
{code:java}
private synchronized void unload(KeyspaceMetadata ksm)
{
distributedKeyspaces = distributedKeyspaces.without(ksm.name);
if(!ksm.name.equals("keyspace_04"))
distributedAndLocalKeyspaces =
distributedAndLocalKeyspaces.without(ksm.name);
this.tableMetadataRefCache = tableMetadataRefCache.withRemovedRefs(ksm);
SchemaDiagnostics.metadataRemoved(this, ksm);
}{code}
I suspect after the fix in CASSANDRA-18747 we can close this one. [~blerer] ,
do you agree with this analysis?
was (Author: e.dimitrova):
There is no more in the logs of nightlies than the error reported here.
I tried to reproduce the reported failure on a commit before the fix of
CASSANDRA-18747 unsuccessfully - both locally and in CI -
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18949-5.0]
One observation is that this test does not create keyspace_04, that one is
created by calling _prepareData,_ which is called by the other two test methods
in the same class but not the one that was reported -
testClearSnapshotWithOlderThanFlag and
testClearSnapshotWithOlderThanTimestampFlag.
So at the end I managed to reproduce by changing the Schema#unload method and
then running the whole test class (if I run the testClearSnapshot_RemoveByName
separately, it passes):
{code:java}
private synchronized void unload(KeyspaceMetadata ksm)
{
distributedKeyspaces = distributedKeyspaces.without(ksm.name);
if(!ksm.name.equals("keyspace_04"))
distributedAndLocalKeyspaces =
distributedAndLocalKeyspaces.without(ksm.name);
this.tableMetadataRefCache = tableMetadataRefCache.withRemovedRefs(ksm);
SchemaDiagnostics.metadataRemoved(this, ksm);
}{code}
I suspect after the fix in CASSANDRA-18747 we can close this one. [~blerer] ,
do you agree with this analysis?
> Test failure:
> org.apache.cassandra.tools.nodetool.ClearSnapshotTest.testClearSnapshot_RemoveByName-.jdk11.arch=x86_64.python2.7
> ---
>
> Key: CASSANDRA-18949
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18949
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0-rc
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1747/testReport/org.apache.cassandra.tools.nodetool/ClearSnapshotTest/testClearSnapshot_RemoveByName__jdk11_arch_x86_64_python2_7/]
> h3.
> {code:java}
> Error Message
> [bin/nodetool, -p, 36753, -h, 127.0.0.1, snapshot, -t, some-name] exited with
> code 2 stderr: error: Unknown keyspace keyspace_04 -- StackTrace --
> java.lang.AssertionError: Unknown keyspace keyspace_04 at
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324) at
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162) at
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)
> at
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)
> at org.apache.cassandra.db.Keyspace.open(Keyspace.java:162) at
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151) at
> com.google.common.collect.Iterators$6.transform(Iterators.java:828) at
> com.google.common.collect.TransformedIterator.next(TransformedIterator.java:52)
> at
> org.apache.cassandra.service.StorageService.takeSnapshot(StorageService.java:4356)
> at
> org.apache.cassandra.service.StorageService.takeSnapshot(StorageService.java:4221)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
>
[jira] [Commented] (CASSANDRA-18934) Downgrade to 4.1 fails due to schema changes
[
https://issues.apache.org/jira/browse/CASSANDRA-18934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782379#comment-17782379
]
Ekaterina Dimitrova commented on CASSANDRA-18934:
-
Thank you, [~maxwellguo] !
> Downgrade to 4.1 fails due to schema changes
>
>
> Key: CASSANDRA-18934
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18934
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Startup and Shutdown
>Reporter: David Capwell
>Assignee: Maxwell Guo
>Priority: Normal
> Fix For: 5.0-beta, 5.0.x, 5.x
>
>
> We are required to support 5.0 downgrading to 4.1 as a migration step, but we
> don’t have tests to show this is working… I wrote a quick test to make sure a
> change we needed in Accord wouldn’t block the downgrade and see that we fail
> right now.
> {code}
> ERROR 20:56:39 Exiting due to error while processing commit log during
> initialization.
> org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException:
> Unexpected error deserializing mutation; saved to
> /var/folders/h1/s_3p1x3s3hl0hltbpck67m0hgn/T/mutation418421767150092dat.
> This may be caused by replaying a mutation against a table with the same
> name but incompatible schema. Exception follows: java.lang.RuntimeException:
> Unknown column compaction_properties during deserialization
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readMutation(CommitLogReader.java:464)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readSection(CommitLogReader.java:397)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:244)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:147)
> at
> org.apache.cassandra.db.commitlog.CommitLogReplayer.replayFiles(CommitLogReplayer.java:191)
> at
> org.apache.cassandra.db.commitlog.CommitLog.recoverFiles(CommitLog.java:223)
> at
> org.apache.cassandra.db.commitlog.CommitLog.recoverSegmentsOnDisk(CommitLog.java:204)
> {code}
> This was caused by a schema change in CASSANDRA-18061
> {code}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one
> * or more contributor license agreements. See the NOTICE file
> * distributed with this work for additional information
> * regarding copyright ownership. The ASF licenses this file
> * to you under the Apache License, Version 2.0 (the
> * "License"); you may not use this file except in compliance
> * with the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.cassandra.distributed.upgrade;
> import java.io.IOException;
> import java.io.File;
> import java.util.concurrent.atomic.AtomicBoolean;
> import org.junit.Test;
> import org.apache.cassandra.distributed.api.IUpgradeableInstance;
> public class DowngradeTest extends UpgradeTestBase
> {
> @Test
> public void test() throws Throwable
> {
> AtomicBoolean first = new AtomicBoolean(true);
> new TestCase()
> .nodes(1)
> .withConfig(c -> {
> if (first.compareAndSet(true, false))
> c.set("storage_compatibility_mode", "CASSANDRA_4");
> })
> .downgradeTo(v41)
> .setup(cluster -> {})
> // Uncomment if you want to test what happens after reading the commit log,
> which fails right now
> //.runBeforeNodeRestart((cluster, nodeId) -> {
> //IUpgradeableInstance inst = cluster.get(nodeId);
> //File f = new File((String)
> inst.config().get("commitlog_directory"));
> //deleteRecursive(f);
> //})
> .runAfterClusterUpgrade(cluster -> {})
> .run();
> }
> private void deleteRecursive(File f)
> {
> if (f.isDirectory())
> {
> File[] children = f.listFiles();
> if (children != null)
> {
> for (File c : children)
> deleteRecursive(c);
> }
> }
> f.delete();
> }
> }
> {code}
> {code}
> diff --git
> a/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
>
> b/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
> index 5ee8780204..b4111e3b44 100644
> ---
>
[jira] [Commented] (CASSANDRA-18949) Test failure: org.apache.cassandra.tools.nodetool.ClearSnapshotTest.testClearSnapshot_RemoveByName-.jdk11.arch=x86_64.python2.7
[
https://issues.apache.org/jira/browse/CASSANDRA-18949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782378#comment-17782378
]
Ekaterina Dimitrova commented on CASSANDRA-18949:
-
I tried to reproduce this one on a commit before the fix of CASSANDRA-18747
unsuccessfully - both locally and in CI -
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18949-5.0
One observation is that this test does not create keyspace_04, that one is
created by calling _prepareData,_ which is called by the other two test methods
in the same class but not the one that was reported -
testClearSnapshotWithOlderThanFlag and
testClearSnapshotWithOlderThanTimestampFlag.
So at the end I managed to reproduce by changing the Schema#unload method and
then running the whole test class (if I run the testClearSnapshot_RemoveByName
separately, it passes):
{code:java}
private synchronized void unload(KeyspaceMetadata ksm)
{
distributedKeyspaces = distributedKeyspaces.without(ksm.name);
if(!ksm.name.equals("keyspace_04"))
distributedAndLocalKeyspaces =
distributedAndLocalKeyspaces.without(ksm.name);
this.tableMetadataRefCache = tableMetadataRefCache.withRemovedRefs(ksm);
SchemaDiagnostics.metadataRemoved(this, ksm);
}{code}
I suspect after the fix in CASSANDRA-18747 we can close this one. [~blerer] ,
do you agree with this analysis?
> Test failure:
> org.apache.cassandra.tools.nodetool.ClearSnapshotTest.testClearSnapshot_RemoveByName-.jdk11.arch=x86_64.python2.7
> ---
>
> Key: CASSANDRA-18949
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18949
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0-rc
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1747/testReport/org.apache.cassandra.tools.nodetool/ClearSnapshotTest/testClearSnapshot_RemoveByName__jdk11_arch_x86_64_python2_7/]
> h3.
> {code:java}
> Error Message
> [bin/nodetool, -p, 36753, -h, 127.0.0.1, snapshot, -t, some-name] exited with
> code 2 stderr: error: Unknown keyspace keyspace_04 -- StackTrace --
> java.lang.AssertionError: Unknown keyspace keyspace_04 at
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324) at
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162) at
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)
> at
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)
> at org.apache.cassandra.db.Keyspace.open(Keyspace.java:162) at
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151) at
> com.google.common.collect.Iterators$6.transform(Iterators.java:828) at
> com.google.common.collect.TransformedIterator.next(TransformedIterator.java:52)
> at
> org.apache.cassandra.service.StorageService.takeSnapshot(StorageService.java:4356)
> at
> org.apache.cassandra.service.StorageService.takeSnapshot(StorageService.java:4221)
> 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
> sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) at
> jdk.internal.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566) at
> java.base/sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:260) at
> java.management/com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
> at
> java.management/com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
> at
> java.management/com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> at
> java.management/com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> at
> java.management/com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> at
> java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:809)
> at
> java.management/com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> at
> java.management.rmi/javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1466)
> at
>
[jira] [Assigned] (CASSANDRA-18934) Downgrade to 4.1 fails due to schema changes
[
https://issues.apache.org/jira/browse/CASSANDRA-18934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxwell Guo reassigned CASSANDRA-18934:
---
Assignee: Maxwell Guo
> Downgrade to 4.1 fails due to schema changes
>
>
> Key: CASSANDRA-18934
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18934
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Startup and Shutdown
>Reporter: David Capwell
>Assignee: Maxwell Guo
>Priority: Normal
> Fix For: 5.0-beta, 5.0.x, 5.x
>
>
> We are required to support 5.0 downgrading to 4.1 as a migration step, but we
> don’t have tests to show this is working… I wrote a quick test to make sure a
> change we needed in Accord wouldn’t block the downgrade and see that we fail
> right now.
> {code}
> ERROR 20:56:39 Exiting due to error while processing commit log during
> initialization.
> org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException:
> Unexpected error deserializing mutation; saved to
> /var/folders/h1/s_3p1x3s3hl0hltbpck67m0hgn/T/mutation418421767150092dat.
> This may be caused by replaying a mutation against a table with the same
> name but incompatible schema. Exception follows: java.lang.RuntimeException:
> Unknown column compaction_properties during deserialization
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readMutation(CommitLogReader.java:464)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readSection(CommitLogReader.java:397)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:244)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:147)
> at
> org.apache.cassandra.db.commitlog.CommitLogReplayer.replayFiles(CommitLogReplayer.java:191)
> at
> org.apache.cassandra.db.commitlog.CommitLog.recoverFiles(CommitLog.java:223)
> at
> org.apache.cassandra.db.commitlog.CommitLog.recoverSegmentsOnDisk(CommitLog.java:204)
> {code}
> This was caused by a schema change in CASSANDRA-18061
> {code}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one
> * or more contributor license agreements. See the NOTICE file
> * distributed with this work for additional information
> * regarding copyright ownership. The ASF licenses this file
> * to you under the Apache License, Version 2.0 (the
> * "License"); you may not use this file except in compliance
> * with the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.cassandra.distributed.upgrade;
> import java.io.IOException;
> import java.io.File;
> import java.util.concurrent.atomic.AtomicBoolean;
> import org.junit.Test;
> import org.apache.cassandra.distributed.api.IUpgradeableInstance;
> public class DowngradeTest extends UpgradeTestBase
> {
> @Test
> public void test() throws Throwable
> {
> AtomicBoolean first = new AtomicBoolean(true);
> new TestCase()
> .nodes(1)
> .withConfig(c -> {
> if (first.compareAndSet(true, false))
> c.set("storage_compatibility_mode", "CASSANDRA_4");
> })
> .downgradeTo(v41)
> .setup(cluster -> {})
> // Uncomment if you want to test what happens after reading the commit log,
> which fails right now
> //.runBeforeNodeRestart((cluster, nodeId) -> {
> //IUpgradeableInstance inst = cluster.get(nodeId);
> //File f = new File((String)
> inst.config().get("commitlog_directory"));
> //deleteRecursive(f);
> //})
> .runAfterClusterUpgrade(cluster -> {})
> .run();
> }
> private void deleteRecursive(File f)
> {
> if (f.isDirectory())
> {
> File[] children = f.listFiles();
> if (children != null)
> {
> for (File c : children)
> deleteRecursive(c);
> }
> }
> f.delete();
> }
> }
> {code}
> {code}
> diff --git
> a/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
>
> b/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
> index 5ee8780204..b4111e3b44 100644
> ---
> a/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
> +++
>
[jira] [Commented] (CASSANDRA-18934) Downgrade to 4.1 fails due to schema changes
[
https://issues.apache.org/jira/browse/CASSANDRA-18934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782377#comment-17782377
]
Maxwell Guo commented on CASSANDRA-18934:
-
Thanks [~e.dimitrova], I will take a look at this.
> Downgrade to 4.1 fails due to schema changes
>
>
> Key: CASSANDRA-18934
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18934
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Startup and Shutdown
>Reporter: David Capwell
>Priority: Normal
> Fix For: 5.0-beta, 5.0.x, 5.x
>
>
> We are required to support 5.0 downgrading to 4.1 as a migration step, but we
> don’t have tests to show this is working… I wrote a quick test to make sure a
> change we needed in Accord wouldn’t block the downgrade and see that we fail
> right now.
> {code}
> ERROR 20:56:39 Exiting due to error while processing commit log during
> initialization.
> org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException:
> Unexpected error deserializing mutation; saved to
> /var/folders/h1/s_3p1x3s3hl0hltbpck67m0hgn/T/mutation418421767150092dat.
> This may be caused by replaying a mutation against a table with the same
> name but incompatible schema. Exception follows: java.lang.RuntimeException:
> Unknown column compaction_properties during deserialization
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readMutation(CommitLogReader.java:464)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readSection(CommitLogReader.java:397)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:244)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:147)
> at
> org.apache.cassandra.db.commitlog.CommitLogReplayer.replayFiles(CommitLogReplayer.java:191)
> at
> org.apache.cassandra.db.commitlog.CommitLog.recoverFiles(CommitLog.java:223)
> at
> org.apache.cassandra.db.commitlog.CommitLog.recoverSegmentsOnDisk(CommitLog.java:204)
> {code}
> This was caused by a schema change in CASSANDRA-18061
> {code}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one
> * or more contributor license agreements. See the NOTICE file
> * distributed with this work for additional information
> * regarding copyright ownership. The ASF licenses this file
> * to you under the Apache License, Version 2.0 (the
> * "License"); you may not use this file except in compliance
> * with the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.cassandra.distributed.upgrade;
> import java.io.IOException;
> import java.io.File;
> import java.util.concurrent.atomic.AtomicBoolean;
> import org.junit.Test;
> import org.apache.cassandra.distributed.api.IUpgradeableInstance;
> public class DowngradeTest extends UpgradeTestBase
> {
> @Test
> public void test() throws Throwable
> {
> AtomicBoolean first = new AtomicBoolean(true);
> new TestCase()
> .nodes(1)
> .withConfig(c -> {
> if (first.compareAndSet(true, false))
> c.set("storage_compatibility_mode", "CASSANDRA_4");
> })
> .downgradeTo(v41)
> .setup(cluster -> {})
> // Uncomment if you want to test what happens after reading the commit log,
> which fails right now
> //.runBeforeNodeRestart((cluster, nodeId) -> {
> //IUpgradeableInstance inst = cluster.get(nodeId);
> //File f = new File((String)
> inst.config().get("commitlog_directory"));
> //deleteRecursive(f);
> //})
> .runAfterClusterUpgrade(cluster -> {})
> .run();
> }
> private void deleteRecursive(File f)
> {
> if (f.isDirectory())
> {
> File[] children = f.listFiles();
> if (children != null)
> {
> for (File c : children)
> deleteRecursive(c);
> }
> }
> f.delete();
> }
> }
> {code}
> {code}
> diff --git
> a/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
>
> b/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
> index 5ee8780204..b4111e3b44 100644
> ---
> a/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
> +++
>
[PR] CASSANDRA-18969: Mark spotbugs-annotation and jcip-annotations as provided dependencies [4.12.x branch] [cassandra-java-driver]
hhughes opened a new pull request, #1756: URL: https://github.com/apache/cassandra-java-driver/pull/1756 patch by Henry Hughes; reviewed by Mick Semb Wever for CASSANDRA-18969 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] CASSANDRA-18969: Mark spotbugs-annotation and jcip-annotations as provided dependencies [4.11.x branch] [cassandra-java-driver]
hhughes opened a new pull request, #1755: URL: https://github.com/apache/cassandra-java-driver/pull/1755 patch by Henry Hughes; reviewed by Mick Semb Wever for CASSANDRA-18969 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] CASSANDRA-18969: Mark spotbugs-annotation and jcip-annotations as provided dependencies [4.8.0_fixes branch] [cassandra-java-driver]
hhughes opened a new pull request, #1754: URL: https://github.com/apache/cassandra-java-driver/pull/1754 patch by Henry Hughes; reviewed by Mick Semb Wever for CASSANDRA-18969 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] CASSANDRA-18969: Mark spotbugs-annotation and jcip-annotations as provided dependencies [4.7.x branch] [cassandra-java-driver]
hhughes opened a new pull request, #1753: URL: https://github.com/apache/cassandra-java-driver/pull/1753 patch by Henry Hughes; reviewed by Mick Semb Wever for CASSANDRA-18969 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] CASSANDRA-18969: Mark spotbugs-annotation and jcip-annotations as provided dependencies [4.6.1_fixes branch] [cassandra-java-driver]
hhughes opened a new pull request, #1752: URL: https://github.com/apache/cassandra-java-driver/pull/1752 patch by Henry Hughes; reviewed by Mick Semb Wever for CASSANDRA-18969 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] CASSANDRA-18969: Mark spotbugs-annotation and jcip-annotations as provided dependencies [4.6.x branch] [cassandra-java-driver]
hhughes opened a new pull request, #1751: URL: https://github.com/apache/cassandra-java-driver/pull/1751 patch by Henry Hughes; reviewed by Mick Semb Wever for CASSANDRA-18969 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] CASSANDRA-18969: Mark spotbugs-annotation and jcip-annotations as provided dependencies [4.5.0_fixes branch] [cassandra-java-driver]
hhughes opened a new pull request, #1750: URL: https://github.com/apache/cassandra-java-driver/pull/1750 patch by Henry Hughes; reviewed by Mick Semb Wever for CASSANDRA-18969 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] CASSANDRA-18969: Mark spotbugs-annotation and jcip-annotations as provided dependencies [4.5.x branch] [cassandra-java-driver]
hhughes opened a new pull request, #1749: URL: https://github.com/apache/cassandra-java-driver/pull/1749 patch by Henry Hughes; reviewed by Mick Semb Wever for CASSANDRA-18969 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] CASSANDRA-18969: Mark spotbugs-annotation and jcip-annotations as provided dependencies [4.4.0_fixes branch] [cassandra-java-driver]
hhughes opened a new pull request, #1748: URL: https://github.com/apache/cassandra-java-driver/pull/1748 patch by Henry Hughes; reviewed by Mick Semb Wever for CASSANDRA-18969 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] CASSANDRA-18969: Mark spotbugs-annotation and jcip-annotations as provided dependencies [4.3.0_fixes branch] [cassandra-java-driver]
hhughes opened a new pull request, #1747: URL: https://github.com/apache/cassandra-java-driver/pull/1747 patch by Henry Hughes; reviewed by Mick Semb Wever for CASSANDRA-18969 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] CASSANDRA-18969: Mark spotbugs-annotation and jcip-annotations as provided dependencies [4.3.x branch] [cassandra-java-driver]
hhughes opened a new pull request, #1746: URL: https://github.com/apache/cassandra-java-driver/pull/1746 patch by Henry Hughes; reviewed by Mick Semb Wever for CASSANDRA-18969 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] Mark spotbugs-annotation and jcip-annotations as provided dependencies [4.2.x branch] [cassandra-java-driver]
hhughes opened a new pull request, #1745: URL: https://github.com/apache/cassandra-java-driver/pull/1745 patch by Henry Hughes; reviewed by Mick Semb Wever for CASSANDRA-18969 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] CASSANDRA-18969: Mark spotbugs-annotation and jcip-annotations as provided dependencies [4.1.0_fixes branch] [cassandra-java-driver]
hhughes opened a new pull request, #1744: URL: https://github.com/apache/cassandra-java-driver/pull/1744 patch by Henry Hughes; reviewed by Mick Semb Wever for CASSANDRA-18969 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra-website) branch asf-staging updated (bc24f4cc4 -> e37a649c7)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard bc24f4cc4 generate docs for f996c739 new e37a649c7 generate docs for f996c739 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (bc24f4cc4) \ N -- N -- N refs/heads/asf-staging (e37a649c7) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: site-ui/build/ui-bundle.zip | Bin 4881412 -> 4881412 bytes 1 file changed, 0 insertions(+), 0 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18635) Test failure: org.apache.cassandra.distributed.test.UpgradeSSTablesTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782349#comment-17782349
]
Ekaterina Dimitrova commented on CASSANDRA-18635:
-
[~ifesdjeen] [~JoshuaMcKenzie], did you have any chance to look into this one?
Do we know whether this is a production or test bug to triage it better?
> Test failure: org.apache.cassandra.distributed.test.UpgradeSSTablesTest
> ---
>
> Key: CASSANDRA-18635
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18635
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> Seen here:
> https://app.circleci.com/pipelines/github/driftx/cassandra/1095/workflows/6114e2e3-8dcc-4bb0-b664-ae7d82c3349f/jobs/33405/tests
> {noformat}
> junit.framework.AssertionFailedError: expected:<0> but was:<2>
> at
> org.apache.cassandra.distributed.test.UpgradeSSTablesTest.upgradeSSTablesInterruptsOngoingCompaction(UpgradeSSTablesTest.java:86)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] JAVA-3051: Memory leak [cassandra-java-driver]
SiyaoIsHiding opened a new pull request, #1743: URL: https://github.com/apache/cassandra-java-driver/pull/1743 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18710) Test failure: org.apache.cassandra.io.DiskSpaceMetricsTest.testFlushSize-.jdk17 (from org.apache.cassandra.io.DiskSpaceMetricsTest-.jdk17)
[
https://issues.apache.org/jira/browse/CASSANDRA-18710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782331#comment-17782331
]
Ekaterina Dimitrova edited comment on CASSANDRA-18710 at 11/2/23 9:21 PM:
--
{quote}After CASSANDRA-17071 that has moved to CFS.onTableDropped and it seems
the timing of this now does cause the small flushes. I'm not super strong in
this area of the code but it seems like maybe this could be massaged again to
prevent this from happening as before?
{quote}
So if I read correctly, this _may be_ a 4.1+ regression?
[~jlewandowski] , [~blambov] , do you mind to take a look and advise, please?
was (Author: e.dimitrova):
{quote}After CASSANDRA-17071 that has moved to CFS.onTableDropped and it seems
the timing of this now does cause the small flushes. I'm not super strong in
this area of the code but it seems like maybe this could be massaged again to
prevent this from happening as before?
{quote}
So if I read correctly this is 4.1+ regression?
[~jlewandowski] , [~blambov] , do you mind to take a look and advise, please?
> Test failure:
> org.apache.cassandra.io.DiskSpaceMetricsTest.testFlushSize-.jdk17 (from
> org.apache.cassandra.io.DiskSpaceMetricsTest-.jdk17)
> --
>
> Key: CASSANDRA-18710
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18710
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.0-beta, 5.0.x, 5.x
>
> Attachments: org.apache.cassandra.io.DiskSpaceMetricsTest.txt
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1644/testReport/org.apache.cassandra.io/DiskSpaceMetricsTest/testFlushSize__jdk17/]
> h3.
> {code:java}
> Error Message
> expected:<7200.0> but was:<1367.83970468544>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<7200.0> but
> was:<1367.83970468544> at
> org.apache.cassandra.io.DiskSpaceMetricsTest.testFlushSize(DiskSpaceMetricsTest.java:119)
> 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}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18710) Test failure: org.apache.cassandra.io.DiskSpaceMetricsTest.testFlushSize-.jdk17 (from org.apache.cassandra.io.DiskSpaceMetricsTest-.jdk17)
[
https://issues.apache.org/jira/browse/CASSANDRA-18710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782331#comment-17782331
]
Ekaterina Dimitrova commented on CASSANDRA-18710:
-
{quote}After CASSANDRA-17071 that has moved to CFS.onTableDropped and it seems
the timing of this now does cause the small flushes. I'm not super strong in
this area of the code but it seems like maybe this could be massaged again to
prevent this from happening as before?
{quote}
So if I read correctly this is 4.1+ regression?
[~jlewandowski] , [~blambov] , do you mind to take a look and advise, please?
> Test failure:
> org.apache.cassandra.io.DiskSpaceMetricsTest.testFlushSize-.jdk17 (from
> org.apache.cassandra.io.DiskSpaceMetricsTest-.jdk17)
> --
>
> Key: CASSANDRA-18710
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18710
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.0-beta, 5.0.x, 5.x
>
> Attachments: org.apache.cassandra.io.DiskSpaceMetricsTest.txt
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1644/testReport/org.apache.cassandra.io/DiskSpaceMetricsTest/testFlushSize__jdk17/]
> h3.
> {code:java}
> Error Message
> expected:<7200.0> but was:<1367.83970468544>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<7200.0> but
> was:<1367.83970468544> at
> org.apache.cassandra.io.DiskSpaceMetricsTest.testFlushSize(DiskSpaceMetricsTest.java:119)
> 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}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18934) Downgrade to 4.1 fails due to schema changes
[
https://issues.apache.org/jira/browse/CASSANDRA-18934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782330#comment-17782330
]
Ekaterina Dimitrova commented on CASSANDRA-18934:
-
[~maxwellguo] , [~stefan.miklosovic] , [~jlewandowski] , I was unsure whether
you noticed this ticket. Is it on your radar to take a look at it? According to
the description it was caused by CASSANDRA-18061.
> Downgrade to 4.1 fails due to schema changes
>
>
> Key: CASSANDRA-18934
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18934
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Startup and Shutdown
>Reporter: David Capwell
>Priority: Normal
> Fix For: 5.0-beta, 5.0.x, 5.x
>
>
> We are required to support 5.0 downgrading to 4.1 as a migration step, but we
> don’t have tests to show this is working… I wrote a quick test to make sure a
> change we needed in Accord wouldn’t block the downgrade and see that we fail
> right now.
> {code}
> ERROR 20:56:39 Exiting due to error while processing commit log during
> initialization.
> org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException:
> Unexpected error deserializing mutation; saved to
> /var/folders/h1/s_3p1x3s3hl0hltbpck67m0hgn/T/mutation418421767150092dat.
> This may be caused by replaying a mutation against a table with the same
> name but incompatible schema. Exception follows: java.lang.RuntimeException:
> Unknown column compaction_properties during deserialization
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readMutation(CommitLogReader.java:464)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readSection(CommitLogReader.java:397)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:244)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:147)
> at
> org.apache.cassandra.db.commitlog.CommitLogReplayer.replayFiles(CommitLogReplayer.java:191)
> at
> org.apache.cassandra.db.commitlog.CommitLog.recoverFiles(CommitLog.java:223)
> at
> org.apache.cassandra.db.commitlog.CommitLog.recoverSegmentsOnDisk(CommitLog.java:204)
> {code}
> This was caused by a schema change in CASSANDRA-18061
> {code}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one
> * or more contributor license agreements. See the NOTICE file
> * distributed with this work for additional information
> * regarding copyright ownership. The ASF licenses this file
> * to you under the Apache License, Version 2.0 (the
> * "License"); you may not use this file except in compliance
> * with the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.cassandra.distributed.upgrade;
> import java.io.IOException;
> import java.io.File;
> import java.util.concurrent.atomic.AtomicBoolean;
> import org.junit.Test;
> import org.apache.cassandra.distributed.api.IUpgradeableInstance;
> public class DowngradeTest extends UpgradeTestBase
> {
> @Test
> public void test() throws Throwable
> {
> AtomicBoolean first = new AtomicBoolean(true);
> new TestCase()
> .nodes(1)
> .withConfig(c -> {
> if (first.compareAndSet(true, false))
> c.set("storage_compatibility_mode", "CASSANDRA_4");
> })
> .downgradeTo(v41)
> .setup(cluster -> {})
> // Uncomment if you want to test what happens after reading the commit log,
> which fails right now
> //.runBeforeNodeRestart((cluster, nodeId) -> {
> //IUpgradeableInstance inst = cluster.get(nodeId);
> //File f = new File((String)
> inst.config().get("commitlog_directory"));
> //deleteRecursive(f);
> //})
> .runAfterClusterUpgrade(cluster -> {})
> .run();
> }
> private void deleteRecursive(File f)
> {
> if (f.isDirectory())
> {
> File[] children = f.listFiles();
> if (children != null)
> {
> for (File c : children)
> deleteRecursive(c);
> }
> }
> f.delete();
> }
> }
> {code}
> {code}
> diff --git
> a/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
>
>
Re: [PR] CASSANDRA-18969: Mark spotbugs-annotation and jcip-annotations as provided dependencies [cassandra-java-driver]
hhughes commented on PR #1741: URL: https://github.com/apache/cassandra-java-driver/pull/1741#issuecomment-1791471450 Squashed and re-worded ✅ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] CASSANDRA-18969: move spotbugs-annotation and jcip-annotations to be provided dependencies [cassandra-java-driver]
michaelsembwever commented on PR #1741: URL: https://github.com/apache/cassandra-java-driver/pull/1741#issuecomment-1791462352 LGTM. Want to squash the commits, and use the C* commit msg format ? (then let me know and I'll merge it) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18992) Exclude jna transitive dependecy from the ohc library
[ https://issues.apache.org/jira/browse/CASSANDRA-18992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782309#comment-17782309 ] Ekaterina Dimitrova commented on CASSANDRA-18992: - I agree with you, but also, there was a mention on the other ticket that we do not exercise in tests very well the usage of ohc in the C* codebase. Thus, I was trying to be more careful. Any thoughts about what I mentioned about ASM? > Exclude jna transitive dependecy from the ohc library > - > > Key: CASSANDRA-18992 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18992 > Project: Cassandra > Issue Type: Task > Components: Dependencies >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.0-beta, 5.0.x, 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > The concern is related to the JNA dependency on the ohc library. We are now > using version 0.5.1 of the ohc library in Cassandra. The ohc 0.5.1 depends on > version 4.1.0 of the net.java.dev.jna . For the Cassandra project, JNA has > been updated since the 4.0 release version up to JNA 5.6.0 in CASSANDRA-16212 > to support running nodes on the arm64 architecture, so I assume that JNA > 4.1.0 is no longer in Casssandra's classpath. > The common practice in the Cassandra project is to exclude these kinds of > transitive dependencies when they are explicitly mentioned in the main parent > pom, since Ant may resolve them incorrectly. See comment: > https://issues.apache.org/jira/browse/CASSANDRA-14667?focusedCommentId=17765091=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17765091 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18969) Pre-release required legal changes for cassandra-java-driver
[ https://issues.apache.org/jira/browse/CASSANDRA-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782302#comment-17782302 ] Henry Hughes commented on CASSANDRA-18969: -- https://github.com/apache/cassandra-java-driver/pull/1741 is ready for review. This change moves spotbugs (and similar JCIP-annotaitons) to the provided scope. It includes tests that verify these jars, and a few others such as graal-sdk (also provided) and TinkerPop (optional) etc, are not pulled in when depending on java-driver's published jars. > Pre-release required legal changes for cassandra-java-driver > > > Key: CASSANDRA-18969 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18969 > Project: Cassandra > Issue Type: Sub-task > Components: Build >Reporter: Michael Semb Wever >Priority: Urgent > Time Spent: 20m > Remaining Estimate: 0h > > TODO > * there is still code copyrighted to others that isn't mentioned in > NOTICE.txt (e.g. ci/install-jdk.sh ) > * "© DataStax" still appears in the README > * spotbugs is LGPL, in 4.x, and not correctly made provided scope > * add any BSD/MIT deps to LICENCE > * ensure copyright headers are on all files, use rat plugin > These things must be done before a release. > Cat X deps we included as build tool by using scope provided we should put a > test in to ensure they work at runtime without the dep doesn't regress in the > future. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18992) Exclude jna transitive dependecy from the ohc library
[ https://issues.apache.org/jira/browse/CASSANDRA-18992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782274#comment-17782274 ] Maxim Muzafarov commented on CASSANDRA-18992: - [~e.dimitrova] Sure, give me a few days to build the ohc project and re-check all tests, I'll check it and get back here. However, since we use the Cassandra build/lib/jar classpath directory, which contains a newer version of the JNA library, to run tests it should be enough to run CI on the Cassandra side to ensure that this exclusion doesn't break anything. A newer version of the JNA will be in use by the tests that have row cache enabled (basically row_cache_size > 0). > Exclude jna transitive dependecy from the ohc library > - > > Key: CASSANDRA-18992 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18992 > Project: Cassandra > Issue Type: Task > Components: Dependencies >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.0-beta, 5.0.x, 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > The concern is related to the JNA dependency on the ohc library. We are now > using version 0.5.1 of the ohc library in Cassandra. The ohc 0.5.1 depends on > version 4.1.0 of the net.java.dev.jna . For the Cassandra project, JNA has > been updated since the 4.0 release version up to JNA 5.6.0 in CASSANDRA-16212 > to support running nodes on the arm64 architecture, so I assume that JNA > 4.1.0 is no longer in Casssandra's classpath. > The common practice in the Cassandra project is to exclude these kinds of > transitive dependencies when they are explicitly mentioned in the main parent > pom, since Ant may resolve them incorrectly. See comment: > https://issues.apache.org/jira/browse/CASSANDRA-14667?focusedCommentId=17765091=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17765091 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18992) Exclude jna transitive dependecy from the ohc library
[ https://issues.apache.org/jira/browse/CASSANDRA-18992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18992: Fix Version/s: 5.0-beta > Exclude jna transitive dependecy from the ohc library > - > > Key: CASSANDRA-18992 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18992 > Project: Cassandra > Issue Type: Task > Components: Dependencies >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.0-beta, 5.0.x, 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > The concern is related to the JNA dependency on the ohc library. We are now > using version 0.5.1 of the ohc library in Cassandra. The ohc 0.5.1 depends on > version 4.1.0 of the net.java.dev.jna . For the Cassandra project, JNA has > been updated since the 4.0 release version up to JNA 5.6.0 in CASSANDRA-16212 > to support running nodes on the arm64 architecture, so I assume that JNA > 4.1.0 is no longer in Casssandra's classpath. > The common practice in the Cassandra project is to exclude these kinds of > transitive dependencies when they are explicitly mentioned in the main parent > pom, since Ant may resolve them incorrectly. See comment: > https://issues.apache.org/jira/browse/CASSANDRA-14667?focusedCommentId=17765091=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17765091 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18930) Test failure: dtest-novnode.sslnodetonode_test.TestNodeToNodeSSLEncryption.test_ssl_client_auth_required_fail
[
https://issues.apache.org/jira/browse/CASSANDRA-18930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18930:
---
Fix Version/s: 5.0-rc
(was: 5.x)
> Test failure:
> dtest-novnode.sslnodetonode_test.TestNodeToNodeSSLEncryption.test_ssl_client_auth_required_fail
>
> --
>
> Key: CASSANDRA-18930
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18930
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0-rc
>
>
> Seen on trunk:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1744/testReport/dtest-novnode.sslnodetonode_test/TestNodeToNodeSSLEncryption/test_ssl_client_auth_required_fail/]
> {code:java}
> Error Message
> assert False
> Stacktrace
> self = 0x7f45f37786d0> def test_ssl_client_auth_required_fail(self): """peers need
> to perform mutual auth (cient auth required), but do not supply the local
> cert""" credNode1 = sslkeygen.generate_credentials("127.0.0.1") credNode2 =
> sslkeygen.generate_credentials("127.0.0.2") self.setup_nodes(credNode1,
> credNode2, client_auth=True) self.fixture_dtest_setup.allow_log_errors = True
> self.cluster.start(no_wait=True) time.sleep(2) found =
> self._grep_msg(self.node1, _LOG_ERR_HANDSHAKE, _LOG_ERR_GENERAL) > assert
> found E assert False sslnodetonode_test.py:83: AssertionError
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18934) Downgrade to 4.1 fails due to schema changes
[
https://issues.apache.org/jira/browse/CASSANDRA-18934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-18934:
Fix Version/s: 5.0-beta
5.0.x
> Downgrade to 4.1 fails due to schema changes
>
>
> Key: CASSANDRA-18934
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18934
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Startup and Shutdown
>Reporter: David Capwell
>Priority: Normal
> Fix For: 5.0-beta, 5.0.x, 5.x
>
>
> We are required to support 5.0 downgrading to 4.1 as a migration step, but we
> don’t have tests to show this is working… I wrote a quick test to make sure a
> change we needed in Accord wouldn’t block the downgrade and see that we fail
> right now.
> {code}
> ERROR 20:56:39 Exiting due to error while processing commit log during
> initialization.
> org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException:
> Unexpected error deserializing mutation; saved to
> /var/folders/h1/s_3p1x3s3hl0hltbpck67m0hgn/T/mutation418421767150092dat.
> This may be caused by replaying a mutation against a table with the same
> name but incompatible schema. Exception follows: java.lang.RuntimeException:
> Unknown column compaction_properties during deserialization
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readMutation(CommitLogReader.java:464)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readSection(CommitLogReader.java:397)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:244)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:147)
> at
> org.apache.cassandra.db.commitlog.CommitLogReplayer.replayFiles(CommitLogReplayer.java:191)
> at
> org.apache.cassandra.db.commitlog.CommitLog.recoverFiles(CommitLog.java:223)
> at
> org.apache.cassandra.db.commitlog.CommitLog.recoverSegmentsOnDisk(CommitLog.java:204)
> {code}
> This was caused by a schema change in CASSANDRA-18061
> {code}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one
> * or more contributor license agreements. See the NOTICE file
> * distributed with this work for additional information
> * regarding copyright ownership. The ASF licenses this file
> * to you under the Apache License, Version 2.0 (the
> * "License"); you may not use this file except in compliance
> * with the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.cassandra.distributed.upgrade;
> import java.io.IOException;
> import java.io.File;
> import java.util.concurrent.atomic.AtomicBoolean;
> import org.junit.Test;
> import org.apache.cassandra.distributed.api.IUpgradeableInstance;
> public class DowngradeTest extends UpgradeTestBase
> {
> @Test
> public void test() throws Throwable
> {
> AtomicBoolean first = new AtomicBoolean(true);
> new TestCase()
> .nodes(1)
> .withConfig(c -> {
> if (first.compareAndSet(true, false))
> c.set("storage_compatibility_mode", "CASSANDRA_4");
> })
> .downgradeTo(v41)
> .setup(cluster -> {})
> // Uncomment if you want to test what happens after reading the commit log,
> which fails right now
> //.runBeforeNodeRestart((cluster, nodeId) -> {
> //IUpgradeableInstance inst = cluster.get(nodeId);
> //File f = new File((String)
> inst.config().get("commitlog_directory"));
> //deleteRecursive(f);
> //})
> .runAfterClusterUpgrade(cluster -> {})
> .run();
> }
> private void deleteRecursive(File f)
> {
> if (f.isDirectory())
> {
> File[] children = f.listFiles();
> if (children != null)
> {
> for (File c : children)
> deleteRecursive(c);
> }
> }
> f.delete();
> }
> }
> {code}
> {code}
> diff --git
> a/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
>
> b/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
> index 5ee8780204..b4111e3b44 100644
> ---
> a/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
> +++
>
[jira] [Commented] (CASSANDRA-18933) Correct comment for nc SSTable format
[
https://issues.apache.org/jira/browse/CASSANDRA-18933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782208#comment-17782208
]
Francisco Guerrero commented on CASSANDRA-18933:
[~mck] yeah, I took a look and it seems to be a problem in both
[trunk|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/io/sstable/format/big/BigFormat.java#L433C50-L433C50]
and
[5.0|https://github.com/apache/cassandra/blob/cassandra-5.0/src/java/org/apache/cassandra/io/sstable/format/big/BigFormat.java#L340]
given that 4.0 only supports `nb` format
> Correct comment for nc SSTable format
> -
>
> Key: CASSANDRA-18933
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18933
> Project: Cassandra
> Issue Type: Task
> Components: Local/SSTable
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Fix For: 5.0-alpha2, 5.0, 5.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> In [CASSANDRA-18134 |https://issues.apache.org/jira/browse/CASSANDRA-18134],
> the {{nc}} SSTable format was introduced. The patch was merged into {{5.0+}},
> however the comment in source incorrectly mentions that the format was added
> to version {{4.1}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18947) Test failure: dtest-novnode.disk_balance_test.TestDiskBalance.test_disk_balance_stress
[
https://issues.apache.org/jira/browse/CASSANDRA-18947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18947:
---
Fix Version/s: 5.0-rc
(was: 5.0.x)
> Test failure:
> dtest-novnode.disk_balance_test.TestDiskBalance.test_disk_balance_stress
> --
>
> Key: CASSANDRA-18947
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18947
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0-rc
>
>
> Seen here:
> https://ci-cassandra.apache.org/job/Cassandra-5.0/72/testReport/dtest-novnode.disk_balance_test/TestDiskBalance/test_disk_balance_stress/
> h3.
> {code:java}
> Error Message
> AssertionError: values not within 10.00% of the max: (2534183, 2762123,
> 2423706) (node1)
> Stacktrace
> self = def
> test_disk_balance_stress(self): cluster = self.cluster if
> self.dtest_config.use_vnodes:
> cluster.set_configuration_options(values={'num_tokens': 256})
> cluster.populate(4).start() node1 = cluster.nodes['node1']
> node1.stress(['write', 'n=50k', 'no-warmup', '-rate', 'threads=100',
> '-schema', 'replication(factor=3)',
> 'compaction(strategy=SizeTieredCompactionStrategy,enabled=false)'])
> cluster.flush() # make sure the data directories are balanced: for node in
> cluster.nodelist(): > self.assert_balanced(node) disk_balance_test.py:48: _ _
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> disk_balance_test.py:186: in assert_balanced assert_almost_equal(*new_sums,
> error=0.1, error_message=node.name) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ args = (2534183, 2762123, 2423706)
> kwargs = {'error': 0.1, 'error_message': 'node1'}, error = 0.1, vmax =
> 2762123 vmin = 2423706, error_message = 'node1' def
> assert_almost_equal(*args, **kwargs): """ Assert variable number of arguments
> all fall within a margin of error. @params *args variable number of numerical
> arguments to check @params error Optional margin of error. Default 0.16
> @params error_message Optional error message to print. Default '' Examples:
> assert_almost_equal(sizes[2], init_size) assert_almost_equal(ttl_session1,
> ttl_session2[0][0], error=0.005) """ error = kwargs['error'] if 'error' in
> kwargs else 0.16 vmax = max(args) vmin = min(args) error_message = '' if
> 'error_message' not in kwargs else kwargs['error_message'] assert vmin > vmax
> * (1.0 - error) or vmin == vmax, \ > "values not within {:.2f}% of the max:
> {} ({})".format(error * 100, args, error_message) E AssertionError: values
> not within 10.00% of the max: (2534183, 2762123, 2423706) (node1)
> tools/assertions.py:206: AssertionError
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18911) KeyCacheTest is failing with sstable_preemptive_open_interval < 0
[ https://issues.apache.org/jira/browse/CASSANDRA-18911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-18911: --- Fix Version/s: 5.0-beta (was: 5.0) > KeyCacheTest is failing with sstable_preemptive_open_interval < 0 > - > > Key: CASSANDRA-18911 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18911 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Jacek Lewandowski >Assignee: Jacek Lewandowski >Priority: Normal > Fix For: 5.0-beta, 5.1 > > > Discovered by [~maedhroz] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18744) cassandra-stress in simplenative mode and prepared fails with exceptions
[ https://issues.apache.org/jira/browse/CASSANDRA-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Bychkov reassigned CASSANDRA-18744: -- Assignee: Dmitry Bychkov > cassandra-stress in simplenative mode and prepared fails with exceptions > > > Key: CASSANDRA-18744 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18744 > Project: Cassandra > Issue Type: Bug > Components: Tool/stress >Reporter: Brad Schoening >Assignee: Dmitry Bychkov >Priority: Low > Fix For: 4.0.x, 4.1.x, 5.x > > > % cassandra-stress write n=10 -mode simplenative cql3 prepared > ... > ap'; org.apache.cassandra.transport.messages.ResultMessage$Prepared is in > unnamed module of loader 'app') > java.lang.ClassCastException: class [B cannot be cast to class > org.apache.cassandra.transport.messages.ResultMessage$Prepared ([B is in > module java.base of loader 'bootstrap'; > org.apache.cassandra.transport.messages.ResultMessage$Prepared is in unnamed > module of loader 'app') > java.io.IOException: Operation x10 on key(s) [4e334f364c4c4b373530]: Error > executing: (ClassCastException): class [B cannot be cast to class > org.apache.cassandra.transport.messages.ResultMessage$Prepared ([B is in > module java.base of loader 'bootstrap'; > org.apache.cassandra.transport.messages.ResultMessage$Prepared is in unnamed > module of loader 'app') > > at org.apache.cassandra.stress.Operation.error(Operation.java:127) > at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:91) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:99) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:242) > at > org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:471) > java.io.IOException: Operation x10 on key(s) [373038504b3436363830]: Error > executing: (ClassCastException): class [B cannot be cast to class > org.apache.cassandra.transport.messages.ResultMessage$Prepared ([B is in > module java.base of loader 'bootstrap'; > org.apache.cassandra.transport.messages.ResultMessage$Prepared is in unnamed > module of loader 'app') > > at org.apache.cassandra.stress.Operation.error(Operation.java:127) > at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:91) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:99) > at > org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:242) > at > org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:471) > java.lang.RuntimeException: Failed to execute warmup > at org.apache.cassandra.stress.StressAction.warmup(StressAction.java:128) > at org.apache.cassandra.stress.StressAction.run(StressAction.java:71) > at org.apache.cassandra.stress.Stress.run(Stress.java:101) > at org.apache.cassandra.stress.Stress.main(Stress.java:54) -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18963) Test Failure: sstableutil_test.TestSSTableUtil
[
https://issues.apache.org/jira/browse/CASSANDRA-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18963:
---
Fix Version/s: 5.0-beta
(was: 5.0-rc)
> Test Failure: sstableutil_test.TestSSTableUtil
> --
>
> Key: CASSANDRA-18963
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18963
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Priority: Normal
> Fix For: 5.0-beta
>
>
> Seems flaky
> [https://app.circleci.com/pipelines/github/driftx/cassandra/1342/workflows/9554c7b5-dd60-4f08-8db5-c954febc8ad6/jobs/58957/tests]
> *
> h4. test_abortedcompaction
> sstableutil_test.TestSSTableUtil
>
> {code:java}
> self = def
> test_abortedcompaction(self): """ @jira_ticket CASSANDRA-7066 @jira_ticket
> CASSANDRA-11497 Check that we can cleanup temporary files after a compaction
> is aborted. """ log_file_name = 'debug.log' cluster = self.cluster
> cluster.populate(1).start() node = cluster.nodelist()[0] numrecords = 25
> self._create_data(node, KeyspaceName, TableName, numrecords) finalfiles,
> tmpfiles = self._check_files(node, KeyspaceName, TableName) assert
> len(finalfiles) > 0, "Expected to find some final files" assert 0 ==
> len(tmpfiles), "Expected no tmp files" t = InterruptCompaction(node,
> TableName, filename=log_file_name, delay=2) t.start() try:
> logger.debug("Compacting...") node.compact() except ToolError: pass #
> expected to fail t.join() finalfiles =
> _normcase_all(self._invoke_sstableutil(KeyspaceName, TableName,
> type='final')) tmpfiles =
> _normcase_all(self._invoke_sstableutil(KeyspaceName, TableName, type='tmp'))
> # In most cases we should end up with some temporary files to clean up, but
> it may happen # that no temporary files are created if compaction finishes
> too early or starts too late # see CASSANDRA-11497 logger.debug("Got {} final
> files and {} tmp files after compaction was interrupted"
> .format(len(finalfiles), len(tmpfiles)))
> self._invoke_sstableutil(KeyspaceName, TableName, cleanup=True)
> self._check_files(node, KeyspaceName, TableName, finalfiles, []) # restart to
> make sure not data is lost logger.debug("Restarting node...") >
> node.start(wait_for_binary_proto=True) sstableutil_test.py:97: _ _ _ _ _ _ _
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> ../env3.6/lib/python3.6/site-packages/ccmlib/node.py:914: in start
> self.wait_for_binary_interface(from_mark=self.mark)
> ../env3.6/lib/python3.6/site-packages/ccmlib/node.py:702: in
> wait_for_binary_interface self.watch_log_for("Starting listening for CQL
> clients", **kwargs) ../env3.6/lib/python3.6/site-packages/ccmlib/node.py:599:
> in watch_log_for self.raise_node_error_if_cassandra_process_is_terminated() _
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> self = def
> raise_node_error_if_cassandra_process_is_terminated(self): if not
> self._is_pid_running(): msg = "C* process with {pid} is
> terminated".format(pid=self.pid) common.debug(msg) > raise NodeError(msg) E
> ccmlib.node.NodeError: C* process with 19530 is terminated
> ../env3.6/lib/python3.6/site-packages/ccmlib/node.py:683: NodeError{code}
> {code:java}
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node1] 'ERROR [SSTableBatchOpen:1] 2023-10-19
> 22:25:07,449 DefaultFSErrorHandler.java:129 - Exiting forcefully due to file
> system exception on startup, disk failure policy
> "stop"\norg.apache.cassandra.io.sstable.CorruptSSTableException: Corrupted:
> /tmp/dtest-ahz16wrh/test/node1/data0/system/prepared_statements-18a9c2576a0c3841ba718cd529849fef/nc-4-big\n\tat
>
> org.apache.cassandra.io.sstable.format.SSTableReaderLoadingBuilder.build(SSTableReaderLoadingBuilder.java:111)\n\tat
>
> org.apache.cassandra.io.sstable.format.SSTableReader.open(SSTableReader.java:397)\n\tat
>
> org.apache.cassandra.io.sstable.format.SSTableReader.open(SSTableReader.java:353)\n\tat
>
> org.apache.cassandra.io.sstable.format.SSTableReader.lambda$openAll$4(SSTableReader.java:414)\n\tat
> org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)\n\tat
> org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)\n\tat
> org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)\n\tat
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)\nCaused by:
>
[jira] [Updated] (CASSANDRA-18710) Test failure: org.apache.cassandra.io.DiskSpaceMetricsTest.testFlushSize-.jdk17 (from org.apache.cassandra.io.DiskSpaceMetricsTest-.jdk17)
[
https://issues.apache.org/jira/browse/CASSANDRA-18710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18710:
---
Fix Version/s: 5.0-beta
(was: 5.0-rc)
> Test failure:
> org.apache.cassandra.io.DiskSpaceMetricsTest.testFlushSize-.jdk17 (from
> org.apache.cassandra.io.DiskSpaceMetricsTest-.jdk17)
> --
>
> Key: CASSANDRA-18710
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18710
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.0-beta, 5.0.x, 5.x
>
> Attachments: org.apache.cassandra.io.DiskSpaceMetricsTest.txt
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1644/testReport/org.apache.cassandra.io/DiskSpaceMetricsTest/testFlushSize__jdk17/]
> h3.
> {code:java}
> Error Message
> expected:<7200.0> but was:<1367.83970468544>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<7200.0> but
> was:<1367.83970468544> at
> org.apache.cassandra.io.DiskSpaceMetricsTest.testFlushSize(DiskSpaceMetricsTest.java:119)
> 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}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18934) Downgrade to 4.1 fails due to schema changes
[
https://issues.apache.org/jira/browse/CASSANDRA-18934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18934:
---
Fix Version/s: (was: 5.0-beta)
> Downgrade to 4.1 fails due to schema changes
>
>
> Key: CASSANDRA-18934
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18934
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Startup and Shutdown
>Reporter: David Capwell
>Priority: Normal
> Fix For: 5.x
>
>
> We are required to support 5.0 downgrading to 4.1 as a migration step, but we
> don’t have tests to show this is working… I wrote a quick test to make sure a
> change we needed in Accord wouldn’t block the downgrade and see that we fail
> right now.
> {code}
> ERROR 20:56:39 Exiting due to error while processing commit log during
> initialization.
> org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException:
> Unexpected error deserializing mutation; saved to
> /var/folders/h1/s_3p1x3s3hl0hltbpck67m0hgn/T/mutation418421767150092dat.
> This may be caused by replaying a mutation against a table with the same
> name but incompatible schema. Exception follows: java.lang.RuntimeException:
> Unknown column compaction_properties during deserialization
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readMutation(CommitLogReader.java:464)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readSection(CommitLogReader.java:397)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:244)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:147)
> at
> org.apache.cassandra.db.commitlog.CommitLogReplayer.replayFiles(CommitLogReplayer.java:191)
> at
> org.apache.cassandra.db.commitlog.CommitLog.recoverFiles(CommitLog.java:223)
> at
> org.apache.cassandra.db.commitlog.CommitLog.recoverSegmentsOnDisk(CommitLog.java:204)
> {code}
> This was caused by a schema change in CASSANDRA-18061
> {code}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one
> * or more contributor license agreements. See the NOTICE file
> * distributed with this work for additional information
> * regarding copyright ownership. The ASF licenses this file
> * to you under the Apache License, Version 2.0 (the
> * "License"); you may not use this file except in compliance
> * with the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.cassandra.distributed.upgrade;
> import java.io.IOException;
> import java.io.File;
> import java.util.concurrent.atomic.AtomicBoolean;
> import org.junit.Test;
> import org.apache.cassandra.distributed.api.IUpgradeableInstance;
> public class DowngradeTest extends UpgradeTestBase
> {
> @Test
> public void test() throws Throwable
> {
> AtomicBoolean first = new AtomicBoolean(true);
> new TestCase()
> .nodes(1)
> .withConfig(c -> {
> if (first.compareAndSet(true, false))
> c.set("storage_compatibility_mode", "CASSANDRA_4");
> })
> .downgradeTo(v41)
> .setup(cluster -> {})
> // Uncomment if you want to test what happens after reading the commit log,
> which fails right now
> //.runBeforeNodeRestart((cluster, nodeId) -> {
> //IUpgradeableInstance inst = cluster.get(nodeId);
> //File f = new File((String)
> inst.config().get("commitlog_directory"));
> //deleteRecursive(f);
> //})
> .runAfterClusterUpgrade(cluster -> {})
> .run();
> }
> private void deleteRecursive(File f)
> {
> if (f.isDirectory())
> {
> File[] children = f.listFiles();
> if (children != null)
> {
> for (File c : children)
> deleteRecursive(c);
> }
> }
> f.delete();
> }
> }
> {code}
> {code}
> diff --git
> a/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
>
> b/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
> index 5ee8780204..b4111e3b44 100644
> ---
> a/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
> +++
>
[jira] [Updated] (CASSANDRA-18944) Test failure: org.apache.cassandra.simulator.test.ShortPaxosSimulationTest.simulationTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18944:
---
Fix Version/s: 5.0-rc
(was: 5.0.x)
> Test failure:
> org.apache.cassandra.simulator.test.ShortPaxosSimulationTest.simulationTest
> -
>
> Key: CASSANDRA-18944
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18944
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> The simulator test
> {{org.apache.cassandra.simulator.test.ShortPaxosSimulationTest#simulationTest}}
> is flaky on 5.0 and trunk:
> *
> https://app.circleci.com/pipelines/github/mike-tr-adamson/cassandra/332/workflows/946e28f4-2dec-4384-ac38-de011093f6c6/jobs/25735/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3253/workflows/e48b49e9-cf36-412a-a811-d813031e6f01/jobs/83735/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3254/workflows/69f451ef-fb39-48e4-b1d1-40ee4141b0c1/jobs/83739/tests
> {code}
> org.apache.cassandra.simulator.SimulationException: Failed on seed
> 0xb01206bb3b021127
> Caused by: java.lang.ClassCastException: class
> org.apache.cassandra.net.NoPayload cannot be cast to class
> org.apache.cassandra.gms.GossipShutdown (org.apache.cassandra.net.NoPayload
> and org.apache.cassandra.gms.GossipShutdown are in unnamed module of loader
> org.apache.cassandra.distributed.shared.InstanceClassLoader @68801feb)
> at
> org.apache.cassandra.gms.GossipShutdown$Serializer.serialize(GossipShutdown.java:41)
> at
> org.apache.cassandra.net.Message$Serializer.serialize(Message.java:722)
> at
> org.apache.cassandra.distributed.impl.Instance.serializeMessage(Instance.java:427)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$registerOutboundFilter$5(Instance.java:370)
> at
> org.apache.cassandra.net.OutboundSink$Filtered.accept(OutboundSink.java:54)
> at org.apache.cassandra.net.OutboundSink.accept(OutboundSink.java:70)
> at
> org.apache.cassandra.net.MessagingService.send(MessagingService.java:449)
> at
> org.apache.cassandra.net.MessagingService.send(MessagingService.java:419)
> at
> org.apache.cassandra.gms.Gossiper.unsafeSendShutdown(Gossiper.java:2634)
> at
> org.apache.cassandra.simulator.cluster.OnInstanceSendShutdown.lambda$invokableSendShutdown$1(OnInstanceSendShutdown.java:48)
> at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
> at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)
> at
> org.apache.cassandra.concurrent.SyncFutureTask$1.call(SyncFutureTask.java:46)
> at
> org.apache.cassandra.concurrent.SyncFutureTask.run(SyncFutureTask.java:68)
> at
> org.apache.cassandra.simulator.systems.InterceptingExecutor$AbstractSingleThreadedExecutorPlus.lambda$new$0(InterceptingExecutor.java:584)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> {code}
> The test failure can easily be reproduced on CircleCI with:
> {code}
> .circleci/generate.sh -sp \
> -e
> REPEATED_SIMULATOR_DTESTS=org.apache.cassandra.simulator.test.ShortPaxosSimulationTest
> \
> -e REPEATED_SIMULATOR_DTESTS_COUNT=100
> {code}
> Flakiness seems ~18%.
> The test failure is not reported on Butler because simulator tests are not
> run by Jenkins.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18902) Test failure: org.apache.cassandra.distributed.test.MigrationCoordinatorTest.explicitEndpointIgnore
[ https://issues.apache.org/jira/browse/CASSANDRA-18902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-18902: --- Fix Version/s: 5.0-rc (was: 5.0.x) > Test failure: > org.apache.cassandra.distributed.test.MigrationCoordinatorTest.explicitEndpointIgnore > --- > > Key: CASSANDRA-18902 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18902 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Jacek Lewandowski >Priority: Normal > Fix For: 5.0-rc, 5.x > > > Repeated run from `cassandra-4.1` > [https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/941/workflows/46fc6cb7-135e-4862-b9d3-6996c0993de8] > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18895) Test failure: https://ci-cassandra.apache.org/job/Cassandra-5.0/47/testReport/org.apache.cassandra.distributed.test/MessageFiltersTest/hintSerializationTest__jdk17/
[
https://issues.apache.org/jira/browse/CASSANDRA-18895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18895:
---
Fix Version/s: 5.0-rc
(was: 5.0.x)
> Test failure:
> https://ci-cassandra.apache.org/job/Cassandra-5.0/47/testReport/org.apache.cassandra.distributed.test/MessageFiltersTest/hintSerializationTest__jdk17/
>
>
> Key: CASSANDRA-18895
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18895
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0-rc
>
>
> h3.
> {code:java}
> https://ci-cassandra.apache.org/job/Cassandra-5.0/47/testReport/org.apache.cassandra.distributed.test/MessageFiltersTest/hintSerializationTest__jdk17/{code}
> {code:java}
> Error Message
> Uncaught exceptions were thrown during test
> Stacktrace
> org.apache.cassandra.distributed.shared.ShutdownException: Uncaught
> exceptions were thrown during test at
> org.apache.cassandra.distributed.impl.AbstractCluster.checkAndResetUncaughtExceptions(AbstractCluster.java:1104)
> at
> org.apache.cassandra.distributed.impl.AbstractCluster.close(AbstractCluster.java:1090)
> at
> org.apache.cassandra.distributed.test.MessageFiltersTest.hintSerializationTest(MessageFiltersTest.java:297)
> 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)
> Suppressed: java.lang.IllegalStateException: Can't use shutdown instances,
> delegate is null at
> org.apache.cassandra.distributed.impl.AbstractCluster$Wrapper.delegate(AbstractCluster.java:285)
> at
> org.apache.cassandra.distributed.impl.DelegatingInvokableInstance.transfer(DelegatingInvokableInstance.java:49)
> at
> org.apache.cassandra.distributed.api.IInvokableInstance.acceptsOnInstance(IInvokableInstance.java:49)
> at
> org.apache.cassandra.distributed.test.MessageFiltersTest.lambda$hintSerializationTest$11(MessageFiltersTest.java:287)
> at
> org.apache.cassandra.distributed.impl.MessageFilters$Filter.matches(MessageFilters.java:137)
> at
> org.apache.cassandra.distributed.impl.MessageFilters.permit(MessageFilters.java:61)
> at
> org.apache.cassandra.distributed.impl.MessageFilters.permitInbound(MessageFilters.java:37)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$registerInboundFilter$4(Instance.java:361)
> at org.apache.cassandra.net.InboundSink$Filtered.accept(InboundSink.java:63)
> at org.apache.cassandra.net.InboundSink$Filtered.accept(InboundSink.java:50)
> at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:97) at
> org.apache.cassandra.net.InboundSink.accept(InboundSink.java:45) at
> org.apache.cassandra.net.InboundMessageHandler$ProcessMessage.run(InboundMessageHandler.java:430)
> at
> org.apache.cassandra.concurrent.ExecutionFailure$1.run(ExecutionFailure.java:133)
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:143) at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
>
> {code:java}
> ERROR 12:39:56 uncaught exception in thread
> Thread[node1_MemtablePostFlush:1,5,MemtablePostFlush]
> java.util.concurrent.RejectedExecutionException: MemtableReclaimMemory has
> shut down at
> org.apache.cassandra.concurrent.ThreadPoolExecutorBase.lambda$static$0(ThreadPoolExecutorBase.java:49)
> at
> org.apache.cassandra.concurrent.ThreadPoolExecutorJMXAdapter.lambda$rejectedExecutionHandler$0(ThreadPoolExecutorJMXAdapter.java:238)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:833)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1365)
> at
> org.apache.cassandra.concurrent.ThreadPoolExecutorPlus.addTask(ThreadPoolExecutorPlus.java:50)
> at
> org.apache.cassandra.concurrent.ThreadPoolExecutorPlus.execute(ThreadPoolExecutorPlus.java:57)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.safeExecute(ListenerList.java:166)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.notifyListener(ListenerList.java:157)
> at
> org.apache.cassandra.utils.concurrent.ListenerList$RunnableWithExecutor.notifySelf(ListenerList.java:345)
> at
> org.apache.cassandra.utils.concurrent.ListenerList.lambda$notifyExclusive$0(ListenerList.java:124)
> at
>
[jira] [Updated] (CASSANDRA-18934) Downgrade to 4.1 fails due to schema changes
[
https://issues.apache.org/jira/browse/CASSANDRA-18934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18934:
---
Fix Version/s: 5.0-beta
(was: 5.0.x)
> Downgrade to 4.1 fails due to schema changes
>
>
> Key: CASSANDRA-18934
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18934
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Startup and Shutdown
>Reporter: David Capwell
>Priority: Normal
> Fix For: 5.0-beta, 5.x
>
>
> We are required to support 5.0 downgrading to 4.1 as a migration step, but we
> don’t have tests to show this is working… I wrote a quick test to make sure a
> change we needed in Accord wouldn’t block the downgrade and see that we fail
> right now.
> {code}
> ERROR 20:56:39 Exiting due to error while processing commit log during
> initialization.
> org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException:
> Unexpected error deserializing mutation; saved to
> /var/folders/h1/s_3p1x3s3hl0hltbpck67m0hgn/T/mutation418421767150092dat.
> This may be caused by replaying a mutation against a table with the same
> name but incompatible schema. Exception follows: java.lang.RuntimeException:
> Unknown column compaction_properties during deserialization
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readMutation(CommitLogReader.java:464)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readSection(CommitLogReader.java:397)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:244)
> at
> org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:147)
> at
> org.apache.cassandra.db.commitlog.CommitLogReplayer.replayFiles(CommitLogReplayer.java:191)
> at
> org.apache.cassandra.db.commitlog.CommitLog.recoverFiles(CommitLog.java:223)
> at
> org.apache.cassandra.db.commitlog.CommitLog.recoverSegmentsOnDisk(CommitLog.java:204)
> {code}
> This was caused by a schema change in CASSANDRA-18061
> {code}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one
> * or more contributor license agreements. See the NOTICE file
> * distributed with this work for additional information
> * regarding copyright ownership. The ASF licenses this file
> * to you under the Apache License, Version 2.0 (the
> * "License"); you may not use this file except in compliance
> * with the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.cassandra.distributed.upgrade;
> import java.io.IOException;
> import java.io.File;
> import java.util.concurrent.atomic.AtomicBoolean;
> import org.junit.Test;
> import org.apache.cassandra.distributed.api.IUpgradeableInstance;
> public class DowngradeTest extends UpgradeTestBase
> {
> @Test
> public void test() throws Throwable
> {
> AtomicBoolean first = new AtomicBoolean(true);
> new TestCase()
> .nodes(1)
> .withConfig(c -> {
> if (first.compareAndSet(true, false))
> c.set("storage_compatibility_mode", "CASSANDRA_4");
> })
> .downgradeTo(v41)
> .setup(cluster -> {})
> // Uncomment if you want to test what happens after reading the commit log,
> which fails right now
> //.runBeforeNodeRestart((cluster, nodeId) -> {
> //IUpgradeableInstance inst = cluster.get(nodeId);
> //File f = new File((String)
> inst.config().get("commitlog_directory"));
> //deleteRecursive(f);
> //})
> .runAfterClusterUpgrade(cluster -> {})
> .run();
> }
> private void deleteRecursive(File f)
> {
> if (f.isDirectory())
> {
> File[] children = f.listFiles();
> if (children != null)
> {
> for (File c : children)
> deleteRecursive(c);
> }
> }
> f.delete();
> }
> }
> {code}
> {code}
> diff --git
> a/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
>
> b/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
> index 5ee8780204..b4111e3b44 100644
> ---
> a/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
> +++
>
[jira] [Commented] (CASSANDRA-18960) Upgrade Python driver to 3.28.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782241#comment-17782241
]
Andres de la Peña commented on CASSANDRA-18960:
---
Thanks, committed to 5.0 as
[f41ecf586c0459476d68e755c6431119f08ff4e1|https://github.com/apache/cassandra/commit/f41ecf586c0459476d68e755c6431119f08ff4e1]
and merged to
[{{trunk}}|https://github.com/apache/cassandra/commit/53c25f8faa68065040c37f29f3f7f0f0b7161a98].
> Upgrade Python driver to 3.28.0
> ---
>
> Key: CASSANDRA-18960
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18960
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Vector Search, Tool/cqlsh
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The version of the Python driver that is used by cqlsh (3.25.0) doesn't
> entirely support the new vector data type introduced by CASSANDRA-18504.
> While we can perfectly write data, read vectors are presented as blobs:
> {code}
> > CREATE TABLE t (k int PRIMARY KEY, v vector);
> > INSERT INTO t(k, v) VALUES (0, [1, 2]);
> > SELECT * FROM t;
> k | v
> ---+-
> 0 | b'\x00\x00\x00\x01\x00\x00\x00\x02'
> {code}
> I think that would we fixed if we update the driver to (at least) 3.28.0,
> which includes support for the new vector data type.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra) branch cassandra-5.0 updated: Upgrade Python driver to 3.28.0
This is an automated email from the ASF dual-hosted git repository.
adelapena pushed a commit to branch cassandra-5.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/cassandra-5.0 by this push:
new f41ecf586c Upgrade Python driver to 3.28.0
f41ecf586c is described below
commit f41ecf586c0459476d68e755c6431119f08ff4e1
Author: Andrés de la Peña
AuthorDate: Thu Nov 2 13:59:58 2023 +
Upgrade Python driver to 3.28.0
patch by Andrés de la Peña and Jeremiah Jordan; reviewed by Brandon
Williams for CASSANDRA-18960
Co-authored-by: Jeremiah Jordan
Co-authored-by: Andrés de la Peña
---
CHANGES.txt | 1 +
lib/cassandra-driver-internal-only-3.25.0.zip | Bin 345177 -> 0 bytes
lib/cassandra-driver-internal-only-3.28.0.zip | Bin 0 -> 356837 bytes
pylib/cqlshlib/formatting.py | 15 +++
pylib/cqlshlib/test/test_cqlsh_output.py | 22 ++
5 files changed, 34 insertions(+), 4 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index f288f3206e..f54569f342 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
5.0-alpha2
+ * Upgrade Python driver to 3.28.0 (CASSANDRA-18960)
* Add retries to IR messages (CASSANDRA-18962)
* Add metrics and logging to repair retries (CASSANDRA-18952)
* Remove deprecated code in Cassandra 1.x and 2.x (CASSANDRA-18959)
diff --git a/lib/cassandra-driver-internal-only-3.25.0.zip
b/lib/cassandra-driver-internal-only-3.25.0.zip
deleted file mode 100644
index ecfd6a946e..00
Binary files a/lib/cassandra-driver-internal-only-3.25.0.zip and /dev/null
differ
diff --git a/lib/cassandra-driver-internal-only-3.28.0.zip
b/lib/cassandra-driver-internal-only-3.28.0.zip
new file mode 100644
index 00..07e0379447
Binary files /dev/null and b/lib/cassandra-driver-internal-only-3.28.0.zip
differ
diff --git a/pylib/cqlshlib/formatting.py b/pylib/cqlshlib/formatting.py
index 4eb36581c6..23bf1efbbf 100644
--- a/pylib/cqlshlib/formatting.py
+++ b/pylib/cqlshlib/formatting.py
@@ -149,8 +149,8 @@ class CqlType:
def parse(self, typestring, ksmeta):
"""
Parse the typestring by looking at this pattern: *<*>. If there is no
match then the type
-is either a simple type or a user type, otherwise it must be a
composite type
-for which we need to look-up the sub-types. For user types the sub
types can be extracted
+is either a simple type or a user type, otherwise it must be a
composite type or a vector type,
+for which we need to look up the subtypes. For user types the subtypes
can be extracted
from the keyspace metadata.
"""
while True:
@@ -167,8 +167,15 @@ class CqlType:
typestring = m.group(2)
continue
-name = m.group(1) # a composite type, parse sub types
-return name, self.parse_sub_types(m.group(2), ksmeta),
self._get_formatter(name)
+name = m.group(1) # a composite or vector type, parse subtypes
+try:
+# Vector types are parameterized as name so add
custom handling for that here
+type_args = m.group(2).split(',')
+vector_type = CqlType(type_args[0])
+vector_size = int(type_args[1])
+return name, [vector_type for _ in range(vector_size)],
self._get_formatter(name)
+except (ValueError, IndexError):
+return name, self.parse_sub_types(m.group(2), ksmeta),
self._get_formatter(name)
@staticmethod
def _get_formatter(name):
diff --git a/pylib/cqlshlib/test/test_cqlsh_output.py
b/pylib/cqlshlib/test/test_cqlsh_output.py
index c17def624a..9ca7988d2e 100644
--- a/pylib/cqlshlib/test/test_cqlsh_output.py
+++ b/pylib/cqlshlib/test/test_cqlsh_output.py
@@ -935,6 +935,28 @@ class TestCqlshOutput(BaseTestCase):
"""),
))
+def test_vectors_output(self):
+self.assertQueriesGiveColoredOutput((
+("SELECT vectorcol FROM has_all_types;", r"""
+ vectorcol
+ M
+---
+
+ [1, -2, NaN]
+ BGBBGGBBGGGB
+ [1, 2, 3]
+ BGBBGBBGB
+ [0, 0, 0]
+ BGBBGBBGB
+ null
+
+ [1e+08, 1e+08, 1e+08]
+ BGBBGBBGB
+
+(5 rows)
+"""),
+))
+
def test_expanded_output_counts_past_page(self):
query = "PAGING 5; EXPAND ON; SELECT * FROM twenty_rows_table;"
output, result = testcall_cqlsh(prompt=None, env=self.default_env,
-
To unsubscribe,
[jira] [Updated] (CASSANDRA-18883) CEP-15: Support State Eviction
[ https://issues.apache.org/jira/browse/CASSANDRA-18883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-18883: --- Fix Version/s: 5.x (was: 5.0) > CEP-15: Support State Eviction > -- > > Key: CASSANDRA-18883 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18883 > Project: Cassandra > Issue Type: Improvement > Components: Accord >Reporter: Caleb Rackliffe >Assignee: Benedict Elliott Smith >Priority: Normal > Fix For: 5.x > > > Permit the state machine to erase transactions that are known to be applied > across the cluster. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra) 01/01: Merge branch 'cassandra-5.0' into trunk
This is an automated email from the ASF dual-hosted git repository.
adelapena pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit 53c25f8faa68065040c37f29f3f7f0f0b7161a98
Merge: bb686fc27d f41ecf586c
Author: Andrés de la Peña
AuthorDate: Thu Nov 2 17:10:13 2023 +
Merge branch 'cassandra-5.0' into trunk
CHANGES.txt | 1 +
lib/cassandra-driver-internal-only-3.25.0.zip | Bin 345177 -> 0 bytes
lib/cassandra-driver-internal-only-3.28.0.zip | Bin 0 -> 356837 bytes
pylib/cqlshlib/formatting.py | 15 +++
pylib/cqlshlib/test/test_cqlsh_output.py | 22 ++
5 files changed, 34 insertions(+), 4 deletions(-)
diff --cc CHANGES.txt
index c7bbed34a0,f54569f342..d7a0a03b6d
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,8 -1,5 +1,9 @@@
-5.0-alpha2
+5.1
+ * Add ELAPSED command to cqlsh (CASSANDRA-18861)
+ * Add the ability to disable bulk loading of SSTables (CASSANDRA-18781)
+ * Clean up obsolete functions and simplify cql_version handling in cqlsh
(CASSANDRA-18787)
+Merged from 5.0:
+ * Upgrade Python driver to 3.28.0 (CASSANDRA-18960)
* Add retries to IR messages (CASSANDRA-18962)
* Add metrics and logging to repair retries (CASSANDRA-18952)
* Remove deprecated code in Cassandra 1.x and 2.x (CASSANDRA-18959)
diff --cc pylib/cqlshlib/test/test_cqlsh_output.py
index 3cb6d51300,9ca7988d2e..65ac5be482
--- a/pylib/cqlshlib/test/test_cqlsh_output.py
+++ b/pylib/cqlshlib/test/test_cqlsh_output.py
@@@ -935,9 -935,31 +935,31 @@@ class TestCqlshOutput(BaseTestCase)
"""),
))
+ def test_vectors_output(self):
+ self.assertQueriesGiveColoredOutput((
+ ("SELECT vectorcol FROM has_all_types;", r"""
+ vectorcol
+ M
+ ---
+
+ [1, -2, NaN]
+ BGBBGGBBGGGB
+ [1, 2, 3]
+ BGBBGBBGB
+ [0, 0, 0]
+ BGBBGBBGB
+ null
+
+ [1e+08, 1e+08, 1e+08]
+ BGBBGBBGB
+
+ (5 rows)
+ """),
+ ))
+
def test_expanded_output_counts_past_page(self):
query = "PAGING 5; EXPAND ON; SELECT * FROM twenty_rows_table;"
-output, result = testcall_cqlsh(prompt=None, env=self.default_env,
+output, result = cqlsh_testcall(prompt=None, env=self.default_env,
tty=False, input=query)
self.assertEqual(0, result)
# format is "@ Row 1"
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18963) Test Failure: sstableutil_test.TestSSTableUtil
[
https://issues.apache.org/jira/browse/CASSANDRA-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18963:
---
Fix Version/s: 5.0-rc
(was: 5.0.x)
> Test Failure: sstableutil_test.TestSSTableUtil
> --
>
> Key: CASSANDRA-18963
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18963
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Priority: Normal
> Fix For: 5.0-rc
>
>
> Seems flaky
> [https://app.circleci.com/pipelines/github/driftx/cassandra/1342/workflows/9554c7b5-dd60-4f08-8db5-c954febc8ad6/jobs/58957/tests]
> *
> h4. test_abortedcompaction
> sstableutil_test.TestSSTableUtil
>
> {code:java}
> self = def
> test_abortedcompaction(self): """ @jira_ticket CASSANDRA-7066 @jira_ticket
> CASSANDRA-11497 Check that we can cleanup temporary files after a compaction
> is aborted. """ log_file_name = 'debug.log' cluster = self.cluster
> cluster.populate(1).start() node = cluster.nodelist()[0] numrecords = 25
> self._create_data(node, KeyspaceName, TableName, numrecords) finalfiles,
> tmpfiles = self._check_files(node, KeyspaceName, TableName) assert
> len(finalfiles) > 0, "Expected to find some final files" assert 0 ==
> len(tmpfiles), "Expected no tmp files" t = InterruptCompaction(node,
> TableName, filename=log_file_name, delay=2) t.start() try:
> logger.debug("Compacting...") node.compact() except ToolError: pass #
> expected to fail t.join() finalfiles =
> _normcase_all(self._invoke_sstableutil(KeyspaceName, TableName,
> type='final')) tmpfiles =
> _normcase_all(self._invoke_sstableutil(KeyspaceName, TableName, type='tmp'))
> # In most cases we should end up with some temporary files to clean up, but
> it may happen # that no temporary files are created if compaction finishes
> too early or starts too late # see CASSANDRA-11497 logger.debug("Got {} final
> files and {} tmp files after compaction was interrupted"
> .format(len(finalfiles), len(tmpfiles)))
> self._invoke_sstableutil(KeyspaceName, TableName, cleanup=True)
> self._check_files(node, KeyspaceName, TableName, finalfiles, []) # restart to
> make sure not data is lost logger.debug("Restarting node...") >
> node.start(wait_for_binary_proto=True) sstableutil_test.py:97: _ _ _ _ _ _ _
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> ../env3.6/lib/python3.6/site-packages/ccmlib/node.py:914: in start
> self.wait_for_binary_interface(from_mark=self.mark)
> ../env3.6/lib/python3.6/site-packages/ccmlib/node.py:702: in
> wait_for_binary_interface self.watch_log_for("Starting listening for CQL
> clients", **kwargs) ../env3.6/lib/python3.6/site-packages/ccmlib/node.py:599:
> in watch_log_for self.raise_node_error_if_cassandra_process_is_terminated() _
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> self = def
> raise_node_error_if_cassandra_process_is_terminated(self): if not
> self._is_pid_running(): msg = "C* process with {pid} is
> terminated".format(pid=self.pid) common.debug(msg) > raise NodeError(msg) E
> ccmlib.node.NodeError: C* process with 19530 is terminated
> ../env3.6/lib/python3.6/site-packages/ccmlib/node.py:683: NodeError{code}
> {code:java}
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node1] 'ERROR [SSTableBatchOpen:1] 2023-10-19
> 22:25:07,449 DefaultFSErrorHandler.java:129 - Exiting forcefully due to file
> system exception on startup, disk failure policy
> "stop"\norg.apache.cassandra.io.sstable.CorruptSSTableException: Corrupted:
> /tmp/dtest-ahz16wrh/test/node1/data0/system/prepared_statements-18a9c2576a0c3841ba718cd529849fef/nc-4-big\n\tat
>
> org.apache.cassandra.io.sstable.format.SSTableReaderLoadingBuilder.build(SSTableReaderLoadingBuilder.java:111)\n\tat
>
> org.apache.cassandra.io.sstable.format.SSTableReader.open(SSTableReader.java:397)\n\tat
>
> org.apache.cassandra.io.sstable.format.SSTableReader.open(SSTableReader.java:353)\n\tat
>
> org.apache.cassandra.io.sstable.format.SSTableReader.lambda$openAll$4(SSTableReader.java:414)\n\tat
> org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96)\n\tat
> org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)\n\tat
> org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)\n\tat
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:829)\nCaused by:
>
[jira] [Updated] (CASSANDRA-18950) Test failure: dtest.sslnodetonode_test.TestNodeToNodeSSLEncryption.test_ca_mismatch
[
https://issues.apache.org/jira/browse/CASSANDRA-18950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18950:
---
Fix Version/s: 5.0-rc
(was: 5.x)
> Test failure:
> dtest.sslnodetonode_test.TestNodeToNodeSSLEncryption.test_ca_mismatch
> ---
>
> Key: CASSANDRA-18950
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18950
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0-rc
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1746/testReport/dtest.sslnodetonode_test/TestNodeToNodeSSLEncryption/test_ca_mismatch/]
>
> {code:java}
> self = 0x7f45da997710> def test_ca_mismatch(self): """CA mismatch should cause nodes
> to fail to connect""" credNode1 = sslkeygen.generate_credentials("127.0.0.1")
> credNode2 = sslkeygen.generate_credentials("127.0.0.2") # mismatching CA!
> self.setup_nodes(credNode1, credNode2)
> self.fixture_dtest_setup.allow_log_errors = True
> self.cluster.start(no_wait=True) found = self._grep_msg(self.node1,
> _LOG_ERR_HANDSHAKE) self.cluster.stop() > assert found E assert False
> sslnodetonode_test.py:115: AssertionError{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18710) Test failure: org.apache.cassandra.io.DiskSpaceMetricsTest.testFlushSize-.jdk17 (from org.apache.cassandra.io.DiskSpaceMetricsTest-.jdk17)
[
https://issues.apache.org/jira/browse/CASSANDRA-18710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18710:
---
Fix Version/s: 5.0-rc
(was: 5.0-beta)
> Test failure:
> org.apache.cassandra.io.DiskSpaceMetricsTest.testFlushSize-.jdk17 (from
> org.apache.cassandra.io.DiskSpaceMetricsTest-.jdk17)
> --
>
> Key: CASSANDRA-18710
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18710
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.0-rc, 5.0.x, 5.x
>
> Attachments: org.apache.cassandra.io.DiskSpaceMetricsTest.txt
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1644/testReport/org.apache.cassandra.io/DiskSpaceMetricsTest/testFlushSize__jdk17/]
> h3.
> {code:java}
> Error Message
> expected:<7200.0> but was:<1367.83970468544>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<7200.0> but
> was:<1367.83970468544> at
> org.apache.cassandra.io.DiskSpaceMetricsTest.testFlushSize(DiskSpaceMetricsTest.java:119)
> 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}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18949) Test failure: org.apache.cassandra.tools.nodetool.ClearSnapshotTest.testClearSnapshot_RemoveByName-.jdk11.arch=x86_64.python2.7
[
https://issues.apache.org/jira/browse/CASSANDRA-18949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18949:
---
Fix Version/s: 5.0-rc
(was: 5.x)
> Test failure:
> org.apache.cassandra.tools.nodetool.ClearSnapshotTest.testClearSnapshot_RemoveByName-.jdk11.arch=x86_64.python2.7
> ---
>
> Key: CASSANDRA-18949
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18949
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0-rc
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1747/testReport/org.apache.cassandra.tools.nodetool/ClearSnapshotTest/testClearSnapshot_RemoveByName__jdk11_arch_x86_64_python2_7/]
> h3.
> {code:java}
> Error Message
> [bin/nodetool, -p, 36753, -h, 127.0.0.1, snapshot, -t, some-name] exited with
> code 2 stderr: error: Unknown keyspace keyspace_04 -- StackTrace --
> java.lang.AssertionError: Unknown keyspace keyspace_04 at
> org.apache.cassandra.db.Keyspace.(Keyspace.java:324) at
> org.apache.cassandra.db.Keyspace.lambda$open$0(Keyspace.java:162) at
> org.apache.cassandra.utils.concurrent.LoadingMap.blockingLoadIfAbsent(LoadingMap.java:105)
> at
> org.apache.cassandra.schema.Schema.maybeAddKeyspaceInstance(Schema.java:251)
> at org.apache.cassandra.db.Keyspace.open(Keyspace.java:162) at
> org.apache.cassandra.db.Keyspace.open(Keyspace.java:151) at
> com.google.common.collect.Iterators$6.transform(Iterators.java:828) at
> com.google.common.collect.TransformedIterator.next(TransformedIterator.java:52)
> at
> org.apache.cassandra.service.StorageService.takeSnapshot(StorageService.java:4356)
> at
> org.apache.cassandra.service.StorageService.takeSnapshot(StorageService.java:4221)
> 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
> sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) at
> jdk.internal.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566) at
> java.base/sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:260) at
> java.management/com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
> at
> java.management/com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
> at
> java.management/com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> at
> java.management/com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> at
> java.management/com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> at
> java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:809)
> at
> java.management/com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> at
> java.management.rmi/javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1466)
> at
> java.management.rmi/javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1307)
> at
> java.management.rmi/javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1399)
> at
> java.management.rmi/javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:827)
> at java.base/jdk.internal.reflect.GeneratedMethodAccessor16.invoke(Unknown
> Source) at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566) at
> java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359)
> at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200) at
> java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197) at
> java.base/java.security.AccessController.doPrivileged(Native Method) at
> java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196) at
> java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562)
> at
> java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796)
> at
> java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677)
> at
[jira] [Updated] (CASSANDRA-18960) Upgrade Python driver to 3.28.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-18960:
--
Fix Version/s: 5.0-alpha2
5.1
(was: 5.x)
(was: 5.0.x)
Source Control Link:
https://github.com/apache/cassandra/commit/f41ecf586c0459476d68e755c6431119f08ff4e1
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Upgrade Python driver to 3.28.0
> ---
>
> Key: CASSANDRA-18960
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18960
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Vector Search, Tool/cqlsh
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.0-alpha2, 5.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The version of the Python driver that is used by cqlsh (3.25.0) doesn't
> entirely support the new vector data type introduced by CASSANDRA-18504.
> While we can perfectly write data, read vectors are presented as blobs:
> {code}
> > CREATE TABLE t (k int PRIMARY KEY, v vector);
> > INSERT INTO t(k, v) VALUES (0, [1, 2]);
> > SELECT * FROM t;
> k | v
> ---+-
> 0 | b'\x00\x00\x00\x01\x00\x00\x00\x02'
> {code}
> I think that would we fixed if we update the driver to (at least) 3.28.0,
> which includes support for the new vector data type.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18919) Test failure: org.apache.cassandra.io.sstable.VerifyTest.testMutateRepair-.jdk11
[
https://issues.apache.org/jira/browse/CASSANDRA-18919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18919:
---
Fix Version/s: 5.0-rc
(was: 5.0.x)
> Test failure:
> org.apache.cassandra.io.sstable.VerifyTest.testMutateRepair-.jdk11
>
>
> Key: CASSANDRA-18919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18919
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0-rc
>
>
>
> {code:java}
> org.apache.cassandra.io.sstable.VerifyTest.testMutateRepair-.jdk11 (from
> org.apache.cassandra.io.sstable.VerifyTest-.jdk11)
> Failing for the past 1 build (Since #60 ) Took 0.42 sec. Failed 1 times
> in the last 16 runs. Flakiness: 6%, Stability: 93% Stacktrace
> java.io.EOFException at
> org.apache.cassandra.io.util.RebufferingInputStream.readByte(RebufferingInputStream.java:180)
> at
> org.apache.cassandra.io.util.RebufferingInputStream.readPrimitiveSlowly(RebufferingInputStream.java:142)
> at
> org.apache.cassandra.io.util.RebufferingInputStream.readLong(RebufferingInputStream.java:231)
> at
> org.apache.cassandra.io.sstable.VerifyTest.testMutateRepair(VerifyTest.java:538)
> 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}
> Seen here:
> https://ci-cassandra.apache.org/job/Cassandra-5.0/60/testReport/org.apache.cassandra.io.sstable/VerifyTest/testMutateRepair__jdk11/
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18635) Test failure: org.apache.cassandra.distributed.test.UpgradeSSTablesTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18635:
---
Fix Version/s: 5.0-rc
> Test failure: org.apache.cassandra.distributed.test.UpgradeSSTablesTest
> ---
>
> Key: CASSANDRA-18635
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18635
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 5.0-rc, 5.x
>
>
> Seen here:
> https://app.circleci.com/pipelines/github/driftx/cassandra/1095/workflows/6114e2e3-8dcc-4bb0-b664-ae7d82c3349f/jobs/33405/tests
> {noformat}
> junit.framework.AssertionFailedError: expected:<0> but was:<2>
> at
> org.apache.cassandra.distributed.test.UpgradeSSTablesTest.upgradeSSTablesInterruptsOngoingCompaction(UpgradeSSTablesTest.java:86)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra) branch trunk updated (bb686fc27d -> 53c25f8faa)
This is an automated email from the ASF dual-hosted git repository. adelapena pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from bb686fc27d Merge branch 'cassandra-5.0' into trunk new f41ecf586c Upgrade Python driver to 3.28.0 new 53c25f8faa Merge branch 'cassandra-5.0' into trunk The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt | 1 + lib/cassandra-driver-internal-only-3.25.0.zip | Bin 345177 -> 0 bytes lib/cassandra-driver-internal-only-3.28.0.zip | Bin 0 -> 356837 bytes pylib/cqlshlib/formatting.py | 15 +++ pylib/cqlshlib/test/test_cqlsh_output.py | 22 ++ 5 files changed, 34 insertions(+), 4 deletions(-) delete mode 100644 lib/cassandra-driver-internal-only-3.25.0.zip create mode 100644 lib/cassandra-driver-internal-only-3.28.0.zip - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18811) Set right client auth for creating SSL context in mTLS optional mode
[ https://issues.apache.org/jira/browse/CASSANDRA-18811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-18811: --- Fix Version/s: 5.0.x (was: 5.0-beta) > Set right client auth for creating SSL context in mTLS optional mode > > > Key: CASSANDRA-18811 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18811 > Project: Cassandra > Issue Type: Bug > Components: Messaging/Client, Messaging/Internode >Reporter: Jyothsna Konisa >Assignee: Jyothsna Konisa >Priority: Normal > Fix For: 4.1.x, 5.0.x, 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > Adding a new value `optional` for require_client_auth in Encryption options. > when require_client_auth is optional, the SSL context that is created will > allow client connections that provide a client certificate along with the > client connections that do not provide certificates. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18811) Set right client auth for creating SSL context in mTLS optional mode
[ https://issues.apache.org/jira/browse/CASSANDRA-18811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-18811: --- Fix Version/s: 5.0-beta (was: 5.0-alpha) > Set right client auth for creating SSL context in mTLS optional mode > > > Key: CASSANDRA-18811 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18811 > Project: Cassandra > Issue Type: Bug > Components: Messaging/Client, Messaging/Internode >Reporter: Jyothsna Konisa >Assignee: Jyothsna Konisa >Priority: Normal > Fix For: 4.1.x, 5.0-beta, 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > Adding a new value `optional` for require_client_auth in Encryption options. > when require_client_auth is optional, the SSL context that is created will > allow client connections that provide a client certificate along with the > client connections that do not provide certificates. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18948) Test failure: org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testReplayLogic-compression.jdk17.arch=x86_64.python2.7
[
https://issues.apache.org/jira/browse/CASSANDRA-18948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18948:
---
Fix Version/s: 5.0-rc
(was: 5.0.x)
> Test failure:
> org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testReplayLogic-compression.jdk17.arch=x86_64.python2.7
>
> ---
>
> Key: CASSANDRA-18948
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18948
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.0-rc
>
>
> Seen here:
> https://ci-cassandra.apache.org/job/Cassandra-5.0/71/testReport/org.apache.cassandra.db.commitlog/CommitLogSegmentManagerCDCTest/testReplayLogic_compression_jdk17_arch_x86_64_python2_7/
> h3.
> {code:java}
> Error Message
> Missing old CDCIndexData in new set after replay:
> CommitLog-7-1697673230997_cdc.idx,1747785 List of CDCIndexData in new set of
> indexes after replay: CommitLog-7-1697673230996_cdc.idx,3510561
> CommitLog-7-1697673230998_cdc.idx,3509214
> Stacktrace
> junit.framework.AssertionFailedError: Missing old CDCIndexData in new set
> after replay: CommitLog-7-1697673230997_cdc.idx,1747785 List of CDCIndexData
> in new set of indexes after replay: CommitLog-7-1697673230996_cdc.idx,3510561
> CommitLog-7-1697673230998_cdc.idx,3509214 at
> org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testReplayLogic(CommitLogSegmentManagerCDCTest.java:319)
> 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}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18798) Appending to list in Accord transactions uses insertion timestamp
[
https://issues.apache.org/jira/browse/CASSANDRA-18798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18798:
---
Fix Version/s: (was: 5.0-beta)
> Appending to list in Accord transactions uses insertion timestamp
> -
>
> Key: CASSANDRA-18798
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18798
> Project: Cassandra
> Issue Type: Bug
> Components: Accord
>Reporter: Jaroslaw Kijanowski
>Assignee: Henrik Ingo
>Priority: Normal
> Fix For: 5.x
>
> Attachments: image-2023-09-26-20-05-25-846.png
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Given the following schema:
> {code:java}
> CREATE KEYSPACE IF NOT EXISTS accord WITH replication = {'class':
> 'SimpleStrategy', 'replication_factor': 3};
> CREATE TABLE IF NOT EXISTS accord.list_append(id int PRIMARY KEY,contents
> LIST);
> TRUNCATE accord.list_append;{code}
> And the following two possible queries executed by 10 threads in parallel:
> {code:java}
> BEGIN TRANSACTION
> LET row = (SELECT * FROM list_append WHERE id = ?);
> SELECT row.contents;
> COMMIT TRANSACTION;"
> BEGIN TRANSACTION
> UPDATE list_append SET contents += ? WHERE id = ?;
> COMMIT TRANSACTION;"
> {code}
> there seems to be an issue with transaction guarantees. Here's an excerpt in
> the edn format from a test.
> {code:java}
> {:type :invoke :process 8 :value [[:append 5 352]] :tid 3 :n 52
> :time 1692607285967116627}
> {:type :invoke :process 9 :value [[:r 5 nil]] :tid 1 :n 54
> :time 1692607286078732473}
> {:type :invoke :process 6 :value [[:append 5 553]] :tid 5 :n 53
> :time 1692607286133833428}
> {:type :invoke :process 7 :value [[:append 5 455]] :tid 4 :n 55
> :time 1692607286149702511}
> {:type :ok :process 8 :value [[:append 5 352]] :tid 3 :n 52
> :time 1692607286156314099}
> {:type :invoke :process 5 :value [[:r 5 nil]] :tid 9 :n 52
> :time 1692607286167090389}
> {:type :ok :process 9 :value [[:r 5 [303 304 604 6 306 509 909 409 912
> 411 514 415 719 419 19 623 22 425 24 926 25 832 130 733 430 533 29 933 333
> 537 934 538 740 139 744 938 544 42 646 749 242 546 547 548 753 450 150 349 48
> 852 352]]] :tid 1 :n 54 :time 1692607286168657534}
> {:type :invoke :process 1 :value [[:r 5 nil]] :tid 0 :n 51
> :time 1692607286201762938}
> {:type :ok :process 7 :value [[:append 5 455]] :tid 4 :n 55
> :time 1692607286245571513}
> {:type :invoke :process 7 :value [[:r 5 nil]] :tid 4 :n 56
> :time 1692607286245655775}
> {:type :ok :process 5 :value [[:r 5 [303 304 604 6 306 509 909 409 912
> 411 514 415 719 419 19 623 22 425 24 926 25 832 130 733 430 533 29 933 333
> 537 934 538 740 139 744 938 544 42 646 749 242 546 547 548 753 450 150 349 48
> 852 352 455]]] :tid 9 :n 52 :time 1692607286253928906}
> {:type :invoke :process 5 :value [[:r 5 nil]] :tid 9 :n 53
> :time 1692607286254095215}
> {:type :ok :process 6 :value [[:append 5 553]] :tid 5 :n 53
> :time 1692607286266263422}
> {:type :ok :process 1 :value [[:r 5 [303 304 604 6 306 509 909 409 912
> 411 514 415 719 419 19 623 22 425 24 926 25 832 130 733 430 533 29 933 333
> 537 934 538 740 139 744 938 544 42 646 749 242 546 547 548 753 450 150 349 48
> 852 352 553 455]]] :tid 0 :n 51 :time 1692607286271617955}
> {:type :ok :process 7 :value [[:r 5 [303 304 604 6 306 509 909 409 912
> 411 514 415 719 419 19 623 22 425 24 926 25 832 130 733 430 533 29 933 333
> 537 934 538 740 139 744 938 544 42 646 749 242 546 547 548 753 450 150 349 48
> 852 352 553 455]]] :tid 4 :n 56 :time 1692607286271816933}
> {:type :ok :process 5 :value [[:r 5 [303 304 604 6 306 509 909 409 912
> 411 514 415 719 419 19 623 22 425 24 926 25 832 130 733 430 533 29 933 333
> 537 934 538 740 139 744 938 544 42 646 749 242 546 547 548 753 450 150 349 48
> 852 352 553 455]]] :tid 9 :n 53 :time 1692607286281483026}
> {:type :invoke :process 9 :value [[:r 5 nil]] :tid 1 :n 56
> :time 1692607286284097561}
> {:type :ok :process 9 :value [[:r 5 [303 304 604 6 306 509 909 409 912
> 411 514 415 719 419 19 623 22 425 24 926 25 832 130 733 430 533 29 933 333
> 537 934 538 740 139 744 938 544 42 646 749 242 546 547 548 753 450 150 349 48
> 852 352 553 455]]] :tid 1 :n 56 :time 1692607286306445242}
> {code}
> Processes process 6 and process 7 are appending the values 553 and 455
> respectively. 455 succeeded and a read by process 5 confirms that. But then
> also 553 is appended and a read by process 1 confirms that as well, however
> it sees 553 before 455.
> process 5 reads [...
[jira] [Updated] (CASSANDRA-18945) Unified Compaction Strategy is creating too many sstables
[
https://issues.apache.org/jira/browse/CASSANDRA-18945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18945:
---
Fix Version/s: 5.0-beta
(was: 5.x)
(was: 5.0)
> Unified Compaction Strategy is creating too many sstables
> -
>
> Key: CASSANDRA-18945
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18945
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
>Reporter: Branimir Lambov
>Assignee: Ethan Brown
>Priority: Normal
> Fix For: 5.0-beta
>
> Attachments: file_ucs_shenandoah.html, file_ucs_shenandoah_3.html,
> file_ucs_shenandoah_off_heap_memtable.html,
> file_ucs_shenandoah_on_heap_memtable_2.html,
> file_ucs_shenandoah_on_heap_memtable_3.html, key-value-oss.html
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The unified compaction strategy currently aims to create sstables with close
> to the same size, defaulting to 1 GiB. Unfortunately tests show that
> Cassandra starts to have performance problems when the number of sstables
> grows to the order of a thousand, and in particular that even 1 TiB of data
> with the default configuration is creating too many sstables for efficient
> processing. This matters even more for SAI, where the number of sstables in
> the system can have a proportional effect on the complexity of operations.
> It is quite easy to create a configuration option that allows sstables to
> take some part of the data growth by adding a multiplier to [the shard count
> calculation|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/compaction/UnifiedCompactionStrategy.md#sharding]
> formula, replacing
> {{2 ^ round(log2(d / (t * b))) * b}}
> with
> {{2 ^ round((1 - 휆) * log2(d / (t * b))) * b}},
> where 휆 is a parameter whose value is between 0 and 1.
> With this, a 휆 of 0.5 would mean that shard count and sstable size grow in
> parallel at the square root of the data size growth. 0 would result in no
> growth, and 1 in always using the same number of shards.
> It may also be valuable to introduce a threshold for engaging the base shard
> count to avoid splitting lowest-level sstables into fragments that are too
> small.
> Once both of these are in place, we can set defaults that better suit all
> node densities, including 10 TiB and beyond, for example:
> - target size of 1 GiB
> - 휆 of 1/3
> - base shard count of 4
> - minimum size 100 MiB
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18534) Make sstable format configurable per table
[
https://issues.apache.org/jira/browse/CASSANDRA-18534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-18534:
---
Fix Version/s: 5.x
(was: 5.0)
> Make sstable format configurable per table
> --
>
> Key: CASSANDRA-18534
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18534
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Schema, Local/SSTable
>Reporter: Branimir Lambov
>Assignee: Maxwell Guo
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Some SSTable format settings need to be configurable per table for better
> efficiency. This includes:
> - {{row_index_granularity}}
> - {{bloom_filter_fp_chance}}
> - {{crc_check_chance}}
> - {{min/max_index_interval}}
> Some of these are currently configurable using direct properties of tables.
> Having them as format properties makes better sense and should also support
> specifying useable combinations of settings, e.g.
> {code:java}
> CREATE TABLE ... WITH sstable_format = "bti-fast";
> CREATE TABLE ... WITH sstable_format = "bti-small";
> {code}
> where {{bti-fast}} and {{bti-small}} can be defined in {{cassandra.yaml}}
> e.g. as
> {code:java}
> sstable.format.options:
> - bti-fast:
> row_index_granularity: 1kiB
> bloom_filter_fp_chance: 0.01
> - bti-small:
> row_index_granularity: 32kiB
> bloom_filter_fp_chance: 0.1
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18533) Move format-specific sstable options into the format configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-18533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782190#comment-17782190
]
Maxwell Guo commented on CASSANDRA-18533:
-
[~blambov]I have update the upper comment , would mind to take a look again ?
thanks.
> Move format-specific sstable options into the format configuration
> --
>
> Key: CASSANDRA-18533
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18533
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Schema, Local/SSTable
>Reporter: Branimir Lambov
>Assignee: Maxwell Guo
>Priority: Normal
> Fix For: 5.x
>
>
> This mainly concerns cassandra yaml settings:
> - {{column_index_size}}, which should also be renamed to
> {{row_index_granularity}}
> - {{column_index_cache_size}}
> - {{index_summary_capacity}}
> - {{index_summary_resize_interval}}
> and possibly
> - {{key_cache_size}}, {{key_cache_keys_to_save}}, {{key_cache_save_period}},
> {{key_cache_migrate_during_compaction}}
> - {{sstable_preemptive_open_interval}}
> Existing settings should be deprecated but still picked up if defined.
> At this point we will not consider table-level options that make better sense
> as format parameters ({{min/max_index_interval}}, {{bloom_filter_fp_chance}},
> {{crc_check_chance}} and possibly {{compression}}), because we do not yet
> support per-table format selection/configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18994) SAI range query does not play together with "IN"
[
https://issues.apache.org/jira/browse/CASSANDRA-18994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-18994:
Epic Link: CASSANDRA-18473
> SAI range query does not play together with "IN"
>
>
> Key: CASSANDRA-18994
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18994
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/SAI
>Reporter: Stefan Miklosovic
>Assignee: Mike Adamson
>Priority: Normal
>
> I am using schema from the website's quickstart.
> {code}
> cqlsh> DESCRIBE KEYSPACE cycling ;
> CREATE KEYSPACE cycling WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;
> CREATE TABLE cycling.cyclist_semi_pro (
> id int PRIMARY KEY,
> affiliation text,
> age int,
> country text,
> firstname text,
> lastname text,
> registration date
> ) WITH additional_write_policy = '99p'
> AND allow_auto_snapshot = true
> AND bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND cdc = false
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '16', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND memtable = 'default'
> AND crc_check_chance = 1.0
> AND default_time_to_live = 0
> AND extensions = {}
> AND gc_grace_seconds = 864000
> AND incremental_backups = true
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair = 'BLOCKING'
> AND speculative_retry = '99p';
> CREATE CUSTOM INDEX age_sai_idx ON cycling.cyclist_semi_pro (age) USING
> 'StorageAttachedIndex';
> CREATE CUSTOM INDEX country_sai_idx ON cycling.cyclist_semi_pro (country)
> USING 'StorageAttachedIndex' WITH OPTIONS = {'ascii': 'true',
> 'case_sensitive': 'false', 'normalize': 'true'};
> CREATE CUSTOM INDEX lastname_sai_idx ON cycling.cyclist_semi_pro (lastname)
> USING 'StorageAttachedIndex' WITH OPTIONS = {'ascii': 'true',
> 'case_sensitive': 'false', 'normalize': 'true'};
> CREATE CUSTOM INDEX registration_sai_idx ON cycling.cyclist_semi_pro
> (registration) USING 'StorageAttachedIndex';
> {code}
> Then I do:
> {code}
> cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE lastname in ('Cantona',
> 'Boyd');
> InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot
> execute this query as it might involve data filtering and thus may have
> unpredictable performance. If you want to execute this query despite the
> performance unpredictability, use ALLOW FILTERING"
> cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE lastname in ('Cantona',
> 'Boyd') ALLOW FILTERING;
> id | affiliation | age | country | firstname | lastname | registration
> +-+-+-+---+--+--
> 5 | Como Velocità | 24 | ITA | Irene | Cantona | 2012-07-22
> 20 | London Cyclists | 18 | GBR |Leslie | Boyd | 2012-12-15
> {code}
> But check this:
> {code}
> cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE registration >
> '2010-01-01' AND registration < '2015-12-31' and lastname in ('Cantona',
> 'Boyd') allow filtering;
> ReadFailure: Error from server: code=1300 [Replica(s) failed to execute read]
> message="Operation failed - received 0 responses and 1 failures: UNKNOWN from
> localhost/127.0.0.1:7000" info={'consistency': 'ONE', 'required_responses':
> 1, 'received_responses': 0, 'failures': 1, 'error_code_map': {'127.0.0.1':
> '0x'}}
> {code}
> and in the logs:
> {code}
> java.lang.AssertionError: null
> at
> org.apache.cassandra.index.sai.plan.Expression.add(Expression.java:171)
> at
> org.apache.cassandra.index.sai.plan.Operation.buildIndexExpressions(Operation.java:136)
> at
> org.apache.cassandra.index.sai.plan.Operation$AndNode.analyze(Operation.java:303)
> at
> org.apache.cassandra.index.sai.plan.Operation$Node.doTreeAnalysis(Operation.java:266)
> at
> org.apache.cassandra.index.sai.plan.Operation$Node.analyzeTree(Operation.java:251)
> at
> org.apache.cassandra.index.sai.plan.Operation.buildIterator(Operation.java:185)
> at
> org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher$ResultRetriever.(StorageAttachedIndexSearcher.java:151)
> at
> org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher.search(StorageAttachedIndexSearcher.java:107)
> at
> org.apache.cassandra.db.ReadCommand.executeLocally(ReadCommand.java:431)
> at
>
[jira] [Updated] (CASSANDRA-18994) SAI range query does not play together with "IN"
[
https://issues.apache.org/jira/browse/CASSANDRA-18994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-18994:
Reviewers: Caleb Rackliffe
> SAI range query does not play together with "IN"
>
>
> Key: CASSANDRA-18994
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18994
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/SAI
>Reporter: Stefan Miklosovic
>Assignee: Mike Adamson
>Priority: Normal
>
> I am using schema from the website's quickstart.
> {code}
> cqlsh> DESCRIBE KEYSPACE cycling ;
> CREATE KEYSPACE cycling WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;
> CREATE TABLE cycling.cyclist_semi_pro (
> id int PRIMARY KEY,
> affiliation text,
> age int,
> country text,
> firstname text,
> lastname text,
> registration date
> ) WITH additional_write_policy = '99p'
> AND allow_auto_snapshot = true
> AND bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND cdc = false
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '16', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND memtable = 'default'
> AND crc_check_chance = 1.0
> AND default_time_to_live = 0
> AND extensions = {}
> AND gc_grace_seconds = 864000
> AND incremental_backups = true
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair = 'BLOCKING'
> AND speculative_retry = '99p';
> CREATE CUSTOM INDEX age_sai_idx ON cycling.cyclist_semi_pro (age) USING
> 'StorageAttachedIndex';
> CREATE CUSTOM INDEX country_sai_idx ON cycling.cyclist_semi_pro (country)
> USING 'StorageAttachedIndex' WITH OPTIONS = {'ascii': 'true',
> 'case_sensitive': 'false', 'normalize': 'true'};
> CREATE CUSTOM INDEX lastname_sai_idx ON cycling.cyclist_semi_pro (lastname)
> USING 'StorageAttachedIndex' WITH OPTIONS = {'ascii': 'true',
> 'case_sensitive': 'false', 'normalize': 'true'};
> CREATE CUSTOM INDEX registration_sai_idx ON cycling.cyclist_semi_pro
> (registration) USING 'StorageAttachedIndex';
> {code}
> Then I do:
> {code}
> cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE lastname in ('Cantona',
> 'Boyd');
> InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot
> execute this query as it might involve data filtering and thus may have
> unpredictable performance. If you want to execute this query despite the
> performance unpredictability, use ALLOW FILTERING"
> cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE lastname in ('Cantona',
> 'Boyd') ALLOW FILTERING;
> id | affiliation | age | country | firstname | lastname | registration
> +-+-+-+---+--+--
> 5 | Como Velocità | 24 | ITA | Irene | Cantona | 2012-07-22
> 20 | London Cyclists | 18 | GBR |Leslie | Boyd | 2012-12-15
> {code}
> But check this:
> {code}
> cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE registration >
> '2010-01-01' AND registration < '2015-12-31' and lastname in ('Cantona',
> 'Boyd') allow filtering;
> ReadFailure: Error from server: code=1300 [Replica(s) failed to execute read]
> message="Operation failed - received 0 responses and 1 failures: UNKNOWN from
> localhost/127.0.0.1:7000" info={'consistency': 'ONE', 'required_responses':
> 1, 'received_responses': 0, 'failures': 1, 'error_code_map': {'127.0.0.1':
> '0x'}}
> {code}
> and in the logs:
> {code}
> java.lang.AssertionError: null
> at
> org.apache.cassandra.index.sai.plan.Expression.add(Expression.java:171)
> at
> org.apache.cassandra.index.sai.plan.Operation.buildIndexExpressions(Operation.java:136)
> at
> org.apache.cassandra.index.sai.plan.Operation$AndNode.analyze(Operation.java:303)
> at
> org.apache.cassandra.index.sai.plan.Operation$Node.doTreeAnalysis(Operation.java:266)
> at
> org.apache.cassandra.index.sai.plan.Operation$Node.analyzeTree(Operation.java:251)
> at
> org.apache.cassandra.index.sai.plan.Operation.buildIterator(Operation.java:185)
> at
> org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher$ResultRetriever.(StorageAttachedIndexSearcher.java:151)
> at
> org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher.search(StorageAttachedIndexSearcher.java:107)
> at
> org.apache.cassandra.db.ReadCommand.executeLocally(ReadCommand.java:431)
> at
>
[jira] [Commented] (CASSANDRA-18533) Move format-specific sstable options into the format configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-18533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782193#comment-17782193
]
Branimir Lambov commented on CASSANDRA-18533:
-
I would keep it simple and not add a common settings entry under options. If
necessary, the user can copy the value to both.
> Move format-specific sstable options into the format configuration
> --
>
> Key: CASSANDRA-18533
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18533
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Schema, Local/SSTable
>Reporter: Branimir Lambov
>Assignee: Maxwell Guo
>Priority: Normal
> Fix For: 5.x
>
>
> This mainly concerns cassandra yaml settings:
> - {{column_index_size}}, which should also be renamed to
> {{row_index_granularity}}
> - {{column_index_cache_size}}
> - {{index_summary_capacity}}
> - {{index_summary_resize_interval}}
> and possibly
> - {{key_cache_size}}, {{key_cache_keys_to_save}}, {{key_cache_save_period}},
> {{key_cache_migrate_during_compaction}}
> - {{sstable_preemptive_open_interval}}
> Existing settings should be deprecated but still picked up if defined.
> At this point we will not consider table-level options that make better sense
> as format parameters ({{min/max_index_interval}}, {{bloom_filter_fp_chance}},
> {{crc_check_chance}} and possibly {{compression}}), because we do not yet
> support per-table format selection/configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18533) Move format-specific sstable options into the format configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-18533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779554#comment-17779554
]
Maxwell Guo edited comment on CASSANDRA-18533 at 11/2/23 3:18 PM:
--
[~blambov]Hi, I have some questions here.
1.we are going to put the format-specific options into the [option
map|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/io/sstable/format/AbstractSSTableFormat.java#L27]
here , am I right ?
2.it seems key_cache_size, key_cache_keys_to_save, key_cache_save_period, are
not sstable level but just for key cache which is db level, should I remove
them?
3.I am a little confusing now for table level configuration in CASSANDRA-18534
and options here. if we are going to define sstable option like [this
|https://github.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L1029],then
we may mix the table level options in CASSANDRA-18534 and the options here,
what I am thinking is that YAML needs to define several types of
configurations:(1) sstable option just for bti;(2) sstable option for big;(3)
common option that can be used in bti and big; if we have other sstable format
in the future ,we may need to expand this category.
{code:java}
sstable:
selected_format:big (or some use custom type like big-fast)
format.option:
-common:
row_index_granularity: xxx
-big:
bf_chance:
-bti:
xx
-bti-fast:
{code}
where all the custom-type sstable format will inherit common's option values
all will also have it's own custom option values, take their union as the final
value.
In this way, we can put all sstable configuration here, and CASSANDRA-18534 can
also define the table's custom type of sstable format, through ddl using
sstable_format = 'big', which can use the local yaml's value.
was (Author: maxwellguo):
[~blambov]Hi, I have some questions here.
1.we are going to put the format-specific options into the [option
map|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/io/sstable/format/AbstractSSTableFormat.java#L27]
here , am I right ?
2.it seems key_cache_size, key_cache_keys_to_save, key_cache_save_period, are
not sstable level but just for key cache which is db level, should I remove
them?
3.I am a little confusing now for table level configuration in CASSANDRA-18534
and options here. if we are going to define sstable option like [this
|https://github.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L1029],then
we may mix the table level options in CASSANDRA-18534 and the options here,
feeling not clear as we mix the table level configuration together with those
non-table level, should we separate them at yaml level, though the original
yaml do not define a configuration as table level or not .if we define sstable
format like this :
{code:java}
sstable:
selected_format: big
format.options:
- bit-fast:
row_index_granularity: 1kiB
bloom_filter_fp_chance: 0.01
- big-small:
row_index_granularity: 1kiB
bloom_filter_fp_chance: 0.01
{code}
what about change to
{code:java}
sstable:
selected_format: big
format.options:
- bit-fast:
row_index_granularity: 1kiB
table-level:
bloom_filter_fp_chance: 0.01
{code}
{code}
> Move format-specific sstable options into the format configuration
> --
>
> Key: CASSANDRA-18533
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18533
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Schema, Local/SSTable
>Reporter: Branimir Lambov
>Assignee: Maxwell Guo
>Priority: Normal
> Fix For: 5.x
>
>
> This mainly concerns cassandra yaml settings:
> - {{column_index_size}}, which should also be renamed to
> {{row_index_granularity}}
> - {{column_index_cache_size}}
> - {{index_summary_capacity}}
> - {{index_summary_resize_interval}}
> and possibly
> - {{key_cache_size}}, {{key_cache_keys_to_save}}, {{key_cache_save_period}},
> {{key_cache_migrate_during_compaction}}
> - {{sstable_preemptive_open_interval}}
> Existing settings should be deprecated but still picked up if defined.
> At this point we will not consider table-level options that make better sense
> as format parameters ({{min/max_index_interval}}, {{bloom_filter_fp_chance}},
> {{crc_check_chance}} and possibly {{compression}}), because we do not yet
> support per-table format selection/configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands,
[jira] [Updated] (CASSANDRA-18960) Upgrade Python driver to 3.28.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-18960:
--
Test and Documentation Plan:
||PR||CI||
|[5.0
|https://github.com/apache/cassandra/pull/2857]|[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/3273/workflows/662e9d41-5c0b-47af-9d1c-55495a12a3d4]
[j17|https://app.circleci.com/pipelines/github/adelapena/cassandra/3273/workflows/f189a08e-82a0-44e2-892b-0b6f63adf7b7]|
|[trunk|https://github.com/apache/cassandra/pull/2858]|[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/3274/workflows/0ac975f3-9292-4258-a551-3ca2a35821be]
[j17|https://app.circleci.com/pipelines/github/adelapena/cassandra/3274/workflows/56fa5e0d-04c5-44af-b4f3-55d42d7bb074]|
Status: Patch Available (was: In Progress)
> Upgrade Python driver to 3.28.0
> ---
>
> Key: CASSANDRA-18960
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18960
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Vector Search, Tool/cqlsh
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The version of the Python driver that is used by cqlsh (3.25.0) doesn't
> entirely support the new vector data type introduced by CASSANDRA-18504.
> While we can perfectly write data, read vectors are presented as blobs:
> {code}
> > CREATE TABLE t (k int PRIMARY KEY, v vector);
> > INSERT INTO t(k, v) VALUES (0, [1, 2]);
> > SELECT * FROM t;
> k | v
> ---+-
> 0 | b'\x00\x00\x00\x01\x00\x00\x00\x02'
> {code}
> I think that would we fixed if we update the driver to (at least) 3.28.0,
> which includes support for the new vector data type.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18960) Upgrade Python driver to 3.28.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782191#comment-17782191
]
Brandon Williams commented on CASSANDRA-18960:
--
bq. Then we will upgrade the driver again when it supports variable length
vectors.
That makes sense to me, and this looks good. +1
> Upgrade Python driver to 3.28.0
> ---
>
> Key: CASSANDRA-18960
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18960
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Vector Search, Tool/cqlsh
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The version of the Python driver that is used by cqlsh (3.25.0) doesn't
> entirely support the new vector data type introduced by CASSANDRA-18504.
> While we can perfectly write data, read vectors are presented as blobs:
> {code}
> > CREATE TABLE t (k int PRIMARY KEY, v vector);
> > INSERT INTO t(k, v) VALUES (0, [1, 2]);
> > SELECT * FROM t;
> k | v
> ---+-
> 0 | b'\x00\x00\x00\x01\x00\x00\x00\x02'
> {code}
> I think that would we fixed if we update the driver to (at least) 3.28.0,
> which includes support for the new vector data type.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18960) Upgrade Python driver to 3.28.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18960:
-
Reviewers: Brandon Williams
Status: Review In Progress (was: Patch Available)
> Upgrade Python driver to 3.28.0
> ---
>
> Key: CASSANDRA-18960
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18960
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Vector Search, Tool/cqlsh
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The version of the Python driver that is used by cqlsh (3.25.0) doesn't
> entirely support the new vector data type introduced by CASSANDRA-18504.
> While we can perfectly write data, read vectors are presented as blobs:
> {code}
> > CREATE TABLE t (k int PRIMARY KEY, v vector);
> > INSERT INTO t(k, v) VALUES (0, [1, 2]);
> > SELECT * FROM t;
> k | v
> ---+-
> 0 | b'\x00\x00\x00\x01\x00\x00\x00\x02'
> {code}
> I think that would we fixed if we update the driver to (at least) 3.28.0,
> which includes support for the new vector data type.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18960) Upgrade Python driver to 3.28.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18960:
-
Status: Ready to Commit (was: Review In Progress)
> Upgrade Python driver to 3.28.0
> ---
>
> Key: CASSANDRA-18960
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18960
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Vector Search, Tool/cqlsh
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The version of the Python driver that is used by cqlsh (3.25.0) doesn't
> entirely support the new vector data type introduced by CASSANDRA-18504.
> While we can perfectly write data, read vectors are presented as blobs:
> {code}
> > CREATE TABLE t (k int PRIMARY KEY, v vector);
> > INSERT INTO t(k, v) VALUES (0, [1, 2]);
> > SELECT * FROM t;
> k | v
> ---+-
> 0 | b'\x00\x00\x00\x01\x00\x00\x00\x02'
> {code}
> I think that would we fixed if we update the driver to (at least) 3.28.0,
> which includes support for the new vector data type.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18994) SAI range query does not play together with "IN"
[
https://issues.apache.org/jira/browse/CASSANDRA-18994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Adamson reassigned CASSANDRA-18994:
Assignee: Mike Adamson
> SAI range query does not play together with "IN"
>
>
> Key: CASSANDRA-18994
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18994
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/SAI
>Reporter: Stefan Miklosovic
>Assignee: Mike Adamson
>Priority: Normal
>
> I am using schema from the website's quickstart.
> {code}
> cqlsh> DESCRIBE KEYSPACE cycling ;
> CREATE KEYSPACE cycling WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;
> CREATE TABLE cycling.cyclist_semi_pro (
> id int PRIMARY KEY,
> affiliation text,
> age int,
> country text,
> firstname text,
> lastname text,
> registration date
> ) WITH additional_write_policy = '99p'
> AND allow_auto_snapshot = true
> AND bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND cdc = false
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '16', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND memtable = 'default'
> AND crc_check_chance = 1.0
> AND default_time_to_live = 0
> AND extensions = {}
> AND gc_grace_seconds = 864000
> AND incremental_backups = true
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair = 'BLOCKING'
> AND speculative_retry = '99p';
> CREATE CUSTOM INDEX age_sai_idx ON cycling.cyclist_semi_pro (age) USING
> 'StorageAttachedIndex';
> CREATE CUSTOM INDEX country_sai_idx ON cycling.cyclist_semi_pro (country)
> USING 'StorageAttachedIndex' WITH OPTIONS = {'ascii': 'true',
> 'case_sensitive': 'false', 'normalize': 'true'};
> CREATE CUSTOM INDEX lastname_sai_idx ON cycling.cyclist_semi_pro (lastname)
> USING 'StorageAttachedIndex' WITH OPTIONS = {'ascii': 'true',
> 'case_sensitive': 'false', 'normalize': 'true'};
> CREATE CUSTOM INDEX registration_sai_idx ON cycling.cyclist_semi_pro
> (registration) USING 'StorageAttachedIndex';
> {code}
> Then I do:
> {code}
> cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE lastname in ('Cantona',
> 'Boyd');
> InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot
> execute this query as it might involve data filtering and thus may have
> unpredictable performance. If you want to execute this query despite the
> performance unpredictability, use ALLOW FILTERING"
> cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE lastname in ('Cantona',
> 'Boyd') ALLOW FILTERING;
> id | affiliation | age | country | firstname | lastname | registration
> +-+-+-+---+--+--
> 5 | Como Velocità | 24 | ITA | Irene | Cantona | 2012-07-22
> 20 | London Cyclists | 18 | GBR |Leslie | Boyd | 2012-12-15
> {code}
> But check this:
> {code}
> cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE registration >
> '2010-01-01' AND registration < '2015-12-31' and lastname in ('Cantona',
> 'Boyd') allow filtering;
> ReadFailure: Error from server: code=1300 [Replica(s) failed to execute read]
> message="Operation failed - received 0 responses and 1 failures: UNKNOWN from
> localhost/127.0.0.1:7000" info={'consistency': 'ONE', 'required_responses':
> 1, 'received_responses': 0, 'failures': 1, 'error_code_map': {'127.0.0.1':
> '0x'}}
> {code}
> and in the logs:
> {code}
> java.lang.AssertionError: null
> at
> org.apache.cassandra.index.sai.plan.Expression.add(Expression.java:171)
> at
> org.apache.cassandra.index.sai.plan.Operation.buildIndexExpressions(Operation.java:136)
> at
> org.apache.cassandra.index.sai.plan.Operation$AndNode.analyze(Operation.java:303)
> at
> org.apache.cassandra.index.sai.plan.Operation$Node.doTreeAnalysis(Operation.java:266)
> at
> org.apache.cassandra.index.sai.plan.Operation$Node.analyzeTree(Operation.java:251)
> at
> org.apache.cassandra.index.sai.plan.Operation.buildIterator(Operation.java:185)
> at
> org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher$ResultRetriever.(StorageAttachedIndexSearcher.java:151)
> at
> org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher.search(StorageAttachedIndexSearcher.java:107)
> at
> org.apache.cassandra.db.ReadCommand.executeLocally(ReadCommand.java:431)
> at
>
[jira] [Updated] (CASSANDRA-18994) SAI range query does not play together with "IN"
[
https://issues.apache.org/jira/browse/CASSANDRA-18994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Adamson updated CASSANDRA-18994:
-
Bug Category: Parent values: Correctness(12982)
Complexity: Low Hanging Fruit
Discovered By: Adhoc Test
Severity: Low
Status: Open (was: Triage Needed)
> SAI range query does not play together with "IN"
>
>
> Key: CASSANDRA-18994
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18994
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/SAI
>Reporter: Stefan Miklosovic
>Assignee: Mike Adamson
>Priority: Normal
>
> I am using schema from the website's quickstart.
> {code}
> cqlsh> DESCRIBE KEYSPACE cycling ;
> CREATE KEYSPACE cycling WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;
> CREATE TABLE cycling.cyclist_semi_pro (
> id int PRIMARY KEY,
> affiliation text,
> age int,
> country text,
> firstname text,
> lastname text,
> registration date
> ) WITH additional_write_policy = '99p'
> AND allow_auto_snapshot = true
> AND bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND cdc = false
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '16', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND memtable = 'default'
> AND crc_check_chance = 1.0
> AND default_time_to_live = 0
> AND extensions = {}
> AND gc_grace_seconds = 864000
> AND incremental_backups = true
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair = 'BLOCKING'
> AND speculative_retry = '99p';
> CREATE CUSTOM INDEX age_sai_idx ON cycling.cyclist_semi_pro (age) USING
> 'StorageAttachedIndex';
> CREATE CUSTOM INDEX country_sai_idx ON cycling.cyclist_semi_pro (country)
> USING 'StorageAttachedIndex' WITH OPTIONS = {'ascii': 'true',
> 'case_sensitive': 'false', 'normalize': 'true'};
> CREATE CUSTOM INDEX lastname_sai_idx ON cycling.cyclist_semi_pro (lastname)
> USING 'StorageAttachedIndex' WITH OPTIONS = {'ascii': 'true',
> 'case_sensitive': 'false', 'normalize': 'true'};
> CREATE CUSTOM INDEX registration_sai_idx ON cycling.cyclist_semi_pro
> (registration) USING 'StorageAttachedIndex';
> {code}
> Then I do:
> {code}
> cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE lastname in ('Cantona',
> 'Boyd');
> InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot
> execute this query as it might involve data filtering and thus may have
> unpredictable performance. If you want to execute this query despite the
> performance unpredictability, use ALLOW FILTERING"
> cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE lastname in ('Cantona',
> 'Boyd') ALLOW FILTERING;
> id | affiliation | age | country | firstname | lastname | registration
> +-+-+-+---+--+--
> 5 | Como Velocità | 24 | ITA | Irene | Cantona | 2012-07-22
> 20 | London Cyclists | 18 | GBR |Leslie | Boyd | 2012-12-15
> {code}
> But check this:
> {code}
> cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE registration >
> '2010-01-01' AND registration < '2015-12-31' and lastname in ('Cantona',
> 'Boyd') allow filtering;
> ReadFailure: Error from server: code=1300 [Replica(s) failed to execute read]
> message="Operation failed - received 0 responses and 1 failures: UNKNOWN from
> localhost/127.0.0.1:7000" info={'consistency': 'ONE', 'required_responses':
> 1, 'received_responses': 0, 'failures': 1, 'error_code_map': {'127.0.0.1':
> '0x'}}
> {code}
> and in the logs:
> {code}
> java.lang.AssertionError: null
> at
> org.apache.cassandra.index.sai.plan.Expression.add(Expression.java:171)
> at
> org.apache.cassandra.index.sai.plan.Operation.buildIndexExpressions(Operation.java:136)
> at
> org.apache.cassandra.index.sai.plan.Operation$AndNode.analyze(Operation.java:303)
> at
> org.apache.cassandra.index.sai.plan.Operation$Node.doTreeAnalysis(Operation.java:266)
> at
> org.apache.cassandra.index.sai.plan.Operation$Node.analyzeTree(Operation.java:251)
> at
> org.apache.cassandra.index.sai.plan.Operation.buildIterator(Operation.java:185)
> at
> org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher$ResultRetriever.(StorageAttachedIndexSearcher.java:151)
> at
>
[jira] [Commented] (CASSANDRA-18533) Move format-specific sstable options into the format configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-18533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782184#comment-17782184
]
Branimir Lambov commented on CASSANDRA-18533:
-
1. Yes, precisely.
2. The key cache is constructed in a completely separate portion of the code,
isn't it? Ignore the key cache settings (except migration), I don't think
changing this is something we can do at the moment.
3. Although it is not at the moment, the row index granularity in particular
should be a table-level property -- there's no real reason to use one setting
for all tables, and there's an advantage to be had by making it configurable.
However, things like the key cache size or index summary capacity are something
to be shared, not just between tables but also potentially between formats; I
don't want to get into a complicated solution for this, I would either ignore
any table-level modification for these (with a warning) or check that the value
is the same among all tables. This, along with format variations (e.g.
"bti-fast"), is also out of scope for this ticket.
> Move format-specific sstable options into the format configuration
> --
>
> Key: CASSANDRA-18533
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18533
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Schema, Local/SSTable
>Reporter: Branimir Lambov
>Assignee: Maxwell Guo
>Priority: Normal
> Fix For: 5.x
>
>
> This mainly concerns cassandra yaml settings:
> - {{column_index_size}}, which should also be renamed to
> {{row_index_granularity}}
> - {{column_index_cache_size}}
> - {{index_summary_capacity}}
> - {{index_summary_resize_interval}}
> and possibly
> - {{key_cache_size}}, {{key_cache_keys_to_save}}, {{key_cache_save_period}},
> {{key_cache_migrate_during_compaction}}
> - {{sstable_preemptive_open_interval}}
> Existing settings should be deprecated but still picked up if defined.
> At this point we will not consider table-level options that make better sense
> as format parameters ({{min/max_index_interval}}, {{bloom_filter_fp_chance}},
> {{crc_check_chance}} and possibly {{compression}}), because we do not yet
> support per-table format selection/configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18969) Pre-release required legal changes for cassandra-java-driver
[ https://issues.apache.org/jira/browse/CASSANDRA-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782181#comment-17782181 ] Henry Hughes commented on CASSANDRA-18969: -- Despite being in `provided` scope, both `graal-sdk` and `spotbugs` do not need to be provided by developers at compile-time or runtime in order for java-driver to function correctly. I have a [change|[https://github.com/apache/cassandra-java-driver/pull/1741]] in progress to move `spotbugs` to `provided` scope and an working on adding a test to assert we're not including either of these deps when projects depend on java-driver. > Pre-release required legal changes for cassandra-java-driver > > > Key: CASSANDRA-18969 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18969 > Project: Cassandra > Issue Type: Sub-task > Components: Build >Reporter: Michael Semb Wever >Priority: Urgent > Time Spent: 20m > Remaining Estimate: 0h > > TODO > * there is still code copyrighted to others that isn't mentioned in > NOTICE.txt (e.g. ci/install-jdk.sh ) > * "© DataStax" still appears in the README > * spotbugs is LGPL, in 4.x, and not correctly made provided scope > * add any BSD/MIT deps to LICENCE > * ensure copyright headers are on all files, use rat plugin > These things must be done before a release. > Cat X deps we included as build tool by using scope provided we should put a > test in to ensure they work at runtime without the dep doesn't regress in the > future. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18969) Pre-release required legal changes for cassandra-java-driver
[ https://issues.apache.org/jira/browse/CASSANDRA-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782181#comment-17782181 ] Henry Hughes edited comment on CASSANDRA-18969 at 11/2/23 2:58 PM: --- Despite being in `provided` scope, both `graal-sdk` and `spotbugs` do not need to be provided by developers at compile-time or runtime in order for java-driver to function correctly. I have a [change|[https://github.com/apache/cassandra-java-driver/pull/1741]] in progress to move `spotbugs` to `provided` scope and an working on adding a test to assert we're not including either of these deps when projects depend on java-driver. was (Author: JIRAUSER301149): Despite being in `provided` scope, both `graal-sdk` and `spotbugs` do not need to be provided by developers at compile-time or runtime in order for java-driver to function correctly. I have a [change|[https://github.com/apache/cassandra-java-driver/pull/1741]] in progress to move `spotbugs` to `provided` scope and an working on adding a test to assert we're not including either of these deps when projects depend on java-driver. > Pre-release required legal changes for cassandra-java-driver > > > Key: CASSANDRA-18969 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18969 > Project: Cassandra > Issue Type: Sub-task > Components: Build >Reporter: Michael Semb Wever >Priority: Urgent > Time Spent: 20m > Remaining Estimate: 0h > > TODO > * there is still code copyrighted to others that isn't mentioned in > NOTICE.txt (e.g. ci/install-jdk.sh ) > * "© DataStax" still appears in the README > * spotbugs is LGPL, in 4.x, and not correctly made provided scope > * add any BSD/MIT deps to LICENCE > * ensure copyright headers are on all files, use rat plugin > These things must be done before a release. > Cat X deps we included as build tool by using scope provided we should put a > test in to ensure they work at runtime without the dep doesn't regress in the > future. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18969) Pre-release required legal changes for cassandra-java-driver
[ https://issues.apache.org/jira/browse/CASSANDRA-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782176#comment-17782176 ] Michael Semb Wever commented on CASSANDRA-18969: "For example, using a GPL'ed tool during the build is okay, but including GPL'ed source code is not." > Pre-release required legal changes for cassandra-java-driver > > > Key: CASSANDRA-18969 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18969 > Project: Cassandra > Issue Type: Sub-task > Components: Build >Reporter: Michael Semb Wever >Priority: Urgent > Time Spent: 20m > Remaining Estimate: 0h > > TODO > * there is still code copyrighted to others that isn't mentioned in > NOTICE.txt (e.g. ci/install-jdk.sh ) > * "© DataStax" still appears in the README > * spotbugs is LGPL, in 4.x, and not correctly made provided scope > * add any BSD/MIT deps to LICENCE > * ensure copyright headers are on all files, use rat plugin > These things must be done before a release. > Cat X deps we included as build tool by using scope provided we should put a > test in to ensure they work at runtime without the dep doesn't regress in the > future. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18969) Pre-release required legal changes for cassandra-java-driver
[ https://issues.apache.org/jira/browse/CASSANDRA-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18969: --- Description: TODO * there is still code copyrighted to others that isn't mentioned in NOTICE.txt (e.g. ci/install-jdk.sh ) * "© DataStax" still appears in the README * spotbugs is LGPL, in 4.x, and not correctly made provided scope * add any BSD/MIT deps to LICENCE * ensure copyright headers are on all files, use rat plugin These things must be done before a release. Cat X deps we included as build tool by using scope provided we should put a test in to ensure they work at runtime without the dep doesn't regress in the future. was: TODO * there is still code copyrighted to others that isn't mentioned in NOTICE.txt (alleged…?) * "© DataStax" still appears in the README * spotbugs is LGPL, in 4.x, and not correctly made provided scope * add any BSD/MIT deps to LICENCE * add copyright to a few missing files (e.g. ci/install-jdk.sh ), use rat plugin to ensure all These things must be done before a release. Cat X deps we included as build tool by using scope provided we should put a test in to ensure they work at runtime without the dep doesn't regress in the future. > Pre-release required legal changes for cassandra-java-driver > > > Key: CASSANDRA-18969 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18969 > Project: Cassandra > Issue Type: Sub-task > Components: Build >Reporter: Michael Semb Wever >Priority: Urgent > Time Spent: 20m > Remaining Estimate: 0h > > TODO > * there is still code copyrighted to others that isn't mentioned in > NOTICE.txt (e.g. ci/install-jdk.sh ) > * "© DataStax" still appears in the README > * spotbugs is LGPL, in 4.x, and not correctly made provided scope > * add any BSD/MIT deps to LICENCE > * ensure copyright headers are on all files, use rat plugin > These things must be done before a release. > Cat X deps we included as build tool by using scope provided we should put a > test in to ensure they work at runtime without the dep doesn't regress in the > future. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18969) Pre-release required legal changes for cassandra-java-driver
[ https://issues.apache.org/jira/browse/CASSANDRA-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782175#comment-17782175 ] Justin Mclean commented on CASSANDRA-18969: --- The NOTICE file contains: JNR project - Copyright (C) 2008-2010 Wayne Meissner Protocol Buffers - Copyright 2008 Google Inc. Guava - Copyright (C) 2007 The Guava Authors The file I mentioned above contains: (C) 2018 Christian Stein Can you please please show where ASF policy says it's OK for Category X to be in the provided scope? While ASF policy does make some exceptions for some well-known build tools, I don't think that applies here See https://www.apache.org/legal/resolved.html#build-tools So I fail to see how this is "Bullshit" as you put it. > Pre-release required legal changes for cassandra-java-driver > > > Key: CASSANDRA-18969 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18969 > Project: Cassandra > Issue Type: Sub-task > Components: Build >Reporter: Michael Semb Wever >Priority: Urgent > Time Spent: 20m > Remaining Estimate: 0h > > TODO > * there is still code copyrighted to others that isn't mentioned in > NOTICE.txt (alleged…?) > * "© DataStax" still appears in the README > * spotbugs is LGPL, in 4.x, and not correctly made provided scope > * add any BSD/MIT deps to LICENCE > * add copyright to a few missing files (e.g. ci/install-jdk.sh ), use rat > plugin to ensure all > These things must be done before a release. > Cat X deps we included as build tool by using scope provided we should put a > test in to ensure they work at runtime without the dep doesn't regress in the > future. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18533) Move format-specific sstable options into the format configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-18533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782170#comment-17782170
]
Maxwell Guo commented on CASSANDRA-18533:
-
ping [~blambov]
> Move format-specific sstable options into the format configuration
> --
>
> Key: CASSANDRA-18533
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18533
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Schema, Local/SSTable
>Reporter: Branimir Lambov
>Assignee: Maxwell Guo
>Priority: Normal
> Fix For: 5.x
>
>
> This mainly concerns cassandra yaml settings:
> - {{column_index_size}}, which should also be renamed to
> {{row_index_granularity}}
> - {{column_index_cache_size}}
> - {{index_summary_capacity}}
> - {{index_summary_resize_interval}}
> and possibly
> - {{key_cache_size}}, {{key_cache_keys_to_save}}, {{key_cache_save_period}},
> {{key_cache_migrate_during_compaction}}
> - {{sstable_preemptive_open_interval}}
> Existing settings should be deprecated but still picked up if defined.
> At this point we will not consider table-level options that make better sense
> as format parameters ({{min/max_index_interval}}, {{bloom_filter_fp_chance}},
> {{crc_check_chance}} and possibly {{compression}}), because we do not yet
> support per-table format selection/configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
Re: [PR] CASSANDRA-18969 - added missing copyrights [cassandra-java-driver]
Maxwell-Guo commented on code in PR #1742: URL: https://github.com/apache/cassandra-java-driver/pull/1742#discussion_r1380148838 ## NOTICE.txt: ## @@ -17,4 +17,9 @@ see core/src/main/java/com/datastax/oss/driver/internal/core/type/util/VIntCodin Guava Copyright (C) 2007 The Guava Authors This product includes software developed as part of the Guava project ( https://guava.dev ). -see core/src/main/java/com/datastax/oss/driver/internal/core/util/CountingIterator.java \ No newline at end of file +see core/src/main/java/com/datastax/oss/driver/internal/core/util/CountingIterator.java + +(C) 2018 Christian Stein +This product includes software developed by Christian Stein +see ci/install-jdk.sh + Review Comment: I think line 25 can be removed -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18990) Fix SAI docs issues
[
https://issues.apache.org/jira/browse/CASSANDRA-18990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782144#comment-17782144
]
Stefan Miklosovic edited comment on CASSANDRA-18990 at 11/2/23 1:32 PM:
[~polandll]
the links in "tip" at the very bottom of
https://cassandra.apache.org/doc/trunk/cassandra/getting-started/sai-quickstart.html
are broken
{code}
CREATE TABLE IF NOT EXISTS cycling.comments_vs (
record_id timeuuid,
id uuid,
commenter text,
comment text,
comment_vector VECTOR ;
created_at timestamp,
PRIMARY KEY (id, created_at)
)
WITH CLUSTERING ORDER BY (created_at DESC);
{code}
check "VECTOR;"
There should be "," instead of ";" otherwise it is invalid cql.
was (Author: smiklosovic):
[~polandll]
the links in "tip" at the very bottom of
https://cassandra.apache.org/doc/trunk/cassandra/getting-started/sai-quickstart.html
are broken
> Fix SAI docs issues
> ---
>
> Key: CASSANDRA-18990
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18990
> Project: Cassandra
> Issue Type: Task
>Reporter: Lorina Poland
>Assignee: Lorina Poland
>Priority: Normal
>
> # Change CREATE CUSTOM INDEX syntax to CREATE INDEX in SAI quickstart.
> # Consolidate SAI code examples.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[PR] CASSANDRA-18969 - added missing copyrights [cassandra-java-driver]
Claudenw opened a new pull request, #1742: URL: https://github.com/apache/cassandra-java-driver/pull/1742 added Christian Stein copyright notice performing grep for `[Cc]opyright`, `(C)`, and `(c)` only uncovered the one copyright not listed in the Notice file. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-82) Expose additional SSL configuration options for the Sidecar Service
[
https://issues.apache.org/jira/browse/CASSANDRASC-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francisco Guerrero updated CASSANDRASC-82:
--
Change Category: Operability
Complexity: Low Hanging Fruit
Assignee: Francisco Guerrero
Status: Open (was: Triage Needed)
> Expose additional SSL configuration options for the Sidecar Service
> ---
>
> Key: CASSANDRASC-82
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-82
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: low-hanging-fruit, lowhanging-fruit
>
> Sidecar exposes some SSL configuration options, but there are additional
> options that Sidecar should be exposing for users. Similar to what Cassandra
> offers in terms of configurations, we should be able to configure
> {{cipher_suites}} as well as {{accepted_protocols}} under SSL configuration.
> Additionally, we should explore if there are any other SSL knobs that
> Cassandra exposes that Sidecar doesn't and add it as part of this jira.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRASC-82) Expose additional SSL configuration options for the Sidecar Service
[
https://issues.apache.org/jira/browse/CASSANDRASC-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francisco Guerrero reassigned CASSANDRASC-82:
-
Assignee: (was: Francisco Guerrero)
> Expose additional SSL configuration options for the Sidecar Service
> ---
>
> Key: CASSANDRASC-82
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-82
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
>Reporter: Francisco Guerrero
>Priority: Normal
> Labels: low-hanging-fruit, lowhanging-fruit
>
> Sidecar exposes some SSL configuration options, but there are additional
> options that Sidecar should be exposing for users. Similar to what Cassandra
> offers in terms of configurations, we should be able to configure
> {{cipher_suites}} as well as {{accepted_protocols}} under SSL configuration.
> Additionally, we should explore if there are any other SSL knobs that
> Cassandra exposes that Sidecar doesn't and add it as part of this jira.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18990) Fix SAI docs issues
[ https://issues.apache.org/jira/browse/CASSANDRA-18990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782144#comment-17782144 ] Stefan Miklosovic commented on CASSANDRA-18990: --- [~polandll] the links in "tip" at the very bottom of https://cassandra.apache.org/doc/trunk/cassandra/getting-started/sai-quickstart.html are broken > Fix SAI docs issues > --- > > Key: CASSANDRA-18990 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18990 > Project: Cassandra > Issue Type: Task >Reporter: Lorina Poland >Assignee: Lorina Poland >Priority: Normal > > # Change CREATE CUSTOM INDEX syntax to CREATE INDEX in SAI quickstart. > # Consolidate SAI code examples. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18994) SAI range query does not play together with "IN"
[
https://issues.apache.org/jira/browse/CASSANDRA-18994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782142#comment-17782142
]
Stefan Miklosovic commented on CASSANDRA-18994:
---
[~maedhroz] [~mike_tr_adamson] I apologize in advance if this is a duplicate.
> SAI range query does not play together with "IN"
>
>
> Key: CASSANDRA-18994
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18994
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/SAI
>Reporter: Stefan Miklosovic
>Priority: Normal
>
> I am using schema from the website's quickstart.
> {code}
> cqlsh> DESCRIBE KEYSPACE cycling ;
> CREATE KEYSPACE cycling WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;
> CREATE TABLE cycling.cyclist_semi_pro (
> id int PRIMARY KEY,
> affiliation text,
> age int,
> country text,
> firstname text,
> lastname text,
> registration date
> ) WITH additional_write_policy = '99p'
> AND allow_auto_snapshot = true
> AND bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND cdc = false
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '16', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND memtable = 'default'
> AND crc_check_chance = 1.0
> AND default_time_to_live = 0
> AND extensions = {}
> AND gc_grace_seconds = 864000
> AND incremental_backups = true
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair = 'BLOCKING'
> AND speculative_retry = '99p';
> CREATE CUSTOM INDEX age_sai_idx ON cycling.cyclist_semi_pro (age) USING
> 'StorageAttachedIndex';
> CREATE CUSTOM INDEX country_sai_idx ON cycling.cyclist_semi_pro (country)
> USING 'StorageAttachedIndex' WITH OPTIONS = {'ascii': 'true',
> 'case_sensitive': 'false', 'normalize': 'true'};
> CREATE CUSTOM INDEX lastname_sai_idx ON cycling.cyclist_semi_pro (lastname)
> USING 'StorageAttachedIndex' WITH OPTIONS = {'ascii': 'true',
> 'case_sensitive': 'false', 'normalize': 'true'};
> CREATE CUSTOM INDEX registration_sai_idx ON cycling.cyclist_semi_pro
> (registration) USING 'StorageAttachedIndex';
> {code}
> Then I do:
> {code}
> cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE lastname in ('Cantona',
> 'Boyd');
> InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot
> execute this query as it might involve data filtering and thus may have
> unpredictable performance. If you want to execute this query despite the
> performance unpredictability, use ALLOW FILTERING"
> cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE lastname in ('Cantona',
> 'Boyd') ALLOW FILTERING;
> id | affiliation | age | country | firstname | lastname | registration
> +-+-+-+---+--+--
> 5 | Como Velocità | 24 | ITA | Irene | Cantona | 2012-07-22
> 20 | London Cyclists | 18 | GBR |Leslie | Boyd | 2012-12-15
> {code}
> But check this:
> {code}
> cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE registration >
> '2010-01-01' AND registration < '2015-12-31' and lastname in ('Cantona',
> 'Boyd') allow filtering;
> ReadFailure: Error from server: code=1300 [Replica(s) failed to execute read]
> message="Operation failed - received 0 responses and 1 failures: UNKNOWN from
> localhost/127.0.0.1:7000" info={'consistency': 'ONE', 'required_responses':
> 1, 'received_responses': 0, 'failures': 1, 'error_code_map': {'127.0.0.1':
> '0x'}}
> {code}
> and in the logs:
> {code}
> java.lang.AssertionError: null
> at
> org.apache.cassandra.index.sai.plan.Expression.add(Expression.java:171)
> at
> org.apache.cassandra.index.sai.plan.Operation.buildIndexExpressions(Operation.java:136)
> at
> org.apache.cassandra.index.sai.plan.Operation$AndNode.analyze(Operation.java:303)
> at
> org.apache.cassandra.index.sai.plan.Operation$Node.doTreeAnalysis(Operation.java:266)
> at
> org.apache.cassandra.index.sai.plan.Operation$Node.analyzeTree(Operation.java:251)
> at
> org.apache.cassandra.index.sai.plan.Operation.buildIterator(Operation.java:185)
> at
> org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher$ResultRetriever.(StorageAttachedIndexSearcher.java:151)
> at
> org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher.search(StorageAttachedIndexSearcher.java:107)
> at
> org.apache.cassandra.db.ReadCommand.executeLocally(ReadCommand.java:431)
>
[jira] [Created] (CASSANDRA-18994) SAI range query does not play together with "IN"
Stefan Miklosovic created CASSANDRA-18994:
-
Summary: SAI range query does not play together with "IN"
Key: CASSANDRA-18994
URL: https://issues.apache.org/jira/browse/CASSANDRA-18994
Project: Cassandra
Issue Type: Bug
Components: Feature/SAI
Reporter: Stefan Miklosovic
I am using schema from the website's quickstart.
{code}
cqlsh> DESCRIBE KEYSPACE cycling ;
CREATE KEYSPACE cycling WITH replication = {'class': 'SimpleStrategy',
'replication_factor': '1'} AND durable_writes = true;
CREATE TABLE cycling.cyclist_semi_pro (
id int PRIMARY KEY,
affiliation text,
age int,
country text,
firstname text,
lastname text,
registration date
) WITH additional_write_policy = '99p'
AND allow_auto_snapshot = true
AND bloom_filter_fp_chance = 0.01
AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND cdc = false
AND comment = ''
AND compaction = {'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}
AND compression = {'chunk_length_in_kb': '16', 'class':
'org.apache.cassandra.io.compress.LZ4Compressor'}
AND memtable = 'default'
AND crc_check_chance = 1.0
AND default_time_to_live = 0
AND extensions = {}
AND gc_grace_seconds = 864000
AND incremental_backups = true
AND max_index_interval = 2048
AND memtable_flush_period_in_ms = 0
AND min_index_interval = 128
AND read_repair = 'BLOCKING'
AND speculative_retry = '99p';
CREATE CUSTOM INDEX age_sai_idx ON cycling.cyclist_semi_pro (age) USING
'StorageAttachedIndex';
CREATE CUSTOM INDEX country_sai_idx ON cycling.cyclist_semi_pro (country) USING
'StorageAttachedIndex' WITH OPTIONS = {'ascii': 'true', 'case_sensitive':
'false', 'normalize': 'true'};
CREATE CUSTOM INDEX lastname_sai_idx ON cycling.cyclist_semi_pro (lastname)
USING 'StorageAttachedIndex' WITH OPTIONS = {'ascii': 'true', 'case_sensitive':
'false', 'normalize': 'true'};
CREATE CUSTOM INDEX registration_sai_idx ON cycling.cyclist_semi_pro
(registration) USING 'StorageAttachedIndex';
{code}
Then I do:
{code}
cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE lastname in ('Cantona',
'Boyd');
InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot
execute this query as it might involve data filtering and thus may have
unpredictable performance. If you want to execute this query despite the
performance unpredictability, use ALLOW FILTERING"
cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE lastname in ('Cantona',
'Boyd') ALLOW FILTERING;
id | affiliation | age | country | firstname | lastname | registration
+-+-+-+---+--+--
5 | Como Velocità | 24 | ITA | Irene | Cantona | 2012-07-22
20 | London Cyclists | 18 | GBR |Leslie | Boyd | 2012-12-15
{code}
But check this:
{code}
cqlsh> SELECT * FROM cycling.cyclist_semi_pro WHERE registration > '2010-01-01'
AND registration < '2015-12-31' and lastname in ('Cantona', 'Boyd') allow
filtering;
ReadFailure: Error from server: code=1300 [Replica(s) failed to execute read]
message="Operation failed - received 0 responses and 1 failures: UNKNOWN from
localhost/127.0.0.1:7000" info={'consistency': 'ONE', 'required_responses': 1,
'received_responses': 0, 'failures': 1, 'error_code_map': {'127.0.0.1':
'0x'}}
{code}
and in the logs:
{code}
java.lang.AssertionError: null
at
org.apache.cassandra.index.sai.plan.Expression.add(Expression.java:171)
at
org.apache.cassandra.index.sai.plan.Operation.buildIndexExpressions(Operation.java:136)
at
org.apache.cassandra.index.sai.plan.Operation$AndNode.analyze(Operation.java:303)
at
org.apache.cassandra.index.sai.plan.Operation$Node.doTreeAnalysis(Operation.java:266)
at
org.apache.cassandra.index.sai.plan.Operation$Node.analyzeTree(Operation.java:251)
at
org.apache.cassandra.index.sai.plan.Operation.buildIterator(Operation.java:185)
at
org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher$ResultRetriever.(StorageAttachedIndexSearcher.java:151)
at
org.apache.cassandra.index.sai.plan.StorageAttachedIndexSearcher.search(StorageAttachedIndexSearcher.java:107)
at
org.apache.cassandra.db.ReadCommand.executeLocally(ReadCommand.java:431)
at
org.apache.cassandra.service.StorageProxy$LocalReadRunnable.runMayThrow(StorageProxy.java:2184)
at
org.apache.cassandra.service.StorageProxy$DroppableRunnable.run(StorageProxy.java:2581)
at
org.apache.cassandra.concurrent.ExecutionFailure$2.run(ExecutionFailure.java:163)
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:143)
{code}
If it is not supported it should not throw and it should print appropriate
message.
[jira] [Commented] (CASSANDRA-18314) Lift MessagingService.minimum_version to 40
[
https://issues.apache.org/jira/browse/CASSANDRA-18314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782118#comment-17782118
]
Aleksey Yeschenko commented on CASSANDRA-18314:
---
I think you may have been overly enthusiastic with these removals.
Specifically, removing 3.0 deser support for {{Mutation}} affects more than
just messaging service. Even in 5.0 you still need to be able to deserialize
old mutations in hints, commit log, and batch log. Someone going from 3.0 via
4.0 to 5.0 will still have those present.
> Lift MessagingService.minimum_version to 40
> ---
>
> Key: CASSANDRA-18314
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18314
> Project: Cassandra
> Issue Type: Task
> Components: Messaging/Internode
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 5.0, 5.0-alpha1
>
> Time Spent: 15h 20m
> Remaining Estimate: 0h
>
> MessagingService's VERSION_30 and VERSION_3014 don't have to be supported in
> Cassandra 5.0 anymore.
> (Cassandra 5.0 currently is still using VERSION_40)
> Patch:
> https://github.com/apache/cassandra/compare/trunk...thelastpickle:cassandra:mck/18314/trunk
> Raises the question whether backward compatibility to the previous major is
> defined by the Cassandra version or by the internal component version
> (MessagingService).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18960) Upgrade Python driver to 3.28.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña reassigned CASSANDRA-18960:
-
Assignee: Andres de la Peña
> Upgrade Python driver to 3.28.0
> ---
>
> Key: CASSANDRA-18960
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18960
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Vector Search, Tool/cqlsh
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The version of the Python driver that is used by cqlsh (3.25.0) doesn't
> entirely support the new vector data type introduced by CASSANDRA-18504.
> While we can perfectly write data, read vectors are presented as blobs:
> {code}
> > CREATE TABLE t (k int PRIMARY KEY, v vector);
> > INSERT INTO t(k, v) VALUES (0, [1, 2]);
> > SELECT * FROM t;
> k | v
> ---+-
> 0 | b'\x00\x00\x00\x01\x00\x00\x00\x02'
> {code}
> I think that would we fixed if we update the driver to (at least) 3.28.0,
> which includes support for the new vector data type.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18960) Upgrade Python driver to 3.28.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-18960:
--
Change Category: Semantic
Complexity: Low Hanging Fruit
Status: Open (was: Triage Needed)
> Upgrade Python driver to 3.28.0
> ---
>
> Key: CASSANDRA-18960
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18960
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Vector Search, Tool/cqlsh
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The version of the Python driver that is used by cqlsh (3.25.0) doesn't
> entirely support the new vector data type introduced by CASSANDRA-18504.
> While we can perfectly write data, read vectors are presented as blobs:
> {code}
> > CREATE TABLE t (k int PRIMARY KEY, v vector);
> > INSERT INTO t(k, v) VALUES (0, [1, 2]);
> > SELECT * FROM t;
> k | v
> ---+-
> 0 | b'\x00\x00\x00\x01\x00\x00\x00\x02'
> {code}
> I think that would we fixed if we update the driver to (at least) 3.28.0,
> which includes support for the new vector data type.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
(cassandra-java-driver) branch 4.x updated: Add .asf.yaml (CASSANDRA-18969)
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch 4.x in repository https://gitbox.apache.org/repos/asf/cassandra-java-driver.git The following commit(s) were added to refs/heads/4.x by this push: new 2bf500e0c Add .asf.yaml (CASSANDRA-18969) 2bf500e0c is described below commit 2bf500e0ce6fee0ba464916a100070a5f4d99cec Author: mck AuthorDate: Thu Nov 2 11:26:29 2023 +0100 Add .asf.yaml (CASSANDRA-18969) https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features --- .asf.yaml | 19 +++ README.md | 5 + 2 files changed, 20 insertions(+), 4 deletions(-) diff --git a/.asf.yaml b/.asf.yaml new file mode 100644 index 0..c6549f8ee --- /dev/null +++ b/.asf.yaml @@ -0,0 +1,19 @@ +notifications: + commits: commits@cassandra.apache.org + issues: commits@cassandra.apache.org + pullrequests: p...@cassandra.apache.org + +github: + description: "Java Driver for Apache Cassandra®" + homepage: https://cassandra.apache.org/ + enabled_merge_buttons: +squash: false +merge: false +rebase: true + features: +wiki: false +issues: false +projects: false + +notifications: + jira_options: link worklog diff --git a/README.md b/README.md index 78aee1887..b43b90b71 100644 --- a/README.md +++ b/README.md @@ -96,7 +96,7 @@ See the [Cassandra error handling done right blog](https://www.datastax.com/blog ## License - DataStax, Inc. + The Apache Software Foundation Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. @@ -112,9 +112,6 @@ limitations under the License. -DataStax is a registered trademark of DataStax, Inc. and its subsidiaries in the United States -and/or other countries. - Apache Cassandra, Apache, Tomcat, Lucene, Solr, Hadoop, Spark, TinkerPop, and Cassandra are trademarks of the [Apache Software Foundation](http://www.apache.org/) or its subsidiaries in Canada, the United States and/or other countries. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18969) Pre-release required legal changes for cassandra-java-driver
[ https://issues.apache.org/jira/browse/CASSANDRA-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18969: --- Description: TODO * there is still code copyrighted to others that isn't mentioned in NOTICE.txt (alleged…?) * "© DataStax" still appears in the README * spotbugs is LGPL, in 4.x, and not correctly made provided scope * add any BSD/MIT deps to LICENCE * add copyright to a few missing files (e.g. ci/install-jdk.sh ), use rat plugin to ensure all These things must be done before a release. Cat X deps we included as build tool by using scope provided we should put a test in to ensure they work at runtime without the dep doesn't regress in the future. was: TODO * there is still code copyrighted to others that isn't mentioned in NOTICE.txt * "© DataStax" still appears in the README * spotbugs is LGPL, in 4.x, and not correctly made provided scope * add any BSD/MIT deps to LICENCE * add copyright to a few missing files (e.g. ci/install-jdk.sh ), use rat plugin to ensure all These things must be done before a release. Cat X deps we included as build tool by using scope provided we should put a test in to ensure they work at runtime without the dep doesn't regress in the future. > Pre-release required legal changes for cassandra-java-driver > > > Key: CASSANDRA-18969 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18969 > Project: Cassandra > Issue Type: Sub-task > Components: Build >Reporter: Michael Semb Wever >Priority: Urgent > > TODO > * there is still code copyrighted to others that isn't mentioned in > NOTICE.txt (alleged…?) > * "© DataStax" still appears in the README > * spotbugs is LGPL, in 4.x, and not correctly made provided scope > * add any BSD/MIT deps to LICENCE > * add copyright to a few missing files (e.g. ci/install-jdk.sh ), use rat > plugin to ensure all > These things must be done before a release. > Cat X deps we included as build tool by using scope provided we should put a > test in to ensure they work at runtime without the dep doesn't regress in the > future. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18975) Remove deprecated code in Cassandra 3.x for Cassandra 5.0
[ https://issues.apache.org/jira/browse/CASSANDRA-18975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782068#comment-17782068 ] Stefan Miklosovic edited comment on CASSANDRA-18975 at 11/2/23 9:10 AM: Circle build for the above branch seems good [https://app.circleci.com/pipelines/github/instaclustr/cassandra/3420/workflows/06439753-b9be-460e-ad1c-419c81b2a594] was (Author: smiklosovic): Circle build for the above branch seems good [https://app.circleci.com/pipelines/github/instaclustr/cassandra?branch=CASSANDRA-18975-trunk|https://app.circleci.com/pipelines/github/instaclustr/cassandra/3420/workflows/06439753-b9be-460e-ad1c-419c81b2a594] > Remove deprecated code in Cassandra 3.x for Cassandra 5.0 > - > > Key: CASSANDRA-18975 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18975 > Project: Cassandra > Issue Type: Task > Components: Legacy/Core >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Labels: code-polishing > Fix For: 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > This ticket tracks the removal of deprecations which were added in Cassandra > 3.x for Cassandra 5 > ||Deprecation||jmx/public||interface||notes|| > |[/src/java/org/apache/cassandra/db/ColumnFamilyStore.java#L282|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/db/ColumnFamilyStore.java#L282]|no|no| > | > |[/src/java/org/apache/cassandra/db/ColumnFamilyStore.java#L924|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/db/ColumnFamilyStore.java#L924]|no|no| > | > |[/src/java/org/apache/cassandra/db/ColumnFamilyStoreMBean.java#L43|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/db/ColumnFamilyStoreMBean.java#L43]|yes|yes| > | > |[/src/java/org/apache/cassandra/db/filter/RowFilter.java#L470|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/db/filter/RowFilter.java#L470]|no|no|.| > |[/src/java/org/apache/cassandra/schema/CompressionParams.java#L85|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/schema/CompressionParams.java#L85]|no|no|CASSANDRA-18872| > |[/src/java/org/apache/cassandra/config/Config.java#L794|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/config/Config.java#L794]|yes|no|.| > |[/src/java/org/apache/cassandra/config/Config.java#L834|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/config/Config.java#L834]|yes|no|.| > |[/src/java/org/apache/cassandra/service/StorageService.java#L343|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageService.java#L343]|no|no|.| > |[/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L273|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L273]|yes|yes|.| > |[/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L279|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L279]|yes|yes|.| > |[/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L285|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L285]|yes|yes|.| > |[/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L375|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L375]|yes|yes|.| > |[/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L405|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L405]|yes|yes|.| > |[/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L423|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L423]|yes|yes|.| > |[/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L430|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L430]|yes|yes|.| >
[jira] [Commented] (CASSANDRA-18975) Remove deprecated code in Cassandra 3.x for Cassandra 5.0
[ https://issues.apache.org/jira/browse/CASSANDRA-18975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782068#comment-17782068 ] Stefan Miklosovic commented on CASSANDRA-18975: --- Circle build for the above branch seems good [https://app.circleci.com/pipelines/github/instaclustr/cassandra?branch=CASSANDRA-18975-trunk|https://app.circleci.com/pipelines/github/instaclustr/cassandra/3420/workflows/06439753-b9be-460e-ad1c-419c81b2a594] > Remove deprecated code in Cassandra 3.x for Cassandra 5.0 > - > > Key: CASSANDRA-18975 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18975 > Project: Cassandra > Issue Type: Task > Components: Legacy/Core >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Labels: code-polishing > Fix For: 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > This ticket tracks the removal of deprecations which were added in Cassandra > 3.x for Cassandra 5 > ||Deprecation||jmx/public||interface||notes|| > |[/src/java/org/apache/cassandra/db/ColumnFamilyStore.java#L282|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/db/ColumnFamilyStore.java#L282]|no|no| > | > |[/src/java/org/apache/cassandra/db/ColumnFamilyStore.java#L924|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/db/ColumnFamilyStore.java#L924]|no|no| > | > |[/src/java/org/apache/cassandra/db/ColumnFamilyStoreMBean.java#L43|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/db/ColumnFamilyStoreMBean.java#L43]|yes|yes| > | > |[/src/java/org/apache/cassandra/db/filter/RowFilter.java#L470|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/db/filter/RowFilter.java#L470]|no|no|.| > |[/src/java/org/apache/cassandra/schema/CompressionParams.java#L85|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/schema/CompressionParams.java#L85]|no|no|CASSANDRA-18872| > |[/src/java/org/apache/cassandra/config/Config.java#L794|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/config/Config.java#L794]|yes|no|.| > |[/src/java/org/apache/cassandra/config/Config.java#L834|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/config/Config.java#L834]|yes|no|.| > |[/src/java/org/apache/cassandra/service/StorageService.java#L343|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageService.java#L343]|no|no|.| > |[/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L273|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L273]|yes|yes|.| > |[/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L279|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L279]|yes|yes|.| > |[/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L285|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L285]|yes|yes|.| > |[/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L375|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L375]|yes|yes|.| > |[/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L405|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L405]|yes|yes|.| > |[/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L423|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L423]|yes|yes|.| > |[/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L430|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L430]|yes|yes|.| > |[/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L452|https://github.com/apache/cassandra/blob/3d022d3c5f2512e03c8c7fbc52de70afd058b2e7/src/java/org/apache/cassandra/service/StorageServiceMBean.java#L452]|yes|yes|.| >
[jira] [Updated] (CASSANDRA-18969) Pre-release required legal changes for cassandra-java-driver
[ https://issues.apache.org/jira/browse/CASSANDRA-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18969: --- Change Category: Semantic Complexity: Low Hanging Fruit Priority: Urgent (was: Normal) Status: Open (was: Triage Needed) > Pre-release required legal changes for cassandra-java-driver > > > Key: CASSANDRA-18969 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18969 > Project: Cassandra > Issue Type: Sub-task > Components: Build >Reporter: Michael Semb Wever >Priority: Urgent > > TODO > * there is still code copyrighted to others that isn't mentioned in NOTICE.txt > * "© DataStax" still appears in the README > * spotbugs is LGPL, in 4.x, and not correctly made provided scope > * add any BSD/MIT deps to LICENCE > * add copyright to a few missing files (e.g. ci/install-jdk.sh ), use rat > plugin to ensure all > These things must be done before a release. > Cat X deps we included as build tool by using scope provided we should put a > test in to ensure they work at runtime without the dep doesn't regress in the > future. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18969) Pre-release required legal changes for cassandra-java-driver
[ https://issues.apache.org/jira/browse/CASSANDRA-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782054#comment-17782054 ] Michael Semb Wever commented on CASSANDRA-18969: Calling bullshit, please do your homework first Justin, you're now just wasting everyone's time here. The copyright is in the NOTICE file. And this is clear as it's intentionally the last commit before the donation. Provided scope, for the sake of build tools, while the distribution binary otherwise runs without it, is explicitly documented as ok for cat X. > Pre-release required legal changes for cassandra-java-driver > > > Key: CASSANDRA-18969 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18969 > Project: Cassandra > Issue Type: Sub-task > Components: Build >Reporter: Michael Semb Wever >Priority: Normal > > TODO > * there is still code copyrighted to others that isn't mentioned in NOTICE.txt > * "© DataStax" still appears in the README > * spotbugs is LGPL, in 4.x, and not correctly made provided scope > * add any BSD/MIT deps to LICENCE > * add copyright to a few missing files (e.g. ci/install-jdk.sh ), use rat > plugin to ensure all > These things must be done before a release. > Cat X deps we included as build tool by using scope provided we should put a > test in to ensure they work at runtime without the dep doesn't regress in the > future. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18969) Pre-release required legal changes for cassandra-java-driver
[ https://issues.apache.org/jira/browse/CASSANDRA-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18969: --- Description: TODO * there is still code copyrighted to others that isn't mentioned in NOTICE.txt * "© DataStax" still appears in the README * spotbugs is LGPL, in 4.x, and not correctly made provided scope * add any BSD/MIT deps to LICENCE * add copyright to a few missing files (e.g. These things must be done before a release. Cat X deps we included as build tool by using scope provided we should put a test in to ensure they work at runtime without the dep doesn't regress in the future. was: TODO * there is still code copyrighted to others that isn't mentioned in NOTICE.txt * "© DataStax" still appears in the README * spotbugs is LGPL, in 4.x, and not correctly made provided scope * add any BSD/MIT deps to LICENCE These things must be done before a release. > Pre-release required legal changes for cassandra-java-driver > > > Key: CASSANDRA-18969 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18969 > Project: Cassandra > Issue Type: Sub-task > Components: Build >Reporter: Michael Semb Wever >Priority: Normal > > TODO > * there is still code copyrighted to others that isn't mentioned in NOTICE.txt > * "© DataStax" still appears in the README > * spotbugs is LGPL, in 4.x, and not correctly made provided scope > * add any BSD/MIT deps to LICENCE > * add copyright to a few missing files (e.g. > These things must be done before a release. > Cat X deps we included as build tool by using scope provided we should put a > test in to ensure they work at runtime without the dep doesn't regress in the > future. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
