[jira] [Commented] (CASSANDRA-17712) Remove javadocs step from CI and release process
[
https://issues.apache.org/jira/browse/CASSANDRA-17712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580585#comment-17580585
]
Berenguer Blasi commented on CASSANDRA-17712:
-
Ci needs to be against jenkins right? Started them
[here|https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch/1878/]
and the following ones
> Remove javadocs step from CI and release process
>
>
> Key: CASSANDRA-17712
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17712
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Berenguer Blasi
>Assignee: Brandon Williams
>Priority: Normal
>
> Currently the javadocs step is both:
> - Taking up jenkins cycles and generating a [large
> output|https://ci-cassandra.apache.org/job/Cassandra-trunk-artifacts/1313/jdk=jdk_1.8_latest,label=cassandra/consoleFull]
> in CI when building artifacts
> - Failing randomly on javadoc issues such as {{AlterTableStatement.java:135:
> error: text not allowed in element}}
> Apidocs are not being bundled, uploaded or used anywhere. Hence it would be
> best to remove javadocs generation on every CI. Mainly removing javadoc from
> artifacts and mvn-install.
--
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-17712) Remove javadocs step from CI and release process
[
https://issues.apache.org/jira/browse/CASSANDRA-17712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-17712:
Reviewers: Berenguer Blasi, Berenguer Blasi
Berenguer Blasi, Berenguer Blasi (was: Berenguer Blasi)
Status: Review In Progress (was: Patch Available)
> Remove javadocs step from CI and release process
>
>
> Key: CASSANDRA-17712
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17712
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Berenguer Blasi
>Assignee: Brandon Williams
>Priority: Normal
>
> Currently the javadocs step is both:
> - Taking up jenkins cycles and generating a [large
> output|https://ci-cassandra.apache.org/job/Cassandra-trunk-artifacts/1313/jdk=jdk_1.8_latest,label=cassandra/consoleFull]
> in CI when building artifacts
> - Failing randomly on javadoc issues such as {{AlterTableStatement.java:135:
> error: text not allowed in element}}
> Apidocs are not being bundled, uploaded or used anywhere. Hence it would be
> best to remove javadocs generation on every CI. Mainly removing javadoc from
> artifacts and mvn-install.
--
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-site updated (766f9e23 -> 08728742)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch asf-site in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 766f9e23 generate docs for 7183f731 add 8f277185 ninja-fix restore path to caution img add 08728742 generate docs for 8f277185 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 (766f9e23) \ N -- N -- N refs/heads/asf-site (08728742) 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. No new revisions were added by this update. Summary of changes: content/_/download.html| 2 +- content/search-index.js| 2 +- .../source/modules/ROOT/pages/download.adoc| 2 +- site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078 bytes 4 files changed, 3 insertions(+), 3 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (262f9341 -> 08728742)
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 262f9341 generate docs for 8f277185 new 08728742 generate docs for 8f277185 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 (262f9341) \ N -- N -- N refs/heads/asf-staging (08728742) 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 4740078 -> 4740078 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 (2698ca35 -> 262f9341)
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 2698ca35 generate docs for 8f277185 new 262f9341 generate docs for 8f277185 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 (2698ca35) \ N -- N -- N refs/heads/asf-staging (262f9341) 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 4740078 -> 4740078 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 (e2005308 -> 2698ca35)
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 e2005308 generate docs for 8f277185 new 2698ca35 generate docs for 8f277185 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 (e2005308) \ N -- N -- N refs/heads/asf-staging (2698ca35) 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 4740078 -> 4740078 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17792) Fix race condition on updating cdc size and advancing to next segment
[
https://issues.apache.org/jira/browse/CASSANDRA-17792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANDRA-17792:
--
Authors: Yifan Cai (was: Yifan Cai)
Fix Version/s: 4.0.6
4.1.x
4.2
(was: 4.x)
Since Version: 4.0
Source Control Link:
https://github.com/apache/cassandra/commit/84e10d0cad5e34ef50d6951ca33714dfde0caa53
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed into cassandra 4.0 as
[84e10d0cad5|https://github.com/apache/cassandra/commit/84e10d0cad5e34ef50d6951ca33714dfde0caa53]
and merged up to 4.1 and trunk.
> Fix race condition on updating cdc size and advancing to next segment
> -
>
> Key: CASSANDRA-17792
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17792
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Yifan Cai
>Priority: Normal
> Fix For: 4.0.6, 4.1.x, 4.2
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> org.apache.cassandra.distributed.test.cdc.ToggleCDCOnRepairEnabledTest is a
> bit flaky on [trunk.
> As [this
> run|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=17666]
> shows it was flaky since it was introduced a month ago as part of
> CASSANDRA-17666 but the flakiness is so low that if we don't run it in a loop
> it is hard to hit it.
> Both tests in the test class can fail with the same exception:
> {code:java}
> org.apache.cassandra.distributed.shared.ShutdownException: Uncaught
> exceptions were thrown during test at
> org.apache.cassandra.distributed.impl.AbstractCluster.checkAndResetUncaughtExceptions(AbstractCluster.java:1056)
> at
> org.apache.cassandra.distributed.impl.AbstractCluster.close(AbstractCluster.java:1042)
> at
> org.apache.cassandra.distributed.test.cdc.ToggleCDCOnRepairEnabledTest.testCDCOnRepairEnabled(ToggleCDCOnRepairEnabledTest.java:95)
> at
> org.apache.cassandra.distributed.test.cdc.ToggleCDCOnRepairEnabledTest.testCDCOnRepairIsEnabled(ToggleCDCOnRepairEnabledTest.java:40)
> 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)
> Suppressed: java.lang.NullPointerException at
> org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDC$CDCSizeTracker.recalculateOverflowSize(CommitLogSegmentManagerCDC.java:390)
> at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:81) at
> org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:47) at
> org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:57) 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}
> CC [~ycai] , [~jmckenzie]
--
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-4.1' into trunk
This is an automated email from the ASF dual-hosted git repository. ycai pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 0bf9955abf12b65325af01d2618ba0d3f4eb701c Merge: cbc127ab79 590de42a06 Author: Yifan Cai AuthorDate: Tue Aug 16 15:25:20 2022 -0700 Merge branch 'cassandra-4.1' into trunk CHANGES.txt| 1 + .../cassandra/config/DatabaseDescriptor.java | 8 +-- .../cassandra/db/commitlog/CommitLogSegment.java | 8 ++- .../db/commitlog/CommitLogSegmentManagerCDC.java | 69 -- .../commitlog/CommitLogSegmentManagerStandard.java | 3 +- .../commitlog/CommitLogSegmentManagerCDCTest.java | 8 +-- 6 files changed, 55 insertions(+), 42 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (cbc127ab79 -> 0bf9955abf)
This is an automated email from the ASF dual-hosted git repository. ycai pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from cbc127ab79 Merge branch 'cassandra-4.1' into trunk add 84e10d0cad Fix race condition on updating cdc size and advancing to next segment add 590de42a06 Merge branch 'cassandra-4.0' into cassandra-4.1 new 0bf9955abf Merge branch 'cassandra-4.1' into trunk The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt| 1 + .../cassandra/config/DatabaseDescriptor.java | 8 +-- .../cassandra/db/commitlog/CommitLogSegment.java | 8 ++- .../db/commitlog/CommitLogSegmentManagerCDC.java | 69 -- .../commitlog/CommitLogSegmentManagerStandard.java | 3 +- .../commitlog/CommitLogSegmentManagerCDCTest.java | 8 +-- 6 files changed, 55 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-4.1 updated (e02923305c -> 590de42a06)
This is an automated email from the ASF dual-hosted git repository. ycai pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from e02923305c Merge branch 'cassandra-4.0' into cassandra-4.1 add 84e10d0cad Fix race condition on updating cdc size and advancing to next segment add 590de42a06 Merge branch 'cassandra-4.0' into cassandra-4.1 No new revisions were added by this update. Summary of changes: CHANGES.txt| 1 + .../cassandra/config/DatabaseDescriptor.java | 8 +-- .../cassandra/db/commitlog/CommitLogSegment.java | 8 ++- .../db/commitlog/CommitLogSegmentManagerCDC.java | 69 -- .../commitlog/CommitLogSegmentManagerStandard.java | 3 +- .../commitlog/CommitLogSegmentManagerCDCTest.java | 8 +-- 6 files changed, 55 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-4.0 updated (5fafa709fb -> 84e10d0cad)
This is an automated email from the ASF dual-hosted git repository. ycai pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 5fafa709fb Merge branch 'cassandra-3.11' into cassandra-4.0 add 84e10d0cad Fix race condition on updating cdc size and advancing to next segment No new revisions were added by this update. Summary of changes: CHANGES.txt| 1 + .../cassandra/db/commitlog/CommitLogSegment.java | 8 ++- .../db/commitlog/CommitLogSegmentManagerCDC.java | 79 +++--- .../commitlog/CommitLogSegmentManagerStandard.java | 3 +- 4 files changed, 65 insertions(+), 26 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17792) Fix race condition on updating cdc size and advancing to next segment
[
https://issues.apache.org/jira/browse/CASSANDRA-17792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17578642#comment-17578642
]
Yifan Cai edited comment on CASSANDRA-17792 at 8/16/22 10:15 PM:
-
Starting commit
CI Results:
||Branch||Source||Circle CI||
|cassandra-4.0|[branch|https://github.com/yifan-c/cassandra/tree/commit_remote_branch/CASSANDRA-17792-cassandra-4.0-B379A7D7-6E64-466B-BF81-7D8654F4110C]|[build|https://app.circleci.com/pipelines/github/yifan-c/cassandra?branch=commit_remote_branch%2FCASSANDRA-17792-cassandra-4.0-B379A7D7-6E64-466B-BF81-7D8654F4110C]|
|cassandra-4.1|[branch|https://github.com/yifan-c/cassandra/tree/commit_remote_branch/CASSANDRA-17792-cassandra-4.1-B379A7D7-6E64-466B-BF81-7D8654F4110C]|[build|https://app.circleci.com/pipelines/github/yifan-c/cassandra?branch=commit_remote_branch%2FCASSANDRA-17792-cassandra-4.1-B379A7D7-6E64-466B-BF81-7D8654F4110C]|
|trunk|[branch|https://github.com/yifan-c/cassandra/tree/commit_remote_branch/CASSANDRA-17792-trunk-B379A7D7-6E64-466B-BF81-7D8654F4110C]|[build|https://app.circleci.com/pipelines/github/yifan-c/cassandra?branch=commit_remote_branch%2FCASSANDRA-17792-trunk-B379A7D7-6E64-466B-BF81-7D8654F4110C]|
Result looks green, except one failure. The test failure already has a tracking
JIRA CASSANDRA-17674
was (Author: yifanc):
Starting commit
CI Results (pending):
||Branch||Source||Circle CI||
|cassandra-4.0|[branch|https://github.com/yifan-c/cassandra/tree/commit_remote_branch/CASSANDRA-17792-cassandra-4.0-B379A7D7-6E64-466B-BF81-7D8654F4110C]|[build|https://app.circleci.com/pipelines/github/yifan-c/cassandra?branch=commit_remote_branch%2FCASSANDRA-17792-cassandra-4.0-B379A7D7-6E64-466B-BF81-7D8654F4110C]|
|cassandra-4.1|[branch|https://github.com/yifan-c/cassandra/tree/commit_remote_branch/CASSANDRA-17792-cassandra-4.1-B379A7D7-6E64-466B-BF81-7D8654F4110C]|[build|https://app.circleci.com/pipelines/github/yifan-c/cassandra?branch=commit_remote_branch%2FCASSANDRA-17792-cassandra-4.1-B379A7D7-6E64-466B-BF81-7D8654F4110C]|
|trunk|[branch|https://github.com/yifan-c/cassandra/tree/commit_remote_branch/CASSANDRA-17792-trunk-B379A7D7-6E64-466B-BF81-7D8654F4110C]|[build|https://app.circleci.com/pipelines/github/yifan-c/cassandra?branch=commit_remote_branch%2FCASSANDRA-17792-trunk-B379A7D7-6E64-466B-BF81-7D8654F4110C]|
> Fix race condition on updating cdc size and advancing to next segment
> -
>
> Key: CASSANDRA-17792
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17792
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Yifan Cai
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> org.apache.cassandra.distributed.test.cdc.ToggleCDCOnRepairEnabledTest is a
> bit flaky on [trunk.
> As [this
> run|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=17666]
> shows it was flaky since it was introduced a month ago as part of
> CASSANDRA-17666 but the flakiness is so low that if we don't run it in a loop
> it is hard to hit it.
> Both tests in the test class can fail with the same exception:
> {code:java}
> org.apache.cassandra.distributed.shared.ShutdownException: Uncaught
> exceptions were thrown during test at
> org.apache.cassandra.distributed.impl.AbstractCluster.checkAndResetUncaughtExceptions(AbstractCluster.java:1056)
> at
> org.apache.cassandra.distributed.impl.AbstractCluster.close(AbstractCluster.java:1042)
> at
> org.apache.cassandra.distributed.test.cdc.ToggleCDCOnRepairEnabledTest.testCDCOnRepairEnabled(ToggleCDCOnRepairEnabledTest.java:95)
> at
> org.apache.cassandra.distributed.test.cdc.ToggleCDCOnRepairEnabledTest.testCDCOnRepairIsEnabled(ToggleCDCOnRepairEnabledTest.java:40)
> 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)
> Suppressed: java.lang.NullPointerException at
> org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDC$CDCSizeTracker.recalculateOverflowSize(CommitLogSegmentManagerCDC.java:390)
> at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:81) at
> org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:47) at
> org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:57) at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
>
[jira] [Created] (CASSANDRA-17824) Enable using a deterministic table id at table creation time
Cheng Wang created CASSANDRA-17824:
--
Summary: Enable using a deterministic table id at table creation
time
Key: CASSANDRA-17824
URL: https://issues.apache.org/jira/browse/CASSANDRA-17824
Project: Cassandra
Issue Type: Improvement
Components: Cluster/Schema
Reporter: Cheng Wang
Assignee: Cheng Wang
When the *CREATE TABLE* statement is executed on a coordinator node, it is
assigned a new random, globally unique ID (i.e., time UUID). That ID doesn't
change on the *ALTER TABLE* statement, whereas the *DROP* and then *CREATE*
table will create a new ID. Cassandra relies on the fact that tables with the
same table ID have compatible schemas and use the table ID to reach the schema
agreement.
One of the issues with the random UUID is when concurrent schema changes are
running on different coordinator nodes since clients may implement the schema
change programmatically and issue the events from different nodes concurrently.
Since Cassandra is an eventually consistent system, not just in terms of data
it stores, but also in terms of schemas by relying on the gossip protocol, it
may take a non-deterministic amount of time before all the nodes in the cluster
converge on one schema version.
Once a cluster is in the state of schema disagreement, it is a non-trivial
effort to recover the cluster to a healthy state, and such a recovery process
may potentially involve downtime.
Therefore, we propose an option of using the deterministic table id per the
*CREATE TABLE* statement. Some key properties of the deterministic id are:
* The *CREATE TABLE* queries which are syntactically the same should always
generate the same table id. And the id should be globally unique.
* The *CREATE TABLE* queries which are semantically the same should also
guarantee to have the table id, even though the queries may look syntactically
different. For example, the parsed query should ignore white spaces,
lower/upper cases, etc..
* Similar to the requirement #2, queries with the default options/parameters
should always have the same id, no matter if they are declared implicitly or
explicitly.
* Queries which are semantically different should generate the different table
ids, even though they may have the same keyspace name and table name.
To fulfill all the requirements discussed above, the input of the hash function
should include the full metadata of the CREATE TABLE statement. Therefore, we
use the serialized version of the class *CreateTableStatement* in
Cassandra{*},{*} which includes all the metadata of the CREATE TABLE statement.
--
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 (f69d102e -> e2005308)
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 f69d102e generate docs for 7183f731 add 8f277185 ninja-fix restore path to caution img new e2005308 generate docs for 8f277185 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 (f69d102e) \ N -- N -- N refs/heads/asf-staging (e2005308) 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/_/download.html| 2 +- .../source/modules/ROOT/pages/download.adoc| 2 +- site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078 bytes 3 files changed, 2 insertions(+), 2 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (766f9e23 -> f69d102e)
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 omit 766f9e23 generate docs for 7183f731 new f69d102e generate docs for 7183f731 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 (766f9e23) \ N -- N -- N refs/heads/asf-staging (f69d102e) 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 4740078 -> 4740078 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] [Comment Edited] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580486#comment-17580486 ] Michael Semb Wever edited comment on CASSANDRA-17748 at 8/16/22 9:46 PM: - I still need to remove all the deb/rpm files from dist.a.o The plan is to do that after the next release, and all announcement warnings have been made as agreed upon. was (Author: michaelsembwever): I still need to remove all files from dist.a.o The plan is to do that after the next release, and all announcement warnings have been made as agreed upon. > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > Labels: pull-request-available > Fix For: 3.11.14, 4.0.6, 4.1, 4.2 > > Time Spent: 20m > Remaining Estimate: 0h > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- 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-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580486#comment-17580486 ] Michael Semb Wever commented on CASSANDRA-17748: I still need to remove all files from dist.a.o The plan is to do that after the next release, and all announcement warnings have been made as agreed upon. > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > Labels: pull-request-available > Fix For: 3.11.14, 4.0.6, 4.1, 4.2 > > Time Spent: 20m > Remaining Estimate: 0h > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- 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-17823) WEBSITE – in-tree trunk should be marked as `prerelease: true`
[ https://issues.apache.org/jira/browse/CASSANDRA-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17823: --- Fix Version/s: 4.x > WEBSITE – in-tree trunk should be marked as `prerelease: true` > -- > > Key: CASSANDRA-17823 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17823 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Michael Semb Wever >Priority: Normal > Labels: lhf > Fix For: 4.x > > > this will avoid the "A newer version of this documentation is available." > banner displaying on the version docs for our latest released version. > ref: https://docs.antora.org/antora/latest/component-prerelease/#true > change is to be applied to > https://github.com/apache/cassandra/blob/trunk/doc/antora.yml -- 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-17823) WEBSITE – in-tree trunk should be marked as `prerelease: true`
[ https://issues.apache.org/jira/browse/CASSANDRA-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17823: --- Labels: lhf (was: ) > WEBSITE – in-tree trunk should be marked as `prerelease: true` > -- > > Key: CASSANDRA-17823 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17823 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Michael Semb Wever >Priority: Normal > Labels: lhf > > this will avoid the "A newer version of this documentation is available." > banner displaying on the version docs for our latest released version. > ref: https://docs.antora.org/antora/latest/component-prerelease/#true > change is to be applied to > https://github.com/apache/cassandra/blob/trunk/doc/antora.yml -- 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-17823) WEBSITE – in-tree trunk should be marked as `prerelease: true`
[ https://issues.apache.org/jira/browse/CASSANDRA-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17823: --- Bug Category: Parent values: Correctness(12982)Level 1 values: API / Semantic Definition(13162) Complexity: Low Hanging Fruit Discovered By: User Report Severity: Low Status: Open (was: Triage Needed) > WEBSITE – in-tree trunk should be marked as `prerelease: true` > -- > > Key: CASSANDRA-17823 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17823 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Michael Semb Wever >Priority: Normal > Labels: lhf > > this will avoid the "A newer version of this documentation is available." > banner displaying on the version docs for our latest released version. > ref: https://docs.antora.org/antora/latest/component-prerelease/#true > change is to be applied to > https://github.com/apache/cassandra/blob/trunk/doc/antora.yml -- 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-17823) WEBSITE – in-tree trunk should be marked as `prerelease: true`
Michael Semb Wever created CASSANDRA-17823: -- Summary: WEBSITE – in-tree trunk should be marked as `prerelease: true` Key: CASSANDRA-17823 URL: https://issues.apache.org/jira/browse/CASSANDRA-17823 Project: Cassandra Issue Type: Bug Components: Documentation/Website Reporter: Michael Semb Wever this will avoid the "A newer version of this documentation is available." banner displaying on the version docs for our latest released version. ref: https://docs.antora.org/antora/latest/component-prerelease/#true change is to be applied to https://github.com/apache/cassandra/blob/trunk/doc/antora.yml -- 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 trunk updated: ninja-fix restore path to caution img
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-website.git The following commit(s) were added to refs/heads/trunk by this push: new 8f277185 ninja-fix restore path to caution img 8f277185 is described below commit 8f2771855aa6d148ed356dc539d2d6cb5f67db2d Author: mck AuthorDate: Tue Aug 16 23:29:02 2022 +0200 ninja-fix restore path to caution img --- site-content/source/modules/ROOT/pages/download.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site-content/source/modules/ROOT/pages/download.adoc b/site-content/source/modules/ROOT/pages/download.adoc index 4cdbcbfd..cb2be816 100644 --- a/site-content/source/modules/ROOT/pages/download.adoc +++ b/site-content/source/modules/ROOT/pages/download.adoc @@ -88,7 +88,7 @@ Older (unsupported) versions of Cassandra are archived https://archive.apache.or [caution] -image:../assets/img/caution.svg[alt="Caution",width=64,height=64] Debian and RedHat package repositories have moved! +image:/assets/img/caution.svg[alt="Caution",width=64,height=64] Debian and RedHat package repositories have moved! Debian's `sources.list` and RedHat's `cassandra.repo` files must be updated to point to the new repository URLs (see below). - 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 (22b9fac1 -> 766f9e23)
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 22b9fac1 generate docs for eaa6b3e7 add 7183f731 ninja-fix caution image needs size, and trunk needs to be copied into content/ new 766f9e23 generate docs for 7183f731 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 (22b9fac1) \ N -- N -- N refs/heads/asf-staging (766f9e23) 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/_/download.html| 5 - .../4.2}/cassandra/_images/Figure_1_backups.jpg| Bin .../4.2}/cassandra/_images/Figure_1_data_model.jpg | Bin .../4.2}/cassandra/_images/Figure_1_guarantees.jpg | Bin .../cassandra/_images/Figure_1_read_repair.jpg | Bin .../4.2}/cassandra/_images/Figure_2_data_model.jpg | Bin .../cassandra/_images/Figure_2_read_repair.jpg | Bin .../cassandra/_images/Figure_3_read_repair.jpg | Bin .../cassandra/_images/Figure_4_read_repair.jpg | Bin .../cassandra/_images/Figure_5_read_repair.jpg | Bin .../cassandra/_images/Figure_6_read_repair.jpg | Bin .../_images/cassandra_ssl_context_factory_pem.png | Bin .../_images/data_modeling_chebotko_logical.png | Bin .../_images/data_modeling_chebotko_physical.png| Bin .../_images/data_modeling_hotel_bucketing.png | Bin .../cassandra/_images/data_modeling_hotel_erd.png | Bin .../_images/data_modeling_hotel_logical.png| Bin .../_images/data_modeling_hotel_physical.png | Bin .../_images/data_modeling_hotel_queries.png| Bin .../_images/data_modeling_hotel_relational.png | Bin .../_images/data_modeling_reservation_logical.png | Bin .../_images/data_modeling_reservation_physical.png | Bin .../4.2}/cassandra/_images/docs_commit.png | Bin .../4.2}/cassandra/_images/docs_create_branch.png | Bin .../4.2}/cassandra/_images/docs_create_file.png| Bin .../4.2}/cassandra/_images/docs_editor.png | Bin .../4.2}/cassandra/_images/docs_fork.png | Bin .../4.2}/cassandra/_images/docs_pr.png | Bin .../4.2}/cassandra/_images/docs_preview.png| Bin .../4.2}/cassandra/_images/eclipse_debug0.png | Bin .../4.2}/cassandra/_images/eclipse_debug1.png | Bin .../4.2}/cassandra/_images/eclipse_debug2.png | Bin .../4.2}/cassandra/_images/eclipse_debug3.png | Bin .../4.2}/cassandra/_images/eclipse_debug4.png | Bin .../4.2}/cassandra/_images/eclipse_debug5.png | Bin .../4.2}/cassandra/_images/eclipse_debug6.png | Bin .../cassandra/_images/example-stress-graph.png | Bin .../4.2}/cassandra/_images/generatetokens.rst | 0 .../trunk => doc/4.2}/cassandra/_images/hints.svg | 0 .../trunk => doc/4.2}/cassandra/_images/ring.svg | 0 .../trunk => doc/4.2}/cassandra/_images/vnodes.svg | 0 .../4.2}/cassandra/architecture/dynamo.html| 0 .../4.2}/cassandra/architecture/guarantees.html| 0 .../4.2}/cassandra/architecture/index.html | 0 .../4.2}/cassandra/architecture/overview.html | 0 .../4.2}/cassandra/architecture/snitch.html| 0 .../cassandra/architecture/storage_engine.html | 0 .../configuration/cass_cl_archive_file.html| 0 .../cassandra/configuration/cass_env_sh_file.html | 0 .../configuration/cass_jvm_options_file.html | 0 .../configuration/cass_logback_xml_file.html | 0 .../cassandra/configuration/cass_rackdc_file.html | 0 .../cassandra/configuration/cass_topo_file.html| 0 .../cassandra/configuration/cass_yaml_file.html| 0 .../4.2}/cassandra/configuration/index.html| 0 .../trunk => doc/4.2}/cassandra/cql/SASI.html | 0 .../4.2}/cassandra/cql/appendices.html | 0 .../trunk => doc/4.2}/cassandra/cql/changes.html | 0 .../4.2}/cassandra/cql/cql_singlefile.html | 0 .../trunk => doc/4.2}/cassandra/cql/ddl.html | 0 .../4.2}/cassandra/cql/definitions.html| 0 .../trunk => doc/4.2}/cassandra/cql/dml.html | 0 .../trunk => doc/4.2}/cassandra/cql/functions.html | 0
[jira] (CASSANDRA-17669) CentOS/RHEL installation requires JRE not available in Java 11
[ https://issues.apache.org/jira/browse/CASSANDRA-17669 ]
Richard Hesse deleted comment on CASSANDRA-17669:
---
was (Author: richardchesse):
This might work for installs, but it's broken for upgrades. Example error:
{noformat}
Resolving Dependencies
--> Running transaction check
---> Package cassandra.noarch 0:4.0.3-1 will be updated
---> Package cassandra.noarch 0:4.0.5-1 will be an update
Error: Invalid version flag: or
{noformat}
RPM 4.11 (which CentOS/RedHat uses) doesn't have boolean support.
> CentOS/RHEL installation requires JRE not available in Java 11
> --
>
> Key: CASSANDRA-17669
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17669
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Erick Ramirez
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0.5, 4.1-beta
>
>
> h2. Background
> A user [reported on Stack
> Overflow|https://stackoverflow.com/questions/72377621/] and the DataStax
> Developers [dtsx.io/discord|https://dtsx.io/discord] an issue with installing
> Cassandra when only Java 11 is installed.
> h2. Symptoms
> Attempts to install Cassandra using YUM requires Java 8:
> {noformat}
> $ sudo yum install cassandra
> Dependencies resolved.
>
> Package Architecture
> Version Repository
> Size
>
> Installing:
> cassandranoarch
> 4.0.4-1 cassandra
> 45 M
> Installing dependencies:
> java-1.8.0-openjdk x86_64
> 1:1.8.0.312.b07-2.el8_5 appstream
> 341 k
> java-1.8.0-openjdk-headless x86_64
> 1:1.8.0.312.b07-2.el8_5 appstream
> 34 M
> Installing weak dependencies:
> gtk2 x86_64
> 2.24.32-5.el8appstream
> 3.4 M
> Transaction Summary
>
> Install 4 Packages
> {noformat}
> Similarly, attempts to install the RPM results in:
> {noformat}
> $ sudo rpm -i cassandra-4.0.4-1.noarch.rpm
> warning: cassandra-4.0.4-1.noarch.rpm: Header V4 RSA/SHA256 Signature, key ID
> 7e3e87cb: NOKEY
> error: Failed dependencies:
> jre >= 1.8.0 is needed by cassandra-4.0.4-1.noarch{noformat}
> h2. Root cause
> Package installs on CentOS and RHEL platforms has [a dependency on JRE
> 1.8+|https://github.com/apache/cassandra/blob/trunk/redhat/cassandra.spec#L49]:
> {noformat}
> Requires: jre >= 1.8.0{noformat}
> However, JRE is no longer available in Java 11. From the [JDK 11 release
> notes|https://www.oracle.com/java/technologies/javase/11-relnote-issues.html]:
> {quote}In this release, the JRE or Server JRE is no longer offered. Only the
> JDK is offered.
> {quote}
> h2. Workaround
> Override the dependency check when installing the RPM with the {{--nodeps}}
> option:
> {noformat}
> $ sudo rpm --nodeps -i cassandra-4.0.4-1.noarch.rpm {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17669) CentOS/RHEL installation requires JRE not available in Java 11
[
https://issues.apache.org/jira/browse/CASSANDRA-17669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580478#comment-17580478
]
Richard Hesse commented on CASSANDRA-17669:
---
This might work for installs, but it's broken for upgrades. Example error:
{noformat}
Resolving Dependencies
--> Running transaction check
---> Package cassandra.noarch 0:4.0.3-1 will be updated
---> Package cassandra.noarch 0:4.0.5-1 will be an update
Error: Invalid version flag: or
{noformat}
RPM 4.11 (which CentOS/RedHat uses) doesn't have boolean support.
> CentOS/RHEL installation requires JRE not available in Java 11
> --
>
> Key: CASSANDRA-17669
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17669
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Erick Ramirez
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0.5, 4.1-beta
>
>
> h2. Background
> A user [reported on Stack
> Overflow|https://stackoverflow.com/questions/72377621/] and the DataStax
> Developers [dtsx.io/discord|https://dtsx.io/discord] an issue with installing
> Cassandra when only Java 11 is installed.
> h2. Symptoms
> Attempts to install Cassandra using YUM requires Java 8:
> {noformat}
> $ sudo yum install cassandra
> Dependencies resolved.
>
> Package Architecture
> Version Repository
> Size
>
> Installing:
> cassandranoarch
> 4.0.4-1 cassandra
> 45 M
> Installing dependencies:
> java-1.8.0-openjdk x86_64
> 1:1.8.0.312.b07-2.el8_5 appstream
> 341 k
> java-1.8.0-openjdk-headless x86_64
> 1:1.8.0.312.b07-2.el8_5 appstream
> 34 M
> Installing weak dependencies:
> gtk2 x86_64
> 2.24.32-5.el8appstream
> 3.4 M
> Transaction Summary
>
> Install 4 Packages
> {noformat}
> Similarly, attempts to install the RPM results in:
> {noformat}
> $ sudo rpm -i cassandra-4.0.4-1.noarch.rpm
> warning: cassandra-4.0.4-1.noarch.rpm: Header V4 RSA/SHA256 Signature, key ID
> 7e3e87cb: NOKEY
> error: Failed dependencies:
> jre >= 1.8.0 is needed by cassandra-4.0.4-1.noarch{noformat}
> h2. Root cause
> Package installs on CentOS and RHEL platforms has [a dependency on JRE
> 1.8+|https://github.com/apache/cassandra/blob/trunk/redhat/cassandra.spec#L49]:
> {noformat}
> Requires: jre >= 1.8.0{noformat}
> However, JRE is no longer available in Java 11. From the [JDK 11 release
> notes|https://www.oracle.com/java/technologies/javase/11-relnote-issues.html]:
> {quote}In this release, the JRE or Server JRE is no longer offered. Only the
> JDK is offered.
> {quote}
> h2. Workaround
> Override the dependency check when installing the RPM with the {{--nodeps}}
> option:
> {noformat}
> $ sudo rpm --nodeps -i cassandra-4.0.4-1.noarch.rpm {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch trunk updated: ninja-fix caution image needs size, and trunk needs to be copied into content/
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-website.git
The following commit(s) were added to refs/heads/trunk by this push:
new 7183f731 ninja-fix caution image needs size, and trunk needs to be
copied into content/
7183f731 is described below
commit 7183f731a21ac1a6beea9a930fc33b108859c7e7
Author: mck
AuthorDate: Tue Aug 16 23:08:42 2022 +0200
ninja-fix caution image needs size, and trunk needs to be copied into
content/
---
site-content/docker-entrypoint.sh| 2 +-
site-content/source/modules/ROOT/pages/download.adoc | 4 +++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/site-content/docker-entrypoint.sh
b/site-content/docker-entrypoint.sh
index 6ef04e65..183e6078 100755
--- a/site-content/docker-entrypoint.sh
+++ b/site-content/docker-entrypoint.sh
@@ -238,7 +238,7 @@ prepare_site_html_for_publication() {
move_intree_document_directories "3.11" "3.11.11" "3.11.12" "3.11.13"
move_intree_document_directories "4.0" "4.0.0" "4.0.1" "4.0.2" "4.0.3"
"4.0.4" "4.0.5" "stable"
move_intree_document_directories "4.1" "latest"
-move_intree_document_directories "trunk"
+move_intree_document_directories "trunk" "4.2"
fi
popd > /dev/null
diff --git a/site-content/source/modules/ROOT/pages/download.adoc
b/site-content/source/modules/ROOT/pages/download.adoc
index e53649ab..4cdbcbfd 100644
--- a/site-content/source/modules/ROOT/pages/download.adoc
+++ b/site-content/source/modules/ROOT/pages/download.adoc
@@ -88,7 +88,9 @@ Older (unsupported) versions of Cassandra are archived
https://archive.apache.or
[caution]
-image:/assets/img/caution.svg[alt="Caution"] Debian and RedHat package
repositories have moved! Debian's `sources.list` and RedHat's `cassandra.repo`
files must be updated to point to the new repository URLs (see below).
+image:../assets/img/caution.svg[alt="Caution",width=64,height=64] Debian and
RedHat package repositories have moved!
+
+Debian's `sources.list` and RedHat's `cassandra.repo` files must be updated to
point to the new repository URLs (see below).
[example]
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17712) Remove javadocs step from CI and release process
[
https://issues.apache.org/jira/browse/CASSANDRA-17712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580460#comment-17580460
]
Stefan Miklosovic commented on CASSANDRA-17712:
---
Great idea, tired of hitting the same issue all over again, I do not know why
it is flaky. Sometimes it passes, sometimes it does not. "the right thing" is
to fix all Javadocs so they are nice and clean but that is gargantuan task at
this stage.
> Remove javadocs step from CI and release process
>
>
> Key: CASSANDRA-17712
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17712
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Berenguer Blasi
>Assignee: Brandon Williams
>Priority: Normal
>
> Currently the javadocs step is both:
> - Taking up jenkins cycles and generating a [large
> output|https://ci-cassandra.apache.org/job/Cassandra-trunk-artifacts/1313/jdk=jdk_1.8_latest,label=cassandra/consoleFull]
> in CI when building artifacts
> - Failing randomly on javadoc issues such as {{AlterTableStatement.java:135:
> error: text not allowed in element}}
> Apidocs are not being bundled, uploaded or used anywhere. Hence it would be
> best to remove javadocs generation on every CI. Mainly removing javadoc from
> artifacts and mvn-install.
--
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-17821) Add ability to log load profiles at fixed intervals
[ https://issues.apache.org/jira/browse/CASSANDRA-17821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580453#comment-17580453 ] Josh McKenzie commented on CASSANDRA-17821: --- ||Item|Link|| |PR|[link|https://github.com/apache/cassandra/pull/1793]| |JDK8 CI|[link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/270/workflows/e8703175-2aed-49c1-aa19-d51eae478339]| |JDK11 CI|[link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/270/workflows/10cb2cd8-0063-48a2-b674-d1c384efc38d]| > Add ability to log load profiles at fixed intervals > --- > > Key: CASSANDRA-17821 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17821 > Project: Cassandra > Issue Type: New Feature > Components: Tool/nodetool >Reporter: Josh McKenzie >Assignee: Josh McKenzie >Priority: Normal > > A jmx operation to run profileload and log results every X would be helpful > so operators can hot prop it on troubled nodes/clusters to identify > troublesome queries. -- 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-17821) Add ability to log load profiles at fixed intervals
[ https://issues.apache.org/jira/browse/CASSANDRA-17821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh McKenzie updated CASSANDRA-17821: -- Test and Documentation Plan: Unit testing of new timing functionality Status: Patch Available (was: Open) > Add ability to log load profiles at fixed intervals > --- > > Key: CASSANDRA-17821 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17821 > Project: Cassandra > Issue Type: New Feature > Components: Tool/nodetool >Reporter: Josh McKenzie >Assignee: Josh McKenzie >Priority: Normal > > A jmx operation to run profileload and log results every X would be helpful > so operators can hot prop it on troubled nodes/clusters to identify > troublesome queries. -- 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-17821) Add ability to log load profiles at fixed intervals
[ https://issues.apache.org/jira/browse/CASSANDRA-17821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh McKenzie updated CASSANDRA-17821: -- Change Category: Operability Complexity: Normal Status: Open (was: Triage Needed) > Add ability to log load profiles at fixed intervals > --- > > Key: CASSANDRA-17821 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17821 > Project: Cassandra > Issue Type: New Feature > Components: Tool/nodetool >Reporter: Josh McKenzie >Assignee: Josh McKenzie >Priority: Normal > > A jmx operation to run profileload and log results every X would be helpful > so operators can hot prop it on troubled nodes/clusters to identify > troublesome queries. -- 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-13010) nodetool compactionstats should say which disk a compaction is writing to
[
https://issues.apache.org/jira/browse/CASSANDRA-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580433#comment-17580433
]
Stefan Miklosovic edited comment on CASSANDRA-13010 at 8/16/22 8:04 PM:
PR: [https://github.com/apache/cassandra/pull/1791]
build:
[https://app.circleci.com/pipelines/github/instaclustr/cassandra/1207/workflows/19676308-1a92-4b2d-a16a-ea8dad9054d5]
Below is the output from the test case to see this feature in action with some
real-world load.
I renamed the flag to be "-v" or "--verbose". I am not completely sure if that
is what we want but it seem to me it is better that "more info" flag before.
I am looking for a reviewer, [~rustyrazorblade] [~brandon.williams] would you
please take a look if you dont mind and give me the feedback?
EDIT: pinging [~djoshi] and [~jjirsa] who are among the watchers as well, maybe
they would be willing to spare 10 minutes on this? :)
{code:java}
pending tasks: 37
- keyspace_24.table_25: 1
- keyspace_24.table_26: 2
- keyspace_24.table_27: 1
- keyspace_24.table_28: 2
- keyspace_24.table_29: 1
- keyspace_00.table_01: 1
- keyspace_00.table_02: 2
- keyspace_00.table_03: 1
- keyspace_00.table_04: 2
- keyspace_00.table_05: 1
- keyspace_12.table_13: 1
- keyspace_12.table_14: 2
- keyspace_12.table_15: 1
- keyspace_12.table_16: 2
- keyspace_12.table_17: 1
- keyspace_06.table_10: 1
- keyspace_06.table_11: 2
- keyspace_06.table_07: 2
- keyspace_06.table_08: 1
- keyspace_06.table_09: 2
- keyspace_18.table_21: 2
- keyspace_18.table_22: 1
- keyspace_18.table_23: 2
- keyspace_18.table_19: 2
- keyspace_18.table_20: 1
id compaction type keyspace
tablecompleted total unit progress
/my/data/dir0
7e40e800-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_00 table_01 123 123456 bytes 0.10%
7e70d1a0-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_00 table_04 123 123456 bytes 0.10%
7e529b40-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_00 table_02 123 123456 bytes 0.10%
7e638b30-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_00 table_03 123 123456 bytes 0.10%
7e7edb60-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_00 table_05 123 123456 bytes 0.10%
/my/data/dir1
7e9e9860-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_06 table_08 123 123456 bytes 0.10%
7ecea910-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_06 table_11 123 123456 bytes 0.10%
7ebf3fc0-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_06 table_10 123 123456 bytes 0.10%
7eaddaa0-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_06 table_09 123 123456 bytes 0.10%
7e8fcb50-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_06 table_07 123 123456 bytes 0.10%
/my/data/dir2
7ee194d0-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_12 table_13 123 123456 bytes 0.10%
7f1771e0-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_12 table_17 123 123456 bytes 0.10%
7f0b3ce0-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_12 table_16 123 123456 bytes 0.10%
7eef9e90-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_12 table_14 123 123456 bytes 0.10%
7eff5600-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_12 table_15 123 123456 bytes 0.10%
/my/data/dir3
7f257ba0-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_18 table_19 123 123456 bytes 0.10%
7f305110-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_18 table_20 123 123456 bytes 0.10%
7f3b2680-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_18 table_21 123 123456 bytes 0.10%
7f4845e0-1d9c-11ed-8f7d-0df44c673538
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Fix Version/s: 3.11.14 4.0.6 4.1 4.2 (was: 4.x) (was: 3.11.x) (was: 4.0.x) (was: 4.1.x) Source Control Link: https://github.com/apache/cassandra-website/commit/eaa6b3e7ab510547346d5c5584977962e0b9549a https://github.com/apache/cassandra-builds/commit/05a381784449faaa455e481ba8412a87f48dd872 https://github.com/apache/cassandra/commit/b492341eb5789889e56c55bfef6f Resolution: Fixed Status: Resolved (was: Ready to Commit) > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > Labels: pull-request-available > Fix For: 3.11.14, 4.0.6, 4.1, 4.2 > > Time Spent: 20m > Remaining Estimate: 0h > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- 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-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580440#comment-17580440 ] Michael Semb Wever commented on CASSANDRA-17748: Committed: - website [eaa6b3e7ab510547346d5c5584977962e0b9549a|https://github.com/apache/cassandra-website/commit/eaa6b3e7ab510547346d5c5584977962e0b9549a] - builds [05a381784449faaa455e481ba8412a87f48dd872|https://github.com/apache/cassandra-builds/commit/05a381784449faaa455e481ba8412a87f48dd872] - 3.11 upwards [b492341eb5789889e56c55bfef6f6a62b91eb980|https://github.com/apache/cassandra/commit/b492341eb5789889e56c55bfef6f6a62b91eb980] > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > Labels: pull-request-available > Fix For: 3.11.x, 4.0.x, 4.1.x, 4.x > > Time Spent: 20m > Remaining Estimate: 0h > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- 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-17822) NPE in org.apache.cassandra.cql3.Attributes.getTimeToLive
[
https://issues.apache.org/jira/browse/CASSANDRA-17822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580438#comment-17580438
]
Caleb Rackliffe commented on CASSANDRA-17822:
-
+1
> NPE in org.apache.cassandra.cql3.Attributes.getTimeToLive
> -
>
> Key: CASSANDRA-17822
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17822
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Semantics
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.x
>
>
> {code}
> java.lang.NullPointerException
> at org.apache.cassandra.cql3.Attributes.getTimeToLive(Attributes.java:129)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.getTimeToLive(ModificationStatement.java:237)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.makeUpdateParameters(ModificationStatement.java:833)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.makeUpdateParameters(ModificationStatement.java:799)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.addUpdates(ModificationStatement.java:736)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.getMutations(ModificationStatement.java:689)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithoutCondition(ModificationStatement.java:470)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:454)
>at
> org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:255)
>at
> org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:716)
>at
> org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:678)
>at
> org.apache.cassandra.transport.messages.ExecuteMessage.execute(ExecuteMessage.java:160)
>at
> org.apache.cassandra.transport.Message$Request.execute(Message.java:242)
>at
> org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:142)
>at
> org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:158)
>at
> org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:181)
>at
> org.apache.cassandra.transport.Dispatcher.lambda$dispatch$1(Dispatcher.java:108)
>at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
>at
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
>at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:119)
>at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
>at java.base/java.lang.Thread.run(Thread.java:834)
> {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 cassandra-3.11 updated: Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/cassandra-3.11 by this push: new b492341eb5 Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io b492341eb5 is described below commit b492341eb5789889e56c55bfef6f6a62b91eb980 Author: Mick Semb Wever AuthorDate: Mon Jul 25 13:02:47 2022 +0200 Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io patch by Mick Semb Wever; reviewed by Brandon Williams for CASSANDRA-17748 --- doc/modules/cassandra/examples/BASH/add_repo_keys.sh| 2 +- doc/modules/cassandra/examples/BASH/get_deb_package.sh | 4 ++-- doc/modules/cassandra/examples/RESULTS/add_yum_repo.result | 2 +- doc/modules/cassandra/pages/getting_started/installing.adoc | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/modules/cassandra/examples/BASH/add_repo_keys.sh b/doc/modules/cassandra/examples/BASH/add_repo_keys.sh index cdb5881e56..4c1d5f1777 100644 --- a/doc/modules/cassandra/examples/BASH/add_repo_keys.sh +++ b/doc/modules/cassandra/examples/BASH/add_repo_keys.sh @@ -1 +1 @@ -$ curl https://www.apache.org/dist/cassandra/KEYS | sudo apt-key add - +$ curl https://downloads.apache.org/cassandra/KEYS | sudo apt-key add - diff --git a/doc/modules/cassandra/examples/BASH/get_deb_package.sh b/doc/modules/cassandra/examples/BASH/get_deb_package.sh index f52e72c132..0b866a8310 100644 --- a/doc/modules/cassandra/examples/BASH/get_deb_package.sh +++ b/doc/modules/cassandra/examples/BASH/get_deb_package.sh @@ -1,2 +1,2 @@ -$ echo "deb http://www.apache.org/dist/cassandra/debian 311x main" | sudo tee -a /etc/apt/sources.list.d/cassandra.sources.list -deb http://www.apache.org/dist/cassandra/debian 311x main +$ echo "deb https://debian.cassandra.apache.org 311x main" | sudo tee -a /etc/apt/sources.list.d/cassandra.sources.list +deb https://debian.cassandra.apache.org 311x main diff --git a/doc/modules/cassandra/examples/RESULTS/add_yum_repo.result b/doc/modules/cassandra/examples/RESULTS/add_yum_repo.result index 8fdb78c9a4..47ff95f355 100644 --- a/doc/modules/cassandra/examples/RESULTS/add_yum_repo.result +++ b/doc/modules/cassandra/examples/RESULTS/add_yum_repo.result @@ -1,6 +1,6 @@ [cassandra] name=Apache Cassandra -baseurl=https://downloads.apache.org/cassandra/redhat/311x/ +baseurl=https://redhat.cassandra.apache.org/311x/ gpgcheck=1 repo_gpgcheck=1 gpgkey=https://downloads.apache.org/cassandra/KEYS diff --git a/doc/modules/cassandra/pages/getting_started/installing.adoc b/doc/modules/cassandra/pages/getting_started/installing.adoc index 668dbee78d..96dbe520a7 100644 --- a/doc/modules/cassandra/pages/getting_started/installing.adoc +++ b/doc/modules/cassandra/pages/getting_started/installing.adoc @@ -72,7 +72,7 @@ will install the binaries and configuration files as the `cassandra` OS user. include::example$BASH/docker_pull.sh[] -This `docker pull` command will get the specified version of the official +This `docker pull` command will get the specified version of the 'Docker Official' Apache Cassandra image available from the https://hub.docker.com/_/cassandra[Dockerhub]. [arabic, start=2] - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-3.11' into cassandra-4.0
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 5fafa709fb3dbcc0c819f67a08027c4ca83a7c14 Merge: 6591048051 b492341eb5 Author: Mick Semb Wever AuthorDate: Tue Aug 16 21:46:14 2022 +0200 Merge branch 'cassandra-3.11' into cassandra-4.0 doc/modules/cassandra/examples/BASH/add_repo_keys.sh| 2 +- doc/modules/cassandra/examples/BASH/get_deb_package.sh | 4 ++-- doc/modules/cassandra/examples/RESULTS/add_yum_repo.result | 2 +- doc/modules/cassandra/pages/getting_started/installing.adoc | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --cc doc/modules/cassandra/examples/BASH/get_deb_package.sh index 891bed6427,0b866a8310..544512280a --- a/doc/modules/cassandra/examples/BASH/get_deb_package.sh +++ b/doc/modules/cassandra/examples/BASH/get_deb_package.sh @@@ -1,2 -1,2 +1,2 @@@ - $ echo "deb http://www.apache.org/dist/cassandra/debian 40x main" | sudo tee -a /etc/apt/sources.list.d/cassandra.sources.list - deb http://www.apache.org/dist/cassandra/debian 40x main -$ echo "deb https://debian.cassandra.apache.org 311x main" | sudo tee -a /etc/apt/sources.list.d/cassandra.sources.list -deb https://debian.cassandra.apache.org 311x main ++$ echo "deb https://debian.cassandra.apache.org 40x main" | sudo tee -a /etc/apt/sources.list.d/cassandra.sources.list ++deb https://debian.cassandra.apache.org 40x main diff --cc doc/modules/cassandra/examples/RESULTS/add_yum_repo.result index ba06f540f3,47ff95f355..24409f3328 --- a/doc/modules/cassandra/examples/RESULTS/add_yum_repo.result +++ b/doc/modules/cassandra/examples/RESULTS/add_yum_repo.result @@@ -1,6 -1,6 +1,6 @@@ [cassandra] name=Apache Cassandra - baseurl=https://downloads.apache.org/cassandra/redhat/40x/ -baseurl=https://redhat.cassandra.apache.org/311x/ ++baseurl=https://redhat.cassandra.apache.org/40x/ gpgcheck=1 repo_gpgcheck=1 gpgkey=https://downloads.apache.org/cassandra/KEYS diff --cc doc/modules/cassandra/pages/getting_started/installing.adoc index 77e1e6525a,96dbe520a7..c8ddcd0095 --- a/doc/modules/cassandra/pages/getting_started/installing.adoc +++ b/doc/modules/cassandra/pages/getting_started/installing.adoc @@@ -76,7 -72,7 +76,7 @@@ will install the binaries and configura include::example$BASH/docker_pull.sh[] - This `docker pull` command will get the latest version of the official -This `docker pull` command will get the specified version of the 'Docker Official' ++This `docker pull` command will get the latest version of the 'Docker Official' Apache Cassandra image available from the https://hub.docker.com/_/cassandra[Dockerhub]. [arabic, start=2] - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.0' into cassandra-4.1
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit e02923305cfd204e81d5290877c7174e5d6ce539 Merge: 6405a75dd8 5fafa709fb Author: Mick Semb Wever AuthorDate: Tue Aug 16 21:47:05 2022 +0200 Merge branch 'cassandra-4.0' into cassandra-4.1 doc/antora.yml | 4 ++-- doc/modules/cassandra/examples/BASH/add_repo_keys.sh| 2 +- doc/modules/cassandra/examples/BASH/get_deb_package.sh | 4 ++-- doc/modules/cassandra/examples/RESULTS/add_yum_repo.result | 2 +- doc/modules/cassandra/pages/getting_started/installing.adoc | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --cc doc/antora.yml index f9fa1480d1,771311bfd9..08ed5e29ea --- a/doc/antora.yml +++ b/doc/antora.yml @@@ -1,6 -1,6 +1,6 @@@ name: Cassandra - version: 'trunk' - display_version: 'trunk' -version: '4.0' -display_version: '4.0' ++version: '4.1' ++display_version: '4.1' asciidoc: attributes: cass_url: 'http://cassandra.apache.org/' diff --cc doc/modules/cassandra/examples/BASH/get_deb_package.sh index 891bed6427,544512280a..69648e8928 --- a/doc/modules/cassandra/examples/BASH/get_deb_package.sh +++ b/doc/modules/cassandra/examples/BASH/get_deb_package.sh @@@ -1,2 -1,2 +1,2 @@@ - $ echo "deb http://www.apache.org/dist/cassandra/debian 40x main" | sudo tee -a /etc/apt/sources.list.d/cassandra.sources.list - deb http://www.apache.org/dist/cassandra/debian 40x main -$ echo "deb https://debian.cassandra.apache.org 40x main" | sudo tee -a /etc/apt/sources.list.d/cassandra.sources.list -deb https://debian.cassandra.apache.org 40x main ++$ echo "deb https://debian.cassandra.apache.org 41x main" | sudo tee -a /etc/apt/sources.list.d/cassandra.sources.list ++deb https://debian.cassandra.apache.org 41x main diff --cc doc/modules/cassandra/examples/RESULTS/add_yum_repo.result index ba06f540f3,24409f3328..6fe704aa85 --- a/doc/modules/cassandra/examples/RESULTS/add_yum_repo.result +++ b/doc/modules/cassandra/examples/RESULTS/add_yum_repo.result @@@ -1,6 -1,6 +1,6 @@@ [cassandra] name=Apache Cassandra - baseurl=https://downloads.apache.org/cassandra/redhat/40x/ -baseurl=https://redhat.cassandra.apache.org/40x/ ++baseurl=https://redhat.cassandra.apache.org/41x/ gpgcheck=1 repo_gpgcheck=1 gpgkey=https://downloads.apache.org/cassandra/KEYS - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.1' 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 cbc127ab79d75a87a0ded714f41218c4075d712e Merge: 4b7069c06c e02923305c Author: Mick Semb Wever AuthorDate: Tue Aug 16 21:49:06 2022 +0200 Merge branch 'cassandra-4.1' into trunk doc/modules/cassandra/examples/BASH/add_repo_keys.sh| 2 +- doc/modules/cassandra/examples/BASH/get_deb_package.sh | 4 ++-- doc/modules/cassandra/examples/RESULTS/add_yum_repo.result | 2 +- doc/modules/cassandra/pages/getting_started/installing.adoc | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --cc doc/modules/cassandra/examples/BASH/get_deb_package.sh index 891bed6427,69648e8928..8c1b07bb1e --- a/doc/modules/cassandra/examples/BASH/get_deb_package.sh +++ b/doc/modules/cassandra/examples/BASH/get_deb_package.sh @@@ -1,2 -1,2 +1,2 @@@ - $ echo "deb http://www.apache.org/dist/cassandra/debian 40x main" | sudo tee -a /etc/apt/sources.list.d/cassandra.sources.list - deb http://www.apache.org/dist/cassandra/debian 40x main -$ echo "deb https://debian.cassandra.apache.org 41x main" | sudo tee -a /etc/apt/sources.list.d/cassandra.sources.list -deb https://debian.cassandra.apache.org 41x main ++$ echo "deb https://debian.cassandra.apache.org 42x main" | sudo tee -a /etc/apt/sources.list.d/cassandra.sources.list ++deb https://debian.cassandra.apache.org 42x main diff --cc doc/modules/cassandra/examples/RESULTS/add_yum_repo.result index ba06f540f3,6fe704aa85..4b188e1920 --- a/doc/modules/cassandra/examples/RESULTS/add_yum_repo.result +++ b/doc/modules/cassandra/examples/RESULTS/add_yum_repo.result @@@ -1,6 -1,6 +1,6 @@@ [cassandra] name=Apache Cassandra - baseurl=https://downloads.apache.org/cassandra/redhat/40x/ -baseurl=https://redhat.cassandra.apache.org/41x/ ++baseurl=https://redhat.cassandra.apache.org/42x/ gpgcheck=1 repo_gpgcheck=1 gpgkey=https://downloads.apache.org/cassandra/KEYS - 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 (6405a75dd8 -> e02923305c)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 6405a75dd8 Merge branch 'cassandra-4.0' into cassandra-4.1 new b492341eb5 Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io new 5fafa709fb Merge branch 'cassandra-3.11' into cassandra-4.0 new e02923305c Merge branch 'cassandra-4.0' into cassandra-4.1 The 3 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: doc/antora.yml | 4 ++-- doc/modules/cassandra/examples/BASH/add_repo_keys.sh| 2 +- doc/modules/cassandra/examples/BASH/get_deb_package.sh | 4 ++-- doc/modules/cassandra/examples/RESULTS/add_yum_repo.result | 2 +- doc/modules/cassandra/pages/getting_started/installing.adoc | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (4b7069c06c -> cbc127ab79)
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 4b7069c06c Add guardrail for column size new b492341eb5 Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io new 5fafa709fb Merge branch 'cassandra-3.11' into cassandra-4.0 new e02923305c Merge branch 'cassandra-4.0' into cassandra-4.1 new cbc127ab79 Merge branch 'cassandra-4.1' into trunk The 4 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: doc/modules/cassandra/examples/BASH/add_repo_keys.sh| 2 +- doc/modules/cassandra/examples/BASH/get_deb_package.sh | 4 ++-- doc/modules/cassandra/examples/RESULTS/add_yum_repo.result | 2 +- doc/modules/cassandra/pages/getting_started/installing.adoc | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) - 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 (6591048051 -> 5fafa709fb)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 6591048051 Flaky DescribeStatementTest new b492341eb5 Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io new 5fafa709fb Merge branch 'cassandra-3.11' into cassandra-4.0 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: doc/modules/cassandra/examples/BASH/add_repo_keys.sh| 2 +- doc/modules/cassandra/examples/BASH/get_deb_package.sh | 4 ++-- doc/modules/cassandra/examples/RESULTS/add_yum_repo.result | 2 +- doc/modules/cassandra/pages/getting_started/installing.adoc | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-13010) nodetool compactionstats should say which disk a compaction is writing to
[
https://issues.apache.org/jira/browse/CASSANDRA-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580433#comment-17580433
]
Stefan Miklosovic edited comment on CASSANDRA-13010 at 8/16/22 7:52 PM:
PR: [https://github.com/apache/cassandra/pull/1791]
build:
[https://app.circleci.com/pipelines/github/instaclustr/cassandra/1207/workflows/19676308-1a92-4b2d-a16a-ea8dad9054d5]
Below is the output from the test case to see this feature in action with some
real-world load.
I renamed the flag to be "-v" or "--verbose". I am not completely sure if that
is what we want but it seem to me it is better that "more info" flag before.
I am looking for a reviewer, [~rustyrazorblade] [~brandon.williams] would you
please take a look if you dont mind and give me the feedback?
{code:java}
pending tasks: 37
- keyspace_24.table_25: 1
- keyspace_24.table_26: 2
- keyspace_24.table_27: 1
- keyspace_24.table_28: 2
- keyspace_24.table_29: 1
- keyspace_00.table_01: 1
- keyspace_00.table_02: 2
- keyspace_00.table_03: 1
- keyspace_00.table_04: 2
- keyspace_00.table_05: 1
- keyspace_12.table_13: 1
- keyspace_12.table_14: 2
- keyspace_12.table_15: 1
- keyspace_12.table_16: 2
- keyspace_12.table_17: 1
- keyspace_06.table_10: 1
- keyspace_06.table_11: 2
- keyspace_06.table_07: 2
- keyspace_06.table_08: 1
- keyspace_06.table_09: 2
- keyspace_18.table_21: 2
- keyspace_18.table_22: 1
- keyspace_18.table_23: 2
- keyspace_18.table_19: 2
- keyspace_18.table_20: 1
id compaction type keyspace
tablecompleted total unit progress
/my/data/dir0
7e40e800-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_00 table_01 123 123456 bytes 0.10%
7e70d1a0-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_00 table_04 123 123456 bytes 0.10%
7e529b40-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_00 table_02 123 123456 bytes 0.10%
7e638b30-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_00 table_03 123 123456 bytes 0.10%
7e7edb60-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_00 table_05 123 123456 bytes 0.10%
/my/data/dir1
7e9e9860-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_06 table_08 123 123456 bytes 0.10%
7ecea910-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_06 table_11 123 123456 bytes 0.10%
7ebf3fc0-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_06 table_10 123 123456 bytes 0.10%
7eaddaa0-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_06 table_09 123 123456 bytes 0.10%
7e8fcb50-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_06 table_07 123 123456 bytes 0.10%
/my/data/dir2
7ee194d0-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_12 table_13 123 123456 bytes 0.10%
7f1771e0-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_12 table_17 123 123456 bytes 0.10%
7f0b3ce0-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_12 table_16 123 123456 bytes 0.10%
7eef9e90-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_12 table_14 123 123456 bytes 0.10%
7eff5600-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_12 table_15 123 123456 bytes 0.10%
/my/data/dir3
7f257ba0-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_18 table_19 123 123456 bytes 0.10%
7f305110-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_18 table_20 123 123456 bytes 0.10%
7f3b2680-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_18 table_21 123 123456 bytes 0.10%
7f4845e0-1d9c-11ed-8f7d-0df44c673538 Compaction
keyspace_18 table_22 123 123456 bytes 0.10%
7f560180-1d9c-11ed-8f7d-0df44c673538 Compaction
[jira] [Updated] (CASSANDRA-13010) nodetool compactionstats should say which disk a compaction is writing to
[ https://issues.apache.org/jira/browse/CASSANDRA-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-13010: -- Test and Documentation Plan: https://app.circleci.com/pipelines/github/instaclustr/cassandra/1207/workflows/19676308-1a92-4b2d-a16a-ea8dad9054d5 Status: Patch Available (was: In Progress) PR: [https://github.com/apache/cassandra/pull/1791] build: [https://app.circleci.com/pipelines/github/instaclustr/cassandra/1207/workflows/19676308-1a92-4b2d-a16a-ea8dad9054d5] > nodetool compactionstats should say which disk a compaction is writing to > - > > Key: CASSANDRA-13010 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13010 > Project: Cassandra > Issue Type: New Feature > Components: Local/Compaction, Tool/nodetool >Reporter: Jon Haddad >Assignee: Stefan Miklosovic >Priority: Normal > Labels: 4.0-feature-freeze-review-requested > Fix For: 4.x > > Attachments: cleanup.png, multiple operations.png > > -- 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-builds] branch trunk updated: Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
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-builds.git
The following commit(s) were added to refs/heads/trunk by this push:
new 05a3817 Move deb/rpm repositories from dist/downloads .a.o to
apache.jfrog.io
05a3817 is described below
commit 05a381784449faaa455e481ba8412a87f48dd872
Author: Mick Semb Wever
AuthorDate: Thu Jul 14 08:31:19 2022 +0100
Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
patch by Mick Semb Wever; reviewed by Brandon Williams for CASSANDRA-17748
---
cassandra-release/finish_release.sh | 54 +++--
1 file changed, 22 insertions(+), 32 deletions(-)
diff --git a/cassandra-release/finish_release.sh
b/cassandra-release/finish_release.sh
index fdfac44..d08029d 100755
--- a/cassandra-release/finish_release.sh
+++ b/cassandra-release/finish_release.sh
@@ -156,6 +156,21 @@ echo "Apache Cassandra $release release" > "_tmp_msg_"
execute "svn mv -F _tmp_msg_
https://dist.apache.org/repos/dist/dev/cassandra/$release
https://dist.apache.org/repos/dist/release/cassandra/;
rm _tmp_msg_
+#
+# Determine deb/rpm repo series
+#
+
+idx=`expr index "$release" -`
+if [ $idx -eq 0 ]
+then
+release_short=${release}
+else
+release_short=${release:0:$((idx-1))}
+fi
+release_major=$(echo ${release_short} | cut -d '.' -f 1)
+release_minor=$(echo ${release_short} | cut -d '.' -f 2)
+repo_series="${release_major}${release_minor}x"
+
#
# Public deploy the Debian packages
#
@@ -183,34 +198,9 @@ for i in $(find ${debian_dist_dir}/ -mindepth 2 -type f
-mtime -10 -not -path "*
done
cd $tmp_dir
-# Move to dist release top-level debian directory
-idx=`expr index "$release" -`
-if [ $idx -eq 0 ]
-then
-release_short=${release}
-else
-release_short=${release:0:$((idx-1))}
-fi
-release_major=$(echo ${release_short} | cut -d '.' -f 1)
-release_minor=$(echo ${release_short} | cut -d '.' -f 2)
-repo_series="${release_major}${release_minor}x"
-
-echo "performing a server-side: svn mv
^/dist/release/cassandra/$release/debian/pool/main/c/cassandra/*
^/dist/release/cassandra/debian/pool/main/c/cassandra/"
-
-for f in $( svn list
"https://dist.apache.org/repos/dist/release/cassandra/$release/debian/pool/main/c/cassandra/;
)
-do
- echo "Apache Cassandra $release debian artifact $f" > "_tmp_msg_"
- echo "svn mv -F _tmp_msg_
https://dist.apache.org/repos/dist/release/cassandra/$release/debian/pool/main/c/cassandra/$f
https://dist.apache.org/repos/dist/release/cassandra/debian/pool/main/c/cassandra/;
- execute "svn mv -F _tmp_msg_
https://dist.apache.org/repos/dist/release/cassandra/$release/debian/pool/main/c/cassandra/$f
https://dist.apache.org/repos/dist/release/cassandra/debian/pool/main/c/cassandra/;
-done
-
+# Remove dist debian directory. Official download location is
https://debian.cassandra.apache.org
echo "Apache Cassandra $release debian artifacts" > "_tmp_msg_"
-if curl --output /dev/null --silent --head --fail
"https://dist.apache.org/repos/dist/release/cassandra/debian/dists/$repo_series;
; then
-execute "svn rm -F _tmp_msg_
https://dist.apache.org/repos/dist/release/cassandra/debian/dists/$repo_series;
-fi
-execute "svn mv -F _tmp_msg_
https://dist.apache.org/repos/dist/release/cassandra/$release/debian/dists/$repo_series
https://dist.apache.org/repos/dist/release/cassandra/debian/dists/;
-execute "svn rm -F _tmp_msg_
https://dist.apache.org/repos/dist/release/cassandra/$release/debian/dists;
-execute "svn rm -F _tmp_msg_
https://dist.apache.org/repos/dist/release/cassandra/$release/debian/pool;
+execute "svn rm -F _tmp_msg_
https://dist.apache.org/repos/dist/release/cassandra/$release/debian;
#
# Public deploy the RedHat packages
@@ -238,12 +228,9 @@ for i in $(find ${redhat_dist_dir} -mindepth 1 -type f
-mtime -10 -not -path "*/
done
cd $tmp_dir
-# Move to dist release top-level redhat directory
+# Remove dist redhat directory. Official download location is
https://redhat.cassandra.apache.org
echo "Apache Cassandra $release redhat artifacts" > "_tmp_msg_"
-if curl --output /dev/null --silent --head --fail
"https://dist.apache.org/repos/dist/release/cassandra/redhat/$repo_series; ;
then
-execute "svn rm -F _tmp_msg_
https://dist.apache.org/repos/dist/release/cassandra/redhat/$repo_series;
-fi
-execute "svn mv -F _tmp_msg_
https://dist.apache.org/repos/dist/release/cassandra/$release/redhat
https://dist.apache.org/repos/dist/release/cassandra/redhat/$repo_series;
+execute "svn rm -F _tmp_msg_
https://dist.apache.org/repos/dist/release/cassandra/$release/redhat;
# Cleaning up
execute "cd $cassandra_dir"
@@ -270,6 +257,9 @@ echo "" >> $mail_file
series="${release_major}.${release_minor}"
echo "This version is a bug fix release[1] on the $series series. As always,
please pay attention to the release notes[2] and Let us know[3]
[cassandra-website] branch trunk updated: Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
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-website.git
The following commit(s) were added to refs/heads/trunk by this push:
new eaa6b3e7 Move deb/rpm repositories from dist/downloads .a.o to
apache.jfrog.io
eaa6b3e7 is described below
commit eaa6b3e7ab510547346d5c5584977962e0b9549a
Author: mck
AuthorDate: Thu Jul 14 08:27:24 2022 +0100
Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
patch by Mick Semb Wever; reviewed by Brandon Williams for CASSANDRA-17748
---
site-content/Dockerfile | 3 ++-
site-content/docker-entrypoint.sh| 8 +---
site-content/source/modules/ROOT/pages/download.adoc | 9 +++--
3 files changed, 14 insertions(+), 6 deletions(-)
diff --git a/site-content/Dockerfile b/site-content/Dockerfile
index 2993c5be..4f8204ed 100644
--- a/site-content/Dockerfile
+++ b/site-content/Dockerfile
@@ -90,7 +90,8 @@ ENV ANTORA_SITE_START_PAGE="_"
# Build from 3.11.5 as document generation for previous versions is broken.
ENV
ANTORA_CONTENT_SOURCES_CASSANDRA_URL="https://github.com/apache/cassandra.git;
-ENV ANTORA_CONTENT_SOURCES_CASSANDRA_BRANCHES="trunk cassandra-4.0
cassandra-3.11"
+ENV ANTORA_CONTENT_SOURCES_CASSANDRA_BRANCHES="trunk cassandra-4.1
cassandra-4.0 cassandra-3.11"
+# FIXME – we can't generate tags yet as in-tree doc/antora.yml doesn't specify
specifc tag versions
ENV ANTORA_CONTENT_SOURCES_CASSANDRA_TAGS=""
ENV ANTORA_CONTENT_SOURCES_CASSANDRA_START_PATH="doc"
diff --git a/site-content/docker-entrypoint.sh
b/site-content/docker-entrypoint.sh
index 584fe0f0..6ef04e65 100755
--- a/site-content/docker-entrypoint.sh
+++ b/site-content/docker-entrypoint.sh
@@ -234,9 +234,11 @@ prepare_site_html_for_publication() {
if [ "${COMMAND_GENERATE_DOCS}" = "run" ]
then
log_message "INFO" "Moving versioned documentation HTML to content/doc"
-move_intree_document_directories "3.11" "3.11.11" "3.11.12"
-move_intree_document_directories "4.0" "4.0.0" "4.0.1" "4.0.2" "4.0.3"
"stable"
-move_intree_document_directories "trunk" "4.1" "latest"
+# FIXME – we can't generate tags yet as in-tree doc/antora.yml doesn't
specify specifc tag versions, so just copy them for now (see same fixme in
Dockerfile)
+move_intree_document_directories "3.11" "3.11.11" "3.11.12" "3.11.13"
+move_intree_document_directories "4.0" "4.0.0" "4.0.1" "4.0.2" "4.0.3"
"4.0.4" "4.0.5" "stable"
+move_intree_document_directories "4.1" "latest"
+move_intree_document_directories "trunk"
fi
popd > /dev/null
diff --git a/site-content/source/modules/ROOT/pages/download.adoc
b/site-content/source/modules/ROOT/pages/download.adoc
index 830654bd..e53649ab 100644
--- a/site-content/source/modules/ROOT/pages/download.adoc
+++ b/site-content/source/modules/ROOT/pages/download.adoc
@@ -86,6 +86,11 @@ Older (unsupported) versions of Cassandra are archived
https://archive.apache.or
[openblock,inner]
--
+[caution]
+
+image:/assets/img/caution.svg[alt="Caution"] Debian and RedHat package
repositories have moved! Debian's `sources.list` and RedHat's `cassandra.repo`
files must be updated to point to the new repository URLs (see below).
+
+
[example]
@@ -99,7 +104,7 @@ Older (unsupported) versions of Cassandra are archived
https://archive.apache.or
[source]
--
-echo "deb https://downloads.apache.org/cassandra/debian 40x main" | sudo tee
-a /etc/apt/sources.list.d/cassandra.sources.list
+echo "deb https://debian.cassandra.apache.org 40x main" | sudo tee -a
/etc/apt/sources.list.d/cassandra.sources.list
--
* Add the Apache Cassandra repository keys:
@@ -168,7 +173,7 @@ and repeat `sudo apt-get update`. The actual key may be
different, you get it fr
--
[cassandra]
name=Apache Cassandra
-baseurl=https://downloads.apache.org/cassandra/redhat/40x/
+baseurl=https://redhat.cassandra.apache.org/40x/
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://downloads.apache.org/cassandra/KEYS
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Status: Ready to Commit (was: Review In Progress) > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > Labels: pull-request-available > Fix For: 3.11.x, 4.0.x, 4.1.x, 4.x > > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- 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-17748) Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io
[ https://issues.apache.org/jira/browse/CASSANDRA-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17748: --- Reviewers: Brandon Williams Status: Review In Progress (was: Patch Available) > Move deb/rpm repositories from dist/downloads .a.o to apache.jfrog.io > - > > Key: CASSANDRA-17748 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17748 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Urgent > Labels: pull-request-available > Fix For: 3.11.x, 4.0.x, 4.1.x, 4.x > > > Move our official debian and redhat repositories from downloads.apache.org to > Apache's JFrog Artifactory server at apache.jfrog.io > That is, the following URLs would be moved from > ``` > https://downloads.apache.org/cassandra/debian/ > https://downloads.apache.org/cassandra/redhat/ > ``` > to > ``` > https://apache.jfrog.io/artifactory/cassandra-deb/ > https://apache.jfrog.io/artifactory/cassandra-rpm/ > ``` > The rationale to do this is to avoid the strict opinionated checksum and > signature requirements on downloads.a.o (dist.a.o), as the debian and redhat > repositories have their own system for integrity and signing (which we > already do). > Furthermore, as these repositories and their binaries are "convenience > binaries" and not the official Cassandra source binaries, they do not need to > be on downloads.a.o and can be served from apache.jfrog.io. This is similar > to maven binaries (and docker images). Apache Arrow is already taking this > approach: https://arrow.apache.org/install/ > An advantage to using apache.frog.io is that these repositories maintain all > past patch versions on each repo series (major/minor). This has been > requested by users a number of times, for the sake of rolling back to a > previous patch version. downloads.a.o can only contain the latest version. > This will BREAK everyone's existing > `/etc/apt/sources.list.d/cassandra.sources.list` and > `/etc/yum.repos.d/cassandra.repo` files. Folk will need to update these files > to point to the new repo URLs. This would require an announcement to both > users@ and dev@. I do not know how we can avoid this breakage. We could put > in a simple README.md in the original URL locations explaining the breakage > and how to fix. -- 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-17822) NPE in org.apache.cassandra.cql3.Attributes.getTimeToLive
[
https://issues.apache.org/jira/browse/CASSANDRA-17822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-17822:
Reviewers: Caleb Rackliffe, Caleb Rackliffe
Caleb Rackliffe, Caleb Rackliffe (was: Caleb Rackliffe)
Status: Review In Progress (was: Patch Available)
> NPE in org.apache.cassandra.cql3.Attributes.getTimeToLive
> -
>
> Key: CASSANDRA-17822
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17822
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Semantics
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.x
>
>
> {code}
> java.lang.NullPointerException
> at org.apache.cassandra.cql3.Attributes.getTimeToLive(Attributes.java:129)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.getTimeToLive(ModificationStatement.java:237)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.makeUpdateParameters(ModificationStatement.java:833)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.makeUpdateParameters(ModificationStatement.java:799)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.addUpdates(ModificationStatement.java:736)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.getMutations(ModificationStatement.java:689)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithoutCondition(ModificationStatement.java:470)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:454)
>at
> org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:255)
>at
> org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:716)
>at
> org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:678)
>at
> org.apache.cassandra.transport.messages.ExecuteMessage.execute(ExecuteMessage.java:160)
>at
> org.apache.cassandra.transport.Message$Request.execute(Message.java:242)
>at
> org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:142)
>at
> org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:158)
>at
> org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:181)
>at
> org.apache.cassandra.transport.Dispatcher.lambda$dispatch$1(Dispatcher.java:108)
>at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
>at
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
>at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:119)
>at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
>at java.base/java.lang.Thread.run(Thread.java:834)
> {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-17111) CEP-15: (Accord) Transaction dependencies must include at most the txnId
[
https://issues.apache.org/jira/browse/CASSANDRA-17111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17111:
--
Status: Review In Progress (was: Patch Available)
> CEP-15: (Accord) Transaction dependencies must include at most the txnId
>
>
> Key: CASSANDRA-17111
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17111
> Project: Cassandra
> Issue Type: New Feature
> Components: Accord
>Reporter: Benedict Elliott Smith
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
>
> Today we must ship the entire transaction as part of the dependencies we
> share. This is very costly. We may ship only the {{txnId,primary shard key}}
> if we modify recovery to first discover the original transaction, or
> invalidate it if it cannot be found.
--
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-17111) CEP-15: (Accord) Transaction dependencies must include at most the txnId
[
https://issues.apache.org/jira/browse/CASSANDRA-17111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17111:
--
Status: Ready to Commit (was: Review In Progress)
+1
> CEP-15: (Accord) Transaction dependencies must include at most the txnId
>
>
> Key: CASSANDRA-17111
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17111
> Project: Cassandra
> Issue Type: New Feature
> Components: Accord
>Reporter: Benedict Elliott Smith
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
>
> Today we must ship the entire transaction as part of the dependencies we
> share. This is very costly. We may ship only the {{txnId,primary shard key}}
> if we modify recovery to first discover the original transaction, or
> invalidate it if it cannot be found.
--
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-17111) CEP-15: (Accord) Transaction dependencies must include at most the txnId
[
https://issues.apache.org/jira/browse/CASSANDRA-17111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17111:
--
Test and Documentation Plan: tests
Status: Patch Available (was: Open)
> CEP-15: (Accord) Transaction dependencies must include at most the txnId
>
>
> Key: CASSANDRA-17111
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17111
> Project: Cassandra
> Issue Type: New Feature
> Components: Accord
>Reporter: Benedict Elliott Smith
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
>
> Today we must ship the entire transaction as part of the dependencies we
> share. This is very costly. We may ship only the {{txnId,primary shard key}}
> if we modify recovery to first discover the original transaction, or
> invalidate it if it cannot be found.
--
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-17111) CEP-15: (Accord) Transaction dependencies must include at most the txnId
[
https://issues.apache.org/jira/browse/CASSANDRA-17111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell reassigned CASSANDRA-17111:
-
Assignee: Benedict Elliott Smith
> CEP-15: (Accord) Transaction dependencies must include at most the txnId
>
>
> Key: CASSANDRA-17111
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17111
> Project: Cassandra
> Issue Type: New Feature
> Components: Accord
>Reporter: Benedict Elliott Smith
>Assignee: Benedict Elliott Smith
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
>
> Today we must ship the entire transaction as part of the dependencies we
> share. This is very costly. We may ship only the {{txnId,primary shard key}}
> if we modify recovery to first discover the original transaction, or
> invalidate it if it cannot be found.
--
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-17111) CEP-15: (Accord) Transaction dependencies must include at most the txnId
[
https://issues.apache.org/jira/browse/CASSANDRA-17111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17111:
--
Change Category: Performance
Complexity: Normal
Component/s: Accord
Fix Version/s: NA
Reviewers: David Capwell
Status: Open (was: Triage Needed)
> CEP-15: (Accord) Transaction dependencies must include at most the txnId
>
>
> Key: CASSANDRA-17111
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17111
> Project: Cassandra
> Issue Type: New Feature
> Components: Accord
>Reporter: Benedict Elliott Smith
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
>
> Today we must ship the entire transaction as part of the dependencies we
> share. This is very costly. We may ship only the {{txnId,primary shard key}}
> if we modify recovery to first discover the original transaction, or
> invalidate it if it cannot be found.
--
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-17822) NPE in org.apache.cassandra.cql3.Attributes.getTimeToLive
[
https://issues.apache.org/jira/browse/CASSANDRA-17822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17822:
--
Test and Documentation Plan: new tests
Status: Patch Available (was: Open)
> NPE in org.apache.cassandra.cql3.Attributes.getTimeToLive
> -
>
> Key: CASSANDRA-17822
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17822
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Semantics
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.x
>
>
> {code}
> java.lang.NullPointerException
> at org.apache.cassandra.cql3.Attributes.getTimeToLive(Attributes.java:129)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.getTimeToLive(ModificationStatement.java:237)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.makeUpdateParameters(ModificationStatement.java:833)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.makeUpdateParameters(ModificationStatement.java:799)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.addUpdates(ModificationStatement.java:736)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.getMutations(ModificationStatement.java:689)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithoutCondition(ModificationStatement.java:470)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:454)
>at
> org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:255)
>at
> org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:716)
>at
> org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:678)
>at
> org.apache.cassandra.transport.messages.ExecuteMessage.execute(ExecuteMessage.java:160)
>at
> org.apache.cassandra.transport.Message$Request.execute(Message.java:242)
>at
> org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:142)
>at
> org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:158)
>at
> org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:181)
>at
> org.apache.cassandra.transport.Dispatcher.lambda$dispatch$1(Dispatcher.java:108)
>at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
>at
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
>at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:119)
>at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
>at java.base/java.lang.Thread.run(Thread.java:834)
> {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-17822) NPE in org.apache.cassandra.cql3.Attributes.getTimeToLive
[
https://issues.apache.org/jira/browse/CASSANDRA-17822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17822:
--
Bug Category: Parent values: Correctness(12982)Level 1 values: API /
Semantic Implementation(12988)
Complexity: Low Hanging Fruit
Discovered By: User Report
Fix Version/s: 4.x
Severity: Low
Status: Open (was: Triage Needed)
> NPE in org.apache.cassandra.cql3.Attributes.getTimeToLive
> -
>
> Key: CASSANDRA-17822
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17822
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Semantics
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.x
>
>
> {code}
> java.lang.NullPointerException
> at org.apache.cassandra.cql3.Attributes.getTimeToLive(Attributes.java:129)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.getTimeToLive(ModificationStatement.java:237)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.makeUpdateParameters(ModificationStatement.java:833)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.makeUpdateParameters(ModificationStatement.java:799)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.addUpdates(ModificationStatement.java:736)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.getMutations(ModificationStatement.java:689)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithoutCondition(ModificationStatement.java:470)
>at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:454)
>at
> org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:255)
>at
> org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:716)
>at
> org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:678)
>at
> org.apache.cassandra.transport.messages.ExecuteMessage.execute(ExecuteMessage.java:160)
>at
> org.apache.cassandra.transport.Message$Request.execute(Message.java:242)
>at
> org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:142)
>at
> org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:158)
>at
> org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:181)
>at
> org.apache.cassandra.transport.Dispatcher.lambda$dispatch$1(Dispatcher.java:108)
>at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
>at
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
>at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:119)
>at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
>at java.base/java.lang.Thread.run(Thread.java:834)
> {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] [Created] (CASSANDRA-17822) NPE in org.apache.cassandra.cql3.Attributes.getTimeToLive
David Capwell created CASSANDRA-17822:
-
Summary: NPE in org.apache.cassandra.cql3.Attributes.getTimeToLive
Key: CASSANDRA-17822
URL: https://issues.apache.org/jira/browse/CASSANDRA-17822
Project: Cassandra
Issue Type: Bug
Components: CQL/Semantics
Reporter: David Capwell
Assignee: David Capwell
{code}
java.lang.NullPointerException
at org.apache.cassandra.cql3.Attributes.getTimeToLive(Attributes.java:129)
at
org.apache.cassandra.cql3.statements.ModificationStatement.getTimeToLive(ModificationStatement.java:237)
at
org.apache.cassandra.cql3.statements.ModificationStatement.makeUpdateParameters(ModificationStatement.java:833)
at
org.apache.cassandra.cql3.statements.ModificationStatement.makeUpdateParameters(ModificationStatement.java:799)
at
org.apache.cassandra.cql3.statements.ModificationStatement.addUpdates(ModificationStatement.java:736)
at
org.apache.cassandra.cql3.statements.ModificationStatement.getMutations(ModificationStatement.java:689)
at
org.apache.cassandra.cql3.statements.ModificationStatement.executeWithoutCondition(ModificationStatement.java:470)
at
org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:454)
at
org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:255)
at
org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:716)
at
org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:678)
at
org.apache.cassandra.transport.messages.ExecuteMessage.execute(ExecuteMessage.java:160)
at
org.apache.cassandra.transport.Message$Request.execute(Message.java:242)
at
org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:142)
at
org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:158)
at
org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:181)
at
org.apache.cassandra.transport.Dispatcher.lambda$dispatch$1(Dispatcher.java:108)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at
org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:119)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:834)
{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-17712) Remove javadocs step from CI and release process
[
https://issues.apache.org/jira/browse/CASSANDRA-17712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580418#comment-17580418
]
Brandon Williams commented on CASSANDRA-17712:
--
||Branch||CI||
|[3.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17712-3.0]|[circle|https://app.circleci.com/pipelines/github/driftx/cassandra/575/workflows/c448c0af-31aa-4951-8ba3-10f33e95115f]|
|[3.11|https://github.com/driftx/cassandra/tree/CASSANDRA-17712-3.11]|[circle|https://app.circleci.com/pipelines/github/driftx/cassandra/577/workflows/b9d9f03c-a311-4503-a6a7-583aab71b8ac]|
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17712-4.0]|[circle|https://app.circleci.com/pipelines/github/driftx/cassandra/578/workflows/005be4dd-992e-44eb-a138-a1e8714855a6]|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-17712-4.1]|[circle|https://app.circleci.com/pipelines/github/driftx/cassandra/579/workflows/263ce121-e6d2-4423-9fd4-a26cf074ebee]|
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-17712-trunk]|[circle|https://app.circleci.com/pipelines/github/driftx/cassandra/576/workflows/a71dbed3-bd3c-439a-8a70-5e035135edf5]|
> Remove javadocs step from CI and release process
>
>
> Key: CASSANDRA-17712
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17712
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Berenguer Blasi
>Assignee: Brandon Williams
>Priority: Normal
>
> Currently the javadocs step is both:
> - Taking up jenkins cycles and generating a [large
> output|https://ci-cassandra.apache.org/job/Cassandra-trunk-artifacts/1313/jdk=jdk_1.8_latest,label=cassandra/consoleFull]
> in CI when building artifacts
> - Failing randomly on javadoc issues such as {{AlterTableStatement.java:135:
> error: text not allowed in element}}
> Apidocs are not being bundled, uploaded or used anywhere. Hence it would be
> best to remove javadocs generation on every CI. Mainly removing javadoc from
> artifacts and mvn-install.
--
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-17712) Remove javadocs step from CI and release process
[
https://issues.apache.org/jira/browse/CASSANDRA-17712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17712:
-
Test and Documentation Plan: run CI
Status: Patch Available (was: Open)
> Remove javadocs step from CI and release process
>
>
> Key: CASSANDRA-17712
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17712
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Berenguer Blasi
>Assignee: Brandon Williams
>Priority: Normal
>
> Currently the javadocs step is both:
> - Taking up jenkins cycles and generating a [large
> output|https://ci-cassandra.apache.org/job/Cassandra-trunk-artifacts/1313/jdk=jdk_1.8_latest,label=cassandra/consoleFull]
> in CI when building artifacts
> - Failing randomly on javadoc issues such as {{AlterTableStatement.java:135:
> error: text not allowed in element}}
> Apidocs are not being bundled, uploaded or used anywhere. Hence it would be
> best to remove javadocs generation on every CI. Mainly removing javadoc from
> artifacts and mvn-install.
--
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-17712) Remove javadocs step from CI and release process
[
https://issues.apache.org/jira/browse/CASSANDRA-17712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams reassigned CASSANDRA-17712:
Assignee: Brandon Williams
> Remove javadocs step from CI and release process
>
>
> Key: CASSANDRA-17712
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17712
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Berenguer Blasi
>Assignee: Brandon Williams
>Priority: Normal
>
> Currently the javadocs step is both:
> - Taking up jenkins cycles and generating a [large
> output|https://ci-cassandra.apache.org/job/Cassandra-trunk-artifacts/1313/jdk=jdk_1.8_latest,label=cassandra/consoleFull]
> in CI when building artifacts
> - Failing randomly on javadoc issues such as {{AlterTableStatement.java:135:
> error: text not allowed in element}}
> Apidocs are not being bundled, uploaded or used anywhere. Hence it would be
> best to remove javadocs generation on every CI. Mainly removing javadoc from
> artifacts and mvn-install.
--
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-17817) Fix upgrade test test_collection_function on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17817: - Fix Version/s: 4.2 (was: 4.x) Since Version: NA Source Control Link: https://github.com/apache/cassandra-dtest/commit/b91999cad0700024e77c125861e42ba38cd344e4 Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed. > Fix upgrade test test_collection_function on trunk > -- > > Key: CASSANDRA-17817 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17817 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.2 > > > The upgrade test test_collection_functio is failing on trunk post > CASSANDRA-8877 > For unknown to me reason Jenkins shows it started failing post > CASSANDRA-17575 which does not make sense as that ticket improved > documentation. > Bisecting in Circle CI points to CASSANDRA-8877 > The test run in a loop before CASSANDRA-8877 > [passes|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1863/workflows/dea8966b-25f2-48e5-b451-b257d1a7242d] > , it consistently fails with CASSANDRA-8877 > [commit|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1864/workflows/01bbc009-9160-4595-97e2-a2f657fd0798/jobs/14587/steps]. > CC [~adelapena], [~ycai] and [~b.le...@gmail.com] -- 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-17817) Fix upgrade test test_collection_function on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17817: - Status: Ready to Commit (was: Review In Progress) > Fix upgrade test test_collection_function on trunk > -- > > Key: CASSANDRA-17817 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17817 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.x > > > The upgrade test test_collection_functio is failing on trunk post > CASSANDRA-8877 > For unknown to me reason Jenkins shows it started failing post > CASSANDRA-17575 which does not make sense as that ticket improved > documentation. > Bisecting in Circle CI points to CASSANDRA-8877 > The test run in a loop before CASSANDRA-8877 > [passes|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1863/workflows/dea8966b-25f2-48e5-b451-b257d1a7242d] > , it consistently fails with CASSANDRA-8877 > [commit|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1864/workflows/01bbc009-9160-4595-97e2-a2f657fd0798/jobs/14587/steps]. > CC [~adelapena], [~ycai] and [~b.le...@gmail.com] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-dtest] branch trunk updated: Ignore test_collection_function after CASSANDRA-8877
This is an automated email from the ASF dual-hosted git repository.
brandonwilliams pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-dtest.git
The following commit(s) were added to refs/heads/trunk by this push:
new b91999ca Ignore test_collection_function after CASSANDRA-8877
b91999ca is described below
commit b91999cad0700024e77c125861e42ba38cd344e4
Author: Brandon Williams
AuthorDate: Mon Aug 15 17:48:39 2022 -0500
Ignore test_collection_function after CASSANDRA-8877
Patch by brandonwilliams and adelapena; reviewed by adelapena and
brandonwilliams for CASSANDRA-17817
---
upgrade_tests/cql_tests.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/upgrade_tests/cql_tests.py b/upgrade_tests/cql_tests.py
index 59e37cb1..8c3cd975 100644
--- a/upgrade_tests/cql_tests.py
+++ b/upgrade_tests/cql_tests.py
@@ -2430,6 +2430,7 @@ class TestCQL(UpgradeTester):
res = list(cursor.execute("SELECT * FROM test LIMIT
{}".format(int(nb_keys / 2
assert_length_equal(res, nb_keys / 2)
+@since('2.0', max_version='4.1') # CASSANDRA-8877
def test_collection_function(self):
cursor = self.prepare()
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13010) nodetool compactionstats should say which disk a compaction is writing to
[ https://issues.apache.org/jira/browse/CASSANDRA-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-13010: -- Labels: 4.0-feature-freeze-review-requested (was: 4.0-feature-freeze-review-requested lhf) > nodetool compactionstats should say which disk a compaction is writing to > - > > Key: CASSANDRA-13010 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13010 > Project: Cassandra > Issue Type: New Feature > Components: Local/Compaction, Tool/nodetool >Reporter: Jon Haddad >Assignee: Stefan Miklosovic >Priority: Normal > Labels: 4.0-feature-freeze-review-requested > Fix For: 4.x > > Attachments: cleanup.png, multiple operations.png > > -- 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-13010) nodetool compactionstats should say which disk a compaction is writing to
[ https://issues.apache.org/jira/browse/CASSANDRA-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-13010: -- Complexity: Normal (was: Low Hanging Fruit) > nodetool compactionstats should say which disk a compaction is writing to > - > > Key: CASSANDRA-13010 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13010 > Project: Cassandra > Issue Type: New Feature > Components: Local/Compaction, Tool/nodetool >Reporter: Jon Haddad >Assignee: Stefan Miklosovic >Priority: Normal > Labels: 4.0-feature-freeze-review-requested, lhf > Fix For: 4.x > > Attachments: cleanup.png, multiple operations.png > > -- 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] (CASSANDRASC-41) Implement toString for Range in Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRASC-41: - Reviewers: Dinesh Joshi, Francisco Guerrero (was: Francisco Guerrero) > Implement toString for Range in Sidecar > --- > > Key: CASSANDRASC-41 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-41 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > > The toString method for Range is not implemented, leading to the ranges > objects being logged incorrectly. We should add the toString implementation. -- 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] (CASSANDRASC-41) Implement toString for Range in Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRASC-41: - Status: Ready to Commit (was: Review In Progress) > Implement toString for Range in Sidecar > --- > > Key: CASSANDRASC-41 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-41 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > > The toString method for Range is not implemented, leading to the ranges > objects being logged incorrectly. We should add the toString implementation. -- 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] (CASSANDRASC-41) Implement toString for Range in Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRASC-41: - Fix Version/s: 1.0 Source Control Link: https://github.com/apache/cassandra-sidecar/commit/c5669b5e84e33109c407944563e8c466b5a14717 Resolution: Fixed Status: Resolved (was: Ready to Commit) > Implement toString for Range in Sidecar > --- > > Key: CASSANDRASC-41 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-41 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > Fix For: 1.0 > > > The toString method for Range is not implemented, leading to the ranges > objects being logged incorrectly. We should add the toString implementation. -- 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-sidecar] branch trunk updated: Refactor range and add toString
This is an automated email from the ASF dual-hosted git repository.
ycai pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-sidecar.git
The following commit(s) were added to refs/heads/trunk by this push:
new c5669b5 Refactor range and add toString
c5669b5 is described below
commit c5669b5e84e33109c407944563e8c466b5a14717
Author: Yifan Cai
AuthorDate: Fri Aug 5 14:54:32 2022 -0700
Refactor range and add toString
---
CHANGES.txt| 6 +
.../org/apache/cassandra/sidecar/models/Range.java | 186 ++---
.../cassandra/sidecar/utils/FileStreamer.java | 2 +-
.../org/apache/cassandra/sidecar/RangeTest.java| 93 +--
.../routes/StreamSSTableComponentHandlerTest.java | 6 +-
5 files changed, 176 insertions(+), 117 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index 27ce525..1c92ca5 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,5 +1,11 @@
1.0.0
-
+ * Refactor range and add toString (CASSANDRASC-41)
+ * Fix search in list snapshot endpoint (CASSANDRASC-40)
+ * Allow Cassandra input validation to be configurable (CASSANDRAC-39)
+ * Add endpoint to list snapshot files (CASSANDRASC-38)
+ * Optimize file path builder and have separate handler for streaming file
(CASSANDRASC-37)
+ * Support for ErrorHandler in Sidecar (CASSANDRASC-36)
* Allow injecting a LoggerHandler to vertxRouter (CASSANDRASC-34)
* Optionally support multiple cassandra instances in Sidecar (CASSANDRASC-33)
* Call the start method of CassandraAdaptorDelegate to start periodic health
check (CASSANDRASC-32)
diff --git a/src/main/java/org/apache/cassandra/sidecar/models/Range.java
b/src/main/java/org/apache/cassandra/sidecar/models/Range.java
index b005064..4f8a006 100644
--- a/src/main/java/org/apache/cassandra/sidecar/models/Range.java
+++ b/src/main/java/org/apache/cassandra/sidecar/models/Range.java
@@ -31,132 +31,130 @@ import
org.apache.cassandra.sidecar.exceptions.RangeException;
* Accepted Range formats are start-end, start-, -suffix_length
* start-end (start = start index of the range, end = end index of the range,
both inclusive)
* start- (start = start index of the range, end = end of file)
- * -suffix-length (Requested length from end of file)
+ * -suffix-length (Requested length from end of file. The length should be
positive)
*/
public class Range
{
-private static final Pattern START_END =
Pattern.compile("^(\\d+)-(\\d+)$");
-private static final Pattern PARTIAL =
Pattern.compile("^((\\d+)-)$|^(-(\\d+))$");
private static final String RANGE_UNIT = "bytes";
+// matches a. bytes=1-2, b. bytes=1-, c. bytes=-2, d. bytes=-. Need to do
another valid for case d.
+private static final Pattern RANGE_HEADER = Pattern.compile("^" +
RANGE_UNIT + "=(\\d*)-(\\d*)$");
private final long start;
private final long end;
private final long length;
+private static final long BOUND_ABSENT = -1L;
-private Range(final long start, final long end)
+/**
+ * Accepted RangeHeader formats are bytes=start-end, bytes=start-,
bytes=-suffix_length
+ */
+public static Range parseHeader(final String header, final long fileSize)
{
-this.start = start;
-this.end = end;
-this.length = length(start, end);
+if (header == null)
+{
+return new Range(0, fileSize - 1);
+}
+return Range.parse(header, fileSize);
}
-public Range(final long start, final long end, final long length)
+public static Range of(final long start, final long end)
{
-this.start = start;
-this.end = end;
-this.length = length;
+return new Range(start, end);
}
-private long length(final long start, final long end)
+/**
+ * Accepted string formats "bytes=1453-3563", "bytes=-22344", "bytes=5346-"
+ * Sample invalid string formats "bytes=8-3", "bytes=-", "bytes=-0",
"bytes=a-b"
+ *
+ * @param fileSize - passed in to convert partial range into absolute range
+ */
+private static Range parse(@NotNull String rangeHeader, final long
fileSize)
{
-if (start == 0 && end == Long.MAX_VALUE) // avoid overflow (extra byte)
+Matcher m = RANGE_HEADER.matcher(rangeHeader);
+if (!m.matches())
{
-return Long.MAX_VALUE;
+throw invalidRangeHeaderException(rangeHeader);
}
-return end - start + 1;
-}
-public long start()
-{
-return this.start;
+long left = parseLong(m.group(1), rangeHeader);
+long right = parseLong(m.group(2), rangeHeader);
+
+if (left == BOUND_ABSENT && right == BOUND_ABSENT) // matching
"bytes=-"
+{
+throw invalidRangeHeaderException(rangeHeader);
+}
+else if (left == BOUND_ABSENT) // matching "bytes=-1"
+{
+long len = Math.min(right,
[jira] [Commented] (CASSANDRA-17817) Fix upgrade test test_collection_function on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580404#comment-17580404 ] Andres de la Peña commented on CASSANDRA-17817: --- Jenkins looks good too, +1. > Fix upgrade test test_collection_function on trunk > -- > > Key: CASSANDRA-17817 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17817 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.x > > > The upgrade test test_collection_functio is failing on trunk post > CASSANDRA-8877 > For unknown to me reason Jenkins shows it started failing post > CASSANDRA-17575 which does not make sense as that ticket improved > documentation. > Bisecting in Circle CI points to CASSANDRA-8877 > The test run in a loop before CASSANDRA-8877 > [passes|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1863/workflows/dea8966b-25f2-48e5-b451-b257d1a7242d] > , it consistently fails with CASSANDRA-8877 > [commit|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1864/workflows/01bbc009-9160-4595-97e2-a2f657fd0798/jobs/14587/steps]. > CC [~adelapena], [~ycai] and [~b.le...@gmail.com] -- 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-17658) Test Failures: org.apache.cassandra.metrics.KeyspaceMetricsTest.testMetricsCleanupOnDrop
[
https://issues.apache.org/jira/browse/CASSANDRA-17658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580401#comment-17580401
]
Andres de la Peña edited comment on CASSANDRA-17658 at 8/16/22 4:49 PM:
It seems that the new {{SchemaTest.schemaReset}} is flaky, see CASSANDRA-17819.
IIRC that test survived 1000 repeated runs on the multiplexer the last time we
run it for
[4.1|https://app.circleci.com/pipelines/github/adelapena/cassandra/1910/workflows/2ce26187-7143-4c70-a825-1636b78ac63d]
and
[trunk|https://app.circleci.com/pipelines/github/adelapena/cassandra/1909/workflows/b47cb176-62de-40a1-9df5-6e6224080971],
but that was almost one month before commit. Maybe something happened during
the rebase?
was (Author: adelapena):
It seems that the new {{SchemaTest.schemaReset}} is flaky, see CASSANDRA-17819.
> Test Failures:
> org.apache.cassandra.metrics.KeyspaceMetricsTest.testMetricsCleanupOnDrop
>
>
> Key: CASSANDRA-17658
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17658
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.1-beta, 4.2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The test
> {{org.apache.cassandra.metrics.KeyspaceMetricsTest.testMetricsCleanupOnDrop}}
> seems to be flaky on CircleCI, although I haven't seen it failing on Jenkins.
> It was first detected during CASSANDRA-17509, on [this
> run|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/211/workflows/2cbb5465-a970-440b-a502-06e380ce6851/jobs/1977/tests]:
> {code}
> junit.framework.AssertionFailedError:
>
[jira] [Commented] (CASSANDRA-17658) Test Failures: org.apache.cassandra.metrics.KeyspaceMetricsTest.testMetricsCleanupOnDrop
[
https://issues.apache.org/jira/browse/CASSANDRA-17658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580401#comment-17580401
]
Andres de la Peña commented on CASSANDRA-17658:
---
It seems that the new {{SchemaTest.schemaReset}} is flaky, see CASSANDRA-17819.
> Test Failures:
> org.apache.cassandra.metrics.KeyspaceMetricsTest.testMetricsCleanupOnDrop
>
>
> Key: CASSANDRA-17658
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17658
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.1-beta, 4.2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The test
> {{org.apache.cassandra.metrics.KeyspaceMetricsTest.testMetricsCleanupOnDrop}}
> seems to be flaky on CircleCI, although I haven't seen it failing on Jenkins.
> It was first detected during CASSANDRA-17509, on [this
> run|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/211/workflows/2cbb5465-a970-440b-a502-06e380ce6851/jobs/1977/tests]:
> {code}
> junit.framework.AssertionFailedError:
>
[jira] [Updated] (CASSANDRA-17151) Guardrail for column size
[
https://issues.apache.org/jira/browse/CASSANDRA-17151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17151:
--
Fix Version/s: 4.2
(was: 4.x)
Source Control Link:
https://github.com/apache/cassandra/commit/4b7069c06c7913e1f3f2d5622d8cbc04746b0bac
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Guardrail for column size
> -
>
> Key: CASSANDRA-17151
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17151
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 4.2
>
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> Add a guardrail for limiting the max size of column values, for example:
> {code}
> # Failure threshold to prevent writing large column values.
> # Defaults to -1 to disable.
> column_value_size_failure_threshold_in_kb: -1
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17778) WEBSITE - Add CASSANDRA-15234 config page to Docs nav menu
[
https://issues.apache.org/jira/browse/CASSANDRA-17778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580399#comment-17580399
]
Caleb Rackliffe commented on CASSANDRA-17778:
-
[~e.dimitrova] Two minor nits:
{noformat}
memory (B|KiB|MiB|GiB) and duration(d|h|s|ms|us|µs|ns|m)
{noformat}
{noformat}
|Duration | d, h, s, ms, us, µs, ns, m
{noformat}
In both these cases, seems like we'd want {{m}} between {{h}} and {{s}}.
Otherwise, +1
> WEBSITE - Add CASSANDRA-15234 config page to Docs nav menu
> --
>
> Key: CASSANDRA-17778
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17778
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation/Website
>Reporter: Erick Ramirez
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.1.x, 4.x
>
>
> There is no way to navigate to the new configuration page for CASSANDRA-15234
> ([Liberating cassandra.yaml Parameters' Names from Their
> Units|https://cassandra.apache.org/doc/trunk/cassandra/new/configuration.html])
> because it is not referenced anywhere.
> Unless someone has bookmarked the page, there is no way to find it on the
> site.
> Other doc changes expected:
> * Add a small table with supported units per type as currently we list only
> the duration's ones and min units for old parameters. We list the supported
> units only in NEWS.txt.
> * Add info about the RuntimeExceptions we introduced in CASSANDRA-17725 for
> a few deprecated JMX getters.
> * Add a note for Cassandra developers - "Please ensure that any JMX
> setters/getters update the Config class properties and not some local copies.
> Settings Virtual Table reports the configuration loaded at any time from the
> Config class."
--
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-17151) Guardrail for column size
[
https://issues.apache.org/jira/browse/CASSANDRA-17151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580398#comment-17580398
]
Andres de la Peña commented on CASSANDRA-17151:
---
Committed to {{trunk}} as
[4b7069c06c7913e1f3f2d5622d8cbc04746b0bac|https://github.com/apache/cassandra/commit/4b7069c06c7913e1f3f2d5622d8cbc04746b0bac].
Thanks for the reviews.
> Guardrail for column size
> -
>
> Key: CASSANDRA-17151
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17151
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> Add a guardrail for limiting the max size of column values, for example:
> {code}
> # Failure threshold to prevent writing large column values.
> # Defaults to -1 to disable.
> column_value_size_failure_threshold_in_kb: -1
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: Add guardrail for column size
This is an automated email from the ASF dual-hosted git repository. adelapena pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/trunk by this push: new 4b7069c06c Add guardrail for column size 4b7069c06c is described below commit 4b7069c06c7913e1f3f2d5622d8cbc04746b0bac Author: Andrés de la Peña AuthorDate: Mon Jun 13 20:08:55 2022 +0100 Add guardrail for column size patch by Andrés de la Peña; reviewed by Ekaterina Dimitrova and David Capwell for CASSANDRA-17151 --- CHANGES.txt| 1 + NEWS.txt | 1 + conf/cassandra.yaml| 18 + src/java/org/apache/cassandra/config/Config.java | 2 + .../apache/cassandra/config/GuardrailsOptions.java | 28 + .../org/apache/cassandra/cql3/QueryProcessor.java | 2 +- .../apache/cassandra/cql3/UpdateParameters.java| 15 + src/java/org/apache/cassandra/cql3/Validation.java | 2 +- .../apache/cassandra/db/guardrails/Guardrails.java | 43 +- .../cassandra/db/guardrails/GuardrailsConfig.java | 12 + .../cassandra/db/guardrails/GuardrailsMBean.java | 24 + .../guardrails/GuardrailColumnValueSizeTest.java | 650 + 12 files changed, 788 insertions(+), 10 deletions(-) diff --git a/CHANGES.txt b/CHANGES.txt index 7dce2b90bd..2c94811e55 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 4.2 + * Add guardrail for column size (CASSANDRA-17151) * When doing a host replacement, we need to check that the node is a live node before failing with "Cannot replace a live node..." (CASSANDRA-17805) * Add support to generate a One-Shot heap dump on unhandled exceptions (CASSANDRA-17795) * Rate-limit new client connection auth setup to avoid overwhelming bcrypt (CASSANDRA-17812) diff --git a/NEWS.txt b/NEWS.txt index 96ad4b9ac0..74142539f7 100644 --- a/NEWS.txt +++ b/NEWS.txt @@ -73,6 +73,7 @@ New features - Whether SimpleStrategy is allowed on keyspace creation or alteration - Maximum replication factor - Whether DROP KEYSPACE commands are allowed. + - Column value size - It is possible to list ephemeral snapshots by nodetool listsnaphots command when flag "-e" is specified. Upgrading diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml index 21e3f78c10..55c8b5a756 100644 --- a/conf/cassandra.yaml +++ b/conf/cassandra.yaml @@ -1767,6 +1767,24 @@ drop_compact_storage_enabled: false # write_consistency_levels_warned: [] # write_consistency_levels_disallowed: [] # +# Guardrail to warn or fail when writing column values larger than threshold. +# This guardrail is only applied to the values of regular columns because both the serialized partitions keys and the +# values of the components of the clustering key already have a fixed, relatively small size limit of 65535 bytes, which +# is probably lesser than the thresholds defined here. +# Deleting individual elements of non-frozen sets and maps involves creating tombstones that contain the value of the +# deleted element, independently on whether the element existed or not. That tombstone value is also guarded by this +# guardrail, to prevent the insertion of tombstones over the threshold. The downside is that enabling or raising this +# threshold can prevent users from deleting set/map elements that were written when the guardrail was disabled or with a +# lower value. Deleting the entire column, row or partition is always allowed, since the tombstones created for those +# operations don't contain the CQL column values. +# This guardrail is different to max_value_size. max_value_size is checked when deserializing any value to detect +# sstable corruption, whereas this guardrail is checked on the CQL layer at write time to reject regular user queries +# inserting too large columns. +# The two thresholds default to null to disable. +# Min unit: B +# column_value_size_warn_threshold: +# column_value_size_fail_threshold: +# # Guardrail to warn or fail when encountering larger size of collection data than threshold. # At query time this guardrail is applied only to the collection fragment that is being writen, even though in the case # of non-frozen collections there could be unaccounted parts of the collection on the sstables. This is done this way to diff --git a/src/java/org/apache/cassandra/config/Config.java b/src/java/org/apache/cassandra/config/Config.java index f14bb3544a..b5e76d3a01 100644 --- a/src/java/org/apache/cassandra/config/Config.java +++ b/src/java/org/apache/cassandra/config/Config.java @@ -847,6 +847,8 @@ public class Config public volatile boolean read_before_write_list_operations_enabled = true; public volatile boolean allow_filtering_enabled = true; public volatile boolean simplestrategy_enabled = true; +public volatile DataStorageSpec.LongBytesBound
[jira] [Commented] (CASSANDRA-17422) Test Failure: org.apache.cassandra.net.OutboundMessageQueueTest.testRemove-cdc
[
https://issues.apache.org/jira/browse/CASSANDRA-17422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580397#comment-17580397
]
Brandon Williams commented on CASSANDRA-17422:
--
This fell off my radar, but your PR looks good [~Bereng] if you want to create
the other branches and we can close this out.
> Test Failure: org.apache.cassandra.net.OutboundMessageQueueTest.testRemove-cdc
> --
>
> Key: CASSANDRA-17422
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17422
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: shylaja kokoori
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 4.x
>
> Attachments: CASSANDRA-17422.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Branch: 4.0
> https://ci-cassandra.apache.org/job/Cassandra-4.0/350/testReport/org.apache.cassandra.net/OutboundMessageQueueTest/testRemove_cdc/
> {code}
> java.lang.NullPointerException
> at
> org.apache.cassandra.net.OutboundMessageQueueTest.testRemove(OutboundMessageQueueTest.java:91)
> 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}
> Failure: 1 of 3
--
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-17646) Increment CQLSH version for release 4.2
[ https://issues.apache.org/jira/browse/CASSANDRA-17646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams reassigned CASSANDRA-17646: Assignee: Attila Homoki > Increment CQLSH version for release 4.2 > --- > > Key: CASSANDRA-17646 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17646 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Attila Homoki >Assignee: Attila Homoki >Priority: Normal > Fix For: 4.2 > > Attachments: image-2022-05-27-23-08-25-855.png > > > Increment CQLSH version for release 4.2 on trunk -- 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-17821) Add ability to log load profiles at fixed intervals
Josh McKenzie created CASSANDRA-17821: - Summary: Add ability to log load profiles at fixed intervals Key: CASSANDRA-17821 URL: https://issues.apache.org/jira/browse/CASSANDRA-17821 Project: Cassandra Issue Type: New Feature Components: Tool/nodetool Reporter: Josh McKenzie Assignee: Josh McKenzie A jmx operation to run profileload and log results every X would be helpful so operators can hot prop it on troubled nodes/clusters to identify troublesome queries. -- 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-17820) Harry test failure - conflicting replica can be added (expected unique endpoints)
[
https://issues.apache.org/jira/browse/CASSANDRA-17820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-17820:
--
Resolution: Invalid
Status: Resolved (was: Triage Needed)
Scratch that; I have something else I'm working on that this depends on. Will
subsume this into that when I prep it.
> Harry test failure - conflicting replica can be added (expected unique
> endpoints)
> -
>
> Key: CASSANDRA-17820
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17820
> Project: Cassandra
> Issue Type: Bug
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
>
> Changes to natural and pending replicas are not synchronized, so it can
> happen that a replica is in the natural set a replication strategy calculates
> but is also in pending endpoints in the StorageService. We need to filter out
> all pending replicas that are also present in the natural set so we don't end
> up with duplication between them in our {{EndpointsForToken}} calculations.
--
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-17820) Harry test failure - conflicting replica can be added (expected unique endpoints)
Josh McKenzie created CASSANDRA-17820:
-
Summary: Harry test failure - conflicting replica can be added
(expected unique endpoints)
Key: CASSANDRA-17820
URL: https://issues.apache.org/jira/browse/CASSANDRA-17820
Project: Cassandra
Issue Type: Bug
Reporter: Josh McKenzie
Assignee: Josh McKenzie
Changes to natural and pending replicas are not synchronized, so it can happen
that a replica is in the natural set a replication strategy calculates but is
also in pending endpoints in the StorageService. We need to filter out all
pending replicas that are also present in the natural set so we don't end up
with duplication between them in our {{EndpointsForToken}} calculations.
--
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-17719) CEP-15: (C*) Multi-partition transaction CQL support
[
https://issues.apache.org/jira/browse/CASSANDRA-17719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580374#comment-17580374
]
Caleb Rackliffe commented on CASSANDRA-17719:
-
[~benedict] I've already got unconditional updates working anyway, so I just
removed that bit above.
> CEP-15: (C*) Multi-partition transaction CQL support
>
>
> Key: CASSANDRA-17719
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17719
> Project: Cassandra
> Issue Type: New Feature
> Components: CQL/Syntax
>Reporter: Blake Eggleston
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 5.x
>
>
> The dev list thread regarding CQL transaction support seems to have converged
> on a syntax.
>
> The thread is here:
> [https://lists.apache.org/thread/5sds3968mnnk42c24pvgwphg4qvo2xk0]
>
> The message proposing the syntax ultimately agreed on is here:
> [https://lists.apache.org/thread/y289tczngj68bqpoo7gkso3bzmtf86pl]
>
> I'll describe my understanding of the agreed syntax here for, but I'd
> suggest reading through the thread.
>
> The example query is this:
> {code:sql}
> BEGIN TRANSACTION
> LET car = (SELECT miles_driven, is_running FROM cars WHERE model=’pinto’);
> LET user = (SELECT miles_driven FROM users WHERE name=’Blake’);
> SELECT car.is_running, car.miles_driven;
> IF car.is_running THEN
> UPDATE users SET miles_driven = user.miles_driven + 30 WHERE name='blake';
> UPDATE cars SET miles_driven = car.miles_driven + 30 WHERE model='pinto';
> END IF
> COMMIT TRANSACTION
> {code}
> Sections are described below, and we want to require the statement enforces
> an order on the different types of clauses. First, assignments, then
> select(s), then conditional updates. This may be relaxed in the future, but
> is meant to prevent users from interleaving updates and assignments and
> expecting read your own write behavior that we don't want to support in v1.
> h3. Reference assignments
> {code:sql}
> LET car = (SELECT miles_driven, is_running FROM cars WHERE
> model=’pinto’){code}
>
> The first part is basically assigning the result of a SELECT statement to a
> named reference that can be used in updates/conditions and be returned to the
> user. Tuple names belong to a global scope and must not clash with other LET
> statements or update statements (more on that in the updates section). Also,
> the select statement must either be a point read, with all primary key
> columns defined, or explicitly set a limit of 1.
> h3. Selection
> Data to returned to client. Currently, we're only supporting a single select
> statement. Either a normal select statement, or one returning values assigned
> by LET statements as shown in the example. Ultimately we'll want to support
> multiple select statements and returning the results to the client. Although
> that will require a protocol change.
> h3. Updates
> Normal inserts/updates/deletes with the following extensions:
> * Inserts and updates can reference values assigned earlier in the statement
> * Updates can reference their own columns:
> {code:java}
> miles_driven = miles_driven + 30{code}
> - or -
> {code:java}
> miles_driven += 30{code}
> These will of course need to generate any required reads behind the scenes.
> There's no precedence of table vs reference names, so if a relevant column
> name and reference name conflict, the query needs to fail to parse.
> h3. If blocks
> {code:sql}
> IF THEN
> ;
> ;
> END IF
> {code}
>
> For v1, we only need to support a single condition in the format above. In
> the future, we'd like to support multiple branches with multiple conditions
> like:
>
> {code:sql}
> IF THEN
> ;
> ;
> ELSE IF THEN
> ;
> ELSE
> ;
> END IF
> {code}
>
> h3. Conditions
> Comparisons of value references to literals or other references. IS NULL / IS
> NOT NULL also needs to be supported. Multiple comparisons need to be
> supported, but v1 only needs to support AND'ing them together
> {code:java}
> Supported operators: =, !=, >, >=, <, <=, IS NULL, IS NOT NULL
> = 5
> IS NOT NULL
> IF car IS NOT NULL AND car.miles_driven > 30
> IF car.miles_driven = user.miles_driven{code}
> (Note that {{IS[ NOT ]NULL}} can apply to both tuple references and
> individually dereferenced columns.)
> h3. Implementation notes
> I have a proof of concept I'd created to demo the initially proposed syntax
> here: [https://github.com/bdeggleston/cassandra/tree/accord-cql-poc], It
> could be used as a starting point, a source of ideas for approaches, or not
> used at all. The main thing to keep in mind is that value references prevent
> creating read commands and mutations until later in the transaction process,
> and potentially on another machine,
[jira] [Updated] (CASSANDRA-17719) CEP-15: (C*) Multi-partition transaction CQL support
[
https://issues.apache.org/jira/browse/CASSANDRA-17719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-17719:
Description:
The dev list thread regarding CQL transaction support seems to have converged
on a syntax.
The thread is here:
[https://lists.apache.org/thread/5sds3968mnnk42c24pvgwphg4qvo2xk0]
The message proposing the syntax ultimately agreed on is here:
[https://lists.apache.org/thread/y289tczngj68bqpoo7gkso3bzmtf86pl]
I'll describe my understanding of the agreed syntax here for, but I'd suggest
reading through the thread.
The example query is this:
{code:sql}
BEGIN TRANSACTION
LET car = (SELECT miles_driven, is_running FROM cars WHERE model=’pinto’);
LET user = (SELECT miles_driven FROM users WHERE name=’Blake’);
SELECT car.is_running, car.miles_driven;
IF car.is_running THEN
UPDATE users SET miles_driven = user.miles_driven + 30 WHERE name='blake';
UPDATE cars SET miles_driven = car.miles_driven + 30 WHERE model='pinto';
END IF
COMMIT TRANSACTION
{code}
Sections are described below, and we want to require the statement enforces an
order on the different types of clauses. First, assignments, then select(s),
then conditional updates. This may be relaxed in the future, but is meant to
prevent users from interleaving updates and assignments and expecting read your
own write behavior that we don't want to support in v1.
h3. Reference assignments
{code:sql}
LET car = (SELECT miles_driven, is_running FROM cars WHERE
model=’pinto’){code}
The first part is basically assigning the result of a SELECT statement to a
named reference that can be used in updates/conditions and be returned to the
user. Tuple names belong to a global scope and must not clash with other LET
statements or update statements (more on that in the updates section). Also,
the select statement must either be a point read, with all primary key columns
defined, or explicitly set a limit of 1.
h3. Selection
Data to returned to client. Currently, we're only supporting a single select
statement. Either a normal select statement, or one returning values assigned
by LET statements as shown in the example. Ultimately we'll want to support
multiple select statements and returning the results to the client. Although
that will require a protocol change.
h3. Updates
Normal inserts/updates/deletes with the following extensions:
* Inserts and updates can reference values assigned earlier in the statement
* Updates can reference their own columns:
{code:java}
miles_driven = miles_driven + 30{code}
- or -
{code:java}
miles_driven += 30{code}
These will of course need to generate any required reads behind the scenes.
There's no precedence of table vs reference names, so if a relevant column name
and reference name conflict, the query needs to fail to parse.
h3. If blocks
{code:sql}
IF THEN
;
;
END IF
{code}
For v1, we only need to support a single condition in the format above. In the
future, we'd like to support multiple branches with multiple conditions like:
{code:sql}
IF THEN
;
;
ELSE IF THEN
;
ELSE
;
END IF
{code}
h3. Conditions
Comparisons of value references to literals or other references. IS NULL / IS
NOT NULL also needs to be supported. Multiple comparisons need to be supported,
but v1 only needs to support AND'ing them together
{code:java}
Supported operators: =, !=, >, >=, <, <=, IS NULL, IS NOT NULL
= 5
IS NOT NULL
IF car IS NOT NULL AND car.miles_driven > 30
IF car.miles_driven = user.miles_driven{code}
(Note that {{IS[ NOT ]NULL}} can apply to both tuple references and
individually dereferenced columns.)
h3. Implementation notes
I have a proof of concept I'd created to demo the initially proposed syntax
here: [https://github.com/bdeggleston/cassandra/tree/accord-cql-poc], It could
be used as a starting point, a source of ideas for approaches, or not used at
all. The main thing to keep in mind is that value references prevent creating
read commands and mutations until later in the transaction process, and
potentially on another machine, which means we can't create accord transactions
with fully formed mutations and read commands. CQL statements and terms are
also not serializable, and would require a ton of work to properly serialize,
so there will need to be some intermediate stage that can be serialized.
was:
The dev list thread regarding CQL transaction support seems to have converged
on a syntax.
The thread is here:
[https://lists.apache.org/thread/5sds3968mnnk42c24pvgwphg4qvo2xk0]
The message proposing the syntax ultimately agreed on is here:
[https://lists.apache.org/thread/y289tczngj68bqpoo7gkso3bzmtf86pl]
I'll describe my understanding of the agreed syntax here for, but I'd suggest
reading through the thread.
The example query is this:
{code:sql}
BEGIN TRANSACTION
LET car = (SELECT
[cassandra-website] branch asf-staging updated (2ce6525e -> 324c9df5)
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 2ce6525e generate docs for 930e594a new 324c9df5 generate docs for 930e594a 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 (2ce6525e) \ N -- N -- N refs/heads/asf-staging (324c9df5) 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 4740078 -> 4740078 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17815) Clean stderr in output from InvalidatePermissionsCacheTest
[
https://issues.apache.org/jira/browse/CASSANDRA-17815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-17815:
--
Status: Ready to Commit (was: Review In Progress)
> Clean stderr in output from InvalidatePermissionsCacheTest
> --
>
> Key: CASSANDRA-17815
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17815
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
>
> We use {{tool.getStderr}} in {{InvalidatePermissionsCacheTest}} which can
> make the tests fail if you happen to be running with anything in your
> {{{}JAVA_TOOL_OPTIONS{}}}.
--
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-17815) Clean stderr in output from InvalidatePermissionsCacheTest
[
https://issues.apache.org/jira/browse/CASSANDRA-17815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-17815:
--
Fix Version/s: 4.2
Source Control Link:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=commit;h=7bde2c23abacf60d156de7c444f136dcfe9fe276
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Clean stderr in output from InvalidatePermissionsCacheTest
> --
>
> Key: CASSANDRA-17815
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17815
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.2
>
>
> We use {{tool.getStderr}} in {{InvalidatePermissionsCacheTest}} which can
> make the tests fail if you happen to be running with anything in your
> {{{}JAVA_TOOL_OPTIONS{}}}.
--
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-17815) Clean stderr in output from InvalidatePermissionsCacheTest
[
https://issues.apache.org/jira/browse/CASSANDRA-17815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-17815:
--
Status: Review In Progress (was: Patch Available)
> Clean stderr in output from InvalidatePermissionsCacheTest
> --
>
> Key: CASSANDRA-17815
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17815
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
>
> We use {{tool.getStderr}} in {{InvalidatePermissionsCacheTest}} which can
> make the tests fail if you happen to be running with anything in your
> {{{}JAVA_TOOL_OPTIONS{}}}.
--
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: Replace getStderr calls with getCleanedStderr calls in tests checking for emptiness
This is an automated email from the ASF dual-hosted git repository.
jmckenzie pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/trunk by this push:
new 7bde2c23ab Replace getStderr calls with getCleanedStderr calls in
tests checking for emptiness
7bde2c23ab is described below
commit 7bde2c23abacf60d156de7c444f136dcfe9fe276
Author: Josh McKenzie
AuthorDate: Fri Aug 12 12:43:26 2022 -0400
Replace getStderr calls with getCleanedStderr calls in tests checking for
emptiness
Patch by Jon Meredith; reviewed by Josh McKenzie and Berenguer Blasi for
CASSANDRA-17815
Co-authored-by: Jon Meredith
Co-authored-by: Josh McKenzie
---
.../apache/cassandra/tools/SSTableMetadataViewerTest.java | 8
.../cassandra/tools/nodetool/GetAuthCacheConfigTest.java | 6 +++---
.../tools/nodetool/InvalidatePermissionsCacheTest.java | 14 +++---
.../cassandra/tools/nodetool/SetAuthCacheConfigTest.java | 10 +-
4 files changed, 19 insertions(+), 19 deletions(-)
diff --git
a/test/unit/org/apache/cassandra/tools/SSTableMetadataViewerTest.java
b/test/unit/org/apache/cassandra/tools/SSTableMetadataViewerTest.java
index 4998b6e81a..baf7c8c1cf 100644
--- a/test/unit/org/apache/cassandra/tools/SSTableMetadataViewerTest.java
+++ b/test/unit/org/apache/cassandra/tools/SSTableMetadataViewerTest.java
@@ -108,7 +108,7 @@ public class SSTableMetadataViewerTest extends
OfflineToolUtils
assertTrue(tool.getStdout(),
CharMatcher.ascii().matchesAllOf(tool.getStdout()));
Assertions.assertThat(tool.getStdout()).doesNotContain("Widest
Partitions");
Assertions.assertThat(tool.getStdout()).contains(sstable.replaceAll("-Data\\.db$",
""));
-assertTrue(tool.getStderr(), tool.getStderr().isEmpty());
+assertTrue(tool.getCleanedStderr(), tool.getCleanedStderr().isEmpty());
assertEquals(0, tool.getExitCode());
assertGoodEnvPostTest();
}
@@ -123,7 +123,7 @@ public class SSTableMetadataViewerTest extends
OfflineToolUtils
ToolResult tool =
ToolRunner.invokeClass(SSTableMetadataViewer.class, arg, sstable);
Assertions.assertThat(tool.getStdout()).contains(Util.BLUE);
Assertions.assertThat(tool.getStdout()).contains(sstable.replaceAll("-Data\\.db$",
""));
- assertTrue("Arg: [" + arg + "]\n" + tool.getStderr(),
tool.getStderr().isEmpty());
+ assertTrue("Arg: [" + arg + "]\n" + tool.getCleanedStderr(),
tool.getCleanedStderr().isEmpty());
assertEquals(0, tool.getExitCode());
assertGoodEnvPostTest();
});
@@ -139,7 +139,7 @@ public class SSTableMetadataViewerTest extends
OfflineToolUtils
ToolResult tool =
ToolRunner.invokeClass(SSTableMetadataViewer.class, arg, sstable);
assertTrue(tool.getStdout(),
!CharMatcher.ascii().matchesAllOf(tool.getStdout()));
Assertions.assertThat(tool.getStdout()).contains(sstable.replaceAll("-Data\\.db$",
""));
- assertTrue("Arg: [" + arg + "]\n" + tool.getStderr(),
tool.getStderr().isEmpty());
+ assertTrue("Arg: [" + arg + "]\n" + tool.getCleanedStderr(),
tool.getCleanedStderr().isEmpty());
assertEquals(0, tool.getExitCode());
assertGoodEnvPostTest();
});
@@ -211,7 +211,7 @@ public class SSTableMetadataViewerTest extends
OfflineToolUtils
ToolResult tool =
ToolRunner.invokeClass(SSTableMetadataViewer.class, arg, sstable);
Assertions.assertThat(tool.getStdout()).contains("Widest
Partitions");
Assertions.assertThat(tool.getStdout()).contains(sstable.replaceAll("-Data\\.db$",
""));
- assertTrue("Arg: [" + arg + "]\n" + tool.getStderr(),
tool.getStderr().isEmpty());
+ assertTrue("Arg: [" + arg + "]\n" + tool.getCleanedStderr(),
tool.getCleanedStderr().isEmpty());
assertEquals(0, tool.getExitCode());
});
}
diff --git
a/test/unit/org/apache/cassandra/tools/nodetool/GetAuthCacheConfigTest.java
b/test/unit/org/apache/cassandra/tools/nodetool/GetAuthCacheConfigTest.java
index 6afc1791b1..e32040da66 100644
--- a/test/unit/org/apache/cassandra/tools/nodetool/GetAuthCacheConfigTest.java
+++ b/test/unit/org/apache/cassandra/tools/nodetool/GetAuthCacheConfigTest.java
@@ -95,17 +95,17 @@ public class GetAuthCacheConfigTest extends CQLTester
ToolRunner.ToolResult tool =
ToolRunner.invokeNodetool("getauthcacheconfig");
assertThat(tool.getExitCode()).isEqualTo(1);
assertThat(tool.getStdout()).isEqualTo(wrapByDefaultNodetoolMessage("Required
option '--cache-name' is missing"));
-assertThat(tool.getStderr()).isEmpty();
+
[cassandra-website] branch asf-staging updated (7de8f7c6 -> 2ce6525e)
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 7de8f7c6 generate docs for 930e594a new 2ce6525e generate docs for 930e594a 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 (7de8f7c6) \ N -- N -- N refs/heads/asf-staging (2ce6525e) 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 4740078 -> 4740078 bytes 1 file changed, 0 insertions(+), 0 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13010) nodetool compactionstats should say which disk a compaction is writing to
[ https://issues.apache.org/jira/browse/CASSANDRA-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-13010: -- Fix Version/s: 4.x > nodetool compactionstats should say which disk a compaction is writing to > - > > Key: CASSANDRA-13010 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13010 > Project: Cassandra > Issue Type: New Feature > Components: Local/Compaction, Tool/nodetool >Reporter: Jon Haddad >Assignee: Stefan Miklosovic >Priority: Normal > Labels: 4.0-feature-freeze-review-requested, lhf > Fix For: 4.x > > Attachments: cleanup.png, multiple operations.png > > -- 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-17151) Guardrail for column size
[
https://issues.apache.org/jira/browse/CASSANDRA-17151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580272#comment-17580272
]
Andres de la Peña edited comment on CASSANDRA-17151 at 8/16/22 11:45 AM:
-
Final pre-commit CI run after rebasing:
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/1684]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1996/workflows/18bf3171-4e20-4132-9173-2e1b408be1cf]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1996/workflows/fa6639ac-215d-4552-9e52-fafeb288488c]|
Results look good to me. The failures are a Jolokia/port already occupied one,
CASSANDRA-17817 and CASSANDRA-17819.
was (Author: adelapena):
Final pre-commit CI run after rebasing:
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/1684]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1996/workflows/18bf3171-4e20-4132-9173-2e1b408be1cf]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1996/workflows/fa6639ac-215d-4552-9e52-fafeb288488c]|
Results look good to me. There only failures a Jolokia one, CASSANDRA-17817 and
CASSANDRA-17819.
> Guardrail for column size
> -
>
> Key: CASSANDRA-17151
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17151
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> Add a guardrail for limiting the max size of column values, for example:
> {code}
> # Failure threshold to prevent writing large column values.
> # Defaults to -1 to disable.
> column_value_size_failure_threshold_in_kb: -1
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17151) Guardrail for column size
[
https://issues.apache.org/jira/browse/CASSANDRA-17151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580272#comment-17580272
]
Andres de la Peña commented on CASSANDRA-17151:
---
Final pre-commit CI run after rebasing:
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/1684]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1996/workflows/18bf3171-4e20-4132-9173-2e1b408be1cf]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1996/workflows/fa6639ac-215d-4552-9e52-fafeb288488c]|
Results look good to me. There only failures a Jolokia one, CASSANDRA-17817 and
CASSANDRA-17819.
> Guardrail for column size
> -
>
> Key: CASSANDRA-17151
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17151
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> Add a guardrail for limiting the max size of column values, for example:
> {code}
> # Failure threshold to prevent writing large column values.
> # Defaults to -1 to disable.
> column_value_size_failure_threshold_in_kb: -1
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17719) CEP-15: (C*) Multi-partition transaction CQL support
[
https://issues.apache.org/jira/browse/CASSANDRA-17719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580274#comment-17580274
]
Benedict Elliott Smith commented on CASSANDRA-17719:
I'm not sure if this addition is new:
bq. I haven't seen an example of an unconditional update (ie: not contained in
an if block), but I don't see any reason not to support them. Though they don't
need to be delivered in v1.
I think this _is_ a requirement for v1, but could be implemented as simply as
permitting the literal {{true}} in the {{IF}} guard. Users need a simple way to
perform unconditional writes.
> CEP-15: (C*) Multi-partition transaction CQL support
>
>
> Key: CASSANDRA-17719
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17719
> Project: Cassandra
> Issue Type: New Feature
> Components: CQL/Syntax
>Reporter: Blake Eggleston
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 5.x
>
>
> The dev list thread regarding CQL transaction support seems to have converged
> on a syntax.
>
> The thread is here:
> [https://lists.apache.org/thread/5sds3968mnnk42c24pvgwphg4qvo2xk0]
>
> The message proposing the syntax ultimately agreed on is here:
> [https://lists.apache.org/thread/y289tczngj68bqpoo7gkso3bzmtf86pl]
>
> I'll describe my understanding of the agreed syntax here for, but I'd
> suggest reading through the thread.
>
> The example query is this:
> {code:sql}
> BEGIN TRANSACTION
> LET car = (SELECT miles_driven, is_running FROM cars WHERE model=’pinto’);
> LET user = (SELECT miles_driven FROM users WHERE name=’Blake’);
> SELECT car.is_running, car.miles_driven;
> IF car.is_running THEN
> UPDATE users SET miles_driven = user.miles_driven + 30 WHERE name='blake';
> UPDATE cars SET miles_driven = car.miles_driven + 30 WHERE model='pinto';
> END IF
> COMMIT TRANSACTION
> {code}
> Sections are described below, and we want to require the statement enforces
> an order on the different types of clauses. First, assignments, then
> select(s), then conditional updates. This may be relaxed in the future, but
> is meant to prevent users from interleaving updates and assignments and
> expecting read your own write behavior that we don't want to support in v1.
> h3. Reference assignments
> {code:sql}
> LET car = (SELECT miles_driven, is_running FROM cars WHERE
> model=’pinto’){code}
>
> The first part is basically assigning the result of a SELECT statement to a
> named reference that can be used in updates/conditions and be returned to the
> user. Tuple names belong to a global scope and must not clash with other LET
> statements or update statements (more on that in the updates section). Also,
> the select statement must either be a point read, with all primary key
> columns defined, or explicitly set a limit of 1.
> h3. Selection
> Data to returned to client. Currently, we're only supporting a single select
> statement. Either a normal select statement, or one returning values assigned
> by LET statements as shown in the example. Ultimately we'll want to support
> multiple select statements and returning the results to the client. Although
> that will require a protocol change.
> h3. Updates
> Normal inserts/updates/deletes with the following extensions:
> * Inserts and updates can reference values assigned earlier in the statement
> * Updates can reference their own columns:
> {code:java}
> miles_driven = miles_driven + 30{code}
> - or -
> {code:java}
> miles_driven += 30{code}
> These will of course need to generate any required reads behind the scenes.
> There's no precedence of table vs reference names, so if a relevant column
> name and reference name conflict, the query needs to fail to parse.
> h3. If blocks
> {code:sql}
> IF THEN
> ;
> ;
> END IF
> {code}
>
> For v1, we only need to support a single condition in the format above. In
> the future, we'd like to support multiple branches with multiple conditions
> like:
>
> {code:sql}
> IF THEN
> ;
> ;
> ELSE IF THEN
> ;
> ELSE
> ;
> END IF
> {code}
>
> I haven't seen an example of an unconditional update (ie: not contained in an
> if block), but I don't see any reason not to support them. Though they don't
> need to be delivered in v1.
> h3. Conditions
> Comparisons of value references to literals or other references. IS NULL / IS
> NOT NULL also needs to be supported. Multiple comparisons need to be
> supported, but v1 only needs to support AND'ing them together
> {code:java}
> Supported operators: =, !=, >, >=, <, <=, IS NULL, IS NOT NULL
> = 5
> IS NOT NULL
> IF car IS NOT NULL AND car.miles_driven > 30
> IF car.miles_driven = user.miles_driven{code}
> (Note that {{IS[ NOT ]NULL}} can apply to
[jira] [Updated] (CASSANDRA-17819) Test failure: org.apache.cassandra.distributed.test.SchemaTest.schemaReset
[
https://issues.apache.org/jira/browse/CASSANDRA-17819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17819:
--
Fix Version/s: 4.1-beta
4.x
> Test failure: org.apache.cassandra.distributed.test.SchemaTest.schemaReset
> --
>
> Key: CASSANDRA-17819
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17819
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.1-beta, 4.x
>
>
> The test
> {{{}org.apache.cassandra.distributed.test.SchemaTest.schemaReset{}}},
> recently introduced by CASSANDRA-17658, is flaky on 4.1 and trunk:
> * 4.1:
> [https://ci-cassandra.apache.org/job/Cassandra-4.1/134/testReport/org.apache.cassandra.distributed.test/SchemaTest/schemaReset_2/]
> * trunk:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1265/testReport/org.apache.cassandra.distributed.test/SchemaTest/schemaReset_2/]
> {code:java}
> Error Message
> Condition with lambda expression in
> org.apache.cassandra.distributed.test.SchemaTest that uses
> org.apache.cassandra.distributed.Cluster was not fulfilled within 1 minutes.
> Stacktrace
> org.awaitility.core.ConditionTimeoutException: Condition with lambda
> expression in org.apache.cassandra.distributed.test.SchemaTest that uses
> org.apache.cassandra.distributed.Cluster was not fulfilled within 1 minutes.
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
> at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:864)
> at
> org.apache.cassandra.distributed.test.SchemaTest.schemaReset(SchemaTest.java:115)
> 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)
> Standard Output
> INFO [main] 2022-08-15 15:02:14,783 Reflections.java:219 -
> Reflections took 1873 ms to scan 8 urls, producing 1754 keys and 6912 values
> INFO [main] 2022-08-15 15:02:16,407 Reflections.java:219 -
> Reflections took 1561 ms to scan 8 urls, producing 1754 keys and 6912 values
> Node id topology:
> node 1: dc = datacenter0, rack = rack0
> node 2: dc = datacenter0, rack = rack0
> Configured node count: 2, nodeIdTopology size: 2
> DEBUG [main] node1 2022-08-15 15:02:17,554 InternalLoggerFactory.ja
> ...[truncated 1761288 chars]...
> cutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> 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:748)
> INFO [node2_isolatedExecutor:3] node2 2022-08-15 15:03:52,096
> MessagingService.java:519 - Waiting for messaging service to quiesce
> {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-17819) Test failure: org.apache.cassandra.distributed.test.SchemaTest.schemaReset
[
https://issues.apache.org/jira/browse/CASSANDRA-17819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580269#comment-17580269
]
Andres de la Peña commented on CASSANDRA-17819:
---
CC [~jlaskowski] [~edimitrova]
> Test failure: org.apache.cassandra.distributed.test.SchemaTest.schemaReset
> --
>
> Key: CASSANDRA-17819
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17819
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Priority: Normal
>
> The test
> {{{}org.apache.cassandra.distributed.test.SchemaTest.schemaReset{}}},
> recently introduced by CASSANDRA-17658, is flaky on 4.1 and trunk:
> * 4.1:
> [https://ci-cassandra.apache.org/job/Cassandra-4.1/134/testReport/org.apache.cassandra.distributed.test/SchemaTest/schemaReset_2/]
> * trunk:
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1265/testReport/org.apache.cassandra.distributed.test/SchemaTest/schemaReset_2/]
> {code:java}
> Error Message
> Condition with lambda expression in
> org.apache.cassandra.distributed.test.SchemaTest that uses
> org.apache.cassandra.distributed.Cluster was not fulfilled within 1 minutes.
> Stacktrace
> org.awaitility.core.ConditionTimeoutException: Condition with lambda
> expression in org.apache.cassandra.distributed.test.SchemaTest that uses
> org.apache.cassandra.distributed.Cluster was not fulfilled within 1 minutes.
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
> at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:864)
> at
> org.apache.cassandra.distributed.test.SchemaTest.schemaReset(SchemaTest.java:115)
> 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)
> Standard Output
> INFO [main] 2022-08-15 15:02:14,783 Reflections.java:219 -
> Reflections took 1873 ms to scan 8 urls, producing 1754 keys and 6912 values
> INFO [main] 2022-08-15 15:02:16,407 Reflections.java:219 -
> Reflections took 1561 ms to scan 8 urls, producing 1754 keys and 6912 values
> Node id topology:
> node 1: dc = datacenter0, rack = rack0
> node 2: dc = datacenter0, rack = rack0
> Configured node count: 2, nodeIdTopology size: 2
> DEBUG [main] node1 2022-08-15 15:02:17,554 InternalLoggerFactory.ja
> ...[truncated 1761288 chars]...
> cutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> 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:748)
> INFO [node2_isolatedExecutor:3] node2 2022-08-15 15:03:52,096
> MessagingService.java:519 - Waiting for messaging service to quiesce
> {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-17819) Test failure: org.apache.cassandra.distributed.test.SchemaTest.schemaReset
[
https://issues.apache.org/jira/browse/CASSANDRA-17819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17819:
--
Description:
The test {{{}org.apache.cassandra.distributed.test.SchemaTest.schemaReset{}}},
recently introduced by CASSANDRA-17658, is flaky on 4.1 and trunk:
* 4.1:
[https://ci-cassandra.apache.org/job/Cassandra-4.1/134/testReport/org.apache.cassandra.distributed.test/SchemaTest/schemaReset_2/]
* trunk:
[https://ci-cassandra.apache.org/job/Cassandra-trunk/1265/testReport/org.apache.cassandra.distributed.test/SchemaTest/schemaReset_2/]
{code:java}
Error Message
Condition with lambda expression in
org.apache.cassandra.distributed.test.SchemaTest that uses
org.apache.cassandra.distributed.Cluster was not fulfilled within 1 minutes.
Stacktrace
org.awaitility.core.ConditionTimeoutException: Condition with lambda expression
in org.apache.cassandra.distributed.test.SchemaTest that uses
org.apache.cassandra.distributed.Cluster was not fulfilled within 1 minutes.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
at
org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
at
org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:864)
at
org.apache.cassandra.distributed.test.SchemaTest.schemaReset(SchemaTest.java:115)
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)
Standard Output
INFO [main] 2022-08-15 15:02:14,783 Reflections.java:219 - Reflections
took 1873 ms to scan 8 urls, producing 1754 keys and 6912 values
INFO [main] 2022-08-15 15:02:16,407 Reflections.java:219 - Reflections
took 1561 ms to scan 8 urls, producing 1754 keys and 6912 values
Node id topology:
node 1: dc = datacenter0, rack = rack0
node 2: dc = datacenter0, rack = rack0
Configured node count: 2, nodeIdTopology size: 2
DEBUG [main] node1 2022-08-15 15:02:17,554 InternalLoggerFactory.ja
...[truncated 1761288 chars]...
cutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
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:748)
INFO [node2_isolatedExecutor:3] node2 2022-08-15 15:03:52,096
MessagingService.java:519 - Waiting for messaging service to quiesce
{code}
was:
The test {{org.apache.cassandra.distributed.test.SchemaTest.schemaReset}},
recently introduced by CASSANDRA 17658, is flaky on 4.1 and trunk:
* 4.1:
https://ci-cassandra.apache.org/job/Cassandra-4.1/134/testReport/org.apache.cassandra.distributed.test/SchemaTest/schemaReset_2/
* trunk:
https://ci-cassandra.apache.org/job/Cassandra-trunk/1265/testReport/org.apache.cassandra.distributed.test/SchemaTest/schemaReset_2/
{code}
Error Message
Condition with lambda expression in
org.apache.cassandra.distributed.test.SchemaTest that uses
org.apache.cassandra.distributed.Cluster was not fulfilled within 1 minutes.
Stacktrace
org.awaitility.core.ConditionTimeoutException: Condition with lambda expression
in org.apache.cassandra.distributed.test.SchemaTest that uses
org.apache.cassandra.distributed.Cluster was not fulfilled within 1 minutes.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
at
org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
at
org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:864)
at
org.apache.cassandra.distributed.test.SchemaTest.schemaReset(SchemaTest.java:115)
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)
Standard Output
INFO [main] 2022-08-15 15:02:14,783 Reflections.java:219 - Reflections
took 1873 ms to scan 8 urls, producing 1754 keys and 6912 values
INFO [main] 2022-08-15 15:02:16,407 Reflections.java:219 - Reflections
took 1561 ms to scan 8 urls, producing 1754 keys and 6912 values
Node id topology:
node 1:
[jira] [Created] (CASSANDRA-17819) Test failure: org.apache.cassandra.distributed.test.SchemaTest.schemaReset
Andres de la Peña created CASSANDRA-17819:
-
Summary: Test failure:
org.apache.cassandra.distributed.test.SchemaTest.schemaReset
Key: CASSANDRA-17819
URL: https://issues.apache.org/jira/browse/CASSANDRA-17819
Project: Cassandra
Issue Type: Bug
Components: Test/dtest/java
Reporter: Andres de la Peña
The test {{org.apache.cassandra.distributed.test.SchemaTest.schemaReset}},
recently introduced by CASSANDRA 17658, is flaky on 4.1 and trunk:
* 4.1:
https://ci-cassandra.apache.org/job/Cassandra-4.1/134/testReport/org.apache.cassandra.distributed.test/SchemaTest/schemaReset_2/
* trunk:
https://ci-cassandra.apache.org/job/Cassandra-trunk/1265/testReport/org.apache.cassandra.distributed.test/SchemaTest/schemaReset_2/
{code}
Error Message
Condition with lambda expression in
org.apache.cassandra.distributed.test.SchemaTest that uses
org.apache.cassandra.distributed.Cluster was not fulfilled within 1 minutes.
Stacktrace
org.awaitility.core.ConditionTimeoutException: Condition with lambda expression
in org.apache.cassandra.distributed.test.SchemaTest that uses
org.apache.cassandra.distributed.Cluster was not fulfilled within 1 minutes.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
at
org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
at
org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:864)
at
org.apache.cassandra.distributed.test.SchemaTest.schemaReset(SchemaTest.java:115)
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)
Standard Output
INFO [main] 2022-08-15 15:02:14,783 Reflections.java:219 - Reflections
took 1873 ms to scan 8 urls, producing 1754 keys and 6912 values
INFO [main] 2022-08-15 15:02:16,407 Reflections.java:219 - Reflections
took 1561 ms to scan 8 urls, producing 1754 keys and 6912 values
Node id topology:
node 1: dc = datacenter0, rack = rack0
node 2: dc = datacenter0, rack = rack0
Configured node count: 2, nodeIdTopology size: 2
DEBUG [main] node1 2022-08-15 15:02:17,554 InternalLoggerFactory.ja
...[truncated 1761288 chars]...
cutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
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:748)
INFO [node2_isolatedExecutor:3] node2 2022-08-15 15:03:52,096
MessagingService.java:519 - Waiting for messaging service to quiesce
{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-13010) nodetool compactionstats should say which disk a compaction is writing to
[ https://issues.apache.org/jira/browse/CASSANDRA-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580255#comment-17580255 ] Stefan Miklosovic commented on CASSANDRA-13010: --- Yeah I think Alex already provided a flag for this if I am not mistaken. > nodetool compactionstats should say which disk a compaction is writing to > - > > Key: CASSANDRA-13010 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13010 > Project: Cassandra > Issue Type: New Feature > Components: Local/Compaction, Tool/nodetool >Reporter: Jon Haddad >Assignee: Stefan Miklosovic >Priority: Normal > Labels: 4.0-feature-freeze-review-requested, lhf > Attachments: cleanup.png, multiple operations.png > > -- 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-13010) nodetool compactionstats should say which disk a compaction is writing to
[ https://issues.apache.org/jira/browse/CASSANDRA-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580246#comment-17580246 ] Brandon Williams commented on CASSANDRA-13010: -- Note that we should add a flag for this to maintain output compatibility, but we can add it to vtables freely. > nodetool compactionstats should say which disk a compaction is writing to > - > > Key: CASSANDRA-13010 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13010 > Project: Cassandra > Issue Type: New Feature > Components: Local/Compaction, Tool/nodetool >Reporter: Jon Haddad >Assignee: Stefan Miklosovic >Priority: Normal > Labels: 4.0-feature-freeze-review-requested, lhf > Attachments: cleanup.png, multiple operations.png > > -- 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-13010) nodetool compactionstats should say which disk a compaction is writing to
[ https://issues.apache.org/jira/browse/CASSANDRA-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned CASSANDRA-13010: - Assignee: Stefan Miklosovic (was: Alex Lourie) > nodetool compactionstats should say which disk a compaction is writing to > - > > Key: CASSANDRA-13010 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13010 > Project: Cassandra > Issue Type: New Feature > Components: Local/Compaction, Tool/nodetool >Reporter: Jon Haddad >Assignee: Stefan Miklosovic >Priority: Normal > Labels: 4.0-feature-freeze-review-requested, lhf > Attachments: cleanup.png, multiple operations.png > > -- 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-17817) Fix upgrade test test_collection_function on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580232#comment-17580232 ] Brandon Williams commented on CASSANDRA-17817: -- Whoops, thanks for catching that. Circle looks good, and assuming Jenkins does too, +1. > Fix upgrade test test_collection_function on trunk > -- > > Key: CASSANDRA-17817 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17817 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.x > > > The upgrade test test_collection_functio is failing on trunk post > CASSANDRA-8877 > For unknown to me reason Jenkins shows it started failing post > CASSANDRA-17575 which does not make sense as that ticket improved > documentation. > Bisecting in Circle CI points to CASSANDRA-8877 > The test run in a loop before CASSANDRA-8877 > [passes|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1863/workflows/dea8966b-25f2-48e5-b451-b257d1a7242d] > , it consistently fails with CASSANDRA-8877 > [commit|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1864/workflows/01bbc009-9160-4595-97e2-a2f657fd0798/jobs/14587/steps]. > CC [~adelapena], [~ycai] and [~b.le...@gmail.com] -- 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
