[jira] [Commented] (CASSANDRA-18360) Test Failure: o.a.c.cql3.validation.operations.AlterTest#testDropListAndAddListWithSameName
[
https://issues.apache.org/jira/browse/CASSANDRA-18360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761949#comment-17761949
]
Berenguer Blasi commented on CASSANDRA-18360:
-
It seems it doesn't repro anymore:
- Not with RepeatableRunner in 5.0 or trunk
- Not on circle on either on 5.0
[500|https://app.circleci.com/pipelines/github/bereng/cassandra/1059/workflows/2a14c247-d90e-4b31-a58c-455f21395351/jobs/27942]
repeats or trunk
[5K|https://app.circleci.com/pipelines/github/bereng/cassandra/1061/workflows/7981875b-5956-4e02-b172-ef26d769046b/jobs/28168]
and
[500|https://app.circleci.com/pipelines/github/bereng/cassandra/1060/workflows/41f40ff6-3724-4121-b759-8f28edca509d/jobs/28055]
repeats.
Either it doesn't repro for me or it is gone. If sbdy could confirm with a
rebase I'd propose to close as won't repro until it does and reopen if needed.
Wdyt?
> Test Failure:
> o.a.c.cql3.validation.operations.AlterTest#testDropListAndAddListWithSameName
> ---
>
> Key: CASSANDRA-18360
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18360
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.x
>
>
> The unit test
> {{org.apache.cassandra.cql3.validation.operations.AlterTest#testDropListAndAddListWithSameName}}
> is flaky at least on trunk. Flakiness seems lesser than 1%.
> While I haven't seen it on Jenkins yet, it can easily be reproduced on
> CircleCI with the multiplexer:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2731/workflows/58edc2f6-9a21-4d09-b783-b7fb15e1b320/jobs/32235
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2731/workflows/58edc2f6-9a21-4d09-b783-b7fb15e1b320/jobs/32234
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2731/workflows/739a95d3-8e42-4447-93dd-122fc16fdd7d/jobs/32233/tests
> Those runs show two types of errors:
> {code}
> junit.framework.AssertionFailedError: Invalid value for row 0 column 1
> (content of type text), expected but got
> at org.apache.cassandra.cql3.CQLTester.assertRows(CQLTester.java:1506)
> at
> org.apache.cassandra.cql3.validation.operations.AlterTest.testDropListAndAddListWithSameName(AlterTest.java:102)
> {code}
> and:
> {code}
> org.apache.cassandra.serializers.MarshalException: Invalid UTF-8 bytes
> 00e0279515437f00
> at
> org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:46)
> at
> org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:29)
> at
> org.apache.cassandra.serializers.TypeSerializer.deserialize(TypeSerializer.java:37)
> at org.apache.cassandra.cql3.CQLTester.assertRows(CQLTester.java:1494)
> at
> org.apache.cassandra.cql3.validation.operations.AlterTest.testDropListAndAddListWithSameName(AlterTest.java:102)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_UTESTS_COUNT=500 \
> -e REPEATED_UTESTS=org.apache.cassandra.cql3.validation.operations.AlterTest
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18360) Test Failure: o.a.c.cql3.validation.operations.AlterTest#testDropListAndAddListWithSameName
[
https://issues.apache.org/jira/browse/CASSANDRA-18360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-18360:
Test and Documentation Plan: See comments
Status: Patch Available (was: In Progress)
> Test Failure:
> o.a.c.cql3.validation.operations.AlterTest#testDropListAndAddListWithSameName
> ---
>
> Key: CASSANDRA-18360
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18360
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.x
>
>
> The unit test
> {{org.apache.cassandra.cql3.validation.operations.AlterTest#testDropListAndAddListWithSameName}}
> is flaky at least on trunk. Flakiness seems lesser than 1%.
> While I haven't seen it on Jenkins yet, it can easily be reproduced on
> CircleCI with the multiplexer:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2731/workflows/58edc2f6-9a21-4d09-b783-b7fb15e1b320/jobs/32235
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2731/workflows/58edc2f6-9a21-4d09-b783-b7fb15e1b320/jobs/32234
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2731/workflows/739a95d3-8e42-4447-93dd-122fc16fdd7d/jobs/32233/tests
> Those runs show two types of errors:
> {code}
> junit.framework.AssertionFailedError: Invalid value for row 0 column 1
> (content of type text), expected but got
> at org.apache.cassandra.cql3.CQLTester.assertRows(CQLTester.java:1506)
> at
> org.apache.cassandra.cql3.validation.operations.AlterTest.testDropListAndAddListWithSameName(AlterTest.java:102)
> {code}
> and:
> {code}
> org.apache.cassandra.serializers.MarshalException: Invalid UTF-8 bytes
> 00e0279515437f00
> at
> org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:46)
> at
> org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:29)
> at
> org.apache.cassandra.serializers.TypeSerializer.deserialize(TypeSerializer.java:37)
> at org.apache.cassandra.cql3.CQLTester.assertRows(CQLTester.java:1494)
> at
> org.apache.cassandra.cql3.validation.operations.AlterTest.testDropListAndAddListWithSameName(AlterTest.java:102)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_UTESTS_COUNT=500 \
> -e REPEATED_UTESTS=org.apache.cassandra.cql3.validation.operations.AlterTest
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (c8acd9e85 -> 3445b5ef0)
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 c8acd9e85 generate docs for d7f28f31 new 3445b5ef0 generate docs for d7f28f31 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 (c8acd9e85) \ N -- N -- N refs/heads/asf-staging (3445b5ef0) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4881369 -> 4881369 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (5a6ebda3c -> c8acd9e85)
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 5a6ebda3c generate docs for d7f28f31 new c8acd9e85 generate docs for d7f28f31 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 (5a6ebda3c) \ N -- N -- N refs/heads/asf-staging (c8acd9e85) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4881369 -> 4881369 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (f50340575 -> 5a6ebda3c)
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 f50340575 generate docs for d7f28f31 new 5a6ebda3c generate docs for d7f28f31 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 (f50340575) \ N -- N -- N refs/heads/asf-staging (5a6ebda3c) 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 4881369 -> 4881369 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-15254) Allow UPDATE on settings virtual table to change running configurations
[ https://issues.apache.org/jira/browse/CASSANDRA-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761887#comment-17761887 ] Stefan Miklosovic commented on CASSANDRA-15254: --- [~mmuzaf] some food for thought https://github.com/apache/cassandra/pull/2334/files#r1315196421 > Allow UPDATE on settings virtual table to change running configurations > --- > > Key: CASSANDRA-15254 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15254 > Project: Cassandra > Issue Type: New Feature > Components: Feature/Virtual Tables >Reporter: Chris Lohfink >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.x > > Attachments: Configuration Registry Diagram.png > > Time Spent: 19h 50m > Remaining Estimate: 0h > > Allow using UPDATE on the system_views.settings virtual table to update > configs at runtime for the equivalent of the dispersed JMX > attributes/operations. -- 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-18819) Re-organize ordering of configuration properties in cassandra.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-18819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761881#comment-17761881 ] Michael Semb Wever commented on CASSANDRA-18819: I think sometimes properties are intentionally hidden from cassandra.yaml , but I don't know if that now/still applies to those two. This feels like a duplicate of (or it will be superseded by) CASSANDRA-17292. > Re-organize ordering of configuration properties in cassandra.yaml > -- > > Key: CASSANDRA-18819 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18819 > Project: Cassandra > Issue Type: Task >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > > I was setting up a cluster from scratch and I was configuring cassandra.yaml, > obviously. What I do not like about the current content of cassandra.yaml is > that some of its sections are seemingly scattered across that file and if > feels like out of place / order. > For example, if one wants to configure encryption it is on line 1458 and 1516 > respectively. Snitch is on line 1402. The whole file has 2100 lines. So in > order to configure a snitch, which is very common scenario when setting up a > node, if I do not know that the field I am going to edit is called > "endpoint_snitch" so I can just jump to it, I need to scroll to the three > quarters of the file to edit it. > I think that the most commonly edited sections of the configuration file > should be on the very top or somewhere around it so as I am editing that file > from scratch I just go section by section and I do not jump around, I just > edit that or I skip it and I configure what is next - ordered by the > probability that a section is going to be configured differently from a > default. > I also noticed that these properties are missing in cassandra.yaml, we can > add it there upon refactorisation of this. > memtable conf > dynamic_snitch -- 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 (bc0b0f2a1 -> f50340575)
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 bc0b0f2a1 generate docs for d7f28f31 new f50340575 generate docs for d7f28f31 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 (bc0b0f2a1) \ N -- N -- N refs/heads/asf-staging (f50340575) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4881369 -> 4881369 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (9c3eb4a91 -> bc0b0f2a1)
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 9c3eb4a91 generate docs for d7f28f31 new bc0b0f2a1 generate docs for d7f28f31 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 (9c3eb4a91) \ N -- N -- N refs/heads/asf-staging (bc0b0f2a1) 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: .../managing/tools/nodetool/replaybatchlog.html| 3 +-- content/search-index.js| 2 +- site-ui/build/ui-bundle.zip| Bin 4881369 -> 4881369 bytes 3 files changed, 2 insertions(+), 3 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r63781 - in /dev/cassandra/5.0-alpha1/redhat: ./ noboolean/ noboolean/repodata/ repodata/
Author: mck Date: Mon Sep 4 15:44:24 2023 New Revision: 63781 Log: staging cassandra rpm packages for 5.0-alpha1 Added: dev/cassandra/5.0-alpha1/redhat/ dev/cassandra/5.0-alpha1/redhat/cassandra-5.0~alpha1-1.noarch.rpm (with props) dev/cassandra/5.0-alpha1/redhat/cassandra-5.0~alpha1-1.src.rpm (with props) dev/cassandra/5.0-alpha1/redhat/cassandra-tools-5.0~alpha1-1.noarch.rpm (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/ dev/cassandra/5.0-alpha1/redhat/noboolean/cassandra-5.0~alpha1-1.noarch.rpm (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/cassandra-5.0~alpha1-1.src.rpm (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/cassandra-tools-5.0~alpha1-1.noarch.rpm (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/ dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/11fef9dd9290a1bffc16e7f1b8dbe14a11cdf98e0cb8071a01f83a19a0c506a9-filelists.xml.gz (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/11fef9dd9290a1bffc16e7f1b8dbe14a11cdf98e0cb8071a01f83a19a0c506a9-filelists.xml.gz.asc dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/18483412580a6b6520905bf42ee9f3548c1bb8c9bd6f951bf9eaaf0902fd4707-primary.sqlite.bz2 (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/18483412580a6b6520905bf42ee9f3548c1bb8c9bd6f951bf9eaaf0902fd4707-primary.sqlite.bz2.asc dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/a93e8b704b32ba06b7d3ed20061af751171721e88b89190dad49ebcf64b9048a-primary.xml.gz (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/a93e8b704b32ba06b7d3ed20061af751171721e88b89190dad49ebcf64b9048a-primary.xml.gz.asc dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/c117264fc8aa2dc67337421eac48755deb5c3e8d099ff865f08135cc7f73b855-other.xml.gz (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/c117264fc8aa2dc67337421eac48755deb5c3e8d099ff865f08135cc7f73b855-other.xml.gz.asc dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/c86fe8317904d2c7d27ec26ee81052e0ca62f9ff402f4eeae014bd77e3f317bd-filelists.sqlite.bz2 (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/c86fe8317904d2c7d27ec26ee81052e0ca62f9ff402f4eeae014bd77e3f317bd-filelists.sqlite.bz2.asc dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/f23b27cef56b42e5eea44f11bca3d965b34bf6fda7b65975f4c3db10a8241e08-other.sqlite.bz2 (with props) dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/f23b27cef56b42e5eea44f11bca3d965b34bf6fda7b65975f4c3db10a8241e08-other.sqlite.bz2.asc dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/repomd.xml dev/cassandra/5.0-alpha1/redhat/noboolean/repodata/repomd.xml.asc dev/cassandra/5.0-alpha1/redhat/repodata/ dev/cassandra/5.0-alpha1/redhat/repodata/34d4285a020404246cf14007285b0e7e23aae77e910005102577af01898b9b9e-filelists.xml.gz (with props) dev/cassandra/5.0-alpha1/redhat/repodata/34d4285a020404246cf14007285b0e7e23aae77e910005102577af01898b9b9e-filelists.xml.gz.asc dev/cassandra/5.0-alpha1/redhat/repodata/712b5fd5fe2aa2a1325e80a3bb9a227c1cfc1a0432c63bdc05a848a7aeb22c27-primary.xml.gz (with props) dev/cassandra/5.0-alpha1/redhat/repodata/712b5fd5fe2aa2a1325e80a3bb9a227c1cfc1a0432c63bdc05a848a7aeb22c27-primary.xml.gz.asc dev/cassandra/5.0-alpha1/redhat/repodata/b9189ec42475d1971b37644e65e8a0b4b33aa65b42c7923e0168dd0a12631919-other.sqlite.bz2 (with props) dev/cassandra/5.0-alpha1/redhat/repodata/b9189ec42475d1971b37644e65e8a0b4b33aa65b42c7923e0168dd0a12631919-other.sqlite.bz2.asc dev/cassandra/5.0-alpha1/redhat/repodata/bc3381dcfbdb0c2b3db2dab77285502b1a21fa6042002146399968495e187140-other.xml.gz (with props) dev/cassandra/5.0-alpha1/redhat/repodata/bc3381dcfbdb0c2b3db2dab77285502b1a21fa6042002146399968495e187140-other.xml.gz.asc dev/cassandra/5.0-alpha1/redhat/repodata/d2aab3836f121ceede4044b1b64462a4a04b771389b273325562f68f9a60221d-primary.sqlite.bz2 (with props) dev/cassandra/5.0-alpha1/redhat/repodata/d2aab3836f121ceede4044b1b64462a4a04b771389b273325562f68f9a60221d-primary.sqlite.bz2.asc dev/cassandra/5.0-alpha1/redhat/repodata/dff7f7a7ca8a1d3cb969def696dba651f1391a6a1642d90aa646072ead924dac-filelists.sqlite.bz2 (with props) dev/cassandra/5.0-alpha1/redhat/repodata/dff7f7a7ca8a1d3cb969def696dba651f1391a6a1642d90aa646072ead924dac-filelists.sqlite.bz2.asc dev/cassandra/5.0-alpha1/redhat/repodata/repomd.xml dev/cassandra/5.0-alpha1/redhat/repodata/repomd.xml.asc Added: dev/cassandra/5.0-alpha1/redhat/cassandra-5.0~alpha1-1.noarch.rpm == Binary file - no diff available. Propchange: dev/cassandra/5.0-alpha1/redhat/cassandra-5.0~alpha1-1.noarch.rpm -- svn:mime-type = application/octet-stream Added: dev/cassandra/5.0-alpha1/redhat/cassandra-5.0~alpha1-1.s
svn commit: r63780 - in /dev/cassandra/5.0-alpha1/debian: ./ dists/ dists/50x/ dists/50x/main/ dists/50x/main/binary-amd64/ dists/50x/main/binary-arm64/ dists/50x/main/binary-i386/ dists/50x/main/sour
Author: mck Date: Mon Sep 4 15:37:39 2023 New Revision: 63780 Log: staging cassandra debian packages for 5.0-alpha1 Added: dev/cassandra/5.0-alpha1/debian/ dev/cassandra/5.0-alpha1/debian/cassandra-tools_5.0~alpha1_all.deb (with props) dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1.dsc dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1.tar.gz (with props) dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1_all.deb (with props) dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1_amd64.buildinfo dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1_amd64.changes dev/cassandra/5.0-alpha1/debian/dists/ dev/cassandra/5.0-alpha1/debian/dists/50x/ dev/cassandra/5.0-alpha1/debian/dists/50x/InRelease dev/cassandra/5.0-alpha1/debian/dists/50x/Release dev/cassandra/5.0-alpha1/debian/dists/50x/Release.gpg dev/cassandra/5.0-alpha1/debian/dists/50x/main/ dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-amd64/ dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-amd64/Packages dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-amd64/Packages.gz (with props) dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-amd64/Release dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-arm64/ dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-arm64/Packages dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-arm64/Packages.gz (with props) dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-arm64/Release dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-i386/ dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-i386/Packages dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-i386/Packages.gz (with props) dev/cassandra/5.0-alpha1/debian/dists/50x/main/binary-i386/Release dev/cassandra/5.0-alpha1/debian/dists/50x/main/source/ dev/cassandra/5.0-alpha1/debian/dists/50x/main/source/Release dev/cassandra/5.0-alpha1/debian/dists/50x/main/source/Sources.gz (with props) dev/cassandra/5.0-alpha1/debian/pool/ dev/cassandra/5.0-alpha1/debian/pool/main/ dev/cassandra/5.0-alpha1/debian/pool/main/c/ dev/cassandra/5.0-alpha1/debian/pool/main/c/cassandra/ dev/cassandra/5.0-alpha1/debian/pool/main/c/cassandra/cassandra-tools_5.0~alpha1_all.deb (with props) dev/cassandra/5.0-alpha1/debian/pool/main/c/cassandra/cassandra_5.0~alpha1.dsc dev/cassandra/5.0-alpha1/debian/pool/main/c/cassandra/cassandra_5.0~alpha1.tar.gz (with props) dev/cassandra/5.0-alpha1/debian/pool/main/c/cassandra/cassandra_5.0~alpha1_all.deb (with props) Added: dev/cassandra/5.0-alpha1/debian/cassandra-tools_5.0~alpha1_all.deb == Binary file - no diff available. Propchange: dev/cassandra/5.0-alpha1/debian/cassandra-tools_5.0~alpha1_all.deb -- svn:mime-type = application/octet-stream Added: dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1.dsc == --- dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1.dsc (added) +++ dev/cassandra/5.0-alpha1/debian/cassandra_5.0~alpha1.dsc Mon Sep 4 15:37:39 2023 @@ -0,0 +1,41 @@ +-BEGIN PGP SIGNED MESSAGE- +Hash: SHA512 + +Format: 1.0 +Source: cassandra +Binary: cassandra, cassandra-tools +Architecture: all +Version: 5.0~alpha1 +Maintainer: Eric Evans +Uploaders: Sylvain Lebresne +Homepage: https://cassandra.apache.org +Standards-Version: 3.8.3 +Vcs-Browser: https://gitbox.apache.org/repos/asf?p=cassandra.git +Vcs-Git: https://gitbox.apache.org/repos/asf/cassandra.git +Build-Depends: debhelper (>= 11), openjdk-11-jdk | openjdk-11-jdk-headless | openjdk-17-jdk | openjdk-17-jdk-headless, ant (>= 1.10), ant-optional (>= 1.10), dh-python, python3-dev (>= 3.6), quilt, bash-completion +Package-List: + cassandra deb misc extra arch=all + cassandra-tools deb misc extra arch=all +Checksums-Sha1: + 0008b59857263567827a3f9121ad4e5c3440 14721390 cassandra_5.0~alpha1.tar.gz +Checksums-Sha256: + 9d191317b7a4604ddb14bd98b662811ef51c88e0763bc6721e9e18e0461e59eb 14721390 cassandra_5.0~alpha1.tar.gz +Files: + 999425fbf0b131d89cd3e6e3f4ca9c98 14721390 cassandra_5.0~alpha1.tar.gz + +-BEGIN PGP SIGNATURE- + +iQIzBAEBCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmT1+ZUACgkQ6RM1134+ +h8vmrBAAhAzpb6xYkvol+VqbX7FobePCef8GCIGqtRkijKT+ACy0WZudNDx0rmVM +qKGFn8OCIbPKGN7i6qnzrKwwik6cUlrKV7pnDwaccPiAnOlUf1tc7y52CzZ8KpV0 +Sj5y7fVnf1g1e6BRgvl+tCxIeaAYNmN5nj3m5BiJVCW8yC57uFQJxzutdTSRbEtO +S49A4HLIXFXkLrRZNdYKhe7Tm51kLeS7wiautcbVb8dSVTNXLTauNr3lv3wuwgUE +vmjfaguxQBlGEmkRHlXHLsI/uDzHTbZGLqD+FiNh+et6/7naSl0oUPeil+PrU+hO +n4Q+xA3GxnU88qguJG0jE77UTAUX1stcb+mcBIZMABvB+pItjXNjjALctkfYco0v +hgadrvoQiml1IUdI5eqsCyF1yTvbJr0KCNmK8r+2epDWFZPvl+imvXD9LanMPOEd +4wnUQVCTgNIx2BLOkKEwvSaKzDEI1CF7O8PHHuydsFAcZnqYuqiQI0pMTysK0Edh +kGPMp0/9S
svn commit: r63779 - /dev/cassandra/5.0-alpha1/
Author: mck Date: Mon Sep 4 15:34:20 2023 New Revision: 63779 Log: staging cassandra 5.0-alpha1 Added: dev/cassandra/5.0-alpha1/ dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz (with props) dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.asc dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha256 dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha512 dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz (with props) dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz.asc dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz.sha256 dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz.sha512 Added: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz == Binary file - no diff available. Propchange: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz -- svn:mime-type = application/octet-stream Added: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.asc == --- dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.asc (added) +++ dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.asc Mon Sep 4 15:34:20 2023 @@ -0,0 +1,16 @@ +-BEGIN PGP SIGNATURE- + +iQIzBAABCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmT1+MIACgkQ6RM1134+ +h8vYoxAAhWtuTyi8qluAgTn3vVs4XHgyDLDmFvmN1mWdbLQXhaR8OdK6ajGE2nWJ +Y5Sj0RYAM7C2saBbWu5fiVdxDNWP6C0w4d4EzEjTbAZLxcsYMVPocrajFvslE3xe +0kgWH7GrfuEiCPadUcfe2Kbozf/zTG9OrsYotdaWFujcbNrKb98TlCUvKhDh0SD0 +Vr8qpdmDWnFQhsMwBu6Qy8+4zRa0GRH+aCzV76FWEPyD/QuEWJaeqzjH4PtXUtQB +w842wqoHTnVjL/y0ZdmETAiakwQwvzlLZTAh8meOHAohNppWm3axf1ggRFSJ1vPS +AqMN9aUgRVpFaFf05jKPR1vR6ak80u1ct6QYxjKLRE1gitjMhhybRxY02vMiA0FU +VlrSX1IbcRxrPnPzf4w1lT2CAK0Rt1j1UV8DzwKVsWIZVXek+I7MV40xjcUs5+dU +SXweIRFw/O6/fV1KyknKCAiGtQvAncursmrolK6W0CgLWo3sxs0RaS+aKokieXu4 +95DPH/C/lZrLEsWWegowiwc92L+taCxJuQ+x6H+AMg0DZbAhm614ZcdBt0hRi+Rk +USs2y2FtLsa53dpswXM/rdqelAK11WzyxliVqjFNgXLvm95oIAoxazS3vgIK/xi+ +xnOxY1jXKsJIYMUYjj54xLHVSNz6euAJ4rHEcZLWgo5xf2TlntU= +=jVf+ +-END PGP SIGNATURE- Added: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha256 == --- dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha256 (added) +++ dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha256 Mon Sep 4 15:34:20 2023 @@ -0,0 +1 @@ +8f556f2e5406d1d3138f18fede0bce142b052791a255fad49a6876c48173537e Added: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha512 == --- dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha512 (added) +++ dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-bin.tar.gz.sha512 Mon Sep 4 15:34:20 2023 @@ -0,0 +1 @@ +095aede626067da34fc60c04c528030e3860d7489752a9200cf0bcffd93f18c1158512759bb56b85d65def98cfec3580a9edea9dfa5addfd80bd4ceab8a84ebf Added: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz == Binary file - no diff available. Propchange: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz -- svn:mime-type = application/octet-stream Added: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz.asc == --- dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz.asc (added) +++ dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz.asc Mon Sep 4 15:34:20 2023 @@ -0,0 +1,16 @@ +-BEGIN PGP SIGNATURE- + +iQIzBAABCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmT1+MYACgkQ6RM1134+ +h8vsow//WZME8a+mLHRX2jNrYS4AvjksxbwmjVsY/RfHwAeUzE1G+nMf7Qz5XBLm +TFQQktD8D3efCM5cakn0a9bQbbt7AksnEmgO858L7kKWy979m8G5eouyrSuDNBB1 +7STNkXTqOhzot76jGJc+OmW2kGcUZC+E++TZBySuvBWgrPFiTSxiTWCEVKeGyIaA +Jk7iDczh0A4E7ywaop2ek5RqrQSJY34oBD1v0yKzsMI2G9dEUK5nP91tTKsW0yBK +q1W+y7EW5j5NkGj36e6aV+8neLZtRtA8tEAuwyHLpFzCqeDJmyVZ178jcCHuzPBi +bciJNB51yN8x7nvhOY0JU2Uo0nZXWq+XV7ySRRh58kOfQYh99vgF/QLp/SIhDvWw +IZnEabzGnz9yrGjvC0SFMBlFg+Ix9m8Pvxg+2D6EDzZD+zhXpyoYqs7I373AZVcl +2/tG2hjlZY/c4EXxRJm+KQCGIScBQ5ADDy7GoLFV49suwOLIOInwczqV97NvMkIx +CtpJibp5XgmCFHljPV/zD/Gcnc/3HUcq6mfiOVDJnulwWfJ6gca4+hEBrvijCCNW +FCIL3VhNIrKcf3lUPV4G90kXqnz9F9D/Mdw2oNA/elhkQFZJFTp/jkwnq2ksQwNo +7KR0fJuwrrj4tr8g7hMd6vTyajf5w9nxzPxZg0wGlLjwuKfzpIs= +=IXZ8 +-END PGP SIGNATURE- Added: dev/cassandra/5.0-alpha1/apache-cassandra-5.0-alpha1-src.tar.gz.sha256 == --- dev/cassand
[cassandra] tag 5.0-alpha1-tentative created (now bc5e3741d4)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to tag 5.0-alpha1-tentative in repository https://gitbox.apache.org/repos/asf/cassandra.git at bc5e3741d4 (commit) This tag includes the following new commits: new bc5e3741d4 Prepare debian changelog for 5.0-alpha1 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. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Prepare debian changelog for 5.0-alpha1
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to tag 5.0-alpha1-tentative in repository https://gitbox.apache.org/repos/asf/cassandra.git commit bc5e3741d475e2e99fd7a10450681fd708431a89 Author: Mick Semb Wever AuthorDate: Mon Sep 4 17:29:13 2023 +0200 Prepare debian changelog for 5.0-alpha1 --- debian/changelog | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index 6388abff14..35337b5862 100644 --- a/debian/changelog +++ b/debian/changelog @@ -2,7 +2,7 @@ cassandra (5.0~alpha1) unstable; urgency=medium * New release - -- Mick Semb Wever Fri, 01 Sep 2023 11:22:35 +0200 + -- Mick Semb Wever Mon, 04 Sep 2023 17:28:27 +0200 cassandra (4.0~rc1) unstable; urgency=medium - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18817) RPM install does not work with jdk17
[ https://issues.apache.org/jira/browse/CASSANDRA-18817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18817: - Reviewers: Brandon Williams (was: Brandon Williams, Michael Semb Wever) > RPM install does not work with jdk17 > > > Key: CASSANDRA-18817 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18817 > Project: Cassandra > Issue Type: Bug > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 5.0, 5.0-alpha1, 5.1 > > > The cassandra.in.sh file was updated as part of CASSANDRA-18255 but the > corresponding redhat/cassandra.in.sh was not. > This means when cassandra starts on a rpm install using jdk17 the > jvm11-server.options file is still used. And so it fails. > Initial patch that works: > https://github.com/apache/cassandra/compare/cassandra-5.0...thelastpickle:cassandra:mck/redhat-jdk17-fix/5.0 > > Maybe it is possible to find a superior solution, like wrapping this file > instead of duplicating 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] [Assigned] (CASSANDRA-18817) RPM install does not work with jdk17
[ https://issues.apache.org/jira/browse/CASSANDRA-18817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams reassigned CASSANDRA-18817: Assignee: Michael Semb Wever > RPM install does not work with jdk17 > > > Key: CASSANDRA-18817 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18817 > Project: Cassandra > Issue Type: Bug > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 5.0, 5.0-alpha1, 5.1 > > > The cassandra.in.sh file was updated as part of CASSANDRA-18255 but the > corresponding redhat/cassandra.in.sh was not. > This means when cassandra starts on a rpm install using jdk17 the > jvm11-server.options file is still used. And so it fails. > Initial patch that works: > https://github.com/apache/cassandra/compare/cassandra-5.0...thelastpickle:cassandra:mck/redhat-jdk17-fix/5.0 > > Maybe it is possible to find a superior solution, like wrapping this file > instead of duplicating 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-5.0 updated: Fix rpm installation on jdk17
This is an automated email from the ASF dual-hosted git repository.
mck pushed a commit to branch cassandra-5.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/cassandra-5.0 by this push:
new 17d0eb138c Fix rpm installation on jdk17
17d0eb138c is described below
commit 17d0eb138c69a1c9c44256695252b2d2213a2633
Author: Mick Semb Wever
AuthorDate: Sun Sep 3 17:13:18 2023 +0200
Fix rpm installation on jdk17
patch by Mick Semb Wever; reviewed by Brandon Williams for CASSANDRA-18817
---
CHANGES.txt| 17 +
redhat/cassandra.in.sh | 26 +-
2 files changed, 18 insertions(+), 25 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index b7880b259a..1977bd1d2b 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,18 +1,15 @@
5.0-alpha2
- * Fix Depends and Build-Depends for Java for Debian packages (CASSANDRA-18809)
- * Update command line flags --add-exports and --add-opens for JDK17
(CASSANDRA-18439)
- * Update commons-lang3 to 3.13.0 (CASSANDRA-18789)
- * Forbid SAI indexes with analysis options on primary key columns
(CASSANDRA-18782)
Merged from 4.1:
- * Waiting indefinitely on ReceivedMessage response in StreamSession#receive()
can cause deadlock (CASSANDRA-18733)
- * Allow empty keystore_password in encryption_options (CASSANDRA-18778)
Merged from 4.0:
Merged from 3.11:
Merged from 3.0:
- * Refactor validation logic in StorageService.rebuild (CASSANDRA-18803)
- * Make alternation of a user type validate the same way as creation of a user
type does (CASSANDRA-18585)
5.0-alpha1
+ * Fix rpm installations to work with jdk17 (CASSANDRA-18817)
+ * Fix Depends and Build-Depends for Java for Debian packages (CASSANDRA-18809)
+ * Update command line flags --add-exports and --add-opens for JDK17
(CASSANDRA-18439)
+ * Update commons-lang3 to 3.13.0 (CASSANDRA-18789)
+ * Forbid SAI indexes with analysis options on primary key columns
(CASSANDRA-18782)
* Expose bootstrap failure state via JMX and nodetool info (CASSANDRA-18749)
* Reduce size of per-SSTable index components for SAI (CASSANDRA-18673)
* Remove unnecessary Netty dependencies after upgrade to version 4.1.96
(CASSANDRA-18729)
@@ -197,12 +194,16 @@ Merged from 3.0:
* Add guardrail for ALTER TABLE ADD / DROP / REMOVE column operations
(CASSANDRA-17495)
* Rename DisableFlag class to EnableFlag on guardrails (CASSANDRA-17544)
Merged from 4.1:
+ * Waiting indefinitely on ReceivedMessage response in StreamSession#receive()
can cause deadlock (CASSANDRA-18733)
+ * Allow empty keystore_password in encryption_options (CASSANDRA-18778)
* Skip ColumnFamilyStore#topPartitions initialization when client or tool
mode (CASSANDRA-18697)
Merged from 4.0:
* Partial compaction can resurrect deleted data (CASSANDRA-18507)
Merged from 3.11:
* Fix NPE when using udfContext in UDF after a restart of a node
(CASSANDRA-18739)
Merged from 3.0:
+ * Refactor validation logic in StorageService.rebuild (CASSANDRA-18803)
+ * Make alternation of a user type validate the same way as creation of a user
type does (CASSANDRA-18585)
* CQLSH emits a warning when the server version doesn't match
(CASSANDRA-18745)
* Fix missing speculative retries in tablestats (CASSANDRA-18767)
* Fix Requires for Java for RPM package (CASSANDRA-18751)
diff --git a/redhat/cassandra.in.sh b/redhat/cassandra.in.sh
index 8ec1905ac0..7f5a374514 100644
--- a/redhat/cassandra.in.sh
+++ b/redhat/cassandra.in.sh
@@ -78,21 +78,13 @@ fi
java_ver_output=`"${JAVA:-java}" -version 2>&1`
jvmver=`echo "$java_ver_output" | grep '[openjdk|java] version' | awk -F'"'
'NR==1 {print $2}' | cut -d\- -f1`
JVM_VERSION=${jvmver%_*}
+short=$(echo "${jvmver}" | cut -c1-2)
-JAVA_VERSION=11
-if [ "$JVM_VERSION" = "1.8.0" ] ; then
-JVM_PATCH_VERSION=${jvmver#*_}
-if [ "$JVM_VERSION" \< "1.8" ] || [ "$JVM_VERSION" \> "1.8.2" ] ; then
-echo "Cassandra 4.0 requires either Java 8 (update 151 or newer) or
Java 11 (or newer). Java $JVM_VERSION is not supported."
-exit 1;
-fi
-if [ "$JVM_PATCH_VERSION" -lt 151 ] ; then
-echo "Cassandra 4.0 requires either Java 8 (update 151 or newer) or
Java 11 (or newer). Java 8 update $JVM_PATCH_VERSION is not supported."
-exit 1;
-fi
-JAVA_VERSION=8
-elif [ "$JVM_VERSION" \< "11" ] ; then
-echo "Cassandra 4.0 requires either Java 8 (update 151 or newer) or Java
11 (or newer)."
+JAVA_VERSION=17
+if [ "$short" = "11" ] ; then
+ JAVA_VERSION=11
+elif [ "$JVM_VERSION" \< "17" ] ; then
+echo "Cassandra 5.0 requires Java 11 or Java 17."
exit 1;
fi
@@ -117,10 +109,10 @@ esac
# Read user-defined JVM options from jvm-server.options file
JVM_OPTS_FILE=$CASSANDRA_CONF/jvm${jvmoptions_variant:--clients}.options
-if [ $JAVA_VERSION -ge 11 ] ; then
+if [ $JAVA_VERSION -ge 17 ] ; then
+
JVM_DEP_OPTS_FILE=$CASSANDRA_CONF/jvm17${jvmoptions_variant:--clients}.opt
[cassandra] branch trunk updated (9bacdc5bdb -> b966f6af11)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 9bacdc5bdb Merge branch 'cassandra-5.0' into trunk new 17d0eb138c Fix rpm installation on jdk17 new b966f6af11 Merge branch 'cassandra-5.0' into trunk The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt| 1 + redhat/cassandra.in.sh | 26 +- 2 files changed, 10 insertions(+), 17 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18817) RPM install does not work with jdk17
[ https://issues.apache.org/jira/browse/CASSANDRA-18817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18817: --- Fix Version/s: 5.0 5.0-alpha1 5.1 (was: 5.0-alpha) Since Version: 5.0-alpha1 Source Control Link: https://github.com/apache/cassandra/commit/17d0eb138c69a1c9c44256695252b2d2213a2633 Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed as [17d0eb138c69a1c9c44256695252b2d2213a2633|https://github.com/apache/cassandra/commit/17d0eb138c69a1c9c44256695252b2d2213a2633]. > RPM install does not work with jdk17 > > > Key: CASSANDRA-18817 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18817 > Project: Cassandra > Issue Type: Bug > Components: Packaging >Reporter: Michael Semb Wever >Priority: Normal > Fix For: 5.0, 5.0-alpha1, 5.1 > > > The cassandra.in.sh file was updated as part of CASSANDRA-18255 but the > corresponding redhat/cassandra.in.sh was not. > This means when cassandra starts on a rpm install using jdk17 the > jvm11-server.options file is still used. And so it fails. > Initial patch that works: > https://github.com/apache/cassandra/compare/cassandra-5.0...thelastpickle:cassandra:mck/redhat-jdk17-fix/5.0 > > Maybe it is possible to find a superior solution, like wrapping this file > instead of duplicating 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] 01/01: Merge branch 'cassandra-5.0' into trunk
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit b966f6af112331a4d01b6be2818e4e5b09245880 Merge: 9bacdc5bdb 17d0eb138c Author: Mick Semb Wever AuthorDate: Mon Sep 4 16:59:50 2023 +0200 Merge branch 'cassandra-5.0' into trunk * cassandra-5.0: Fix rpm installation on jdk17 CHANGES.txt| 1 + redhat/cassandra.in.sh | 26 +- 2 files changed, 10 insertions(+), 17 deletions(-) diff --cc CHANGES.txt index 18b8622715,1977bd1d2b..ade047d007 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,6 -1,11 +1,7 @@@ -5.0-alpha2 -Merged from 4.1: -Merged from 4.0: -Merged from 3.11: -Merged from 3.0: - -5.0-alpha1 +5.1 + * Clean up obsolete functions and simplify cql_version handling in cqlsh (CASSANDRA-18787) +Merged from 5.0: + * Fix rpm installations to work with jdk17 (CASSANDRA-18817) * Fix Depends and Build-Depends for Java for Debian packages (CASSANDRA-18809) * Update command line flags --add-exports and --add-opens for JDK17 (CASSANDRA-18439) * Update commons-lang3 to 3.13.0 (CASSANDRA-18789) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18817) RPM install does not work with jdk17
[ https://issues.apache.org/jira/browse/CASSANDRA-18817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18817: --- Status: Ready to Commit (was: Review In Progress) > RPM install does not work with jdk17 > > > Key: CASSANDRA-18817 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18817 > Project: Cassandra > Issue Type: Bug > Components: Packaging >Reporter: Michael Semb Wever >Priority: Normal > Fix For: 5.0-alpha > > > The cassandra.in.sh file was updated as part of CASSANDRA-18255 but the > corresponding redhat/cassandra.in.sh was not. > This means when cassandra starts on a rpm install using jdk17 the > jvm11-server.options file is still used. And so it fails. > Initial patch that works: > https://github.com/apache/cassandra/compare/cassandra-5.0...thelastpickle:cassandra:mck/redhat-jdk17-fix/5.0 > > Maybe it is possible to find a superior solution, like wrapping this file > instead of duplicating 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-18817) RPM install does not work with jdk17
[ https://issues.apache.org/jira/browse/CASSANDRA-18817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18817: --- Reviewers: Brandon Williams, Michael Semb Wever Status: Review In Progress (was: Patch Available) > RPM install does not work with jdk17 > > > Key: CASSANDRA-18817 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18817 > Project: Cassandra > Issue Type: Bug > Components: Packaging >Reporter: Michael Semb Wever >Priority: Normal > Fix For: 5.0-alpha > > > The cassandra.in.sh file was updated as part of CASSANDRA-18255 but the > corresponding redhat/cassandra.in.sh was not. > This means when cassandra starts on a rpm install using jdk17 the > jvm11-server.options file is still used. And so it fails. > Initial patch that works: > https://github.com/apache/cassandra/compare/cassandra-5.0...thelastpickle:cassandra:mck/redhat-jdk17-fix/5.0 > > Maybe it is possible to find a superior solution, like wrapping this file > instead of duplicating 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-18817) RPM install does not work with jdk17
[ https://issues.apache.org/jira/browse/CASSANDRA-18817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18817: --- Test and Documentation Plan: manual Status: Patch Available (was: Open) > RPM install does not work with jdk17 > > > Key: CASSANDRA-18817 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18817 > Project: Cassandra > Issue Type: Bug > Components: Packaging >Reporter: Michael Semb Wever >Priority: Normal > Fix For: 5.0-alpha > > > The cassandra.in.sh file was updated as part of CASSANDRA-18255 but the > corresponding redhat/cassandra.in.sh was not. > This means when cassandra starts on a rpm install using jdk17 the > jvm11-server.options file is still used. And so it fails. > Initial patch that works: > https://github.com/apache/cassandra/compare/cassandra-5.0...thelastpickle:cassandra:mck/redhat-jdk17-fix/5.0 > > Maybe it is possible to find a superior solution, like wrapping this file > instead of duplicating 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-18781) Add the ability to disable bulk load on server
[ https://issues.apache.org/jira/browse/CASSANDRA-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18781: -- Summary: Add the ability to disable bulk load on server (was: Add the ability to disable bulk load on server end and add metrics for bulk load used) > Add the ability to disable bulk load on server > -- > > Key: CASSANDRA-18781 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18781 > Project: Cassandra > Issue Type: Improvement > Components: Tool/bulk load >Reporter: Runtian Liu >Assignee: Runtian Liu >Priority: Normal > Fix For: 5.x > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently, Cassandra database users can use sstableloader to bulk load data > into Cassandra. However, for a Cassandra operator, there is no way to > forcibly block this behavior. Additionally, there is no metric indicating > whether the bulk load is being used on the server side. If a client is using > sstableloader, they will also need to upgrade the sstableloader code to the > new major version. This lack of control and visibility can become a blocker > during a major version upgrade. > > 1. Can we add a config to disable bulk load feature? Or it falls into > https://issues.apache.org/jira/browse/CASSANDRA-8303 > 2. Can we add metrics for bulk load used on server end? -- 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-18781) Add the ability to disable bulk loading of SSTables on a node
[ https://issues.apache.org/jira/browse/CASSANDRA-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18781: -- Summary: Add the ability to disable bulk loading of SSTables on a node (was: Add the ability to disable bulk load on server) > Add the ability to disable bulk loading of SSTables on a node > - > > Key: CASSANDRA-18781 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18781 > Project: Cassandra > Issue Type: Improvement > Components: Tool/bulk load >Reporter: Runtian Liu >Assignee: Runtian Liu >Priority: Normal > Fix For: 5.x > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently, Cassandra database users can use sstableloader to bulk load data > into Cassandra. However, for a Cassandra operator, there is no way to > forcibly block this behavior. Additionally, there is no metric indicating > whether the bulk load is being used on the server side. If a client is using > sstableloader, they will also need to upgrade the sstableloader code to the > new major version. This lack of control and visibility can become a blocker > during a major version upgrade. > > 1. Can we add a config to disable bulk load feature? Or it falls into > https://issues.apache.org/jira/browse/CASSANDRA-8303 > 2. Can we add metrics for bulk load used on server end? -- 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-18819) Re-organize ordering of configuration properties in cassandra.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-18819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18819: -- Description: I was setting up a cluster from scratch and I was configuring cassandra.yaml, obviously. What I do not like about the current content of cassandra.yaml is that some of its sections are seemingly scattered across that file and if feels like out of place / order. For example, if one wants to configure encryption it is on line 1458 and 1516 respectively. Snitch is on line 1402. The whole file has 2100 lines. So in order to configure a snitch, which is very common scenario when setting up a node, if I do not know that the field I am going to edit is called "endpoint_snitch" so I can just jump to it, I need to scroll to the three quarters of the file to edit it. I think that the most commonly edited sections of the configuration file should be on the very top or somewhere around it so as I am editing that file from scratch I just go section by section and I do not jump around, I just edit that or I skip it and I configure what is next - ordered by the probability that a section is going to be configured differently from a default. I also noticed that these properties are missing in cassandra.yaml, we can add it there upon refactorisation of this. memtable conf dynamic_snitch was: I was setting up a cluster from scratch and I was configuring cassandra.yaml, obviously. What I do not like about the current content of cassandra.yaml is that some of its sections are seemingly scattered across that file and if feels like out of place / order. For example, if one wants to configure encryption it is on line 1458 and 1516 respectively. Snitch is on line 1402. The whole file has 2100 lines. So in order to configure a snitch, which is very common scenario when setting up a node, if I do not know that the field I am going to edit is called "endpoint_snitch" so I can just jump to it, I need to scroll to the three quarters of the file to edit it. I think that the most commonly edited sections of the configuration file should be on the very top or somewhere around it so as I am editing that file from scratch I just go section by section and I do not jump around, I just edit that or I skip it and I configure what is next. I also noticed that these properties are missing in cassandra.yaml, we can add it there upon refactorisation of this. memtable conf dynamic_snitch > Re-organize ordering of configuration properties in cassandra.yaml > -- > > Key: CASSANDRA-18819 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18819 > Project: Cassandra > Issue Type: Task >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > > I was setting up a cluster from scratch and I was configuring cassandra.yaml, > obviously. What I do not like about the current content of cassandra.yaml is > that some of its sections are seemingly scattered across that file and if > feels like out of place / order. > For example, if one wants to configure encryption it is on line 1458 and 1516 > respectively. Snitch is on line 1402. The whole file has 2100 lines. So in > order to configure a snitch, which is very common scenario when setting up a > node, if I do not know that the field I am going to edit is called > "endpoint_snitch" so I can just jump to it, I need to scroll to the three > quarters of the file to edit it. > I think that the most commonly edited sections of the configuration file > should be on the very top or somewhere around it so as I am editing that file > from scratch I just go section by section and I do not jump around, I just > edit that or I skip it and I configure what is next - ordered by the > probability that a section is going to be configured differently from a > default. > I also noticed that these properties are missing in cassandra.yaml, we can > add it there upon refactorisation of this. > memtable conf > dynamic_snitch -- 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-18819) Re-organize ordering of configuration properties in cassandra.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-18819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18819: -- Fix Version/s: 5.x > Re-organize ordering of configuration properties in cassandra.yaml > -- > > Key: CASSANDRA-18819 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18819 > Project: Cassandra > Issue Type: Task >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > > I was setting up a cluster from scratch and I was configuring cassandra.yaml, > obviously. What I do not like about the current content of cassandra.yaml is > that some of its sections are seemingly scattered across that file and if > feels like out of place / order. > For example, if one wants to configure encryption it is on line 1458 and 1516 > respectively. Snitch is on line 1402. The whole file has 2100 lines. So in > order to configure a snitch, which is very common scenario when setting up a > node, if I do not know that the field I am going to edit is called > "endpoint_snitch" so I can just jump to it, I need to scroll to the three > quarters of the file to edit it. > I think that the most commonly edited sections of the configuration file > should be on the very top or somewhere around it so as I am editing that file > from scratch I just go section by section and I do not jump around, I just > edit that or I skip it and I configure what is next. > I also noticed that these properties are missing in cassandra.yaml, we can > add it there upon refactorisation of this. > memtable conf > dynamic_snitch -- 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-18819) Re-organize ordering of configuration properties in cassandra.yaml
Stefan Miklosovic created CASSANDRA-18819: - Summary: Re-organize ordering of configuration properties in cassandra.yaml Key: CASSANDRA-18819 URL: https://issues.apache.org/jira/browse/CASSANDRA-18819 Project: Cassandra Issue Type: Task Reporter: Stefan Miklosovic Assignee: Stefan Miklosovic I was setting up a cluster from scratch and I was configuring cassandra.yaml, obviously. What I do not like about the current content of cassandra.yaml is that some of its sections are seemingly scattered across that file and if feels like out of place / order. For example, if one wants to configure encryption it is on line 1458 and 1516 respectively. Snitch is on line 1402. The whole file has 2100 lines. So in order to configure a snitch, which is very common scenario when setting up a node, if I do not know that the field I am going to edit is called "endpoint_snitch" so I can just jump to it, I need to scroll to the three quarters of the file to edit it. I think that the most commonly edited sections of the configuration file should be on the very top or somewhere around it so as I am editing that file from scratch I just go section by section and I do not jump around, I just edit that or I skip it and I configure what is next. I also noticed that these properties are missing in cassandra.yaml, we can add it there upon refactorisation of this. memtable conf dynamic_snitch -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18360) Test Failure: o.a.c.cql3.validation.operations.AlterTest#testDropListAndAddListWithSameName
[
https://issues.apache.org/jira/browse/CASSANDRA-18360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi reassigned CASSANDRA-18360:
---
Assignee: Berenguer Blasi
> Test Failure:
> o.a.c.cql3.validation.operations.AlterTest#testDropListAndAddListWithSameName
> ---
>
> Key: CASSANDRA-18360
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18360
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.x
>
>
> The unit test
> {{org.apache.cassandra.cql3.validation.operations.AlterTest#testDropListAndAddListWithSameName}}
> is flaky at least on trunk. Flakiness seems lesser than 1%.
> While I haven't seen it on Jenkins yet, it can easily be reproduced on
> CircleCI with the multiplexer:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2731/workflows/58edc2f6-9a21-4d09-b783-b7fb15e1b320/jobs/32235
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2731/workflows/58edc2f6-9a21-4d09-b783-b7fb15e1b320/jobs/32234
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2731/workflows/739a95d3-8e42-4447-93dd-122fc16fdd7d/jobs/32233/tests
> Those runs show two types of errors:
> {code}
> junit.framework.AssertionFailedError: Invalid value for row 0 column 1
> (content of type text), expected but got
> at org.apache.cassandra.cql3.CQLTester.assertRows(CQLTester.java:1506)
> at
> org.apache.cassandra.cql3.validation.operations.AlterTest.testDropListAndAddListWithSameName(AlterTest.java:102)
> {code}
> and:
> {code}
> org.apache.cassandra.serializers.MarshalException: Invalid UTF-8 bytes
> 00e0279515437f00
> at
> org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:46)
> at
> org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:29)
> at
> org.apache.cassandra.serializers.TypeSerializer.deserialize(TypeSerializer.java:37)
> at org.apache.cassandra.cql3.CQLTester.assertRows(CQLTester.java:1494)
> at
> org.apache.cassandra.cql3.validation.operations.AlterTest.testDropListAndAddListWithSameName(AlterTest.java:102)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_UTESTS_COUNT=500 \
> -e REPEATED_UTESTS=org.apache.cassandra.cql3.validation.operations.AlterTest
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18817) RPM install does not work with jdk17
[ https://issues.apache.org/jira/browse/CASSANDRA-18817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761849#comment-17761849 ] Claude Warren commented on CASSANDRA-18817: --- My change is for CASSANDRA-17773 where I propose extracting the common "boilerplate" code to simplify writing files that start/stop Cassandra and its stand-alone tools. I don't think that it would impact this issue in any way. The changes just centralize the code to discover where the cassandra.in.sh file is, it does not change the contents of the file. > RPM install does not work with jdk17 > > > Key: CASSANDRA-18817 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18817 > Project: Cassandra > Issue Type: Bug > Components: Packaging >Reporter: Michael Semb Wever >Priority: Normal > Fix For: 5.0-alpha > > > The cassandra.in.sh file was updated as part of CASSANDRA-18255 but the > corresponding redhat/cassandra.in.sh was not. > This means when cassandra starts on a rpm install using jdk17 the > jvm11-server.options file is still used. And so it fails. > Initial patch that works: > https://github.com/apache/cassandra/compare/cassandra-5.0...thelastpickle:cassandra:mck/redhat-jdk17-fix/5.0 > > Maybe it is possible to find a superior solution, like wrapping this file > instead of duplicating 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] tag 5.0-alpha1-tentative deleted (was b4d99c1a07)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to tag 5.0-alpha1-tentative in repository https://gitbox.apache.org/repos/asf/cassandra.git *** WARNING: tag 5.0-alpha1-tentative was deleted! *** was b4d99c1a07 Prepare debian changelog for 5.0-alpha1 The revisions that were on this tag are still contained in other references; therefore, this change does not discard any commits from the repository. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r63778 - /dev/cassandra/5.0-alpha1/
Author: mck Date: Mon Sep 4 14:27:41 2023 New Revision: 63778 Log: Cassandra 5.0-alpha1 – delete failed cut attempt Removed: dev/cassandra/5.0-alpha1/ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18322) Warn about unqualified prepared statement only if it is a select, update, delete, insert
[
https://issues.apache.org/jira/browse/CASSANDRA-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761819#comment-17761819
]
Stefan Miklosovic edited comment on CASSANDRA-18322 at 9/4/23 1:44 PM:
---
Ah as I dug deeper I see what is the problem ... No need to create another
ticket.
I prepared a patch for trunk here (1).
It applies cleanly back to 4.0.
(1) https://github.com/apache/cassandra/pull/2668
(2) 3.11 PR https://github.com/apache/cassandra/pull/2669
(3) 3.0 PR https://github.com/apache/cassandra/pull/2670/files
I ll do builds when it is reviewed ... it is going to 6 branches so I do not
want to build that prematurely.
was (Author: smiklosovic):
Ah as I dug deeper I see what is the problem ... No need to create another
ticket.
I prepared a patch for trunk here (1).
It applies cleanly back to 4.0.
(1) https://github.com/apache/cassandra/pull/2668
(2) 3.11 PR https://github.com/apache/cassandra/pull/2669
(3) 3.0 PR https://github.com/apache/cassandra/pull/2670/files
I ll do builds when it is review ... it is going to 6 branches so I do not want
to build that prematurely.
> Warn about unqualified prepared statement only if it is a select, update,
> delete, insert
>
>
> Key: CASSANDRA-18322
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18322
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
>Reporter: Mohammad Aburadeh
>Assignee: Stefan Miklosovic
>Priority: Urgent
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> Hi,
> We get the following warnings when we use prepared statements with "create
> keyspace ... " or "drop keyspace" statements.
> "
> {{USE }} with prepared statements is considered to be an
> anti-pattern due to ambiguity in non-qualified table names. Please consider
> removing instances of {{{}Session#setKeyspace(){}}},
> {{Session#execute("USE ")}} and {{cluster.newSession()}}
> from your code, and always use fully qualified table names (e.g.
> .). Keyspace used: null, statement keyspace: null, statement
> id: 8153d922390fdf9a9963bfeda85b2f3b at
> "
> Such statements are already full-qualified. So, why are we getting this
> warning?
> Regards
> Mohammad
--
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-18322) Warn about unqualified prepared statement only if it is a select, update, delete, insert
[
https://issues.apache.org/jira/browse/CASSANDRA-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761819#comment-17761819
]
Stefan Miklosovic edited comment on CASSANDRA-18322 at 9/4/23 1:34 PM:
---
Ah as I dug deeper I see what is the problem ... No need to create another
ticket.
I prepared a patch for trunk here (1).
It applies cleanly back to 4.0.
(1) https://github.com/apache/cassandra/pull/2668
(2) 3.11 PR https://github.com/apache/cassandra/pull/2669
(3) 3.0 PR https://github.com/apache/cassandra/pull/2670/files
I ll do builds when it is review ... it is going to 6 branches so I do not want
to build that prematurely.
was (Author: smiklosovic):
Ah as I dug deeper I see what is the problem ... No need to create another
ticket.
I prepared a patch for trunk here (1).
It applies cleanly back to 4.0.
(1) https://github.com/apache/cassandra/pull/2668
(2) 3.11 PR https://github.com/apache/cassandra/pull/2669
(3) 3.0 PR https://github.com/apache/cassandra/pull/2670/files
> Warn about unqualified prepared statement only if it is a select, update,
> delete, insert
>
>
> Key: CASSANDRA-18322
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18322
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
>Reporter: Mohammad Aburadeh
>Assignee: Stefan Miklosovic
>Priority: Urgent
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> Hi,
> We get the following warnings when we use prepared statements with "create
> keyspace ... " or "drop keyspace" statements.
> "
> {{USE }} with prepared statements is considered to be an
> anti-pattern due to ambiguity in non-qualified table names. Please consider
> removing instances of {{{}Session#setKeyspace(){}}},
> {{Session#execute("USE ")}} and {{cluster.newSession()}}
> from your code, and always use fully qualified table names (e.g.
> .). Keyspace used: null, statement keyspace: null, statement
> id: 8153d922390fdf9a9963bfeda85b2f3b at
> "
> Such statements are already full-qualified. So, why are we getting this
> warning?
> Regards
> Mohammad
--
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-18322) Warn about unqualified prepared statement only if it is a select, update, delete, insert
[
https://issues.apache.org/jira/browse/CASSANDRA-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-18322:
--
Summary: Warn about unqualified prepared statement only if it is a select,
update, delete, insert (was: Warnings when using prepared statement with
"drop/create keyspace .." ( after 15252))
> Warn about unqualified prepared statement only if it is a select, update,
> delete, insert
>
>
> Key: CASSANDRA-18322
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18322
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
>Reporter: Mohammad Aburadeh
>Assignee: Stefan Miklosovic
>Priority: Urgent
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> Hi,
> We get the following warnings when we use prepared statements with "create
> keyspace ... " or "drop keyspace" statements.
> "
> {{USE }} with prepared statements is considered to be an
> anti-pattern due to ambiguity in non-qualified table names. Please consider
> removing instances of {{{}Session#setKeyspace(){}}},
> {{Session#execute("USE ")}} and {{cluster.newSession()}}
> from your code, and always use fully qualified table names (e.g.
> .). Keyspace used: null, statement keyspace: null, statement
> id: 8153d922390fdf9a9963bfeda85b2f3b at
> "
> Such statements are already full-qualified. So, why are we getting this
> warning?
> Regards
> Mohammad
--
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-18322) Warn about unqualified prepared statement only if it is a select, update, delete, insert
[
https://issues.apache.org/jira/browse/CASSANDRA-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-18322:
--
Test and Documentation Plan: CI and manual cassandra-stress execution
Status: Patch Available (was: Open)
> Warn about unqualified prepared statement only if it is a select, update,
> delete, insert
>
>
> Key: CASSANDRA-18322
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18322
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
>Reporter: Mohammad Aburadeh
>Assignee: Stefan Miklosovic
>Priority: Urgent
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> Hi,
> We get the following warnings when we use prepared statements with "create
> keyspace ... " or "drop keyspace" statements.
> "
> {{USE }} with prepared statements is considered to be an
> anti-pattern due to ambiguity in non-qualified table names. Please consider
> removing instances of {{{}Session#setKeyspace(){}}},
> {{Session#execute("USE ")}} and {{cluster.newSession()}}
> from your code, and always use fully qualified table names (e.g.
> .). Keyspace used: null, statement keyspace: null, statement
> id: 8153d922390fdf9a9963bfeda85b2f3b at
> "
> Such statements are already full-qualified. So, why are we getting this
> warning?
> Regards
> Mohammad
--
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-18322) Warn about unqualified prepared statement only if it is a select, update, delete, insert
[
https://issues.apache.org/jira/browse/CASSANDRA-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-18322:
--
Status: Needs Committer (was: Patch Available)
> Warn about unqualified prepared statement only if it is a select, update,
> delete, insert
>
>
> Key: CASSANDRA-18322
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18322
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
>Reporter: Mohammad Aburadeh
>Assignee: Stefan Miklosovic
>Priority: Urgent
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> Hi,
> We get the following warnings when we use prepared statements with "create
> keyspace ... " or "drop keyspace" statements.
> "
> {{USE }} with prepared statements is considered to be an
> anti-pattern due to ambiguity in non-qualified table names. Please consider
> removing instances of {{{}Session#setKeyspace(){}}},
> {{Session#execute("USE ")}} and {{cluster.newSession()}}
> from your code, and always use fully qualified table names (e.g.
> .). Keyspace used: null, statement keyspace: null, statement
> id: 8153d922390fdf9a9963bfeda85b2f3b at
> "
> Such statements are already full-qualified. So, why are we getting this
> warning?
> Regards
> Mohammad
--
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-18322) Warnings when using prepared statement with "drop/create keyspace .." ( after 15252)
[
https://issues.apache.org/jira/browse/CASSANDRA-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-18322:
--
Bug Category: Parent values: Code(13163) (was: Parent values:
Correctness(12982)Level 1 values: Recoverable Corruption / Loss(12986))
Complexity: Normal
Discovered By: Adhoc Test
Fix Version/s: 3.0.x
3.11.x
4.0.x
4.1.x
5.x
Severity: Normal (was: Critical)
Assignee: Stefan Miklosovic
Status: Open (was: Triage Needed)
> Warnings when using prepared statement with "drop/create keyspace .." ( after
> 15252)
>
>
> Key: CASSANDRA-18322
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18322
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
>Reporter: Mohammad Aburadeh
>Assignee: Stefan Miklosovic
>Priority: Urgent
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> Hi,
> We get the following warnings when we use prepared statements with "create
> keyspace ... " or "drop keyspace" statements.
> "
> {{USE }} with prepared statements is considered to be an
> anti-pattern due to ambiguity in non-qualified table names. Please consider
> removing instances of {{{}Session#setKeyspace(){}}},
> {{Session#execute("USE ")}} and {{cluster.newSession()}}
> from your code, and always use fully qualified table names (e.g.
> .). Keyspace used: null, statement keyspace: null, statement
> id: 8153d922390fdf9a9963bfeda85b2f3b at
> "
> Such statements are already full-qualified. So, why are we getting this
> warning?
> Regards
> Mohammad
--
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-18322) Warnings when using prepared statement with "drop/create keyspace .." ( after 15252)
[
https://issues.apache.org/jira/browse/CASSANDRA-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761819#comment-17761819
]
Stefan Miklosovic edited comment on CASSANDRA-18322 at 9/4/23 1:32 PM:
---
Ah as I dug deeper I see what is the problem ... No need to create another
ticket.
I prepared a patch for trunk here (1).
It applies cleanly back to 4.0.
(1) https://github.com/apache/cassandra/pull/2668
(2) 3.11 PR https://github.com/apache/cassandra/pull/2669
(3) 3.0 PR https://github.com/apache/cassandra/pull/2670/files
was (Author: smiklosovic):
Ah as I dug deeper I see what is the problem ... No need to create another
ticket.
I prepared a patch for trunk here (1).
It applies cleanly back to 4.0.
(1) https://github.com/apache/cassandra/pull/2668
> Warnings when using prepared statement with "drop/create keyspace .." ( after
> 15252)
>
>
> Key: CASSANDRA-18322
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18322
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
>Reporter: Mohammad Aburadeh
>Priority: Urgent
>
> Hi,
> We get the following warnings when we use prepared statements with "create
> keyspace ... " or "drop keyspace" statements.
> "
> {{USE }} with prepared statements is considered to be an
> anti-pattern due to ambiguity in non-qualified table names. Please consider
> removing instances of {{{}Session#setKeyspace(){}}},
> {{Session#execute("USE ")}} and {{cluster.newSession()}}
> from your code, and always use fully qualified table names (e.g.
> .). Keyspace used: null, statement keyspace: null, statement
> id: 8153d922390fdf9a9963bfeda85b2f3b at
> "
> Such statements are already full-qualified. So, why are we getting this
> warning?
> Regards
> Mohammad
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18715) Add support for vector search in SAi
[ https://issues.apache.org/jira/browse/CASSANDRA-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Adamson reassigned CASSANDRA-18715: Assignee: Mike Adamson > 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 > -- 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-18715) Add support for vector search in SAi
[
https://issues.apache.org/jira/browse/CASSANDRA-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Adamson updated CASSANDRA-18715:
-
Description: (was: Approximate nearest neighbour search results are
scored. As such, it is important that the results are returned in score order.
In order to do this proposal is that the ANN search is expressed in the grammar
as:
{code:java}
ORDER BY ANN OF {code}
rather than including the ANN search in the where clause.)
> 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
>Priority: Normal
>
--
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-18715) Add support for vector search in SAi
[ https://issues.apache.org/jira/browse/CASSANDRA-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Adamson updated CASSANDRA-18715: - Change Category: Operability Complexity: Challenging Status: Open (was: Triage Needed) > 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 > -- 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-18322) Warnings when using prepared statement with "drop/create keyspace .." ( after 15252)
[
https://issues.apache.org/jira/browse/CASSANDRA-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761819#comment-17761819
]
Stefan Miklosovic edited comment on CASSANDRA-18322 at 9/4/23 12:53 PM:
Ah as I dug deeper I see what is the problem ... No need to create another
ticket.
I prepared a patch for trunk here (1).
It applies cleanly back to 4.0.
(1) https://github.com/apache/cassandra/pull/2668
was (Author: smiklosovic):
Ah as I dug deeper I see what is the problem ... No need to create another
ticket.
I prepared a patch for trunk here (1).
(1) https://github.com/apache/cassandra/pull/2668
> Warnings when using prepared statement with "drop/create keyspace .." ( after
> 15252)
>
>
> Key: CASSANDRA-18322
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18322
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
>Reporter: Mohammad Aburadeh
>Priority: Urgent
>
> Hi,
> We get the following warnings when we use prepared statements with "create
> keyspace ... " or "drop keyspace" statements.
> "
> {{USE }} with prepared statements is considered to be an
> anti-pattern due to ambiguity in non-qualified table names. Please consider
> removing instances of {{{}Session#setKeyspace(){}}},
> {{Session#execute("USE ")}} and {{cluster.newSession()}}
> from your code, and always use fully qualified table names (e.g.
> .). Keyspace used: null, statement keyspace: null, statement
> id: 8153d922390fdf9a9963bfeda85b2f3b at
> "
> Such statements are already full-qualified. So, why are we getting this
> warning?
> Regards
> Mohammad
--
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-18715) Add support for vector search in SAi
[
https://issues.apache.org/jira/browse/CASSANDRA-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Adamson updated CASSANDRA-18715:
-
Summary: Add support for vector search in SAi (was: Add support for ORDER
BY ANN OF )
> 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
>Priority: Normal
>
> Approximate nearest neighbour search results are scored. As such, it is
> important that the results are returned in score order. In order to do this
> proposal is that the ANN search is expressed in the grammar as:
> {code:java}
> ORDER BY ANN OF {code}
> rather than including the ANN search in the where clause.
--
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-18716) In-Memory write support for a vector search index
[ https://issues.apache.org/jira/browse/CASSANDRA-18716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Adamson updated CASSANDRA-18716: - Resolution: Duplicate Status: Resolved (was: Open) > In-Memory write support for a vector search index > - > > Key: CASSANDRA-18716 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18716 > Project: Cassandra > Issue Type: Improvement > Components: Feature/Vector Search >Reporter: Mike Adamson >Assignee: Mike Adamson >Priority: Normal > > This ticket will introduce the write side in-memory components of the vector > index. -- 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-18322) Warnings when using prepared statement with "drop/create keyspace .." ( after 15252)
[
https://issues.apache.org/jira/browse/CASSANDRA-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761819#comment-17761819
]
Stefan Miklosovic commented on CASSANDRA-18322:
---
Ah as I dug deeper I see what is the problem ... No need to create another
ticket.
I prepared a patch for trunk here (1).
(1) https://github.com/apache/cassandra/pull/2668
> Warnings when using prepared statement with "drop/create keyspace .." ( after
> 15252)
>
>
> Key: CASSANDRA-18322
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18322
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
>Reporter: Mohammad Aburadeh
>Priority: Urgent
>
> Hi,
> We get the following warnings when we use prepared statements with "create
> keyspace ... " or "drop keyspace" statements.
> "
> {{USE }} with prepared statements is considered to be an
> anti-pattern due to ambiguity in non-qualified table names. Please consider
> removing instances of {{{}Session#setKeyspace(){}}},
> {{Session#execute("USE ")}} and {{cluster.newSession()}}
> from your code, and always use fully qualified table names (e.g.
> .). Keyspace used: null, statement keyspace: null, statement
> id: 8153d922390fdf9a9963bfeda85b2f3b at
> "
> Such statements are already full-qualified. So, why are we getting this
> warning?
> Regards
> Mohammad
--
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-18707) Test failure: junit.framework.TestSuite.org.apache.cassandra.distributed.test.CASMultiDCTest-.jdk11
[
https://issues.apache.org/jira/browse/CASSANDRA-18707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761803#comment-17761803
]
Andres de la Peña commented on CASSANDRA-18707:
---
I've tried to reproduce it on the multiplexer:
{code}
.circleci/generate.sh -p \
-e REPEATED_JVM_DTESTS=org.apache.cassandra.distributed.test.CASMultiDCTest \
-e REPEATED_JVM_DTESTS_COUNT=100
{code}
https://app.circleci.com/pipelines/github/adelapena/cassandra/3198/workflows/0ee48e01-1c84-44cd-a783-6ec6b487b029
It doesn't hit that failure with 100 runs, but it finds a different failure in
{{testLocalSerialLocalCommit}}:
{code}
junit.framework.AssertionFailedError: numWritten: 2 < 3
at
org.apache.cassandra.distributed.test.CASMultiDCTest.testLocalSerialCommit(CASMultiDCTest.java:111)
at
org.apache.cassandra.distributed.test.CASMultiDCTest.testLocalSerialLocalCommit(CASMultiDCTest.java:121)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
{code}
> Test failure:
> junit.framework.TestSuite.org.apache.cassandra.distributed.test.CASMultiDCTest-.jdk11
>
>
>
> Key: CASSANDRA-18707
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18707
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x
>
>
> Seen here:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit.framework/TestSuite/org_apache_cassandra_distributed_test_CASMultiDCTest__jdk11/]
> h3.
> {code:java}
> Error Message
> Schema agreement not reached. Schema versions of the instances:
> [ef1c8e05-a06d-388d-a46d-53cc22a94762, 6c386108-1805-3985-b48e-8016012a0207,
> 6c386108-1805-3985-b48e-8016012a0207, ef1c8e05-a06d-388d-a46d-53cc22a94762]
> Stacktrace
> java.lang.IllegalStateException: Schema agreement not reached. Schema
> versions of the instances: [ef1c8e05-a06d-388d-a46d-53cc22a94762,
> 6c386108-1805-3985-b48e-8016012a0207, 6c386108-1805-3985-b48e-8016012a0207,
> ef1c8e05-a06d-388d-a46d-53cc22a94762] at
> org.apache.cassandra.distributed.impl.AbstractCluster$ChangeMonitor.waitForCompletion(AbstractCluster.java:907)
> at
> org.apache.cassandra.distributed.impl.AbstractCluster.lambda$schemaChange$8(AbstractCluster.java:836)
> at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96) at
> org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61) at
> org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71) at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18564) Test Failure: MixedModeAvailabilityV30AllOneTest.testAvailabilityCoordinatorUpgraded
[
https://issues.apache.org/jira/browse/CASSANDRA-18564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-18564:
Status: Ready to Commit (was: Review In Progress)
> Test Failure:
> MixedModeAvailabilityV30AllOneTest.testAvailabilityCoordinatorUpgraded
>
>
> Key: CASSANDRA-18564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18564
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The JVM upgrade dtest
> {{MixedModeAvailabilityV3XAllOneTest.testAvailabilityCoordinatorUpgraded}}
> seems to be flaky at least in {{trunk}}:
> {code}
> junit.framework.AssertionFailedError: Error in test '4.0.11 -> [5.0]' while
> upgrading to '5.0'; successful upgrades []
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:348)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:154)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailabilityCoordinatorUpgraded(MixedModeAvailabilityTestBase.java:74)
> Caused by: java.lang.AssertionError: Unexpected error while reading in case
> write-read consistency ALL-ONE with upgraded coordinator and 2 nodes down:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 0 responses.
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.lambda$testAvailability$6(MixedModeAvailabilityTestBase.java:145)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:339)
> Caused by: org.apache.cassandra.exceptions.ReadTimeoutException: Operation
> timed out - received only 0 responses.
> at
> org.apache.cassandra.service.reads.ReadCallback.awaitResults(ReadCallback.java:162)
> at
> org.apache.cassandra.service.reads.AbstractReadExecutor.awaitResponses(AbstractReadExecutor.java:387)
> at
> org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:2124)
> at
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1995)
> at
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1873)
> at
> org.apache.cassandra.db.SinglePartitionReadCommand$Group.execute(SinglePartitionReadCommand.java:1286)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:364)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:293)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:105)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:750)
> {code}
> This has failed 143 times in 500 iterations of this CircleCI run:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2927/workflows/fcd1cd60-826b-484a-8e81-d3ba640f7de9/jobs/47659/tests
> The failure has also recently appeared on Jenkins too:
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1585/testReport/org.apache.cassandra.distributed.upgrade/MixedModeAvailabilityV3XAllOneTest/testAvailabilityCoordinatorUpgraded__jdk11/
> Given that the failure has just appeared on Jenkins and it fails relatively
> easily on CircleCI, it's likely that it has been broken by a very recent
> change.
--
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-18564) Test Failure: MixedModeAvailabilityV30AllOneTest.testAvailabilityCoordinatorUpgraded
[
https://issues.apache.org/jira/browse/CASSANDRA-18564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761783#comment-17761783
]
Andres de la Peña commented on CASSANDRA-18564:
---
Thanks for looking into this. {{trunk}} takes longer because it needs to test
an additional upgrade path, {{5.0-alpha1 -> 5.1}}.
> Test Failure:
> MixedModeAvailabilityV30AllOneTest.testAvailabilityCoordinatorUpgraded
>
>
> Key: CASSANDRA-18564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18564
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The JVM upgrade dtest
> {{MixedModeAvailabilityV3XAllOneTest.testAvailabilityCoordinatorUpgraded}}
> seems to be flaky at least in {{trunk}}:
> {code}
> junit.framework.AssertionFailedError: Error in test '4.0.11 -> [5.0]' while
> upgrading to '5.0'; successful upgrades []
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:348)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:154)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailabilityCoordinatorUpgraded(MixedModeAvailabilityTestBase.java:74)
> Caused by: java.lang.AssertionError: Unexpected error while reading in case
> write-read consistency ALL-ONE with upgraded coordinator and 2 nodes down:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 0 responses.
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.lambda$testAvailability$6(MixedModeAvailabilityTestBase.java:145)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:339)
> Caused by: org.apache.cassandra.exceptions.ReadTimeoutException: Operation
> timed out - received only 0 responses.
> at
> org.apache.cassandra.service.reads.ReadCallback.awaitResults(ReadCallback.java:162)
> at
> org.apache.cassandra.service.reads.AbstractReadExecutor.awaitResponses(AbstractReadExecutor.java:387)
> at
> org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:2124)
> at
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1995)
> at
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1873)
> at
> org.apache.cassandra.db.SinglePartitionReadCommand$Group.execute(SinglePartitionReadCommand.java:1286)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:364)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:293)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:105)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:750)
> {code}
> This has failed 143 times in 500 iterations of this CircleCI run:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2927/workflows/fcd1cd60-826b-484a-8e81-d3ba640f7de9/jobs/47659/tests
> The failure has also recently appeared on Jenkins too:
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1585/testReport/org.apache.cassandra.distributed.upgrade/MixedModeAvailabilityV3XAllOneTest/testAvailabilityCoordinatorUpgraded__jdk11/
> Given that the failure has just appeared on Jenkins and it fails relatively
> easily on CircleCI, it's likely that it has been broken by a very recent
> change.
--
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-18322) Warnings when using prepared statement with "drop/create keyspace .." ( after 15252)
[
https://issues.apache.org/jira/browse/CASSANDRA-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761773#comment-17761773
]
Stefan Miklosovic commented on CASSANDRA-18322:
---
This is still happening in trunk in cassandra-stress for the very first time.
Then prepare statement is cached and it is not happening. I think we should fix
this in cassandra-stress. I will create a new ticket for it.
> Warnings when using prepared statement with "drop/create keyspace .." ( after
> 15252)
>
>
> Key: CASSANDRA-18322
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18322
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
>Reporter: Mohammad Aburadeh
>Priority: Urgent
>
> Hi,
> We get the following warnings when we use prepared statements with "create
> keyspace ... " or "drop keyspace" statements.
> "
> {{USE }} with prepared statements is considered to be an
> anti-pattern due to ambiguity in non-qualified table names. Please consider
> removing instances of {{{}Session#setKeyspace(){}}},
> {{Session#execute("USE ")}} and {{cluster.newSession()}}
> from your code, and always use fully qualified table names (e.g.
> .). Keyspace used: null, statement keyspace: null, statement
> id: 8153d922390fdf9a9963bfeda85b2f3b at
> "
> Such statements are already full-qualified. So, why are we getting this
> warning?
> Regards
> Mohammad
--
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-10804) C* keeps compacting a keyspace when no longer exists
[
https://issues.apache.org/jira/browse/CASSANDRA-10804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761772#comment-17761772
]
Stefan Miklosovic commented on CASSANDRA-10804:
---
I think I saw this happening in the current trunk / 5.0. But I can not
reproduce it. It seems like it is flaky behavior.
> C* keeps compacting a keyspace when no longer exists
>
>
> Key: CASSANDRA-10804
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10804
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
> Environment: Cassandra 2.2.3, Linux, Java 1.8.0U65, dedicated data
> disk
>Reporter: Francisco Madrid
>Priority: Low
> Fix For: 2.2.x, 3.0.x, 3.11.x
>
>
> Testing a 4 node cassandra cluster, I ran the C* stress tool but it failed
> with:
> {code}
> java.util.NoSuchElementException
>at org.apache.cassandra.stress.Operation.error(Operation.java:216)
>at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:188)
>at
> org.apache.cassandra.stress.operations.userdefined.SchemaQuery.run(SchemaQuery.java:156)
>at
> org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:309)
> java.io.IOException: Operation x10 on key(s) [ E>I#;+: Error executing:
> (NoSuchElementException)
> {code}
> I noticed that a compaction was running quite a time afterwards and it didn't
> seem to go on and stayed at 0%:
> {code}
> # ./bin/nodetool compactionstats
> pending tasks: 1
> id compaction type keyspace table
> completedtotalunit progress
>6bf4dbc0-990a-11e5-a703-cd0c425c8a88Compaction test test1
> 0 1873185798 bytes 0,00%
> Active compaction remaining time : 0h01m51s
> {code}
> I dropped the keyspace, but although the keyspace no longer existed the
> compaction continued:
> {code}
> # ./bin/cqlsh
> [cqlsh 5.0.1 | Cassandra 2.2.3 | CQL spec 3.3.1 | Native protocol v4]
> cqlsh> DROP KEYSPACE test;
> /opt/dsc-cassandra-2.2.3/bin/../lib/cassandra-driver-internal-only-2.7.2.zip/cassandra-driver-2.7.2/cassandra/cluster.py:3331:
> DeprecationWarning: ResponseFuture.result timeout argument is deprecated.
> Specify the request timeout via Session.execute[_async].
> cqlsh> DESC KEYSPACES;
> system_traces system_auth system system_distributed
> cqlsh> exit
> {code}
> {code}
> # ./bin/nodetool compactionstats
> pending tasks: 1
> id compaction type keyspace table
> completedtotalunit progress
>6bf4dbc0-990a-11e5-a703-cd0c425c8a88Compaction test test1
> 0 1873185798 bytes 0,00%
> Active compaction remaining time : 0h01m51s
> {code}
> I checked the data disk and there are no files in the keyspace directory.
--
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-18818) Add cqlshrc.sample and credentials.sample into Debian package
[ https://issues.apache.org/jira/browse/CASSANDRA-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18818: -- Status: Needs Committer (was: Patch Available) > Add cqlshrc.sample and credentials.sample into Debian package > - > > Key: CASSANDRA-18818 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18818 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x > > > RPM package contains these two files buy DEB does not. Debian users suffer > from not having these files available so they need to craft them completely > from scratch. -- 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-18818) Add cqlshrc.sample and credentials.sample into Debian package
[ https://issues.apache.org/jira/browse/CASSANDRA-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18818: -- Test and Documentation Plan: deb package installation Status: Patch Available (was: In Progress) [3.0 PR|https://github.com/apache/cassandra/pull/2662] [3.11 PR|https://github.com/apache/cassandra/pull/2663] [4.0 PR|https://github.com/apache/cassandra/pull/2664] [4.1 PR|https://github.com/apache/cassandra/pull/2665] [5.0 PR|https://github.com/apache/cassandra/pull/2666] [trunk PR|https://github.com/apache/cassandra/pull/2667] > Add cqlshrc.sample and credentials.sample into Debian package > - > > Key: CASSANDRA-18818 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18818 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x > > > RPM package contains these two files buy DEB does not. Debian users suffer > from not having these files available so they need to craft them completely > from scratch. -- 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-18818) Add cqlshrc.sample and credentials.sample into Debian package
[ https://issues.apache.org/jira/browse/CASSANDRA-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18818: -- Description: RPM package contains these two files buy DEB does not. Debian users suffer from not having these files available so they need to craft them completely from scratch. (was: RPM package contains these two files buy DEB does not. Debian users suffers from not having these files available so they need to craft them completely from scratch. ) > Add cqlshrc.sample and credentials.sample into Debian package > - > > Key: CASSANDRA-18818 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18818 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x > > > RPM package contains these two files buy DEB does not. Debian users suffer > from not having these files available so they need to craft them completely > from scratch. -- 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-18818) Add cqlshrc.sample and credentials.sample into Debian package
[ https://issues.apache.org/jira/browse/CASSANDRA-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18818: -- Change Category: Operability Complexity: Low Hanging Fruit Fix Version/s: 3.0.x 3.11.x 4.0.x 4.1.x 5.x Status: Open (was: Triage Needed) credentials.sample was added in CASSANDRA-16983 which was released in 4.1 for the first time so it is missing in a Debian package since then. cqlshrc.sample was there from times of 3.0 (maybe even sooner). > Add cqlshrc.sample and credentials.sample into Debian package > - > > Key: CASSANDRA-18818 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18818 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x > > > RPM package contains these two files buy DEB does not. Debian users suffers > from not having these files available so they need to craft them completely > from scratch. -- 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-18818) Add cqlshrc.sample and credentials.sample into Debian package
Stefan Miklosovic created CASSANDRA-18818: - Summary: Add cqlshrc.sample and credentials.sample into Debian package Key: CASSANDRA-18818 URL: https://issues.apache.org/jira/browse/CASSANDRA-18818 Project: Cassandra Issue Type: Task Components: Packaging Reporter: Stefan Miklosovic Assignee: Stefan Miklosovic RPM package contains these two files buy DEB does not. Debian users suffers from not having these files available so they need to craft them completely from scratch. -- 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-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[ https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18366: -- Fix Version/s: 4.0.12 (was: 4.0.x) Since Version: 4.0.8 Source Control Link: https://github.com/apache/cassandra/commit/0b7310c010b84e5eefeb42057725d1da05a4e9cd Resolution: Fixed Status: Resolved (was: Ready to Commit) [~djatnieks] thank you for looking into this > Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - > testFailingMessage[VALIDATION_REQ/parallel/true] > > > Key: CASSANDRA-18366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18366 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Brandon Williams >Assignee: dan jatnieks >Priority: Normal > Fix For: 4.0.12 > > > First seen > [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206] > this test times out for me consistently on both j8 and j11 where 4.1 and > trunk do not. -- 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.0 updated (aa2494b30b -> 0b7310c010)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from aa2494b30b Merge branch 'cassandra-3.11' into cassandra-4.0 add 0b7310c010 Fix FailingRepairTest by making sure Gossip is started before each test No new revisions were added by this update. Summary of changes: .../apache/cassandra/distributed/test/FailingRepairTest.java | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) - 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 (52a8d2947a -> a18a822530)
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 52a8d2947a Flaky test: org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest add 0b7310c010 Fix FailingRepairTest by making sure Gossip is started before each test add fcef3a2558 Merge branch 'cassandra-4.0' into cassandra-4.1 add a18a822530 Merge branch 'cassandra-4.1' into cassandra-5.0 No new revisions were added by this update. Summary of changes: - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (bd7dc322d8 -> 9bacdc5bdb)
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 bd7dc322d8 Merge branch 'cassandra-5.0' into trunk add 0b7310c010 Fix FailingRepairTest by making sure Gossip is started before each test add fcef3a2558 Merge branch 'cassandra-4.0' into cassandra-4.1 add a18a822530 Merge branch 'cassandra-4.1' into cassandra-5.0 add 9bacdc5bdb Merge branch 'cassandra-5.0' into trunk No new revisions were added by this update. Summary of changes: - 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 (20125c5053 -> fcef3a2558)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 20125c5053 Merge branch 'cassandra-4.0' into cassandra-4.1 add 0b7310c010 Fix FailingRepairTest by making sure Gossip is started before each test add fcef3a2558 Merge branch 'cassandra-4.0' into cassandra-4.1 No new revisions were added by this update. Summary of changes: - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18564) Test Failure: MixedModeAvailabilityV30AllOneTest.testAvailabilityCoordinatorUpgraded
[
https://issues.apache.org/jira/browse/CASSANDRA-18564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761729#comment-17761729
]
Berenguer Blasi commented on CASSANDRA-18564:
-
LGTM +1 on the code. Do we have some explanation as to why trunk CI takes an
extra hour? I can't seem to find one :(
> Test Failure:
> MixedModeAvailabilityV30AllOneTest.testAvailabilityCoordinatorUpgraded
>
>
> Key: CASSANDRA-18564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18564
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The JVM upgrade dtest
> {{MixedModeAvailabilityV3XAllOneTest.testAvailabilityCoordinatorUpgraded}}
> seems to be flaky at least in {{trunk}}:
> {code}
> junit.framework.AssertionFailedError: Error in test '4.0.11 -> [5.0]' while
> upgrading to '5.0'; successful upgrades []
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:348)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:154)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailabilityCoordinatorUpgraded(MixedModeAvailabilityTestBase.java:74)
> Caused by: java.lang.AssertionError: Unexpected error while reading in case
> write-read consistency ALL-ONE with upgraded coordinator and 2 nodes down:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 0 responses.
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.lambda$testAvailability$6(MixedModeAvailabilityTestBase.java:145)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:339)
> Caused by: org.apache.cassandra.exceptions.ReadTimeoutException: Operation
> timed out - received only 0 responses.
> at
> org.apache.cassandra.service.reads.ReadCallback.awaitResults(ReadCallback.java:162)
> at
> org.apache.cassandra.service.reads.AbstractReadExecutor.awaitResponses(AbstractReadExecutor.java:387)
> at
> org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:2124)
> at
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1995)
> at
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1873)
> at
> org.apache.cassandra.db.SinglePartitionReadCommand$Group.execute(SinglePartitionReadCommand.java:1286)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:364)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:293)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:105)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:750)
> {code}
> This has failed 143 times in 500 iterations of this CircleCI run:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2927/workflows/fcd1cd60-826b-484a-8e81-d3ba640f7de9/jobs/47659/tests
> The failure has also recently appeared on Jenkins too:
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1585/testReport/org.apache.cassandra.distributed.upgrade/MixedModeAvailabilityV3XAllOneTest/testAvailabilityCoordinatorUpgraded__jdk11/
> Given that the failure has just appeared on Jenkins and it fails relatively
> easily on CircleCI, it's likely that it has been broken by a very recent
> change.
--
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-18564) Test Failure: MixedModeAvailabilityV30AllOneTest.testAvailabilityCoordinatorUpgraded
[
https://issues.apache.org/jira/browse/CASSANDRA-18564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-18564:
Reviewers: Berenguer Blasi, Berenguer Blasi (was: Berenguer Blasi)
Berenguer Blasi, Berenguer Blasi
Status: Review In Progress (was: Patch Available)
> Test Failure:
> MixedModeAvailabilityV30AllOneTest.testAvailabilityCoordinatorUpgraded
>
>
> Key: CASSANDRA-18564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18564
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The JVM upgrade dtest
> {{MixedModeAvailabilityV3XAllOneTest.testAvailabilityCoordinatorUpgraded}}
> seems to be flaky at least in {{trunk}}:
> {code}
> junit.framework.AssertionFailedError: Error in test '4.0.11 -> [5.0]' while
> upgrading to '5.0'; successful upgrades []
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:348)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:154)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailabilityCoordinatorUpgraded(MixedModeAvailabilityTestBase.java:74)
> Caused by: java.lang.AssertionError: Unexpected error while reading in case
> write-read consistency ALL-ONE with upgraded coordinator and 2 nodes down:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 0 responses.
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.lambda$testAvailability$6(MixedModeAvailabilityTestBase.java:145)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:339)
> Caused by: org.apache.cassandra.exceptions.ReadTimeoutException: Operation
> timed out - received only 0 responses.
> at
> org.apache.cassandra.service.reads.ReadCallback.awaitResults(ReadCallback.java:162)
> at
> org.apache.cassandra.service.reads.AbstractReadExecutor.awaitResponses(AbstractReadExecutor.java:387)
> at
> org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:2124)
> at
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1995)
> at
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1873)
> at
> org.apache.cassandra.db.SinglePartitionReadCommand$Group.execute(SinglePartitionReadCommand.java:1286)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:364)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:293)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:105)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:750)
> {code}
> This has failed 143 times in 500 iterations of this CircleCI run:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2927/workflows/fcd1cd60-826b-484a-8e81-d3ba640f7de9/jobs/47659/tests
> The failure has also recently appeared on Jenkins too:
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1585/testReport/org.apache.cassandra.distributed.upgrade/MixedModeAvailabilityV3XAllOneTest/testAvailabilityCoordinatorUpgraded__jdk11/
> Given that the failure has just appeared on Jenkins and it fails relatively
> easily on CircleCI, it's likely that it has been broken by a very recent
> change.
--
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-18781) Add the ability to disable bulk load on server end and add metrics for bulk load used
[ https://issues.apache.org/jira/browse/CASSANDRA-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18781: -- Status: Needs Committer (was: Patch Available) > Add the ability to disable bulk load on server end and add metrics for bulk > load used > - > > Key: CASSANDRA-18781 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18781 > Project: Cassandra > Issue Type: Improvement > Components: Tool/bulk load >Reporter: Runtian Liu >Assignee: Runtian Liu >Priority: Normal > Fix For: 5.x > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently, Cassandra database users can use sstableloader to bulk load data > into Cassandra. However, for a Cassandra operator, there is no way to > forcibly block this behavior. Additionally, there is no metric indicating > whether the bulk load is being used on the server side. If a client is using > sstableloader, they will also need to upgrade the sstableloader code to the > new major version. This lack of control and visibility can become a blocker > during a major version upgrade. > > 1. Can we add a config to disable bulk load feature? Or it falls into > https://issues.apache.org/jira/browse/CASSANDRA-8303 > 2. Can we add metrics for bulk load used on server end? -- 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-18781) Add the ability to disable bulk load on server end and add metrics for bulk load used
[ https://issues.apache.org/jira/browse/CASSANDRA-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761725#comment-17761725 ] Stefan Miklosovic commented on CASSANDRA-18781: --- I am +1 here but we need another committer. I run builds with multiplexer here j17 https://app.circleci.com/pipelines/github/instaclustr/cassandra/3056/workflows/18257079-3d09-4b1d-8d38-2b30366ffb95 j11 https://app.circleci.com/pipelines/github/instaclustr/cassandra/3056/workflows/12f4af2b-64f0-4b86-b180-e8303fac9b20 [~adelapena] do you have a moment to review guardrail part of this at least? [~mck] what do you think about eligibility of this patch to be included in 5.0? One can view this as a security hole as a malicious user can "DDOS" a node / cluster with tons of SSTables, making it unstable / fill the disks. I think we should fix this. > Add the ability to disable bulk load on server end and add metrics for bulk > load used > - > > Key: CASSANDRA-18781 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18781 > Project: Cassandra > Issue Type: Improvement > Components: Tool/bulk load >Reporter: Runtian Liu >Assignee: Runtian Liu >Priority: Normal > Fix For: 5.x > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently, Cassandra database users can use sstableloader to bulk load data > into Cassandra. However, for a Cassandra operator, there is no way to > forcibly block this behavior. Additionally, there is no metric indicating > whether the bulk load is being used on the server side. If a client is using > sstableloader, they will also need to upgrade the sstableloader code to the > new major version. This lack of control and visibility can become a blocker > during a major version upgrade. > > 1. Can we add a config to disable bulk load feature? Or it falls into > https://issues.apache.org/jira/browse/CASSANDRA-8303 > 2. Can we add metrics for bulk load used on server end? -- 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-18781) Add the ability to disable bulk load on server end and add metrics for bulk load used
[ https://issues.apache.org/jira/browse/CASSANDRA-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18781: -- Status: Patch Available (was: In Progress) > Add the ability to disable bulk load on server end and add metrics for bulk > load used > - > > Key: CASSANDRA-18781 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18781 > Project: Cassandra > Issue Type: Improvement > Components: Tool/bulk load >Reporter: Runtian Liu >Assignee: Runtian Liu >Priority: Normal > Fix For: 5.x > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently, Cassandra database users can use sstableloader to bulk load data > into Cassandra. However, for a Cassandra operator, there is no way to > forcibly block this behavior. Additionally, there is no metric indicating > whether the bulk load is being used on the server side. If a client is using > sstableloader, they will also need to upgrade the sstableloader code to the > new major version. This lack of control and visibility can become a blocker > during a major version upgrade. > > 1. Can we add a config to disable bulk load feature? Or it falls into > https://issues.apache.org/jira/browse/CASSANDRA-8303 > 2. Can we add metrics for bulk load used on server end? -- 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-18781) Add the ability to disable bulk load on server end and add metrics for bulk load used
[ https://issues.apache.org/jira/browse/CASSANDRA-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18781: -- Status: In Progress (was: Changes Suggested) > Add the ability to disable bulk load on server end and add metrics for bulk > load used > - > > Key: CASSANDRA-18781 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18781 > Project: Cassandra > Issue Type: Improvement > Components: Tool/bulk load >Reporter: Runtian Liu >Assignee: Runtian Liu >Priority: Normal > Fix For: 5.x > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently, Cassandra database users can use sstableloader to bulk load data > into Cassandra. However, for a Cassandra operator, there is no way to > forcibly block this behavior. Additionally, there is no metric indicating > whether the bulk load is being used on the server side. If a client is using > sstableloader, they will also need to upgrade the sstableloader code to the > new major version. This lack of control and visibility can become a blocker > during a major version upgrade. > > 1. Can we add a config to disable bulk load feature? Or it falls into > https://issues.apache.org/jira/browse/CASSANDRA-8303 > 2. Can we add metrics for bulk load used on server end? -- 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-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[ https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761719#comment-17761719 ] Stefan Miklosovic commented on CASSANDRA-18366: --- Yes, there were quite a non-trivial changes introduced in CASSANDRA-17116 which are not so straightforward to backport into 4.0 I think that if the current solution works, lets just ship it to 4.0. I see that the multiplexer was already run, so I am +1 on this. > Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - > testFailingMessage[VALIDATION_REQ/parallel/true] > > > Key: CASSANDRA-18366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18366 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Brandon Williams >Assignee: dan jatnieks >Priority: Normal > Fix For: 4.0.x > > > First seen > [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206] > this test times out for me consistently on both j8 and j11 where 4.1 and > trunk do not. -- 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-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[ https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18366: -- Status: Ready to Commit (was: Review In Progress) > Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - > testFailingMessage[VALIDATION_REQ/parallel/true] > > > Key: CASSANDRA-18366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18366 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Brandon Williams >Assignee: dan jatnieks >Priority: Normal > Fix For: 4.0.x > > > First seen > [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206] > this test times out for me consistently on both j8 and j11 where 4.1 and > trunk do not. -- 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-18366) Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - testFailingMessage[VALIDATION_REQ/parallel/true]
[ https://issues.apache.org/jira/browse/CASSANDRA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18366: -- Reviewers: Brandon Williams, Stefan Miklosovic (was: Brandon Williams) Status: Review In Progress (was: Needs Committer) > Test failure: org.apache.cassandra.distributed.test.FailingRepairTest - > testFailingMessage[VALIDATION_REQ/parallel/true] > > > Key: CASSANDRA-18366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18366 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Brandon Williams >Assignee: dan jatnieks >Priority: Normal > Fix For: 4.0.x > > > First seen > [here|https://app.circleci.com/pipelines/github/driftx/cassandra/928/workflows/f4e93a72-d4aa-47a2-996f-aa3fb018d848/jobs/16206] > this test times out for me consistently on both j8 and j11 where 4.1 and > trunk do not. -- 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-18393) Flaky test: org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.testConditionalUpdate[1: clusterMinVersion=3.11]-compression.jdk1.8 on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-18393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-18393:
Fix Version/s: (was: 4.1.x)
Since Version: 5.0
Source Control Link:
https://github.com/apache/cassandra/commit/52a8d2947a7509baec05a5b6f6c1377219e3a051
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Flaky test:
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.testConditionalUpdate[1:
> clusterMinVersion=3.11]-compression.jdk1.8 on trunk
>
>
> Key: CASSANDRA-18393
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18393
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.0, 5.0.x
>
>
> Failed 1 times in the last 1 runs. Flakiness: 0%, Stability: 0%
> {code}
> Error Message
> 5.0.0-SNAPSHOT boolean:false
> Stacktrace
> junit.framework.AssertionFailedError: 5.0.0-SNAPSHOT boolean:false
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.lambda$data$1(InsertUpdateIfConditionTest.java:70)
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.beforeSetup(InsertUpdateIfConditionTest.java:95)
> at
> org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.before(InsertUpdateIfConditionTest.java:89)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (abe09cff34 -> bd7dc322d8)
This is an automated email from the ASF dual-hosted git repository. bereng pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from abe09cff34 Clean up obsolete functions and simplify cql_version handling in cqlsh new 52a8d2947a Flaky test: org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest new bd7dc322d8 Merge branch 'cassandra-5.0' into trunk The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: src/java/org/apache/cassandra/gms/Gossiper.java| 13 + .../operations/InsertUpdateIfConditionTest.java| 57 ++ 2 files changed, 28 insertions(+), 42 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. bereng pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit bd7dc322d81d2d6f49fc355fbf86916c90e135d8 Merge: abe09cff34 52a8d2947a Author: Bereng AuthorDate: Mon Sep 4 09:21:06 2023 +0200 Merge branch 'cassandra-5.0' into trunk * cassandra-5.0: Flaky test: org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest src/java/org/apache/cassandra/gms/Gossiper.java| 13 + .../operations/InsertUpdateIfConditionTest.java| 57 ++ 2 files changed, 28 insertions(+), 42 deletions(-) - 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: Flaky test: org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest
This is an automated email from the ASF dual-hosted git repository.
bereng pushed a commit to branch cassandra-5.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/cassandra-5.0 by this push:
new 52a8d2947a Flaky test:
org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest
52a8d2947a is described below
commit 52a8d2947a7509baec05a5b6f6c1377219e3a051
Author: Bereng
AuthorDate: Tue Aug 29 10:53:09 2023 +0200
Flaky test:
org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest
patch by Berenguer Blasi; reviewed by Andres de la Peña for CASSANDRA-18393
---
src/java/org/apache/cassandra/gms/Gossiper.java| 13 +
.../operations/InsertUpdateIfConditionTest.java| 57 ++
2 files changed, 28 insertions(+), 42 deletions(-)
diff --git a/src/java/org/apache/cassandra/gms/Gossiper.java
b/src/java/org/apache/cassandra/gms/Gossiper.java
index 5f104673d1..5f90b2f2c4 100644
--- a/src/java/org/apache/cassandra/gms/Gossiper.java
+++ b/src/java/org/apache/cassandra/gms/Gossiper.java
@@ -2484,21 +2484,12 @@ public class Gossiper implements
IFailureDetectionEventListener, GossiperMBean
* Returns {@code true} if there are nodes on version lower than the
provided version
*/
public boolean isUpgradingFromVersionLowerThan(CassandraVersion
referenceVersion)
-{
-return isUpgradingFromVersionLowerThanC17653(referenceVersion).left;
-}
-
-/* TODO: Aux method for debug purposes on fixing C17653. To be removed*/
-@VisibleForTesting
-public Pair
isUpgradingFromVersionLowerThanC17653(CassandraVersion referenceVersion)
{
CassandraVersion v = upgradeFromVersionMemoized.get();
if (CassandraVersion.NULL_VERSION.equals(v) && scheduledGossipTask ==
null)
-return Pair.create(false, v);
-
-boolean res = v != null && v.compareTo(referenceVersion) < 0;
+return false;
-return Pair.create(res, v);
+return v != null && v.compareTo(referenceVersion) < 0;
}
private boolean nodesAgreeOnSchema(Collection nodes)
diff --git
a/test/unit/org/apache/cassandra/cql3/validation/operations/InsertUpdateIfConditionTest.java
b/test/unit/org/apache/cassandra/cql3/validation/operations/InsertUpdateIfConditionTest.java
index 531c1f6c02..c57f61d6eb 100644
---
a/test/unit/org/apache/cassandra/cql3/validation/operations/InsertUpdateIfConditionTest.java
+++
b/test/unit/org/apache/cassandra/cql3/validation/operations/InsertUpdateIfConditionTest.java
@@ -37,7 +37,6 @@ import org.apache.cassandra.gms.Gossiper;
import org.apache.cassandra.schema.SchemaConstants;
import org.apache.cassandra.schema.SchemaKeyspaceTables;
import org.apache.cassandra.utils.CassandraVersion;
-import org.apache.cassandra.utils.Pair;
import static java.lang.String.format;
import static org.junit.Assert.assertEquals;
@@ -64,18 +63,14 @@ public class InsertUpdateIfConditionTest extends CQLTester
{
ServerTestUtils.daemonInitialization();
return Arrays.asList(new Object[]{ "3.0", (Runnable) () -> {
- Pair res =
Gossiper.instance.isUpgradingFromVersionLowerThanC17653(new
CassandraVersion("3.11"));
- assertTrue(debugMsgCASSANDRA17653(res),
res.left);
+
assertTrue(Gossiper.instance.isUpgradingFromVersionLowerThan(new
CassandraVersion("3.11")));
} },
new Object[]{ "3.11", (Runnable) () -> {
- Pair res =
Gossiper.instance.isUpgradingFromVersionLowerThanC17653(SystemKeyspace.CURRENT_VERSION);
- assertTrue(debugMsgCASSANDRA17653(res),
res.left);
- res =
Gossiper.instance.isUpgradingFromVersionLowerThanC17653(new
CassandraVersion("3.11"));
- assertFalse(debugMsgCASSANDRA17653(res),
res.left);
+
assertTrue(Gossiper.instance.isUpgradingFromVersionLowerThan(SystemKeyspace.CURRENT_VERSION));
+
assertFalse(Gossiper.instance.isUpgradingFromVersionLowerThan(new
CassandraVersion("3.11")));
} },
new Object[]{
SystemKeyspace.CURRENT_VERSION.toString(), (Runnable) () -> {
- Pair res =
Gossiper.instance.isUpgradingFromVersionLowerThanC17653(SystemKeyspace.CURRENT_VERSION);
- assertFalse(debugMsgCASSANDRA17653(res),
res.left);
+
assertFalse(Gossiper.instance.isUpgradingFromVersionLowerThan(SystemKeyspace.CURRENT_VERSION));
} });
}
@@ -93,8 +88,14 @@ public class InsertUpdateIfConditionTest extends CQLTester
public static void beforeSetup(String
