[cassandra-website] branch asf-staging updated (2f0b81998 -> 15917b99e)
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 2f0b81998 generate docs for 207dbf1f new 15917b99e generate docs for 207dbf1f 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 (2f0b81998) \ N -- N -- N refs/heads/asf-staging (15917b99e) 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
[cassandra-website] branch asf-staging updated (e353f3735 -> 2f0b81998)
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 e353f3735 generate docs for 207dbf1f new 2f0b81998 generate docs for 207dbf1f 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 (e353f3735) \ N -- N -- N refs/heads/asf-staging (2f0b81998) 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-16565) Remove dependency on sigar
[ https://issues.apache.org/jira/browse/CASSANDRA-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780116#comment-17780116 ] Stefan Miklosovic commented on CASSANDRA-16565: --- The review was given on the PR. Bunch of stuff. I had some time on my hands so I prepared a PR with everything I found and I created a PR against [~claude]'s branch. I in particular prefer to simplify the actual logic around degradations. The idea is visible in the PR I created. (1) https://github.com/Claudenw/cassandra/pull/6 > Remove dependency on sigar > -- > > Key: CASSANDRA-16565 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16565 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: David Capwell >Assignee: Claude Warren >Priority: Normal > Fix For: 5.x > > > sigar is used to check if the environment has good settings for running C*, > but requires we bundle a lot of native libraries to perform this check (which > can also be done elsewhere). This project also appears to be dead as the > last commit was around 6 years ago. > With the move to resolve artifacts rather than commit them, removing this > dependency would remove majority of the artifacts fetched from GitHub. -- 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-16565) Remove dependency on sigar
[ https://issues.apache.org/jira/browse/CASSANDRA-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-16565: -- Status: Changes Suggested (was: Review In Progress) > Remove dependency on sigar > -- > > Key: CASSANDRA-16565 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16565 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: David Capwell >Assignee: Claude Warren >Priority: Normal > Fix For: 5.x > > > sigar is used to check if the environment has good settings for running C*, > but requires we bundle a lot of native libraries to perform this check (which > can also be done elsewhere). This project also appears to be dead as the > last commit was around 6 years ago. > With the move to resolve artifacts rather than commit them, removing this > dependency would remove majority of the artifacts fetched from GitHub. -- 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-accord] branch trunk updated: CEP-15: (C*) Implement TopologySorter to prioritise hosts based on DynamicSnitch and/or topology layout (#72)
This is an automated email from the ASF dual-hosted git repository.
dcapwell pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-accord.git
The following commit(s) were added to refs/heads/trunk by this push:
new d99ad84c CEP-15: (C*) Implement TopologySorter to prioritise hosts
based on DynamicSnitch and/or topology layout (#72)
d99ad84c is described below
commit d99ad84cc49a96299a9ae55183e38ee6f1aa3f47
Author: dcapwell
AuthorDate: Thu Oct 26 15:44:43 2023 -0700
CEP-15: (C*) Implement TopologySorter to prioritise hosts based on
DynamicSnitch and/or topology layout (#72)
patch by David Capwell; reviewed by Blake Eggleston for CASSANDRA-18929
---
.../src/main/java/accord/topology/Topologies.java | 72 ++
.../main/java/accord/topology/TopologyManager.java | 13 ++--
.../java/accord/messages/TxnRequestScopeTest.java | 8 +--
3 files changed, 56 insertions(+), 37 deletions(-)
diff --git a/accord-core/src/main/java/accord/topology/Topologies.java
b/accord-core/src/main/java/accord/topology/Topologies.java
index 5832cce0..1d729d29 100644
--- a/accord-core/src/main/java/accord/topology/Topologies.java
+++ b/accord-core/src/main/java/accord/topology/Topologies.java
@@ -260,29 +260,25 @@ public interface Topologies extends TopologySorter
private final List topologies;
private final int maxShardsPerEpoch;
-public Multi(TopologySorter.Supplier sorter, int initialCapacity)
-{
-this.topologies = new ArrayList<>(initialCapacity);
-this.supplier = sorter;
-this.sorter = sorter.get(this);
-int maxShardsPerEpoch = 0;
-for (int i = 0 ; i < topologies.size() ; ++i)
-maxShardsPerEpoch = Math.max(maxShardsPerEpoch,
topologies.get(i).size());
-this.maxShardsPerEpoch = maxShardsPerEpoch;
-}
-
public Multi(TopologySorter.Supplier sorter, Topology... topologies)
{
-this(sorter, topologies.length);
-for (Topology topology : topologies)
-add(topology);
+this(sorter, Arrays.asList(topologies));
}
-public Multi(TopologySorter.Supplier sorter, List topologies)
+public Multi(TopologySorter.Supplier sorter, List input)
{
-this(sorter, topologies.size());
-for (Topology topology : topologies)
-add(topology);
+this.topologies = new ArrayList<>(input.size());
+for (Topology topology : input)
+{
+Invariants.checkArgument(topologies.isEmpty() ||
topology.epoch == topologies.get(topologies.size() - 1).epoch - 1);
+topologies.add(topology);
+}
+int maxShardsPerEpoch = 0;
+for (int i = 0 ; i < topologies.size() ; ++i)
+maxShardsPerEpoch = Math.max(maxShardsPerEpoch,
topologies.get(i).size());
+this.maxShardsPerEpoch = maxShardsPerEpoch;
+this.supplier = sorter;
+this.sorter = sorter.get(this);
}
@Override
@@ -392,12 +388,6 @@ public interface Topologies extends TopologySorter
return maxShardsPerEpoch;
}
-public void add(Topology topology)
-{
-Invariants.checkArgument(topologies.isEmpty() || topology.epoch ==
topologies.get(topologies.size() - 1).epoch - 1);
-topologies.add(topology);
-}
-
@Override
public boolean equals(Object obj)
{
@@ -422,4 +412,38 @@ public interface Topologies extends TopologySorter
return sorter.compare(node1, node2, shards);
}
}
+
+class Builder
+{
+private final List topologies;
+
+public Builder(int initialCapacity)
+{
+topologies = new ArrayList<>(initialCapacity);
+}
+
+public void add(Topology topology)
+{
+Invariants.checkArgument(topologies.isEmpty() || topology.epoch ==
topologies.get(topologies.size() - 1).epoch - 1);
+topologies.add(topology);
+}
+
+public boolean isEmpty()
+{
+return topologies.isEmpty();
+}
+
+public Topologies build(TopologySorter.Supplier sorter)
+{
+switch (topologies.size())
+{
+case 0:
+throw new IllegalStateException("Unable to build an empty
Topologies");
+case 1:
+return new Single(sorter, topologies.get(0));
+default:
+return new Multi(sorter, topologies);
+}
+}
+}
}
diff --git a/accord-core/src/main/java/accord/topology/TopologyManager.java
b/accord-core/src/main/java/accord/topology/TopologyManager.java
index a940b109..dcb499c4 100644
--- a/accord-core/src/main/java/accord/topology/TopologyManager.java
+++ b/accor
[jira] [Updated] (CASSANDRA-18929) CEP-15: (C*) Implement TopologySorter to prioritise hosts based on DynamicSnitch and/or topology layout
[ https://issues.apache.org/jira/browse/CASSANDRA-18929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-18929: Status: Ready to Commit (was: Review In Progress) +1 > CEP-15: (C*) Implement TopologySorter to prioritise hosts based on > DynamicSnitch and/or topology layout > --- > > Key: CASSANDRA-18929 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18929 > Project: Cassandra > Issue Type: Improvement > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > Implement TopologySorter to prioritise hosts based on DynamicSnitch and/or > topology layout -- 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-18929) CEP-15: (C*) Implement TopologySorter to prioritise hosts based on DynamicSnitch and/or topology layout
[ https://issues.apache.org/jira/browse/CASSANDRA-18929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-18929: Reviewers: Blake Eggleston Status: Review In Progress (was: Patch Available) > CEP-15: (C*) Implement TopologySorter to prioritise hosts based on > DynamicSnitch and/or topology layout > --- > > Key: CASSANDRA-18929 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18929 > Project: Cassandra > Issue Type: Improvement > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > Implement TopologySorter to prioritise hosts based on DynamicSnitch and/or > topology layout -- 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 (97c6afa31 -> e353f3735)
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 97c6afa31 generate docs for 207dbf1f new e353f3735 generate docs for 207dbf1f 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 (97c6afa31) \ N -- N -- N refs/heads/asf-staging (e353f3735) 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: .../cassandra/developing/cql/cql_singlefile.html | 25 +-- content/doc/5.0/cassandra/developing/cql/ddl.html | 6 - .../cassandra/managing/operating/compression.html | 27 +++-- .../cassandra/developing/cql/cql_singlefile.html | 25 +-- content/doc/5.1/cassandra/developing/cql/ddl.html | 6 - .../cassandra/managing/operating/compression.html | 27 +++-- .../cassandra/developing/cql/cql_singlefile.html | 25 +-- .../doc/trunk/cassandra/developing/cql/ddl.html| 6 - .../cassandra/managing/operating/compression.html | 27 +++-- site-ui/build/ui-bundle.zip| Bin 4881412 -> 4881412 bytes 10 files changed, 90 insertions(+), 84 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18967) Aggregation (SUM) in a transaction block fails
[
https://issues.apache.org/jira/browse/CASSANDRA-18967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18967:
-
Bug Category: Parent values: Correctness(12982)Level 1 values: Transient
Incorrect Response(12987)
Complexity: Normal
Component/s: Accord
Discovered By: User Report
Fix Version/s: 5.x
Severity: Normal
Status: Open (was: Triage Needed)
> Aggregation (SUM) in a transaction block fails
> --
>
> Key: CASSANDRA-18967
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18967
> Project: Cassandra
> Issue Type: Bug
> Components: Accord
>Reporter: Luis E Fernandez
>Priority: Normal
> Fix For: 5.x
>
>
> *System configuration and information:*
> Single node Cassandra with Accord transactions enabled running on docker
> Built from commit:
> [a7cd114435704b988c81f47ef53d0bfd6441f38b|https://github.com/apache/cassandra/commit/a7cd114435704b988c81f47ef53d0bfd6441f38b]
> CQLSH: [cqlsh 6.2.0 | Cassandra 5.0-alpha2-SNAPSHOT | CQL spec 3.4.7 | Native
> protocol v5]
>
> *Steps to reproduce in CQLSH:*
> {code:java}
> CREATE KEYSPACE accord WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;{code}
> {code:java}
> CREATE TABLE accord.accounts (
> partition text,
> account_id int,
> balance int,
> PRIMARY KEY (partition_key, account_id)
> ) WITH CLUSTERING ORDER BY (account_id ASC)
> {code}
> {code:java}
> BEGIN TRANSACTION
> INSERT INTO accord.accounts (partition, account_id, balance) VALUES
> ('default', 0, 100);
> INSERT INTO accord.accounts (partition, account_id, balance) VALUES
> ('default', 1, 100);
> COMMIT TRANSACTION;{code}
> bug happens after executing the following statement:
> I expect the result to be a single row consisting of the sum of all the
> balances (100 + 100 = 200).
> {code:java}
> BEGIN TRANSACTION
> SELECT SUM(balance)
> FROM accord.accounts
> WHERE
> partition = 'default'
> AND account_id IN (0, 1);
> COMMIT TRANSACTION;{code}
>
> Bug / Error:
> ==
> The return result includes all the rows with no sum.
> {code:java}
> system.sum(balance)
>
> 100
> 100{code}
>
> Note that executing the same statement without the transaction returns the
> expected result:
> {code:java}
> system.sum(balance)
>
> 200{code}
> {color:#172b4d}This is found while testing Accord transactions with
> [~henrik.ingo] and team.{color}
--
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-16565) Remove dependency on sigar
[ https://issues.apache.org/jira/browse/CASSANDRA-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-16565: -- Reviewers: Stefan Miklosovic Status: Review In Progress (was: Patch Available) > Remove dependency on sigar > -- > > Key: CASSANDRA-16565 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16565 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: David Capwell >Assignee: Claude Warren >Priority: Normal > Fix For: 5.x > > > sigar is used to check if the environment has good settings for running C*, > but requires we bundle a lot of native libraries to perform this check (which > can also be done elsewhere). This project also appears to be dead as the > last commit was around 6 years ago. > With the move to resolve artifacts rather than commit them, removing this > dependency would remove majority of the artifacts fetched from GitHub. -- 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-16565) Remove dependency on sigar
[ https://issues.apache.org/jira/browse/CASSANDRA-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-16565: -- Test and Documentation Plan: CI Status: Patch Available (was: In Progress) PR: https://github.com/apache/cassandra/pull/2842 > Remove dependency on sigar > -- > > Key: CASSANDRA-16565 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16565 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: David Capwell >Assignee: Claude Warren >Priority: Normal > Fix For: 5.x > > > sigar is used to check if the environment has good settings for running C*, > but requires we bundle a lot of native libraries to perform this check (which > can also be done elsewhere). This project also appears to be dead as the > last commit was around 6 years ago. > With the move to resolve artifacts rather than commit them, removing this > dependency would remove majority of the artifacts fetched from GitHub. -- 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-18872) Remove deprecated crc_check_chance in compression params
[ https://issues.apache.org/jira/browse/CASSANDRA-18872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18872: -- Fix Version/s: 5.0-alpha2 5.1 (was: 5.x) Source Control Link: https://github.com/apache/cassandra/commit/b59b832eba014e8d2fc93133cb3db41b509a1c26 Resolution: Fixed Status: Resolved (was: Ready to Commit) Branimir approved on the PR. dtest changes merged here https://github.com/apache/cassandra-dtest/commit/02307b1ea883e01f79723bfdfde223c7110df128 > Remove deprecated crc_check_chance in compression params > > > Key: CASSANDRA-18872 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18872 > Project: Cassandra > Issue Type: Task > Components: Feature/Compression, Legacy/CQL >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.0-alpha2, 5.1 > > Time Spent: 1h > Remaining Estimate: 0h > > crc_check_chance was moved from compression parameters and it is a standalone > table parameter. This was done in times of 3.0 so it is now time to get rid > of that in 5.0. -- 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-dtest] branch trunk updated: alignement with CASSANDRA-18872
This is an automated email from the ASF dual-hosted git repository.
smiklosovic pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-dtest.git
The following commit(s) were added to refs/heads/trunk by this push:
new 02307b1e alignement with CASSANDRA-18872
02307b1e is described below
commit 02307b1ea883e01f79723bfdfde223c7110df128
Author: Stefan Miklosovic
AuthorDate: Thu Oct 5 13:52:41 2023 +0200
alignement with CASSANDRA-18872
patch by Stefan Miklosovic; reviewed by Branimir Lambov for CASSANDRA-18872
---
compression_test.py | 40 +---
1 file changed, 21 insertions(+), 19 deletions(-)
diff --git a/compression_test.py b/compression_test.py
index 0bb63446..cb7fa88d 100644
--- a/compression_test.py
+++ b/compression_test.py
@@ -3,6 +3,7 @@ import pytest
import logging
from dtest import create_ks
+from distutils.version import LooseVersion
from scrub_test import TestHelper
from tools.assertions import assert_crc_check_chance_equal
@@ -80,25 +81,26 @@ class TestCompression(TestHelper):
assert '256' == meta.options['compression']['chunk_length_in_kb']
assert_crc_check_chance_equal(session, "compression_opts_table", 0.25)
-warn = node.grep_log("The option crc_check_chance was deprecated as a
compression option.")
-assert len(warn) == 0
-session.execute("""
-alter table compression_opts_table
-WITH compression = {
-'class': 'DeflateCompressor',
-'chunk_length_in_kb': 256,
-'crc_check_chance': 0.6
-}
-""")
-warn = node.grep_log("The option crc_check_chance was deprecated as a
compression option.")
-assert len(warn) == 1
-
-# check metadata again after crc_check_chance_update
-session.cluster.refresh_schema_metadata()
-meta =
session.cluster.metadata.keyspaces['ks'].tables['compression_opts_table']
-assert 'org.apache.cassandra.io.compress.DeflateCompressor' ==
meta.options['compression']['class']
-assert '256' == meta.options['compression']['chunk_length_in_kb']
-assert_crc_check_chance_equal(session, "compression_opts_table", 0.6)
+if self.cluster.version() < LooseVersion('5.0'):
+ warn = node.grep_log("The option crc_check_chance was deprecated as
a compression option.")
+ assert len(warn) == 0
+ session.execute("""
+ alter table compression_opts_table
+ WITH compression = {
+ 'class': 'DeflateCompressor',
+ 'chunk_length_in_kb': 256,
+ 'crc_check_chance': 0.6
+ }
+ """)
+ warn = node.grep_log("The option crc_check_chance was deprecated as
a compression option.")
+ assert len(warn) == 1
+
+ # check metadata again after crc_check_chance_update
+ session.cluster.refresh_schema_metadata()
+ meta =
session.cluster.metadata.keyspaces['ks'].tables['compression_opts_table']
+ assert 'org.apache.cassandra.io.compress.DeflateCompressor' ==
meta.options['compression']['class']
+ assert '256' == meta.options['compression']['chunk_length_in_kb']
+ assert_crc_check_chance_equal(session, "compression_opts_table", 0.6)
for n in range(0, 100):
session.execute("insert into compression_opts_table (id) values
(uuid());")
-
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 (7d54a62ccc -> b59b832eba)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-5.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 7d54a62ccc Fix schema loading of UDTs inside vectors inside UDTs add b59b832eba Remove crc_check_chance from CompressionParams No new revisions were added by this update. Summary of changes: CHANGES.txt| 1 + .../pages/developing/cql/cql_singlefile.adoc | 16 .../cassandra/pages/developing/cql/ddl.adoc| 3 -- .../pages/managing/operating/compression.adoc | 17 ++--- .../cql3/statements/schema/TableAttributes.java| 24 ++-- .../org/apache/cassandra/db/ColumnFamilyStore.java | 1 + .../cassandra/io/sstable/format/SSTableReader.java | 1 - .../io/sstable/format/SortedTableWriter.java | 4 ++ .../format/big/BigSSTableReaderLoadingBuilder.java | 5 ++- .../format/bti/BtiTableReaderLoadingBuilder.java | 9 - .../cassandra/io/util/CompressedChunkReader.java | 19 ++ .../org/apache/cassandra/io/util/FileHandle.java | 12 +- .../apache/cassandra/schema/CompressionParams.java | 44 -- .../apache/cassandra/schema/TableMetadataRef.java | 1 - .../miscellaneous/CrcCheckChanceTest.java | 38 +++ 15 files changed, 68 insertions(+), 127 deletions(-) - 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. smiklosovic pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit f8c240147c307bf5c527ff3a34e3c0f3043b7e9c Merge: f5fba9b702 b59b832eba Author: Stefan Miklosovic AuthorDate: Thu Oct 26 22:39:01 2023 +0200 Merge branch 'cassandra-5.0' into trunk CHANGES.txt| 1 + .../pages/developing/cql/cql_singlefile.adoc | 16 .../cassandra/pages/developing/cql/ddl.adoc| 3 -- .../pages/managing/operating/compression.adoc | 17 ++--- .../cql3/statements/schema/TableAttributes.java| 24 ++-- .../org/apache/cassandra/db/ColumnFamilyStore.java | 1 + .../cassandra/io/sstable/format/SSTableReader.java | 1 - .../io/sstable/format/SortedTableWriter.java | 4 ++ .../format/big/BigSSTableReaderLoadingBuilder.java | 5 ++- .../format/bti/BtiTableReaderLoadingBuilder.java | 9 - .../cassandra/io/util/CompressedChunkReader.java | 19 ++ .../org/apache/cassandra/io/util/FileHandle.java | 12 +- .../apache/cassandra/schema/CompressionParams.java | 44 -- .../apache/cassandra/schema/TableMetadataRef.java | 1 - .../miscellaneous/CrcCheckChanceTest.java | 38 +++ 15 files changed, 68 insertions(+), 127 deletions(-) diff --cc CHANGES.txt index 60c5d91aaa,53d2205a18..69d3e456c9 --- 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: + * Remove crc_check_chance from CompressionParams (CASSANDRA-18872) * Fix schema loading of UDTs inside vectors inside UDTs (CASSANDRA-18964) * Add cqlsh autocompletion for the vector data type (CASSANDRA-18946) * Fix nodetool tablehistograms output to avoid printing repeated information and ensure at most two arguments (CASSANDRA-18955) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (f5fba9b702 -> f8c240147c)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from f5fba9b702 Merge branch 'cassandra-5.0' into trunk add b59b832eba Remove crc_check_chance from CompressionParams new f8c240147c Merge branch 'cassandra-5.0' into trunk 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: CHANGES.txt| 1 + .../pages/developing/cql/cql_singlefile.adoc | 16 .../cassandra/pages/developing/cql/ddl.adoc| 3 -- .../pages/managing/operating/compression.adoc | 17 ++--- .../cql3/statements/schema/TableAttributes.java| 24 ++-- .../org/apache/cassandra/db/ColumnFamilyStore.java | 1 + .../cassandra/io/sstable/format/SSTableReader.java | 1 - .../io/sstable/format/SortedTableWriter.java | 4 ++ .../format/big/BigSSTableReaderLoadingBuilder.java | 5 ++- .../format/bti/BtiTableReaderLoadingBuilder.java | 9 - .../cassandra/io/util/CompressedChunkReader.java | 19 ++ .../org/apache/cassandra/io/util/FileHandle.java | 12 +- .../apache/cassandra/schema/CompressionParams.java | 44 -- .../apache/cassandra/schema/TableMetadataRef.java | 1 - .../miscellaneous/CrcCheckChanceTest.java | 38 +++ 15 files changed, 68 insertions(+), 127 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18967) Aggregation (SUM) in a transaction block fails
Luis E Fernandez created CASSANDRA-18967:
Summary: Aggregation (SUM) in a transaction block fails
Key: CASSANDRA-18967
URL: https://issues.apache.org/jira/browse/CASSANDRA-18967
Project: Cassandra
Issue Type: Bug
Reporter: Luis E Fernandez
*System configuration and information:*
Single node Cassandra with Accord transactions enabled running on docker
Built from commit:
[a7cd114435704b988c81f47ef53d0bfd6441f38b|https://github.com/apache/cassandra/commit/a7cd114435704b988c81f47ef53d0bfd6441f38b]
CQLSH: [cqlsh 6.2.0 | Cassandra 5.0-alpha2-SNAPSHOT | CQL spec 3.4.7 | Native
protocol v5]
*Steps to reproduce in CQLSH:*
{code:java}
CREATE KEYSPACE accord WITH replication = {'class': 'SimpleStrategy',
'replication_factor': '1'} AND durable_writes = true;{code}
{code:java}
CREATE TABLE accord.accounts (
partition text,
account_id int,
balance int,
PRIMARY KEY (partition_key, account_id)
) WITH CLUSTERING ORDER BY (account_id ASC)
{code}
{code:java}
BEGIN TRANSACTION
INSERT INTO accord.accounts (partition, account_id, balance) VALUES
('default', 0, 100);
INSERT INTO accord.accounts (partition, account_id, balance) VALUES
('default', 1, 100);
COMMIT TRANSACTION;{code}
bug happens after executing the following statement:
I expect the result to be a single row consisting of the sum of all the
balances (100 + 100 = 200).
{code:java}
BEGIN TRANSACTION
SELECT SUM(balance)
FROM accord.accounts
WHERE
partition = 'default'
AND account_id IN (0, 1);
COMMIT TRANSACTION;{code}
Bug / Error:
==
The return result includes all the rows with no sum.
{code:java}
system.sum(balance)
100
100{code}
Note that executing the same statement without the transaction returns the
expected result:
{code:java}
system.sum(balance)
200{code}
{color:#172b4d}This is found while testing Accord transactions with
[~henrik.ingo] and team.{color}
--
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-18965) IllegalArgumentException "tuple is null" thrown for illegal syntax in cql transaction block
[
https://issues.apache.org/jira/browse/CASSANDRA-18965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luis E Fernandez updated CASSANDRA-18965:
-
Description:
*System configuration and information:*
Single node Cassandra with Accord transactions enabled running on docker
Built from commit:
[a7cd114435704b988c81f47ef53d0bfd6441f38b|https://github.com/apache/cassandra/commit/a7cd114435704b988c81f47ef53d0bfd6441f38b]
CQLSH: [cqlsh 6.2.0 | Cassandra 5.0-alpha2-SNAPSHOT | CQL spec 3.4.7 | Native
protocol v5]
*Steps to reproduce in CQLSH:*
{code:java}
CREATE KEYSPACE accord WITH replication = {'class': 'SimpleStrategy',
'replication_factor': '1'} AND durable_writes = true;{code}
{code:java}
CREATE TABLE accord.accounts (
partition_key text,
account_id int,
balance int,
PRIMARY KEY (partition_key, account_id)
) WITH CLUSTERING ORDER BY (account_id ASC){code}
{code:java}
INSERT INTO accord.accounts (partition_key, account_id, balance) VALUES
('default', 1, 1000);{code}
bug happens after executing the following statement:
After assigning a variable within the transaction block, we are attempting to
perform arithmetic operations in the next SELECT statement. Without the
arithmetic operation, the SELECT statement is valid. Instead of reporting an
IllegalArgumentException, CQL should probably just report invalid syntax.
{code:java}
BEGIN TRANSACTION LET row = (SELECT * FROM accord.accounts WHERE partition_key
= 'default' AND account_id = 1); SELECT (row.balance + 50); COMMIT
TRANSACTION;{code}
Bug / Error:
==
{color:#de350b}SyntaxException: Failed parsing statement: [BEGIN TRANSACTION
LET row = (SELECT * FROM accord.accounts WHERE partition_key = 'default' AND
account_id = 1); SELECT (row.balance + 50); COMMIT TRANSACTION;] reason:
IllegalArgumentException tuple is null{color}
{color:#172b4d}This is found while testing Accord transactions with
[~henrik.ingo] and team.{color}
was:
*System configuration and information:*
Single node Cassandra with Accord transactions enabled running on docker
Built from commit:
[a7cd114435704b988c81f47ef53d0bfd6441f38b|https://github.com/apache/cassandra/commit/a7cd114435704b988c81f47ef53d0bfd6441f38b]
CQLSH: [cqlsh 6.2.0 | Cassandra 5.0-alpha2-SNAPSHOT | CQL spec 3.4.7 | Native
protocol v5]
*Steps to reproduce in CQLSH:*
{code:java}
CREATE KEYSPACE accord WITH replication = {'class': 'SimpleStrategy',
'replication_factor': '1'} AND durable_writes = true;{code}
{code:java}
CREATE TABLE accord.accounts (
partition_key text,
account_id int,
balance int,
PRIMARY KEY (partition_key, account_id)
) WITH CLUSTERING ORDER BY (account_id ASC){code}
{code:java}
INSERT INTO accord.accounts (partition_key, account_id, balance) VALUES
('default', 1, 1000);{code}
bug happens after executing the following statement:
After assigning a variable within the transaction block, we are attempting to
perform arithmetic operations in the next SELECT statement. Without the
arithmetic operation, the SELECT statement is valid. Instead of reporting an
IllegalArgumentException, CQL should probably just report invalid syntax.
{code:java}
BEGIN TRANSACTION LET row = (SELECT * FROM accord.accounts WHERE partition_key
= 'default' AND account_id = 1); SELECT (row.balance + 50); COMMIT
TRANSACTION;{code}
Bug / Error:
==
{color:#de350b}SyntaxException: Failed parsing statement: [BEGIN TRANSACTION
LET row = (SELECT * FROM accord.accounts WHERE partition_key = 'default' AND
account_id = 1); SELECT (row.balance + 50); COMMIT TRANSACTION;] reason:
IllegalArgumentException tuple is null{color}
{color:#172b4d}This is found while testing Accord transactions with
[~henrik.ingo] and team.{color}
> IllegalArgumentException "tuple is null" thrown for illegal syntax in cql
> transaction block
> ---
>
> Key: CASSANDRA-18965
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18965
> Project: Cassandra
> Issue Type: Bug
> Components: Accord
>Reporter: Luis E Fernandez
>Priority: Normal
> Fix For: 5.x
>
>
> *System configuration and information:*
> Single node Cassandra with Accord transactions enabled running on docker
> Built from commit:
> [a7cd114435704b988c81f47ef53d0bfd6441f38b|https://github.com/apache/cassandra/commit/a7cd114435704b988c81f47ef53d0bfd6441f38b]
> CQLSH: [cqlsh 6.2.0 | Cassandra 5.0-alpha2-SNAPSHOT | CQL spec 3.4.7 | Native
> protocol v5]
>
> *Steps to reproduce in CQLSH:*
> {code:java}
> CREATE KEYSPACE accord WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_w
[jira] [Updated] (CASSANDRA-18966) Error thrown when creating transaction with counter column type
[
https://issues.apache.org/jira/browse/CASSANDRA-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18966:
-
Fix Version/s: 5.x
> Error thrown when creating transaction with counter column type
> ---
>
> Key: CASSANDRA-18966
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18966
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Luis E Fernandez
>Priority: Normal
> Fix For: 5.x
>
>
> *System configuration and information:*
> Single node Cassandra with Accord transactions enabled running on docker
> Built from commit:
> [a7cd114435704b988c81f47ef53d0bfd6441f38b|https://github.com/apache/cassandra/commit/a7cd114435704b988c81f47ef53d0bfd6441f38b]
> CQLSH: [cqlsh 6.2.0 | Cassandra 5.0-alpha2-SNAPSHOT | CQL spec 3.4.7 | Native
> protocol v5]
>
> *Steps to reproduce in CQLSH:*
> {code:java}
> CREATE KEYSPACE accord WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;{code}
> {code:java}
> CREATE TABLE accord.accounts (
> partition_key text,
> account_id int,
> balance counter,
> PRIMARY KEY (partition_key, account_id)
> ) WITH CLUSTERING ORDER BY (account_id ASC)
> {code}
> {code:java}
> BEGIN TRANSACTION UPDATE accord.accounts SET balance = balance + 1000 WHERE
> partition_key = 'default' AND account_id = 1; COMMIT TRANSACTION;{code}
> at this point the row is correctly inserted
> bug happens after executing the following statement:
> I was not able to update the `balance` counter column. I expected to be able
> to update the `balance` column to 2000.
> {code:java}
> BEGIN TRANSACTION LET row = (SELECT * FROM accord.accounts WHERE
> partition_key = 'default' AND account_id = 1); SELECT row.balance; UPDATE
> accord.accounts SET balance = balance + 1000 WHERE partition_key = 'default'
> AND account_id = 1; COMMIT TRANSACTION;{code}
>
> Bug / Error:
> ==
> {color:#de350b}Traceback (most recent call last):{color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
> line 755, in recv_results_rows{color}
> {color:#de350b} self.parsed_rows = [{color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
> line 756, in {color}
> {color:#de350b} tuple(ctype.from_binary(val, protocol_version){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
> line 756, in {color}
> {color:#de350b} tuple(ctype.from_binary(val, protocol_version){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
> line 312, in from_binary{color}
> {color:#de350b} return cls.deserialize(byts, protocol_version){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
> line 550, in deserialize{color}
> {color:#de350b} return int64_unpack(byts){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/marshal.py",
> line 22, in {color}
> {color:#de350b} unpack = lambda s: packer.unpack(s)[0]{color}
> {color:#de350b}struct.error: unpack requires a buffer of 8 bytes{color}
> {color:#de350b}During handling of the above exception, another exception
> occurred:{color}
> {color:#de350b}Traceback (most recent call last):{color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
> line 763, in recv_results_rows{color}
> {color:#de350b} self.column_types[i].from_binary(row[i],
> protocol_version){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
> line 312, in from_binary{color}
> {color:#de350b} return cls.deserialize(byts, protocol_version){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
> line 550, in deserialize{color}
> {color:#de350b} return int64_unpack(byts){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/marshal.py",
> line 22, in {color}
> {color:#de350b} unpack = lambda s: packer.unpack(s)[0]{color}
> {color:#de350b}struct.error: unpack requires
[jira] [Commented] (CASSANDRA-18966) Error thrown when creating transaction with counter column type
[
https://issues.apache.org/jira/browse/CASSANDRA-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780046#comment-17780046
]
Brandon Williams commented on CASSANDRA-18966:
--
This is a problem with the driver which CASSANDRA-18960 may solve when it does
an upgrade.
> Error thrown when creating transaction with counter column type
> ---
>
> Key: CASSANDRA-18966
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18966
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Luis E Fernandez
>Priority: Normal
>
> *System configuration and information:*
> Single node Cassandra with Accord transactions enabled running on docker
> Built from commit:
> [a7cd114435704b988c81f47ef53d0bfd6441f38b|https://github.com/apache/cassandra/commit/a7cd114435704b988c81f47ef53d0bfd6441f38b]
> CQLSH: [cqlsh 6.2.0 | Cassandra 5.0-alpha2-SNAPSHOT | CQL spec 3.4.7 | Native
> protocol v5]
>
> *Steps to reproduce in CQLSH:*
> {code:java}
> CREATE KEYSPACE accord WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;{code}
> {code:java}
> CREATE TABLE accord.accounts (
> partition_key text,
> account_id int,
> balance counter,
> PRIMARY KEY (partition_key, account_id)
> ) WITH CLUSTERING ORDER BY (account_id ASC)
> {code}
> {code:java}
> BEGIN TRANSACTION UPDATE accord.accounts SET balance = balance + 1000 WHERE
> partition_key = 'default' AND account_id = 1; COMMIT TRANSACTION;{code}
> at this point the row is correctly inserted
> bug happens after executing the following statement:
> I was not able to update the `balance` counter column. I expected to be able
> to update the `balance` column to 2000.
> {code:java}
> BEGIN TRANSACTION LET row = (SELECT * FROM accord.accounts WHERE
> partition_key = 'default' AND account_id = 1); SELECT row.balance; UPDATE
> accord.accounts SET balance = balance + 1000 WHERE partition_key = 'default'
> AND account_id = 1; COMMIT TRANSACTION;{code}
>
> Bug / Error:
> ==
> {color:#de350b}Traceback (most recent call last):{color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
> line 755, in recv_results_rows{color}
> {color:#de350b} self.parsed_rows = [{color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
> line 756, in {color}
> {color:#de350b} tuple(ctype.from_binary(val, protocol_version){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
> line 756, in {color}
> {color:#de350b} tuple(ctype.from_binary(val, protocol_version){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
> line 312, in from_binary{color}
> {color:#de350b} return cls.deserialize(byts, protocol_version){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
> line 550, in deserialize{color}
> {color:#de350b} return int64_unpack(byts){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/marshal.py",
> line 22, in {color}
> {color:#de350b} unpack = lambda s: packer.unpack(s)[0]{color}
> {color:#de350b}struct.error: unpack requires a buffer of 8 bytes{color}
> {color:#de350b}During handling of the above exception, another exception
> occurred:{color}
> {color:#de350b}Traceback (most recent call last):{color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
> line 763, in recv_results_rows{color}
> {color:#de350b} self.column_types[i].from_binary(row[i],
> protocol_version){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
> line 312, in from_binary{color}
> {color:#de350b} return cls.deserialize(byts, protocol_version){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
> line 550, in deserialize{color}
> {color:#de350b} return int64_unpack(byts){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/marshal.py",
> line 22, in {color}
> {color:#de350
[jira] [Updated] (CASSANDRA-18966) Error thrown when creating transaction with counter column type
[
https://issues.apache.org/jira/browse/CASSANDRA-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18966:
-
Bug Category: Parent values: Correctness(12982)Level 1 values: Recoverable
Corruption / Loss(12986)
Complexity: Normal
Component/s: CQL/Interpreter
Discovered By: User Report
Severity: Normal
Status: Open (was: Triage Needed)
> Error thrown when creating transaction with counter column type
> ---
>
> Key: CASSANDRA-18966
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18966
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Luis E Fernandez
>Priority: Normal
>
> *System configuration and information:*
> Single node Cassandra with Accord transactions enabled running on docker
> Built from commit:
> [a7cd114435704b988c81f47ef53d0bfd6441f38b|https://github.com/apache/cassandra/commit/a7cd114435704b988c81f47ef53d0bfd6441f38b]
> CQLSH: [cqlsh 6.2.0 | Cassandra 5.0-alpha2-SNAPSHOT | CQL spec 3.4.7 | Native
> protocol v5]
>
> *Steps to reproduce in CQLSH:*
> {code:java}
> CREATE KEYSPACE accord WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;{code}
> {code:java}
> CREATE TABLE accord.accounts (
> partition_key text,
> account_id int,
> balance counter,
> PRIMARY KEY (partition_key, account_id)
> ) WITH CLUSTERING ORDER BY (account_id ASC)
> {code}
> {code:java}
> BEGIN TRANSACTION UPDATE accord.accounts SET balance = balance + 1000 WHERE
> partition_key = 'default' AND account_id = 1; COMMIT TRANSACTION;{code}
> at this point the row is correctly inserted
> bug happens after executing the following statement:
> I was not able to update the `balance` counter column. I expected to be able
> to update the `balance` column to 2000.
> {code:java}
> BEGIN TRANSACTION LET row = (SELECT * FROM accord.accounts WHERE
> partition_key = 'default' AND account_id = 1); SELECT row.balance; UPDATE
> accord.accounts SET balance = balance + 1000 WHERE partition_key = 'default'
> AND account_id = 1; COMMIT TRANSACTION;{code}
>
> Bug / Error:
> ==
> {color:#de350b}Traceback (most recent call last):{color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
> line 755, in recv_results_rows{color}
> {color:#de350b} self.parsed_rows = [{color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
> line 756, in {color}
> {color:#de350b} tuple(ctype.from_binary(val, protocol_version){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
> line 756, in {color}
> {color:#de350b} tuple(ctype.from_binary(val, protocol_version){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
> line 312, in from_binary{color}
> {color:#de350b} return cls.deserialize(byts, protocol_version){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
> line 550, in deserialize{color}
> {color:#de350b} return int64_unpack(byts){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/marshal.py",
> line 22, in {color}
> {color:#de350b} unpack = lambda s: packer.unpack(s)[0]{color}
> {color:#de350b}struct.error: unpack requires a buffer of 8 bytes{color}
> {color:#de350b}During handling of the above exception, another exception
> occurred:{color}
> {color:#de350b}Traceback (most recent call last):{color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
> line 763, in recv_results_rows{color}
> {color:#de350b} self.column_types[i].from_binary(row[i],
> protocol_version){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
> line 312, in from_binary{color}
> {color:#de350b} return cls.deserialize(byts, protocol_version){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
> line 550, in deserialize{color}
> {color:#de350b} return int64_unpack(byts){color}
> {color:#de350b} File
> "/opt/cassandra/bin/../lib/cassand
[jira] [Updated] (CASSANDRA-18965) IllegalArgumentException "tuple is null" thrown for illegal syntax in cql transaction block
[
https://issues.apache.org/jira/browse/CASSANDRA-18965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18965:
-
Bug Category: Parent values: Correctness(12982)Level 1 values: Transient
Incorrect Response(12987)
Complexity: Normal
Component/s: Accord
Discovered By: User Report
Fix Version/s: 5.x
Severity: Normal
Status: Open (was: Triage Needed)
> IllegalArgumentException "tuple is null" thrown for illegal syntax in cql
> transaction block
> ---
>
> Key: CASSANDRA-18965
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18965
> Project: Cassandra
> Issue Type: Bug
> Components: Accord
>Reporter: Luis E Fernandez
>Priority: Normal
> Fix For: 5.x
>
>
> *System configuration and information:*
> Single node Cassandra with Accord transactions enabled running on docker
> Built from commit:
> [a7cd114435704b988c81f47ef53d0bfd6441f38b|https://github.com/apache/cassandra/commit/a7cd114435704b988c81f47ef53d0bfd6441f38b]
> CQLSH: [cqlsh 6.2.0 | Cassandra 5.0-alpha2-SNAPSHOT | CQL spec 3.4.7 | Native
> protocol v5]
>
> *Steps to reproduce in CQLSH:*
>
> {code:java}
> CREATE KEYSPACE accord WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;{code}
>
>
> {code:java}
> CREATE TABLE accord.accounts (
> partition_key text,
> account_id int,
> balance int,
> PRIMARY KEY (partition_key, account_id)
> ) WITH CLUSTERING ORDER BY (account_id ASC){code}
>
>
> {code:java}
> INSERT INTO accord.accounts (partition_key, account_id, balance) VALUES
> ('default', 1, 1000);{code}
>
> bug happens after executing the following statement:
> After assigning a variable within the transaction block, we are attempting to
> perform arithmetic operations in the next SELECT statement. Without the
> arithmetic operation, the SELECT statement is valid. Instead of reporting an
> IllegalArgumentException, CQL should probably just report invalid syntax.
>
> {code:java}
> BEGIN TRANSACTION LET row = (SELECT * FROM accord.accounts WHERE
> partition_key = 'default' AND account_id = 1); SELECT (row.balance + 50);
> COMMIT TRANSACTION;{code}
>
>
> Bug / Error:
> ==
> {color:#de350b}SyntaxException: Failed parsing statement: [BEGIN TRANSACTION
> LET row = (SELECT * FROM accord.accounts WHERE partition_key = 'default' AND
> account_id = 1); SELECT (row.balance + 50); COMMIT TRANSACTION;] reason:
> IllegalArgumentException tuple is null{color}
>
> {color:#172b4d}This is found while testing Accord transactions with
> [~henrik.ingo] and team.{color}
--
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] [Created] (CASSANDRA-18966) Error thrown when creating transaction with counter column type
Luis E Fernandez created CASSANDRA-18966:
Summary: Error thrown when creating transaction with counter
column type
Key: CASSANDRA-18966
URL: https://issues.apache.org/jira/browse/CASSANDRA-18966
Project: Cassandra
Issue Type: Bug
Reporter: Luis E Fernandez
*System configuration and information:*
Single node Cassandra with Accord transactions enabled running on docker
Built from commit:
[a7cd114435704b988c81f47ef53d0bfd6441f38b|https://github.com/apache/cassandra/commit/a7cd114435704b988c81f47ef53d0bfd6441f38b]
CQLSH: [cqlsh 6.2.0 | Cassandra 5.0-alpha2-SNAPSHOT | CQL spec 3.4.7 | Native
protocol v5]
*Steps to reproduce in CQLSH:*
{code:java}
CREATE KEYSPACE accord WITH replication = {'class': 'SimpleStrategy',
'replication_factor': '1'} AND durable_writes = true;{code}
{code:java}
CREATE TABLE accord.accounts (
partition_key text,
account_id int,
balance counter,
PRIMARY KEY (partition_key, account_id)
) WITH CLUSTERING ORDER BY (account_id ASC)
{code}
{code:java}
BEGIN TRANSACTION UPDATE accord.accounts SET balance = balance + 1000 WHERE
partition_key = 'default' AND account_id = 1; COMMIT TRANSACTION;{code}
at this point the row is correctly inserted
bug happens after executing the following statement:
I was not able to update the `balance` counter column. I expected to be able to
update the `balance` column to 2000.
{code:java}
BEGIN TRANSACTION LET row = (SELECT * FROM accord.accounts WHERE partition_key
= 'default' AND account_id = 1); SELECT row.balance; UPDATE accord.accounts SET
balance = balance + 1000 WHERE partition_key = 'default' AND account_id = 1;
COMMIT TRANSACTION;{code}
Bug / Error:
==
{color:#de350b}Traceback (most recent call last):{color}
{color:#de350b} File
"/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
line 755, in recv_results_rows{color}
{color:#de350b} self.parsed_rows = [{color}
{color:#de350b} File
"/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
line 756, in {color}
{color:#de350b} tuple(ctype.from_binary(val, protocol_version){color}
{color:#de350b} File
"/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
line 756, in {color}
{color:#de350b} tuple(ctype.from_binary(val, protocol_version){color}
{color:#de350b} File
"/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
line 312, in from_binary{color}
{color:#de350b} return cls.deserialize(byts, protocol_version){color}
{color:#de350b} File
"/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
line 550, in deserialize{color}
{color:#de350b} return int64_unpack(byts){color}
{color:#de350b} File
"/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/marshal.py",
line 22, in {color}
{color:#de350b} unpack = lambda s: packer.unpack(s)[0]{color}
{color:#de350b}struct.error: unpack requires a buffer of 8 bytes{color}
{color:#de350b}During handling of the above exception, another exception
occurred:{color}
{color:#de350b}Traceback (most recent call last):{color}
{color:#de350b} File
"/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/protocol.py",
line 763, in recv_results_rows{color}
{color:#de350b} self.column_types[i].from_binary(row[i],
protocol_version){color}
{color:#de350b} File
"/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
line 312, in from_binary{color}
{color:#de350b} return cls.deserialize(byts, protocol_version){color}
{color:#de350b} File
"/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cqltypes.py",
line 550, in deserialize{color}
{color:#de350b} return int64_unpack(byts){color}
{color:#de350b} File
"/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/marshal.py",
line 22, in {color}
{color:#de350b} unpack = lambda s: packer.unpack(s)[0]{color}
{color:#de350b}struct.error: unpack requires a buffer of 8 bytes{color}
{color:#de350b}During handling of the above exception, another exception
occurred:{color}
{color:#de350b}Traceback (most recent call last):{color}
{color:#de350b} File "/opt/cassandra/bin/../pylib/cqlshlib/cqlshmain.py", line
987, in perform_simple_statement{color}
{color:#de350b} result = future.result(){color}
{color:#de350b} File
"/opt/cassandra/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-dri
[jira] [Created] (CASSANDRA-18965) IllegalArgumentException "tuple is null" thrown for illegal syntax in cql transaction block
Luis E Fernandez created CASSANDRA-18965:
Summary: IllegalArgumentException "tuple is null" thrown for
illegal syntax in cql transaction block
Key: CASSANDRA-18965
URL: https://issues.apache.org/jira/browse/CASSANDRA-18965
Project: Cassandra
Issue Type: Bug
Reporter: Luis E Fernandez
*System configuration and information:*
Single node Cassandra with Accord transactions enabled running on docker
Built from commit:
[a7cd114435704b988c81f47ef53d0bfd6441f38b|https://github.com/apache/cassandra/commit/a7cd114435704b988c81f47ef53d0bfd6441f38b]
CQLSH: [cqlsh 6.2.0 | Cassandra 5.0-alpha2-SNAPSHOT | CQL spec 3.4.7 | Native
protocol v5]
*Steps to reproduce in CQLSH:*
{code:java}
CREATE KEYSPACE accord WITH replication = {'class': 'SimpleStrategy',
'replication_factor': '1'} AND durable_writes = true;{code}
{code:java}
CREATE TABLE accord.accounts (
partition_key text,
account_id int,
balance int,
PRIMARY KEY (partition_key, account_id)
) WITH CLUSTERING ORDER BY (account_id ASC){code}
{code:java}
INSERT INTO accord.accounts (partition_key, account_id, balance) VALUES
('default', 1, 1000);{code}
bug happens after executing the following statement:
After assigning a variable within the transaction block, we are attempting to
perform arithmetic operations in the next SELECT statement. Without the
arithmetic operation, the SELECT statement is valid. Instead of reporting an
IllegalArgumentException, CQL should probably just report invalid syntax.
{code:java}
BEGIN TRANSACTION LET row = (SELECT * FROM accord.accounts WHERE partition_key
= 'default' AND account_id = 1); SELECT (row.balance + 50); COMMIT
TRANSACTION;{code}
Bug / Error:
==
{color:#de350b}SyntaxException: Failed parsing statement: [BEGIN TRANSACTION
LET row = (SELECT * FROM accord.accounts WHERE partition_key = 'default' AND
account_id = 1); SELECT (row.balance + 50); COMMIT TRANSACTION;] reason:
IllegalArgumentException tuple is null{color}
{color:#172b4d}This is found while testing Accord transactions with
[~henrik.ingo] and team.{color}
--
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 (c9bf6c9f5 -> 97c6afa31)
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 c9bf6c9f5 generate docs for 207dbf1f new 97c6afa31 generate docs for 207dbf1f 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 (c9bf6c9f5) \ N -- N -- N refs/heads/asf-staging (97c6afa31) 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] [Updated] (CASSANDRA-18964) Vector type in UDTs can break schema loading
[
https://issues.apache.org/jira/browse/CASSANDRA-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-18964:
--
Fix Version/s: 5.0-alpha2
(was: 5.0)
Since Version: 5.0-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/7d54a62ccc27f89bb6ee55b8f17005cf4c444231
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed to 5.0 and trunk, cheers.
> Vector type in UDTs can break schema loading
> -
>
> Key: CASSANDRA-18964
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18964
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Normal
> Fix For: 5.0-alpha2
>
>
> {{RawVector}} doesn’t override {{referencesUserType(String name)}}, which
> causes {{Types.RawBuilder.build()}} to not populate UDT dependency DAG
> correctly. Then depending on natural iteration order or the vertices map, a
> UDT with a vector referencing another UDT can fail to resolve, if that
> referenced UDT has not been resolved.
--
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-18964) Vector type in UDTs can break schema loading
[
https://issues.apache.org/jira/browse/CASSANDRA-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-18964:
--
Status: Ready to Commit (was: Review In Progress)
> Vector type in UDTs can break schema loading
> -
>
> Key: CASSANDRA-18964
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18964
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Normal
> Fix For: 5.0
>
>
> {{RawVector}} doesn’t override {{referencesUserType(String name)}}, which
> causes {{Types.RawBuilder.build()}} to not populate UDT dependency DAG
> correctly. Then depending on natural iteration order or the vertices map, a
> UDT with a vector referencing another UDT can fail to resolve, if that
> referenced UDT has not been resolved.
--
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-18964) Vector type in UDTs can break schema loading
[
https://issues.apache.org/jira/browse/CASSANDRA-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-18964:
--
Reviewers: Marcus Eriksson, Aleksey Yeschenko (was: Marcus Eriksson)
Marcus Eriksson, Aleksey Yeschenko (was: Aleksey Yeschenko,
Marcus Eriksson)
Status: Review In Progress (was: Patch Available)
> Vector type in UDTs can break schema loading
> -
>
> Key: CASSANDRA-18964
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18964
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Normal
> Fix For: 5.0
>
>
> {{RawVector}} doesn’t override {{referencesUserType(String name)}}, which
> causes {{Types.RawBuilder.build()}} to not populate UDT dependency DAG
> correctly. Then depending on natural iteration order or the vertices map, a
> UDT with a vector referencing another UDT can fail to resolve, if that
> referenced UDT has not been resolved.
--
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 (3088b8114c -> 7d54a62ccc)
This is an automated email from the ASF dual-hosted git repository. aleksey pushed a change to branch cassandra-5.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 3088b8114c Merge branch 'cassandra-4.1' into cassandra-5.0 add 7d54a62ccc Fix schema loading of UDTs inside vectors inside UDTs No new revisions were added by this update. Summary of changes: CHANGES.txt | 1 + src/java/org/apache/cassandra/cql3/CQL3Type.java| 6 ++ .../cql3/validation/operations/CQLVectorTest.java | 17 + 3 files changed, 24 insertions(+) - 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. aleksey pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit f5fba9b702841401dfb769c4fcfc4cdde68822af Merge: 45c6352938 7d54a62ccc Author: Aleksey Yeschenko AuthorDate: Thu Oct 26 17:46:05 2023 +0100 Merge branch 'cassandra-5.0' into trunk CHANGES.txt | 1 + src/java/org/apache/cassandra/cql3/CQL3Type.java| 6 ++ .../cql3/validation/operations/CQLVectorTest.java | 17 + 3 files changed, 24 insertions(+) diff --cc CHANGES.txt index 2bc545c9f7,d0d38a08c8..60c5d91aaa --- 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: + * Fix schema loading of UDTs inside vectors inside UDTs (CASSANDRA-18964) * Add cqlsh autocompletion for the vector data type (CASSANDRA-18946) * Fix nodetool tablehistograms output to avoid printing repeated information and ensure at most two arguments (CASSANDRA-18955) * Change the checksum algorithm SAI-related files use from CRC32 to CRC32C (CASSANDRA-18836) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (45c6352938 -> f5fba9b702)
This is an automated email from the ASF dual-hosted git repository. aleksey pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 45c6352938 Merge branch 'cassandra-5.0' into trunk add 7d54a62ccc Fix schema loading of UDTs inside vectors inside UDTs new f5fba9b702 Merge branch 'cassandra-5.0' into trunk 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: CHANGES.txt | 1 + src/java/org/apache/cassandra/cql3/CQL3Type.java| 6 ++ .../cql3/validation/operations/CQLVectorTest.java | 17 + 3 files changed, 24 insertions(+) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29
[
https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779968#comment-17779968
]
Ke Han commented on CASSANDRA-18956:
[~mikloso...@pm.me] Absolutely, let me give it a try.
> Metadata Loss caused by unchecked rename column when upgrading from 2.x to
> 3.0.29
> -
>
> Key: CASSANDRA-18956
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18956
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Distributed Metadata
>Reporter: Ke Han
>Priority: Normal
> Attachments: data.tar.gz, signature.asc, signature.asc, signature.asc
>
>
> After migrating data from 2.1.22 (released 2022-06-17) to 3.0.29 (released
> 2023-05-05), if user performs a rename operation to rename the primary key to
> an existing column, it will succeed, and the original column will get lost
> permanently.
> h1. Reproduce
> Start up single cassandra node 2.1.22, create the following table using
> cassandra-cli
> {code:java}
> # bin/cassandra-cli
> create keyspace test with strategy_options = {replication_factor:1} and
> placement_strategy = 'org.apache.cassandra.locator.SimpleStrategy';
> use test;
> create column family foos
> with column_type = 'Standard'
> and comparator = 'BytesType'
> and key_validation_class = 'UTF8Type'
> and column_metadata = [{column_name: '2f', validation_class: 'UTF8Type'}];
> {code}
> Stop the daemon
> {code:java}
> bin/nodetool -h :::127.0.0.1 stopdaemon {code}
> Upgrade, start up new version
> {code:java}
> cqlsh> desc test.foos ;
> CREATE TABLE test.foos (
> key text PRIMARY KEY,
> "2f" text
> ) WITH COMPACT STORAGE
> AND bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.1
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = 'NONE';
> cqlsh> ALTER TABLE test.foos RENAME key TO "2f";
> cqlsh> desc test.foos ;
> CREATE TABLE test.foos (
> "2f" text PRIMARY KEY
> ) WITH COMPACT STORAGE
> AND bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.1
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = 'NONE';
> cqlsh> SELECT * FROM test.foos ;
> 2f
>
> (0 rows) {code}
> h1. Root Cause
> The root cause is a missing check for the existing column when the table
> comparator from the old version is BytesType.
> I have uploaded the data dir, use it to start up 3.0.29 and execute the
> commands will reproduce this bug.
--
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 ] Brandon Williams updated CASSANDRA-18902: - Complexity: Normal Discovered By: User Report Severity: Normal Status: Open (was: Triage Needed) > 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.x, 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] [Commented] (CASSANDRA-18715) Add support for vector search in SAI
[ https://issues.apache.org/jira/browse/CASSANDRA-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779948#comment-17779948 ] Jonathan Ellis commented on CASSANDRA-18715: As the primary author of the new JVector dependency, I can also verify that my code, while not a contribution to ASF, is my original work. It also includes complete details of any third-party licenses or restrictions I am aware of, in line with the spirit of clauses #5 and #7 of the ASF ICLA. > Add support for vector search in SAI > > > Key: CASSANDRA-18715 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18715 > Project: Cassandra > Issue Type: Improvement > Components: Feature/Vector Search >Reporter: Mike Adamson >Assignee: Mike Adamson >Priority: Normal > Fix For: 5.0-beta, 5.x > > Time Spent: 24h 50m > Remaining Estimate: 0h > > The patch associated with this ticket adds a new vector index to SAI. This > introduces the following new elements and changes to SAI: > * VectorMemtableIndex - the in-memory representation of the vector indexes > that writes data to a DiskANN instance > * VectorSegmentBuilder - that writes a DiskANN graph to the following > on-disk components: > ** VECTOR - contains the floating point vectors associated with the graph > ** TERMS - contains the HNSW graph on-disk representation written by a > HnswGraphWriter > ** POSTINGS - contains the index postings as written by a > VectorPostingsWriter > * VectorIndexSegmentSearcher - used to search the on-disk DiskANN graph -- 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&focusedCommentId=17779928#comment-17779928
]
Brandon Williams commented on CASSANDRA-18710:
--
Before CASSANDRA-17071 (and currently in 4.0) we also force recycled the
commitlog, but sooner in
[Schema.dropTable|https://github.com/apache/cassandra/blob/cassandra-4.0/src/java/org/apache/cassandra/schema/Schema.java#L803],
and it didn't cause small flushes of the active CF. 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?
Here's a reproduction with additional logging at ERROR showing the drop of
table_00 causing the small flush of table_01 shortly after creation:
{noformat}
[junit-timeout] INFO [main] 2023-10-25 20:12:32,442 ColumnFamilyStore.java:493
- Initializing cql_test_keyspace_alt.table_01
[junit-timeout] DEBUG [main] 2023-10-25 20:12:32,443
DiskBoundaryManager.java:54 - Refreshing disk boundary cache for
cql_test_keyspace_alt.table_01
[junit-timeout] DEBUG [main] 2023-10-25 20:12:32,443
DiskBoundaryManager.java:93 - Got local ranges [] (ringVersion = 0)
[junit-timeout] DEBUG [main] 2023-10-25 20:12:32,447
DiskBoundaryManager.java:57 - Updating boundaries from null to
DiskBoundaries{directories=[DataDirectory{location=build/test/cassandra/data}],
positions=null, ringVersion=0, directoriesVersion=0} for
cql_test_keyspace_alt.table_01
[junit-timeout] INFO [main] 2023-10-25 20:12:32,453 ViewManager.java:127 - Not
submitting build tasks for views in keyspace cql_test_keyspace_alt as storage
service is not initialized
[junit-timeout] DEBUG [OptionalTasks:1] 2023-10-25 20:12:32,459
DefaultSchemaUpdateHandler.java:259 - Schema updated:
SchemaTransformationResult{e9de990e-f2fd-3f3e-97fb-e351f5dae8d3 -->
111d2c16-fe3d-3fcf-9dc1-9cafe8d9b926, diff=KeyspacesDiff{created=[],
dropped=[],
altered=[KeyspaceDiff{before=KeyspaceMetadata{name=cql_test_keyspace,
kind=REGULAR, params=KeyspaceParams{durable_writes=true,
replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy,
replication_factor=1}}, tables=[cql_test_keyspace.table_00], views=[],
functions=[], types=[]}, after=KeyspaceMetadata{name=cql_test_keyspace,
kind=REGULAR, params=KeyspaceParams{durable_writes=true,
replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy,
replication_factor=1}}, tables=[], views=[], functions=[], types=[]},
tables=Diff{created=[], dropped=[cql_test_keyspace.table_00], altered=[]},
views=Diff{created=[], dropped=[], altered=[]}, types=Diff{created=[],
dropped=[], altered=[]}, udfs=Diff{created=[], dropped=[], altered=[]},
udas=Diff{created=[], dropped=[], altered=[]}}]}}
[junit-timeout] ERROR [OptionalTasks:1] 2023-10-25 20:12:32,571
ColumnFamilyStore.java:1013 - Bad flush reason: COMMITLOG_DIRTY
[junit-timeout] ERROR [OptionalTasks:1] 2023-10-25 20:12:32,571
ColumnFamilyStore.java:1014 -
[org.apache.cassandra.db.ColumnFamilyStore.logFlush(ColumnFamilyStore.java:1012)
[junit-timeout]
org.apache.cassandra.db.ColumnFamilyStore.switchMemtable(ColumnFamilyStore.java:999)
[junit-timeout]
org.apache.cassandra.db.ColumnFamilyStore.switchMemtableIfCurrent(ColumnFamilyStore.java:981)
[junit-timeout]
org.apache.cassandra.db.ColumnFamilyStore.flushMemtable(ColumnFamilyStore.java:1065)
[junit-timeout]
org.apache.cassandra.db.ColumnFamilyStore.forceFlush(ColumnFamilyStore.java:1040)
[junit-timeout]
org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager.flushDataFrom(AbstractCommitLogSegmentManager.java:457)
[junit-timeout]
org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager.forceRecycleAll(AbstractCommitLogSegmentManager.java:334)
[junit-timeout]
org.apache.cassandra.db.commitlog.CommitLog.forceRecycleAllSegments(CommitLog.java:261)
[junit-timeout]
org.apache.cassandra.db.ColumnFamilyStore.onTableDropped(ColumnFamilyStore.java:3382)
[junit-timeout] org.apache.cassandra.db.Keyspace.dropCf(Keyspace.java:383)
[junit-timeout] org.apache.cassandra.schema.Schema.dropTable(Schema.java:756)
[junit-timeout]
org.apache.cassandra.schema.Schema.lambda$alterKeyspace$14(Schema.java:672)
[junit-timeout] java.base/java.lang.Iterable.forEach(Iterable.java:75)
[junit-timeout]
org.apache.cassandra.schema.Schema.alterKeyspace(Schema.java:672)
[junit-timeout]
org.apache.cassandra.schema.Schema.lambda$merge$12(Schema.java:655)
[junit-timeout]
com.google.common.collect.ImmutableList.forEach(ImmutableList.java:422)
[junit-timeout] org.apache.cassandra.schema.Schema.merge(Schema.java:655)
[junit-timeout]
org.apache.cassandra.schema.Schema.mergeAndUpdateVersion(Schema.java:607)
[junit-timeout]
org.apache.cassandra.schema.DefaultSchemaUpda
[jira] [Comment Edited] (CASSANDRA-18941) Support max SSTable size in sorted CQLSSTableWriter
[ https://issues.apache.org/jira/browse/CASSANDRA-18941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779925#comment-17779925 ] Maxwell Guo edited comment on CASSANDRA-18941 at 10/26/23 2:34 PM: --- Hi [~yifanc], the code logic are same for different branches, but seems that 4.0 and 4.1 have some nits for code format. Besides, we need some CIs too, the upper CI for trunk have never been started.:) And +1 if all CIs are green. was (Author: maxwellguo): Hi [~yifanc], the code logic are same for different branches, but seems that 4.0 and 4.1 have some nit for code format. Besides, we need some CIs too, the upper CI for trunk have never been started.:) And +1 if all CIs are green. > Support max SSTable size in sorted CQLSSTableWriter > --- > > Key: CASSANDRA-18941 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18941 > Project: Cassandra > Issue Type: Improvement > Components: Tool/sstable >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x > > Time Spent: 3.5h > Remaining Estimate: 0h > > The CQLSSTableWriter can produce a series of SSTables with a bounded size in > the unsorted mode. The functionality is missing in the sorted > CQLSSTableWriter. > It will be great to bringing the parity to the sorted mode, so that it is > able to produce a series of size-bounded SSTable, instead of a single but > giant one. > Unlike the unsorted CQLSSTableWriter, the max SSTable size in the sorted > writer does not require buffering. -- 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-18941) Support max SSTable size in sorted CQLSSTableWriter
[ https://issues.apache.org/jira/browse/CASSANDRA-18941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779925#comment-17779925 ] Maxwell Guo edited comment on CASSANDRA-18941 at 10/26/23 2:34 PM: --- Hi [~yifanc], the code logic are same for different branches, but seems that 4.0 and 4.1 have some nit for code format. Besides, we need some CIs too, the upper CI for trunk have never been started.:) And +1 if all CIs are green. was (Author: maxwellguo): Hi [~yifanc], the code logic are same for different branches, but seems that 4.0 and 4.1 have some nit for code format. Besides, we need some CIs too, the upper CI for trunk have never been started.:) > Support max SSTable size in sorted CQLSSTableWriter > --- > > Key: CASSANDRA-18941 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18941 > Project: Cassandra > Issue Type: Improvement > Components: Tool/sstable >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x > > Time Spent: 3.5h > Remaining Estimate: 0h > > The CQLSSTableWriter can produce a series of SSTables with a bounded size in > the unsorted mode. The functionality is missing in the sorted > CQLSSTableWriter. > It will be great to bringing the parity to the sorted mode, so that it is > able to produce a series of size-bounded SSTable, instead of a single but > giant one. > Unlike the unsorted CQLSSTableWriter, the max SSTable size in the sorted > writer does not require buffering. -- 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-18941) Support max SSTable size in sorted CQLSSTableWriter
[ https://issues.apache.org/jira/browse/CASSANDRA-18941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779925#comment-17779925 ] Maxwell Guo commented on CASSANDRA-18941: - Hi [~yifanc], the code logic are same for different branches, but seems that 4.0 and 4.1 have some nit for code format. Besides, we need some CIs too, the upper CI for trunk have never been started.:) > Support max SSTable size in sorted CQLSSTableWriter > --- > > Key: CASSANDRA-18941 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18941 > Project: Cassandra > Issue Type: Improvement > Components: Tool/sstable >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x > > Time Spent: 3.5h > Remaining Estimate: 0h > > The CQLSSTableWriter can produce a series of SSTables with a bounded size in > the unsorted mode. The functionality is missing in the sorted > CQLSSTableWriter. > It will be great to bringing the parity to the sorted mode, so that it is > able to produce a series of size-bounded SSTable, instead of a single but > giant one. > Unlike the unsorted CQLSSTableWriter, the max SSTable size in the sorted > writer does not require buffering. -- 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-18964) Vector type in UDTs can break schema loading
[
https://issues.apache.org/jira/browse/CASSANDRA-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779921#comment-17779921
]
Marcus Eriksson commented on CASSANDRA-18964:
-
+1
> Vector type in UDTs can break schema loading
> -
>
> Key: CASSANDRA-18964
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18964
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Normal
> Fix For: 5.0
>
>
> {{RawVector}} doesn’t override {{referencesUserType(String name)}}, which
> causes {{Types.RawBuilder.build()}} to not populate UDT dependency DAG
> correctly. Then depending on natural iteration order or the vertices map, a
> UDT with a vector referencing another UDT can fail to resolve, if that
> referenced UDT has not been resolved.
--
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-18964) Vector type in UDTs can break schema loading
[
https://issues.apache.org/jira/browse/CASSANDRA-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-18964:
--
Test and Documentation Plan: Existing test coverage
Status: Patch Available (was: Open)
> Vector type in UDTs can break schema loading
> -
>
> Key: CASSANDRA-18964
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18964
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Normal
> Fix For: 5.0
>
>
> {{RawVector}} doesn’t override {{referencesUserType(String name)}}, which
> causes {{Types.RawBuilder.build()}} to not populate UDT dependency DAG
> correctly. Then depending on natural iteration order or the vertices map, a
> UDT with a vector referencing another UDT can fail to resolve, if that
> referenced UDT has not been resolved.
--
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-18964) Vector type in UDTs can break schema loading
[
https://issues.apache.org/jira/browse/CASSANDRA-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-18964:
--
Bug Category: Parent values: Availability(12983)Level 1 values:
Unavailable(12994)
Complexity: Normal
Component/s: Cluster/Schema
Discovered By: Fuzz Test
Fix Version/s: 5.0
Reviewers: Marcus Eriksson
Severity: Normal
Status: Open (was: Triage Needed)
> Vector type in UDTs can break schema loading
> -
>
> Key: CASSANDRA-18964
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18964
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Normal
> Fix For: 5.0
>
>
> {{RawVector}} doesn’t override {{referencesUserType(String name)}}, which
> causes {{Types.RawBuilder.build()}} to not populate UDT dependency DAG
> correctly. Then depending on natural iteration order or the vertices map, a
> UDT with a vector referencing another UDT can fail to resolve, if that
> referenced UDT has not been resolved.
--
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] [Created] (CASSANDRA-18964) Vector type in UDTs can break schema loading
Aleksey Yeschenko created CASSANDRA-18964:
-
Summary: Vector type in UDTs can break schema loading
Key: CASSANDRA-18964
URL: https://issues.apache.org/jira/browse/CASSANDRA-18964
Project: Cassandra
Issue Type: Bug
Reporter: Aleksey Yeschenko
Assignee: Aleksey Yeschenko
{{RawVector}} doesn’t override {{referencesUserType(String name)}}, which
causes {{Types.RawBuilder.build()}} to not populate UDT dependency DAG
correctly. Then depending on natural iteration order or the vertices map, a
UDT with a vector referencing another UDT can fail to resolve, if that
referenced UDT has not been resolved.
--
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
]
Henrik Ingo updated CASSANDRA-18798:
Test and Documentation Plan:
Added 2 unit tests
Retest with the list append Elle test
Does not impact documentation
Status: Patch Available (was: In Progress)
Ok, above PR now ready for review [~jlewandowski]. Let me know if I need to
squash commits or something first?
> 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.0-alpha2
>
> Attachments: image-2023-09-26-20-05-25-846.png
>
> Time Spent: 10m
> 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 proc
[cassandra] branch cassandra-5.0 updated (5eba52feb8 -> 3088b8114c)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch cassandra-5.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 5eba52feb8 Add cqlsh autocompletion for the vector data type add 5bf1d2f8d5 Suppress CVE-2023-44487 add cec0e1b864 Merge branch 'cassandra-3.0' into cassandra-3.11 add 0a91114dd5 Merge branch 'cassandra-3.11' into cassandra-4.0 add 349ec3e02d Merge branch 'cassandra-3.0' into cassandra-3.11 add 2fa7c1204c Merge branch 'cassandra-3.11' into cassandra-4.0 add d3cc2a65b8 Merge branch 'cassandra-4.0' into cassandra-4.1 add 3088b8114c Merge branch 'cassandra-4.1' into cassandra-5.0 No new revisions were added by this update. Summary of changes: .build/dependency-check-suppressions.xml | 7 +++ CHANGES.txt | 1 + 2 files changed, 8 insertions(+) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18943) http/2 vulnerability: CVE-2023-44487
[ https://issues.apache.org/jira/browse/CASSANDRA-18943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18943: - Fix Version/s: 3.0.30 3.11.17 4.0.12 4.1.4 5.0-alpha2 5.1 (was: 3.0.x) (was: 3.11.x) (was: 5.x) (was: 4.0.x) (was: 4.1.x) (was: 5.0.x) Since Version: NA Source Control Link: https://github.com/apache/cassandra/commit/5bf1d2f8d5b6b37b8f6e2718f85dec068ceb7206 Resolution: Fixed Status: Resolved (was: Ready to Commit) Much appreciated! Thanks for the review, committed. > http/2 vulnerability: CVE-2023-44487 > > > Key: CASSANDRA-18943 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18943 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.30, 3.11.17, 4.0.12, 4.1.4, 5.0-alpha2, 5.1 > > > https://nvd.nist.gov/vuln/detail/CVE-2023-44487 > Basically anything using http/2 is covered by this, but we don't use it. -- 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-18943) http/2 vulnerability: CVE-2023-44487
[ https://issues.apache.org/jira/browse/CASSANDRA-18943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18943: - Status: Ready to Commit (was: Review In Progress) > http/2 vulnerability: CVE-2023-44487 > > > Key: CASSANDRA-18943 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18943 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.0.x, 5.x > > > https://nvd.nist.gov/vuln/detail/CVE-2023-44487 > Basically anything using http/2 is covered by this, but we don't use it. -- 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-18943) http/2 vulnerability: CVE-2023-44487
[ https://issues.apache.org/jira/browse/CASSANDRA-18943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18943: - Reviewers: Berenguer Blasi, Brandon Williams Status: Review In Progress (was: Patch Available) > http/2 vulnerability: CVE-2023-44487 > > > Key: CASSANDRA-18943 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18943 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.0.x, 5.x > > > https://nvd.nist.gov/vuln/detail/CVE-2023-44487 > Basically anything using http/2 is covered by this, but we don't use it. -- 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-18943) http/2 vulnerability: CVE-2023-44487
[ https://issues.apache.org/jira/browse/CASSANDRA-18943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18943: - Reviewers: Berenguer Blasi (was: Berenguer Blasi, Brandon Williams) > http/2 vulnerability: CVE-2023-44487 > > > Key: CASSANDRA-18943 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18943 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.0.x, 5.x > > > https://nvd.nist.gov/vuln/detail/CVE-2023-44487 > Basically anything using http/2 is covered by this, but we don't use it. -- 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-4.1 updated (d6bf4fd98f -> d3cc2a65b8)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from d6bf4fd98f Merge branch 'cassandra-4.0' into cassandra-4.1 new 5bf1d2f8d5 Suppress CVE-2023-44487 new cec0e1b864 Merge branch 'cassandra-3.0' into cassandra-3.11 new 0a91114dd5 Merge branch 'cassandra-3.11' into cassandra-4.0 new 349ec3e02d Merge branch 'cassandra-3.0' into cassandra-3.11 new 2fa7c1204c Merge branch 'cassandra-3.11' into cassandra-4.0 new d3cc2a65b8 Merge branch 'cassandra-4.0' into cassandra-4.1 The 6 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: .build/dependency-check-suppressions.xml | 1 + CHANGES.txt | 1 + 2 files changed, 2 insertions(+) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (e8c5fe31a2 -> 45c6352938)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from e8c5fe31a2 Merge branch 'cassandra-5.0' into trunk new 5bf1d2f8d5 Suppress CVE-2023-44487 new cec0e1b864 Merge branch 'cassandra-3.0' into cassandra-3.11 new 0a91114dd5 Merge branch 'cassandra-3.11' into cassandra-4.0 new 349ec3e02d Merge branch 'cassandra-3.0' into cassandra-3.11 new 2fa7c1204c Merge branch 'cassandra-3.11' into cassandra-4.0 new d3cc2a65b8 Merge branch 'cassandra-4.0' into cassandra-4.1 new 3088b8114c Merge branch 'cassandra-4.1' into cassandra-5.0 new 45c6352938 Merge branch 'cassandra-5.0' into trunk The 8 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: .build/dependency-check-suppressions.xml | 7 +++ CHANGES.txt | 2 ++ 2 files changed, 9 insertions(+) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/03: Merge branch 'cassandra-3.0' into cassandra-3.11
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit cec0e1b86420da90e97c6d1dc5c19d16bfe88d8b Merge: 3987160bb2 5bf1d2f8d5 Author: Brandon Williams AuthorDate: Thu Oct 26 05:55:46 2023 -0500 Merge branch 'cassandra-3.0' into cassandra-3.11 .build/dependency-check-suppressions.xml | 1 + CHANGES.txt | 2 ++ 2 files changed, 3 insertions(+) diff --cc CHANGES.txt index dc7c263cc8,4906a982f3..0f0ea5ffde --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,8 -1,5 +1,10 @@@ +3.11.17 + * Fix delayed SSTable release with unsafe_aggressive_sstable_expiration (CASSANDRA-18756) + * Revert CASSANDRA-18543 (CASSANDRA-18854) + * Fix NPE when using udfContext in UDF after a restart of a node (CASSANDRA-18739) +Merged from 3.0: + 3.0.30 + * Suppress CVE-2023-44487 (CASSANDRA-18943) * Fix nodetool enable/disablebinary to correctly set rpc readiness in gossip (CASSANDRA-18935) * Implement the logic in bin/stop-server (CASSANDRA-18838) * Upgrade snappy-java to 1.1.10.4 (CASSANDRA-18878) - 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-4.0' into cassandra-4.1
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit d3cc2a65b892ddafb59e6b1adbc56cc230b3db7d Merge: d6bf4fd98f 2fa7c1204c Author: Brandon Williams AuthorDate: Thu Oct 26 06:05:42 2023 -0500 Merge branch 'cassandra-4.0' into cassandra-4.1 .build/dependency-check-suppressions.xml | 1 + CHANGES.txt | 1 + 2 files changed, 2 insertions(+) diff --cc CHANGES.txt index 98d47bb1f9,66ac892da7..0213c08aa6 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -19,7 -13,9 +19,8 @@@ Merged from 3.11 * Fix delayed SSTable release with unsafe_aggressive_sstable_expiration (CASSANDRA-18756) * Revert CASSANDRA-18543 (CASSANDRA-18854) * Fix NPE when using udfContext in UDF after a restart of a node (CASSANDRA-18739) - * Moved jflex from runtime to build dependencies (CASSANDRA-18664) Merged from 3.0: + * Suppress CVE-2023-44487 (CASSANDRA-18943) * Fix nodetool enable/disablebinary to correctly set rpc readiness in gossip (CASSANDRA-18935) * Implement the logic in bin/stop-server (CASSANDRA-18838) * Upgrade snappy-java to 1.1.10.4 (CASSANDRA-18878) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/02: Merge branch 'cassandra-4.1' into cassandra-5.0
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 3088b8114c8da14df2204ab70da5dff4f0412bde Merge: 5eba52feb8 d3cc2a65b8 Author: Brandon Williams AuthorDate: Thu Oct 26 06:05:51 2023 -0500 Merge branch 'cassandra-4.1' into cassandra-5.0 .build/dependency-check-suppressions.xml | 7 +++ CHANGES.txt | 1 + 2 files changed, 8 insertions(+) diff --cc .build/dependency-check-suppressions.xml index 6c2e52c3ca,d806926aaf..9a5da808fa --- a/.build/dependency-check-suppressions.xml +++ b/.build/dependency-check-suppressions.xml @@@ -35,6 -35,27 +35,13 @@@ CVE-2021-4235 CVE-2017-18640 ++ ++ + - -^pkg:maven/com\.google\.guava/guava@.*$ -CVE-2020-8908 -CVE-2023-2976 - - - -^pkg:maven/io\.netty/netty\-all@.*$ -CVE-2021-21290 -CVE-2021-21295 -CVE-2021-21409 -CVE-2021-37136 -CVE-2021-37137 -CVE-2021-43797 -CVE-2022-24823 -CVE-2022-41881 -CVE-2022-41915 -CVE-2023-34462 ++^pkg:maven/io\.netty/netty\-.*@.*$ + CVE-2023-44487 + ++ ^pkg:maven/com\.fasterxml\.jackson\.core/jackson\-databind@.*$ diff --cc CHANGES.txt index 317954aafb,0213c08aa6..789fade1bd --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -29,9 -12,15 +29,10 @@@ Merged from 4.0 * Improve performance of compactions when table does not have an index (CASSANDRA-18773) * JMH improvements - faster build and async profiler (CASSANDRA-18871) * Enable 3rd party JDK installations for Debian package (CASSANDRA-18844) - * Fix NTS log message when an unrecognized strategy option is passed (CASSANDRA-18679) - * Fix BulkLoader ignoring cipher suites options (CASSANDRA-18582) - * Migrate Python optparse to argparse (CASSANDRA-17914) Merged from 3.11: - * Fix delayed SSTable release with unsafe_aggressive_sstable_expiration (CASSANDRA-18756) - * Revert CASSANDRA-18543 (CASSANDRA-18854) - * Fix NPE when using udfContext in UDF after a restart of a node (CASSANDRA-18739) Merged from 3.0: + * Suppress CVE-2023-44487 (CASSANDRA-18943) + * Implement the logic in bin/stop-server (CASSANDRA-18838) * Fix nodetool enable/disablebinary to correctly set rpc readiness in gossip (CASSANDRA-18935) * Implement the logic in bin/stop-server (CASSANDRA-18838) * Upgrade snappy-java to 1.1.10.4 (CASSANDRA-18878) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 02/02: Merge branch 'cassandra-5.0' into trunk
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 45c6352938dcba70c4acca10f3211bfcfd1acfa2 Merge: e8c5fe31a2 3088b8114c Author: Brandon Williams AuthorDate: Thu Oct 26 06:07:25 2023 -0500 Merge branch 'cassandra-5.0' into trunk .build/dependency-check-suppressions.xml | 7 +++ CHANGES.txt | 2 ++ 2 files changed, 9 insertions(+) diff --cc CHANGES.txt index e3a8ff051b,789fade1bd..2bc545c9f7 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -34,8 -30,9 +34,10 @@@ Merged from 4.0 * JMH improvements - faster build and async profiler (CASSANDRA-18871) * Enable 3rd party JDK installations for Debian package (CASSANDRA-18844) Merged from 3.11: + * Revert CASSANDRA-18543 (CASSANDRA-18854) Merged from 3.0: + * Suppress CVE-2023-44487 (CASSANDRA-18943) + * Implement the logic in bin/stop-server (CASSANDRA-18838) * Fix nodetool enable/disablebinary to correctly set rpc readiness in gossip (CASSANDRA-18935) * Implement the logic in bin/stop-server (CASSANDRA-18838) * Upgrade snappy-java to 1.1.10.4 (CASSANDRA-18878) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-3.11 updated (3987160bb2 -> 349ec3e02d)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 3987160bb2 Merge branch 'cassandra-3.0' into cassandra-3.11 new 5bf1d2f8d5 Suppress CVE-2023-44487 new 349ec3e02d Merge branch 'cassandra-3.0' into cassandra-3.11 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: .build/dependency-check-suppressions.xml | 1 + CHANGES.txt | 1 + 2 files changed, 2 insertions(+) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 03/03: Merge branch 'cassandra-3.11' into cassandra-4.0
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 2fa7c1204c9f7530d0c82716c7f208b4571105a2 Merge: 0a91114dd5 349ec3e02d Author: Brandon Williams AuthorDate: Thu Oct 26 05:58:35 2023 -0500 Merge branch 'cassandra-3.11' into cassandra-4.0 .build/dependency-check-suppressions.xml | 1 + CHANGES.txt | 1 + 2 files changed, 2 insertions(+) diff --cc .build/dependency-check-suppressions.xml index b7ebb45e57,e3e244e62b..d806926aaf --- a/.build/dependency-check-suppressions.xml +++ b/.build/dependency-check-suppressions.xml @@@ -54,7 -61,35 +54,8 @@@ CVE-2022-41881 CVE-2022-41915 CVE-2023-34462 + CVE-2023-44487 - - - -^pkg:maven/com\.google\.guava/guava@.*$ -CVE-2018-10237 -CVE-2020-8908 -CVE-2023-2976 - - - - -^pkg:maven/org\.apache\.thrift/libthrift@.*$ -CVE-2015-3254 -CVE-2016-5397 -CVE-2018-1320 -CVE-2018-11798 -CVE-2019-0205 - - -^pkg:maven/com\.thinkaurelius\.thrift/thrift-server@.*$ -CVE-2015-3254 -CVE-2016-5397 -CVE-2018-1320 -CVE-2018-11798 -CVE-2019-0205 - - ^pkg:maven/com\.fasterxml\.jackson\.core/jackson\-databind@.*$ diff --cc CHANGES.txt index 52798983a4,683a5c10cc..66ac892da7 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -13,8 -2,8 +13,9 @@@ Merged from 3.11 * Fix delayed SSTable release with unsafe_aggressive_sstable_expiration (CASSANDRA-18756) * Revert CASSANDRA-18543 (CASSANDRA-18854) * Fix NPE when using udfContext in UDF after a restart of a node (CASSANDRA-18739) + * Moved jflex from runtime to build dependencies (CASSANDRA-18664) Merged from 3.0: + * Suppress CVE-2023-44487 (CASSANDRA-18943) * Fix nodetool enable/disablebinary to correctly set rpc readiness in gossip (CASSANDRA-18935) * Implement the logic in bin/stop-server (CASSANDRA-18838) * Upgrade snappy-java to 1.1.10.4 (CASSANDRA-18878) - 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-3.0' into cassandra-3.11
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 349ec3e02d66e72ca7cc9ace02b633c38e4d0fc1 Merge: 3987160bb2 5bf1d2f8d5 Author: Brandon Williams AuthorDate: Thu Oct 26 05:55:46 2023 -0500 Merge branch 'cassandra-3.0' into cassandra-3.11 .build/dependency-check-suppressions.xml | 1 + CHANGES.txt | 1 + 2 files changed, 2 insertions(+) diff --cc CHANGES.txt index dc7c263cc8,4906a982f3..683a5c10cc --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,8 -1,5 +1,9 @@@ -3.0.30 +3.11.17 + * Fix delayed SSTable release with unsafe_aggressive_sstable_expiration (CASSANDRA-18756) + * Revert CASSANDRA-18543 (CASSANDRA-18854) + * Fix NPE when using udfContext in UDF after a restart of a node (CASSANDRA-18739) +Merged from 3.0: + * Suppress CVE-2023-44487 (CASSANDRA-18943) * Fix nodetool enable/disablebinary to correctly set rpc readiness in gossip (CASSANDRA-18935) * Implement the logic in bin/stop-server (CASSANDRA-18838) * Upgrade snappy-java to 1.1.10.4 (CASSANDRA-18878) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.0 updated (d6fcca95b4 -> 2fa7c1204c)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from d6fcca95b4 Merge branch 'cassandra-3.11' into cassandra-4.0 new 5bf1d2f8d5 Suppress CVE-2023-44487 new cec0e1b864 Merge branch 'cassandra-3.0' into cassandra-3.11 new 0a91114dd5 Merge branch 'cassandra-3.11' into cassandra-4.0 new 349ec3e02d Merge branch 'cassandra-3.0' into cassandra-3.11 new 2fa7c1204c Merge branch 'cassandra-3.11' into cassandra-4.0 The 5 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: .build/dependency-check-suppressions.xml | 1 + CHANGES.txt | 1 + 2 files changed, 2 insertions(+) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 02/03: Merge branch 'cassandra-3.11' into cassandra-4.0
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 0a91114dd5b81ce1b4d4a19ff713d9e4f89867e9 Merge: d6fcca95b4 cec0e1b864 Author: Brandon Williams AuthorDate: Thu Oct 26 05:56:47 2023 -0500 Merge branch 'cassandra-3.11' into cassandra-4.0 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-3.0 updated: Suppress CVE-2023-44487
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-3.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/cassandra-3.0 by this push: new 5bf1d2f8d5 Suppress CVE-2023-44487 5bf1d2f8d5 is described below commit 5bf1d2f8d5b6b37b8f6e2718f85dec068ceb7206 Author: Brandon Williams AuthorDate: Thu Oct 19 11:33:05 2023 -0500 Suppress CVE-2023-44487 Patch by brandonwilliams; reviewed by bereng for CASSANDRA-18943 --- .build/dependency-check-suppressions.xml | 1 + CHANGES.txt | 1 + 2 files changed, 2 insertions(+) diff --git a/.build/dependency-check-suppressions.xml b/.build/dependency-check-suppressions.xml index d0a81458db..1d9fba6218 100644 --- a/.build/dependency-check-suppressions.xml +++ b/.build/dependency-check-suppressions.xml @@ -60,6 +60,7 @@ CVE-2022-41881 CVE-2022-41915 CVE-2023-34462 +CVE-2023-44487 diff --git a/CHANGES.txt b/CHANGES.txt index a33f61545f..4906a982f3 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 3.0.30 + * Suppress CVE-2023-44487 (CASSANDRA-18943) * Fix nodetool enable/disablebinary to correctly set rpc readiness in gossip (CASSANDRA-18935) * Implement the logic in bin/stop-server (CASSANDRA-18838) * Upgrade snappy-java to 1.1.10.4 (CASSANDRA-18878) - 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 ] Brandon Williams updated CASSANDRA-18963: - Fix Version/s: 5.0.x (was: 5.0) > 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.x > > > Seems flaky > https://app.circleci.com/pipelines/github/driftx/cassandra/1342/workflows/9554c7b5-dd60-4f08-8db5-c954febc8ad6/jobs/58957/tests -- 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-18715) Add support for vector search in SAI
[ https://issues.apache.org/jira/browse/CASSANDRA-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779830#comment-17779830 ] Mike Adamson commented on CASSANDRA-18715: -- The contributors of the patch associated with this ticket wish to make it clear that the contribution adheres to clauses #5 & #7 of the Apache Foundation [ICLA|https://www.apache.org/licenses/icla.pdf]. > Add support for vector search in SAI > > > Key: CASSANDRA-18715 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18715 > Project: Cassandra > Issue Type: Improvement > Components: Feature/Vector Search >Reporter: Mike Adamson >Assignee: Mike Adamson >Priority: Normal > Fix For: 5.0-beta, 5.x > > Time Spent: 24h 20m > Remaining Estimate: 0h > > The patch associated with this ticket adds a new vector index to SAI. This > introduces the following new elements and changes to SAI: > * VectorMemtableIndex - the in-memory representation of the vector indexes > that writes data to a DiskANN instance > * VectorSegmentBuilder - that writes a DiskANN graph to the following > on-disk components: > ** VECTOR - contains the floating point vectors associated with the graph > ** TERMS - contains the HNSW graph on-disk representation written by a > HnswGraphWriter > ** POSTINGS - contains the index postings as written by a > VectorPostingsWriter > * VectorIndexSegmentSearcher - used to search the on-disk DiskANN graph -- 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-18942) Repeatable test runs
[ https://issues.apache.org/jira/browse/CASSANDRA-18942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18942: --- Reviewers: Michael Semb Wever > Repeatable test runs > > > Key: CASSANDRA-18942 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18942 > Project: Cassandra > Issue Type: New Feature > Components: Build, CI >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 5.0, 5.0.x > > Time Spent: 1h 20m > Remaining Estimate: 0h > > It is our policy to loop new introduced tests to avoid introducing flakies. > We also want to add the possibility to repeat a test N number of times to > test robustness, debug flakies, etc. -- 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-18942) Repeatable test runs
[ https://issues.apache.org/jira/browse/CASSANDRA-18942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779826#comment-17779826 ] Berenguer Blasi commented on CASSANDRA-18942: - Recap so far: - 2 new scripts run-tests-enhanced.sh are added. These add repeat functionality and work with getopts format params - A new [jenkins job|https://ci-cassandra.apache.org/job/Cassandra-5.0-repeat/] can already be used to fire repeated test runs - The original run-tests.sh scripts are kept but they just call the new ones. This allows to A. Not having to modify the current Jenkins DSL and avoiding a big-bang 'release' of the ticket B. Easy revert of the ticket if needed C. Compatibility with any other CI integrations or implementations using the original scripts - All java repeats should work and results are SSH'ed to nightlies. A cron job will be requested for periodic cleanup of that folder. - Python dtests are not working yet - All Jenkins DSL wotk such as adding the new jenkins job or renaming of scripts can happen in a later ticket to not de-stabilize CI once this ticket is merged and seen stable. > Repeatable test runs > > > Key: CASSANDRA-18942 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18942 > Project: Cassandra > Issue Type: New Feature > Components: Build, CI >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 5.0, 5.0.x > > Time Spent: 1h 20m > Remaining Estimate: 0h > > It is our policy to loop new introduced tests to avoid introducing flakies. > We also want to add the possibility to repeat a test N number of times to > test robustness, debug flakies, etc. -- 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-18961) Record commit timestamp - fix data loss when dropping and recreating a column
[ https://issues.apache.org/jira/browse/CASSANDRA-18961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacek Lewandowski updated CASSANDRA-18961: -- Test and Documentation Plan: run regression tests Status: Patch Available (was: In Progress) > Record commit timestamp - fix data loss when dropping and recreating a column > - > > Key: CASSANDRA-18961 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18961 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Jacek Lewandowski >Assignee: Jacek Lewandowski >Priority: Normal > > Drop column transformation is replayed with the current timestamp so the > column appears to be dropped when the node starts regardless of its real drop > time. > As a solution to this problem I propose recording the timestamp of the > transformation, guaranteeing that it is always greater than a timestamp of > any previously committed transformation. Such timestamp is passed to the > execute method of the transformation so that the transformation code can make > use of it, increasing its "purity". -- 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-18943) http/2 vulnerability: CVE-2023-44487
[ https://issues.apache.org/jira/browse/CASSANDRA-18943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779822#comment-17779822 ] Berenguer Blasi commented on CASSANDRA-18943: - LGTM +1. I opened CASSANDRA-18963 for the only not known failure. > http/2 vulnerability: CVE-2023-44487 > > > Key: CASSANDRA-18943 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18943 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.0.x, 5.x > > > https://nvd.nist.gov/vuln/detail/CVE-2023-44487 > Basically anything using http/2 is covered by this, but we don't use it. -- 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-18715) Add support for vector search in SAI
[
https://issues.apache.org/jira/browse/CASSANDRA-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779821#comment-17779821
]
Andres de la Peña commented on CASSANDRA-18715:
---
CI looks good, although it seems one of the trunk repeated runs of
{{VectorDistributedTest}} has failed on {{{}rangeRestrictedTest{}}}. Output
file
[here|https://output.circle-artifacts.com/output/job/4c433c82-c048-4776-9c3f-ee6656f94d24/artifacts/5/stdout/fails/17/org.apache.cassandra.distributed.test.sai.VectorDistributedTest.txt].
> Add support for vector search in SAI
>
>
> Key: CASSANDRA-18715
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18715
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Vector Search
>Reporter: Mike Adamson
>Assignee: Mike Adamson
>Priority: Normal
> Fix For: 5.0-beta, 5.x
>
> Time Spent: 24h 20m
> Remaining Estimate: 0h
>
> The patch associated with this ticket adds a new vector index to SAI. This
> introduces the following new elements and changes to SAI:
> * VectorMemtableIndex - the in-memory representation of the vector indexes
> that writes data to a DiskANN instance
> * VectorSegmentBuilder - that writes a DiskANN graph to the following
> on-disk components:
> ** VECTOR - contains the floating point vectors associated with the graph
> ** TERMS - contains the HNSW graph on-disk representation written by a
> HnswGraphWriter
> ** POSTINGS - contains the index postings as written by a
> VectorPostingsWriter
> * VectorIndexSegmentSearcher - used to search the on-disk DiskANN graph
--
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] [Created] (CASSANDRA-18963) Test Failure: sstableutil_test.TestSSTableUtil
Berenguer Blasi created CASSANDRA-18963: --- Summary: Test Failure: sstableutil_test.TestSSTableUtil Key: CASSANDRA-18963 URL: https://issues.apache.org/jira/browse/CASSANDRA-18963 Project: Cassandra Issue Type: Bug Reporter: Berenguer Blasi Seems flaky https://app.circleci.com/pipelines/github/driftx/cassandra/1342/workflows/9554c7b5-dd60-4f08-8db5-c954febc8ad6/jobs/58957/tests -- 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 ] Berenguer Blasi updated CASSANDRA-18963: Bug Category: Parent values: Correctness(12982) Complexity: Normal Component/s: Test/unit Discovered By: Unit Test Fix Version/s: 5.0 Severity: Normal Status: Open (was: Triage Needed) > 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 > > > Seems flaky > https://app.circleci.com/pipelines/github/driftx/cassandra/1342/workflows/9554c7b5-dd60-4f08-8db5-c954febc8ad6/jobs/58957/tests -- 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-16565) Remove dependency on sigar
[
https://issues.apache.org/jira/browse/CASSANDRA-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779818#comment-17779818
]
Stefan Miklosovic commented on CASSANDRA-16565:
---
Reading it from "/proc/$pid/limits" was kind of my idea ... we got there
because the original solution was executing "bash -c ulimit -u" and I really
think we should not do that. It is just too brittle to do it like that from
Java. A lot of moving parts. Possible security issues. Because bash does not
strictly has to be everywhere. What if there is just "sh"? And more
importantly, check this:
{code}
[root@8e39a687b6c6 /]# sh --help
GNU bash, version 4.2.46(2)-release-(x86_64-redhat-linux-gnu)
Usage: sh [GNU long option] [option] ...
sh [GNU long option] [option] script-file ...
GNU long options:
--debug
--debugger
--dump-po-strings
--dump-strings
--help
--init-file
--login
--noediting
--noprofile
--norc
--posix
--protected
--rcfile
--rpm-requires
--restricted
--verbose
--version
Shell options:
-irsD or -c command or -O shopt_option (invocation only)
-abefhkmnptuvxBCHP or -o option
{code}
check this:
{code}
The --norc flag in a shell command, like sh, instructs the shell to start
without reading the user's ~/.shrc (Bourne shell run commands) or ~/.bashrc
(Bash run commands) configuration files. These configuration files often
contain user-specific settings, aliases, environment variables, and
customizations for the shell environment.
{code}
So if I have a bunch of custom functions in these files, doing god knows what,
then it will be invoked along with "bash -c ulimit -u"? That is a security
hole, isn't it? So we would need to put various arguments to that, and these
arguments might vary across different shells, and there might be a lot of
shells aliasing to sh each doing it differently etc etc. It is just easier to
read a file and that's it.
> Remove dependency on sigar
> --
>
> Key: CASSANDRA-16565
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16565
> Project: Cassandra
> Issue Type: Improvement
> Components: Build
>Reporter: David Capwell
>Assignee: Claude Warren
>Priority: Normal
> Fix For: 5.x
>
>
> sigar is used to check if the environment has good settings for running C*,
> but requires we bundle a lot of native libraries to perform this check (which
> can also be done elsewhere). This project also appears to be dead as the
> last commit was around 6 years ago.
> With the move to resolve artifacts rather than commit them, removing this
> dependency would remove majority of the artifacts fetched from GitHub.
--
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-18872) Remove deprecated crc_check_chance in compression params
[ https://issues.apache.org/jira/browse/CASSANDRA-18872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18872: -- Reviewers: Branimir Lambov, Jacek Lewandowski, Maxwell Guo (was: Jacek Lewandowski, Maxwell Guo) Status: Review In Progress (was: Needs Committer) > Remove deprecated crc_check_chance in compression params > > > Key: CASSANDRA-18872 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18872 > Project: Cassandra > Issue Type: Task > Components: Feature/Compression, Legacy/CQL >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > Time Spent: 1h > Remaining Estimate: 0h > > crc_check_chance was moved from compression parameters and it is a standalone > table parameter. This was done in times of 3.0 so it is now time to get rid > of that in 5.0. -- 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-18872) Remove deprecated crc_check_chance in compression params
[ https://issues.apache.org/jira/browse/CASSANDRA-18872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18872: -- Status: Ready to Commit (was: Review In Progress) > Remove deprecated crc_check_chance in compression params > > > Key: CASSANDRA-18872 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18872 > Project: Cassandra > Issue Type: Task > Components: Feature/Compression, Legacy/CQL >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > Time Spent: 1h > Remaining Estimate: 0h > > crc_check_chance was moved from compression parameters and it is a standalone > table parameter. This was done in times of 3.0 so it is now time to get rid > of that in 5.0. -- 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
