[jira] [Commented] (CASSANDRA-17316) Remove all usages of junit.framework
[
https://issues.apache.org/jira/browse/CASSANDRA-17316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504726#comment-17504726
]
Caleb Rackliffe commented on CASSANDRA-17316:
-
Tests look clean, in the sense that the Python dtests really shouldn't matter
here, and the only failure in Java space is accounted for by CASSANDRA-17286.
> Remove all usages of junit.framework
>
>
> Key: CASSANDRA-17316
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17316
> Project: Cassandra
> Issue Type: Task
> Components: Test/unit
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Let's remove all the vestiges of the legacy {{junit}} library in one piece of
> work instead of slowly over the lifetime of the project :)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17362) Update SUPPORTED_UPGRADE_PATHS to include 3.0 and 3.x to 4.1 paths and remove obsolete tests
[ https://issues.apache.org/jira/browse/CASSANDRA-17362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Rackliffe updated CASSANDRA-17362: Test and Documentation Plan: n/a Status: Patch Available (was: In Progress) |trunk| |[branch|https://github.com/apache/cassandra/pull/1494]| |[CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-17362&filter=all]| > Update SUPPORTED_UPGRADE_PATHS to include 3.0 and 3.x to 4.1 paths and remove > obsolete tests > > > Key: CASSANDRA-17362 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17362 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Caleb Rackliffe >Assignee: Caleb Rackliffe >Priority: Normal > Fix For: 4.x > > Time Spent: 10m > Remaining Estimate: 0h > > There are two things we might want to clean up around the upgrade test > versioning: > 1.) Remove or modify tests on trunk for upgrade paths that start before a > supported version (ex. 2.2) or end before the current version > 2.) Add 3.0 -> 4.1 and 3.x -> 4.1 to the list of supported upgrade paths -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17365) Remove deprecated version specific TLS in CQLSH
[
https://issues.apache.org/jira/browse/CASSANDRA-17365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening reassigned CASSANDRA-17365:
--
Assignee: Brad Schoening
> Remove deprecated version specific TLS in CQLSH
> ---
>
> Key: CASSANDRA-17365
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17365
> Project: Cassandra
> Issue Type: Task
> Components: CQL/Interpreter
>Reporter: Brad Schoening
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.x
>
>
> According to [https://docs.python.org/3/library/ssl.html] use of explicit TLS
> versions v1, v1_1 and v1_2 has been deprecated in Python 3.6+ in favor of
> auto-negotiation of the highest protocol version that both the client and
> server support.
> * {{{}ssl.{}}}{{{}PROTOCOL_TLSv1{}}}
> * {{{}ssl.{}}}{{{}PROTOCOL_TLSv1_1{}}}
> * {{{}ssl.{}}}{{{}PROTOCOL_TLSv1_2{}}}
> The above are deprecated since version 3.6: OpenSSL has deprecated all
> version specific protocols.
> This affects cqlshlib/sslhandling.py and cqlshlib/test/test_sslhandling.py.
> And also config files test/config/{sslhandling.config,
> sslhandling_invalid.config}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17417) Replace use of 'six' compatibility library with python 3 equivalents
[ https://issues.apache.org/jira/browse/CASSANDRA-17417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-17417: --- Test and Documentation Plan: pytest runs successfully w/out errors Status: Patch Available (was: Open) > Replace use of 'six' compatibility library with python 3 equivalents > > > Key: CASSANDRA-17417 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17417 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > Attachments: six.pdf > > > _Six_ is a _Python_ 2 and 3 compatibility library. It provides simple > utilities for wrapping the differences between Python 2 and Python 3. It is > intended to support codebases that work on both Python 2 and 3. > Since CQLSH requires python version >= 3.6, its use can be replace with > native python 3 constructs. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: ninja fix empty line required in test/conf/cassandra.yaml, otherwise cdc and compression unit tests fail
This is an automated email from the ASF dual-hosted git repository. edimitrova 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 51e6f8e ninja fix empty line required in test/conf/cassandra.yaml, otherwise cdc and compression unit tests fail 51e6f8e is described below commit 51e6f8ecc122279ea946b08c528e11105efb40f5 Author: Ekaterina Dimitrova AuthorDate: Thu Mar 10 20:38:39 2022 -0500 ninja fix empty line required in test/conf/cassandra.yaml, otherwise cdc and compression unit tests fail --- test/conf/cassandra.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/conf/cassandra.yaml b/test/conf/cassandra.yaml index 4ca9238..58afdb9 100644 --- a/test/conf/cassandra.yaml +++ b/test/conf/cassandra.yaml @@ -63,4 +63,4 @@ track_warnings: abort_threshold_kb: 8192 row_index_size: warn_threshold_kb: 4096 -abort_threshold_kb: 8192 \ No newline at end of file +abort_threshold_kb: 8192 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17164) CEP-14: Paxos Improvements
[ https://issues.apache.org/jira/browse/CASSANDRA-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504687#comment-17504687 ] Ekaterina Dimitrova commented on CASSANDRA-17164: - [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1429/workflows/a624c555-0417-4664-b10e-23f043854213/jobs/9359] Those finished fine. I will pushed the ninja fix, please, check CI tomorrow if there is anything else that needs attention as now there are thousands of tests failing so It is hard to say whether this will be the only issue. Thanks > CEP-14: Paxos Improvements > -- > > Key: CASSANDRA-17164 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17164 > Project: Cassandra > Issue Type: Improvement > Components: Consistency/Coordination, Consistency/Repair >Reporter: Benedict Elliott Smith >Assignee: Benedict Elliott Smith >Priority: Normal > Fix For: 4.1 > > > This ticket encompasses work for [CEP-14| > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-14%3A+Paxos+Improvements]. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17164) CEP-14: Paxos Improvements
[ https://issues.apache.org/jira/browse/CASSANDRA-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504677#comment-17504677 ] Ekaterina Dimitrova edited comment on CASSANDRA-17164 at 3/11/22, 1:27 AM: --- This commit broke all unit tests - compression and cdc. I believe because of removed empty line in the test cassandra.yaml. I will test now and if I am write I will ninja fix it... [https://jenkins-cm4.apache.org/job/Cassandra-trunk/1002/] was (Author: e.dimitrova): This commit broke all unit tests - compression and cdc. I believe because of removed empty line is the tests cassandra.yaml. I will test now and if I am write I will ninja fix it... https://jenkins-cm4.apache.org/job/Cassandra-trunk/1002/ > CEP-14: Paxos Improvements > -- > > Key: CASSANDRA-17164 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17164 > Project: Cassandra > Issue Type: Improvement > Components: Consistency/Coordination, Consistency/Repair >Reporter: Benedict Elliott Smith >Assignee: Benedict Elliott Smith >Priority: Normal > Fix For: 4.1 > > > This ticket encompasses work for [CEP-14| > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-14%3A+Paxos+Improvements]. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17164) CEP-14: Paxos Improvements
[ https://issues.apache.org/jira/browse/CASSANDRA-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504677#comment-17504677 ] Ekaterina Dimitrova commented on CASSANDRA-17164: - This commit broke all unit tests - compression and cdc. I believe because of removed empty line is the tests cassandra.yaml. I will test now and if I am write I will ninja fix it... https://jenkins-cm4.apache.org/job/Cassandra-trunk/1002/ > CEP-14: Paxos Improvements > -- > > Key: CASSANDRA-17164 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17164 > Project: Cassandra > Issue Type: Improvement > Components: Consistency/Coordination, Consistency/Repair >Reporter: Benedict Elliott Smith >Assignee: Benedict Elliott Smith >Priority: Normal > Fix For: 4.1 > > > This ticket encompasses work for [CEP-14| > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-14%3A+Paxos+Improvements]. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504672#comment-17504672 ] Ekaterina Dimitrova commented on CASSANDRA-17351: - And send email to dev > Pip doesn't install ccm every time > -- > > Key: CASSANDRA-17351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Urgent > Fix For: 4.1 > > > In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to > run without -e for ccm in order to address the moveable tag. That worked for > some time until last night. I successfully retagged and now ccm is not > re-installed in Circle CI. > Jenkins picked stuff though. But it was acting unreliably and weird so > rerunning now things there. Results pending. > Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still > pending results. I don't think this will be permanent solution and I am not > sure whether it will affect also the previous branches in a way. We need to > further investigate it and test. > For now I will ask people to test with -e until we figure it out. > CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504671#comment-17504671 ] Ekaterina Dimitrova commented on CASSANDRA-17351: - CQLsh lib tests failing. Not finding ccm command after the latest ccm change. I will post a workaround for review and temporary commit soon until we find permanent solution. > Pip doesn't install ccm every time > -- > > Key: CASSANDRA-17351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Urgent > Fix For: 4.1 > > > In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to > run without -e for ccm in order to address the moveable tag. That worked for > some time until last night. I successfully retagged and now ccm is not > re-installed in Circle CI. > Jenkins picked stuff though. But it was acting unreliably and weird so > rerunning now things there. Results pending. > Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still > pending results. I don't think this will be permanent solution and I am not > sure whether it will affect also the previous branches in a way. We need to > further investigate it and test. > For now I will ask people to test with -e until we figure it out. > CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17351: Resolution: (was: Fixed) Status: Open (was: Resolved) > Pip doesn't install ccm every time > -- > > Key: CASSANDRA-17351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Urgent > Fix For: 4.1 > > > In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to > run without -e for ccm in order to address the moveable tag. That worked for > some time until last night. I successfully retagged and now ccm is not > re-installed in Circle CI. > Jenkins picked stuff though. But it was acting unreliably and weird so > rerunning now things there. Results pending. > Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still > pending results. I don't think this will be permanent solution and I am not > sure whether it will affect also the previous branches in a way. We need to > further investigate it and test. > For now I will ask people to test with -e until we figure it out. > CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17316) Remove all usages of junit.framework
[
https://issues.apache.org/jira/browse/CASSANDRA-17316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-17316:
Test and Documentation Plan: n/a
Status: Patch Available (was: In Progress)
|trunk|
|[patch|https://github.com/apache/cassandra/pull/1492]|
|[CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-17316&filter=all]|
> Remove all usages of junit.framework
>
>
> Key: CASSANDRA-17316
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17316
> Project: Cassandra
> Issue Type: Task
> Components: Test/unit
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Let's remove all the vestiges of the legacy {{junit}} library in one piece of
> work instead of slowly over the lifetime of the project :)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17246) DOCS - Update changed config + JVM, guide post CASSANDRA-15234
[ https://issues.apache.org/jira/browse/CASSANDRA-17246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Rackliffe updated CASSANDRA-17246: Reviewers: Caleb Rackliffe > DOCS - Update changed config + JVM, guide post CASSANDRA-15234 > -- > > Key: CASSANDRA-17246 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17246 > Project: Cassandra > Issue Type: Task > Components: Documentation/NEWS.txt, Documentation/Website >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > When CASSANDRA-15234 gets committed we need to update everywhere in the docs > the changed parameters names and we need to document: > * new types > * guide how to add new parameters > * some information about the backward compatibility network > Possibly missing some bullets, to be considered while doing the actual work. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17177) List Appends Are Not Linearizable
[ https://issues.apache.org/jira/browse/CASSANDRA-17177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Elliott Smith updated CASSANDRA-17177: --- Fix Version/s: 4.1 Since Version: 1.2.0 Source Control Link: [8960b4d8513e22c4c11c181c520380342935aee7|https://github.com/apache/cassandra/commit/8960b4d8513e22c4c11c181c520380342935aee7] Resolution: Fixed Status: Resolved (was: Ready to Commit) > List Appends Are Not Linearizable > - > > Key: CASSANDRA-17177 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17177 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Coordination >Reporter: Benedict Elliott Smith >Assignee: Benedict Elliott Smith >Priority: Normal > Fix For: 4.1 > > > List TimeUUID are issued using the wall clock of the coordinator, so that two > coordinators with divergent clocks may invert their append order -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17177) List Appends Are Not Linearizable
[ https://issues.apache.org/jira/browse/CASSANDRA-17177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Elliott Smith updated CASSANDRA-17177: --- Status: Ready to Commit (was: Review In Progress) > List Appends Are Not Linearizable > - > > Key: CASSANDRA-17177 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17177 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Coordination >Reporter: Benedict Elliott Smith >Assignee: Benedict Elliott Smith >Priority: Normal > > List TimeUUID are issued using the wall clock of the coordinator, so that two > coordinators with divergent clocks may invert their append order -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17177) List Appends Are Not Linearizable
[ https://issues.apache.org/jira/browse/CASSANDRA-17177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Elliott Smith updated CASSANDRA-17177: --- Reviewers: Blake Eggleston, Benedict Elliott Smith Blake Eggleston, Benedict Elliott Smith (was: Benedict Elliott Smith, Blake Eggleston) Status: Review In Progress (was: Patch Available) > List Appends Are Not Linearizable > - > > Key: CASSANDRA-17177 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17177 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Coordination >Reporter: Benedict Elliott Smith >Assignee: Benedict Elliott Smith >Priority: Normal > > List TimeUUID are issued using the wall clock of the coordinator, so that two > coordinators with divergent clocks may invert their append order -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17177) List Appends Are Not Linearizable
[ https://issues.apache.org/jira/browse/CASSANDRA-17177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Elliott Smith updated CASSANDRA-17177: --- Test and Documentation Plan: Covered by CEP-14 Simulator improvements Status: Patch Available (was: Open) > List Appends Are Not Linearizable > - > > Key: CASSANDRA-17177 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17177 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Coordination >Reporter: Benedict Elliott Smith >Assignee: Benedict Elliott Smith >Priority: Normal > > List TimeUUID are issued using the wall clock of the coordinator, so that two > coordinators with divergent clocks may invert their append order -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17176) Introduce TimeUUID
[ https://issues.apache.org/jira/browse/CASSANDRA-17176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Elliott Smith updated CASSANDRA-17176: --- Fix Version/s: 4.1 Source Control Link: [5a0d6154d144b958404a4d7117602d35157848ba|https://github.com/apache/cassandra/commit/5a0d6154d144b958404a4d7117602d35157848ba] Resolution: Fixed Status: Resolved (was: Ready to Commit) > Introduce TimeUUID > -- > > Key: CASSANDRA-17176 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17176 > Project: Cassandra > Issue Type: Sub-task > Components: Local/Other >Reporter: Benedict Elliott Smith >Assignee: Benedict Elliott Smith >Priority: Normal > Fix For: 4.1 > > > Introduce a dedicated class to represent UUID version 2, to ensure correct > usage within Cassandra -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17176) Introduce TimeUUID
[ https://issues.apache.org/jira/browse/CASSANDRA-17176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Elliott Smith updated CASSANDRA-17176: --- Status: Patch Available (was: In Progress) > Introduce TimeUUID > -- > > Key: CASSANDRA-17176 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17176 > Project: Cassandra > Issue Type: Sub-task > Components: Local/Other >Reporter: Benedict Elliott Smith >Assignee: Benedict Elliott Smith >Priority: Normal > > Introduce a dedicated class to represent UUID version 2, to ensure correct > usage within Cassandra -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17176) Introduce TimeUUID
[ https://issues.apache.org/jira/browse/CASSANDRA-17176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Elliott Smith updated CASSANDRA-17176: --- Status: In Progress (was: Patch Available) > Introduce TimeUUID > -- > > Key: CASSANDRA-17176 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17176 > Project: Cassandra > Issue Type: Sub-task > Components: Local/Other >Reporter: Benedict Elliott Smith >Assignee: Benedict Elliott Smith >Priority: Normal > > Introduce a dedicated class to represent UUID version 2, to ensure correct > usage within Cassandra -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17176) Introduce TimeUUID
[ https://issues.apache.org/jira/browse/CASSANDRA-17176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Elliott Smith updated CASSANDRA-17176: --- Status: Ready to Commit (was: Review In Progress) > Introduce TimeUUID > -- > > Key: CASSANDRA-17176 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17176 > Project: Cassandra > Issue Type: Sub-task > Components: Local/Other >Reporter: Benedict Elliott Smith >Assignee: Benedict Elliott Smith >Priority: Normal > > Introduce a dedicated class to represent UUID version 2, to ensure correct > usage within Cassandra -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17164) CEP-14: Paxos Improvements
[ https://issues.apache.org/jira/browse/CASSANDRA-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Elliott Smith updated CASSANDRA-17164: --- Source Control Link: [d2923275e360a1ee9db498e748c269f701bb3a8b|https://github.com/apache/cassandra/commit/d2923275e360a1ee9db498e748c269f701bb3a8b] (was: [https://github.com/apache/cassandra/commit/d2923275e360a1ee9db498e748c269f701bb3a8b) > CEP-14: Paxos Improvements > -- > > Key: CASSANDRA-17164 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17164 > Project: Cassandra > Issue Type: Improvement > Components: Consistency/Coordination, Consistency/Repair >Reporter: Benedict Elliott Smith >Assignee: Benedict Elliott Smith >Priority: Normal > Fix For: 4.1 > > > This ticket encompasses work for [CEP-14| > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-14%3A+Paxos+Improvements]. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17176) Introduce TimeUUID
[ https://issues.apache.org/jira/browse/CASSANDRA-17176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Elliott Smith updated CASSANDRA-17176: --- Reviewers: Blake Eggleston Status: Review In Progress (was: Patch Available) > Introduce TimeUUID > -- > > Key: CASSANDRA-17176 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17176 > Project: Cassandra > Issue Type: Sub-task > Components: Local/Other >Reporter: Benedict Elliott Smith >Assignee: Benedict Elliott Smith >Priority: Normal > > Introduce a dedicated class to represent UUID version 2, to ensure correct > usage within Cassandra -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17164) CEP-14: Paxos Improvements
[ https://issues.apache.org/jira/browse/CASSANDRA-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Elliott Smith updated CASSANDRA-17164: --- Source Control Link: [https://github.com/apache/cassandra/commit/d2923275e360a1ee9db498e748c269f701bb3a8b Resolution: Fixed Status: Resolved (was: Ready to Commit) > CEP-14: Paxos Improvements > -- > > Key: CASSANDRA-17164 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17164 > Project: Cassandra > Issue Type: Improvement > Components: Consistency/Coordination, Consistency/Repair >Reporter: Benedict Elliott Smith >Assignee: Benedict Elliott Smith >Priority: Normal > Fix For: 4.1 > > > This ticket encompasses work for [CEP-14| > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-14%3A+Paxos+Improvements]. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 02/03: [CASSANDRA-17177] List Appends Are Not Linearizable
This is an automated email from the ASF dual-hosted git repository.
benedict pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit 8960b4d8513e22c4c11c181c520380342935aee7
Author: Benedict Elliott Smith
AuthorDate: Tue Nov 30 17:00:45 2021 +
[CASSANDRA-17177] List Appends Are Not Linearizable
---
.../cassandra/cql3/statements/CQL3CasRequest.java | 38 +++---
.../cql3/statements/ModificationStatement.java | 2 +-
.../org/apache/cassandra/service/CASRequest.java | 3 +-
.../org/apache/cassandra/service/StorageProxy.java | 16 -
4 files changed, 37 insertions(+), 22 deletions(-)
diff --git a/src/java/org/apache/cassandra/cql3/statements/CQL3CasRequest.java
b/src/java/org/apache/cassandra/cql3/statements/CQL3CasRequest.java
index 2a87592..376a65f 100644
--- a/src/java/org/apache/cassandra/cql3/statements/CQL3CasRequest.java
+++ b/src/java/org/apache/cassandra/cql3/statements/CQL3CasRequest.java
@@ -232,11 +232,12 @@ public class CQL3CasRequest implements CASRequest
return builder.build();
}
-public PartitionUpdate makeUpdates(FilteredPartition current, ClientState
state) throws InvalidRequestException
+public PartitionUpdate makeUpdates(FilteredPartition current, ClientState
state, TimeUUID ballot) throws InvalidRequestException
{
PartitionUpdate.Builder updateBuilder = new
PartitionUpdate.Builder(metadata, key, updatedColumns(), conditions.size());
+long timeUuidNanos = 0;
for (RowUpdate upd : updates)
-upd.applyUpdates(current, updateBuilder, state);
+timeUuidNanos = upd.applyUpdates(current, updateBuilder, state,
ballot.msb(), timeUuidNanos);
for (RangeDeletion upd : rangeDeletions)
upd.applyUpdates(current, updateBuilder, state);
@@ -246,6 +247,24 @@ public class CQL3CasRequest implements CASRequest
return partitionUpdate;
}
+private static class CASUpdateParameters extends UpdateParameters
+{
+final long timeUuidMsb;
+long timeUuidNanos;
+
+public CASUpdateParameters(TableMetadata metadata,
RegularAndStaticColumns updatedColumns, ClientState state, QueryOptions
options, long timestamp, int nowInSec, int ttl, Map
prefetchedRows, long timeUuidMsb, long timeUuidNanos) throws
InvalidRequestException
+{
+super(metadata, updatedColumns, state, options, timestamp,
nowInSec, ttl, prefetchedRows);
+this.timeUuidMsb = timeUuidMsb;
+this.timeUuidNanos = timeUuidNanos;
+}
+
+public byte[] nextTimeUUIDAsBytes()
+{
+return TimeUUID.toBytes(timeUuidMsb,
TimeUUIDType.signedBytesToNativeLong(timeUuidNanos++));
+}
+}
+
/**
* Due to some operation on lists, we can't generate the update that a
given Modification statement does before
* we get the values read by the initial read of Paxos. A RowUpdate thus
just store the relevant information
@@ -269,19 +288,14 @@ public class CQL3CasRequest implements CASRequest
this.nowInSeconds = nowInSeconds;
}
-void applyUpdates(FilteredPartition current, PartitionUpdate.Builder
updateBuilder, ClientState state)
+long applyUpdates(FilteredPartition current, PartitionUpdate.Builder
updateBuilder, ClientState state, long timeUuidMsb, long timeUuidNanos)
{
Map map = stmt.requiresRead() ?
Collections.singletonMap(key, current) : null;
-UpdateParameters params =
-new UpdateParameters(metadata,
- updateBuilder.columns(),
- state,
- options,
- timestamp,
- nowInSeconds,
- stmt.getTimeToLive(options),
- map);
+CASUpdateParameters params =
+new CASUpdateParameters(metadata, updateBuilder.columns(),
state, options, timestamp, nowInSeconds,
+ stmt.getTimeToLive(options), map,
timeUuidMsb, timeUuidNanos);
stmt.addUpdateForKey(updateBuilder, clustering, params);
+return params.timeUuidNanos;
}
}
diff --git
a/src/java/org/apache/cassandra/cql3/statements/ModificationStatement.java
b/src/java/org/apache/cassandra/cql3/statements/ModificationStatement.java
index 42b4d45..fd2f044 100644
--- a/src/java/org/apache/cassandra/cql3/statements/ModificationStatement.java
+++ b/src/java/org/apache/cassandra/cql3/statements/ModificationStatement.java
@@ -673,7 +673,7 @@ public abstract class ModificationStatement implements
CQLStatement.SingleKeyspa
if (!request.appliesTo(current))
return current.rowIterator();
-PartitionUpdate updates = request.makeUpdates(current, state);
+
[cassandra] branch trunk updated (eb960b1 -> d292327)
This is an automated email from the ASF dual-hosted git repository. benedict pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git. from eb960b1 Merge branch 'cassandra-4.0' into trunk new 5a0d615 [CASSANDRA-17176] Introduce TimeUUID new 8960b4d [CASSANDRA-17177] List Appends Are Not Linearizable new d292327 CEP-14: Paxos Improvements 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: .build/build-rat.xml |1 + .circleci/config.yml |6 +- .circleci/config.yml.HIGHRES |6 +- .circleci/config.yml.LOWRES|6 +- .circleci/config.yml.MIDRES|6 +- NEWS.txt | 24 + build.xml | 44 +- .../apache/cassandra/auth/FunctionResource.java|2 +- src/java/org/apache/cassandra/batchlog/Batch.java | 16 +- .../cassandra/batchlog/BatchRemoveVerbHandler.java |7 +- .../apache/cassandra/batchlog/BatchlogManager.java | 36 +- .../apache/cassandra/cache/AutoSavingCache.java|5 +- .../cassandra/concurrent/ExecutorFactory.java | 26 +- .../apache/cassandra/concurrent/FutureTask.java|4 +- .../cassandra/concurrent/InfiniteLoopExecutor.java | 73 +- .../org/apache/cassandra/concurrent/Stage.java | 14 +- .../cassandra/concurrent/SyncFutureTask.java |3 +- .../config/CassandraRelevantProperties.java| 15 +- src/java/org/apache/cassandra/config/Config.java | 202 +++- .../apache/cassandra/config/DataStorageSpec.java |2 +- .../cassandra/config/DatabaseDescriptor.java | 199 +++- .../org/apache/cassandra/config/DurationSpec.java |4 +- .../apache/cassandra/config/EncryptionOptions.java | 17 +- src/java/org/apache/cassandra/cql3/CQL3Type.java |6 + src/java/org/apache/cassandra/cql3/Lists.java |7 +- .../org/apache/cassandra/cql3/QueryOptions.java| 16 + .../org/apache/cassandra/cql3/QueryProcessor.java | 40 +- src/java/org/apache/cassandra/cql3/Sets.java |2 +- .../apache/cassandra/cql3/UntypedResultSet.java| 18 + .../apache/cassandra/cql3/UpdateParameters.java|6 + .../cassandra/cql3/functions/AggregateFcts.java| 28 +- .../cql3/functions/BytesConversionFcts.java| 16 +- .../cassandra/cql3/functions/FunctionCall.java |4 +- .../cassandra/cql3/functions/FunctionResolver.java |5 +- .../apache/cassandra/cql3/functions/TimeFcts.java | 16 +- .../cassandra/cql3/statements/CQL3CasRequest.java | 50 +- .../cql3/statements/ModificationStatement.java | 12 +- .../cassandra/cql3/statements/SelectStatement.java | 50 +- .../schema/CreateAggregateStatement.java |4 +- .../statements/schema/CreateFunctionStatement.java |6 +- .../statements/schema/DropAggregateStatement.java |2 +- .../statements/schema/DropFunctionStatement.java |2 +- .../org/apache/cassandra/db/ColumnFamilyStore.java | 84 +- .../org/apache/cassandra/db/ConsistencyLevel.java |6 +- .../org/apache/cassandra/db/CounterMutation.java |7 + src/java/org/apache/cassandra/db/IMutation.java|2 + src/java/org/apache/cassandra/db/Keyspace.java |5 + src/java/org/apache/cassandra/db/Mutation.java | 25 +- .../apache/cassandra/db/MutationVerbHandler.java | 16 +- .../cassandra/db/PartitionRangeReadCommand.java|4 +- src/java/org/apache/cassandra/db/ReadCommand.java |3 +- src/java/org/apache/cassandra/db/ReadQuery.java|8 +- src/java/org/apache/cassandra/db/ReadResponse.java | 12 + .../org/apache/cassandra/db/SimpleBuilders.java|5 +- .../cassandra/db/SinglePartitionReadCommand.java | 17 +- .../org/apache/cassandra/db/SystemKeyspace.java| 242 +++- .../cassandra/db/SystemKeyspaceMigrator40.java |3 +- .../cassandra/db/commitlog/CommitLogReplayer.java |1 - .../db/compaction/AbstractCompactionStrategy.java |4 +- .../db/compaction/AbstractCompactionTask.java |4 +- .../db/compaction/AbstractStrategyHolder.java |4 +- .../cassandra/db/compaction/CompactionInfo.java| 12 +- .../compaction/CompactionInterruptedException.java | 10 +- .../db/compaction/CompactionIterator.java | 103 +- .../cassandra/db/compaction/CompactionManager.java | 29 +- .../db/compaction/CompactionStrategyHolder.java|4 +- .../db/compaction/CompactionStrategyManager.java | 16 +- .../cassandra/db/compaction/CompactionTask.java|8 +- .../db/compaction/PendingRepairHolder.java |8 +- .../db/compaction/PendingRepairManager.java| 86 +- .../a
[cassandra-dtest] branch trunk updated: CASSANDRA-17164
This is an automated email from the ASF dual-hosted git repository.
benedict 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 cf10400 CASSANDRA-17164
cf10400 is described below
commit cf10400a79755de2d3e8ae058cfd45fe262e476b
Author: Benedict Elliott Smith
AuthorDate: Mon Nov 29 22:22:52 2021 +
CASSANDRA-17164
---
client_request_metrics_local_remote_test.py | 2 +-
secondary_indexes_test.py | 20 ++--
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/client_request_metrics_local_remote_test.py
b/client_request_metrics_local_remote_test.py
index f0207ec..476d462 100644
--- a/client_request_metrics_local_remote_test.py
+++ b/client_request_metrics_local_remote_test.py
@@ -59,7 +59,7 @@ class TestClientRequestMetricsLocalRemote(Tester):
# Run batch test:
query = 'BEGIN BATCH '
for i in murmur3_hashes.keys():
-for y in range(0, 100):
+for y in range(0, 50):
query += "INSERT INTO ks.test (id, ord, val) VALUES ({}, {},
'aaa')".format(i, y)
query += 'APPLY BATCH;'
session.execute(query)
diff --git a/secondary_indexes_test.py b/secondary_indexes_test.py
index 8007757..16cf447 100644
--- a/secondary_indexes_test.py
+++ b/secondary_indexes_test.py
@@ -345,8 +345,8 @@ class TestSecondaryIndexes(Tester):
# Verify that the index is marked as built and it can answer queries
and accept writes
assert_one(session, """SELECT table_name, index_name FROM
system."IndexInfo" WHERE table_name='k'""", ['k', 'idx'])
-assert_length_equal(node.grep_log('became queryable after successful
build'), 1)
-assert_length_equal(node.grep_log('registered and writable'), 1)
+assert_length_equal(node.grep_log('idx.*became queryable after
successful build'), 1)
+assert_length_equal(node.grep_log('idx.*registered and writable'), 1)
session.execute("INSERT INTO k.t(k, v) VALUES (1, 1)")
assert_all(session, "SELECT k FROM k.t WHERE v = 1", [[0], [1]],
ignore_order=True)
@@ -361,8 +361,8 @@ class TestSecondaryIndexes(Tester):
# Verify that the index is not built, not marked as built, and it
still can answer queries and accept writes
assert before_files == after_files
assert_none(session, """SELECT * FROM system."IndexInfo" WHERE
table_name='k'""")
-assert_length_equal(node.grep_log('became queryable', from_mark=mark),
0)
-assert_length_equal(node.grep_log('became writable', from_mark=mark),
0)
+assert_length_equal(node.grep_log('idx.*became queryable',
from_mark=mark), 0)
+assert_length_equal(node.grep_log('idx.*became writable',
from_mark=mark), 0)
session.execute("INSERT INTO k.t(k, v) VALUES (2, 1)")
assert_all(session, "SELECT k FROM k.t WHERE v = 1", [[0], [1], [2]],
ignore_order=True)
@@ -379,8 +379,8 @@ class TestSecondaryIndexes(Tester):
# Verify that the index is rebuilt, marked as built, and it still can
answer queries and accept writes
assert before_files != after_files
assert_one(session, """SELECT table_name, index_name FROM
system."IndexInfo" WHERE table_name='k'""", ['k', 'idx'])
-assert_length_equal(node.grep_log('became queryable after successful
build', from_mark=mark), 1)
-assert_length_equal(node.grep_log('registered and writable',
from_mark=mark), 1)
+assert_length_equal(node.grep_log('idx.*became queryable after
successful build', from_mark=mark), 1)
+assert_length_equal(node.grep_log('idx.*registered and writable',
from_mark=mark), 1)
session.execute("INSERT INTO k.t(k, v) VALUES (3, 1)")
assert_all(session, "SELECT k FROM k.t WHERE v = 1", [[0], [1], [2],
[3]], ignore_order=True)
@@ -395,8 +395,8 @@ class TestSecondaryIndexes(Tester):
# Verify that the index is not built, not marked as built, and it
still can answer queries and accept writes
assert before_files == after_files
assert_none(session, """SELECT * FROM system."IndexInfo" WHERE
table_name='k'""")
-assert_length_equal(node.grep_log('became queryable', from_mark=mark),
0)
-assert_length_equal(node.grep_log('became writable', from_mark=mark),
0)
+assert_length_equal(node.grep_log('idx.*became queryable',
from_mark=mark), 0)
+assert_length_equal(node.grep_log('idx.*became writable',
from_mark=mark), 0)
session.execute("INSERT INTO k.t(k, v) VALUES (4, 1)")
assert_all(session, "SELECT k FROM k.t WHERE v = 1", [[0], [1], [2],
[3], [4]], ignore_order=True)
@@ -409,8 +409,8 @@ class TestSecondaryIndexes(Tester):
# Verify that the index is rebuilt, marked as built, and it still can
answer queries and accept writes
assert before_files != after_files
[jira] [Commented] (CASSANDRA-17425) Add new CQL function maxWritetime
[ https://issues.apache.org/jira/browse/CASSANDRA-17425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504483#comment-17504483 ] Yifan Cai commented on CASSANDRA-17425: --- Hi Benjamin, the goal of this patch is to add a function to retrieve the latest modification time of a multi-cell type. It is different from CASSANDRA-8877, which is to retrieve the timestamp of _one_ cell from a multi-cell type and end-user cannot tell if the retrieved timestamp is the latest. bq. I am always a bit reluctant to add new selectors as I often had to modify all of them to introduce new features. I can see the concerns when I was working on the patch. It feels like the selector framework needs some refactor, which I did not do in this patch. We can look more closely at the patch and only commit when the majority is happy with changes. > Add new CQL function maxWritetime > - > > Key: CASSANDRA-17425 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17425 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Syntax >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > > The function "writetime" does not support multi-cell types, e.g. collections > and UDT. It would be useful to enable querying the latest modified timestamp > of a column value. > I'd like to propose to add a new function named "maxWritetime", which returns > the largest timestamp amongst the cells. When being applied to the single > cell types, it returns the same result as "writetime". -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17429) Use only one image for all CircleCI builds; Switch to "latest" tag
[ https://issues.apache.org/jira/browse/CASSANDRA-17429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17429: Fix Version/s: 3.0.x 3.11.x 4.0.x 4.x > Use only one image for all CircleCI builds; Switch to "latest" tag > -- > > Key: CASSANDRA-17429 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17429 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x > > > While working on the latest CircleCI issues, we noticed some inconsistencies > in our config. > There were different images used in CircleCI for Java 8 and Java 11. > We need to use only the latest images everywhere, same as in Jenkins. > Also, we use specific date tag which is inconvenient as every time a new > image is published, we need to change the tag in config.yml on all Cassandra > branches. Better to switch to "latest" tag as we already use it successfully > in Jenkins. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17429) Use only one image for all CircleCI builds; Switch to "latest" tag
[ https://issues.apache.org/jira/browse/CASSANDRA-17429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17429: Change Category: Quality Assurance Complexity: Low Hanging Fruit Component/s: CI Assignee: Ekaterina Dimitrova Status: Open (was: Triage Needed) > Use only one image for all CircleCI builds; Switch to "latest" tag > -- > > Key: CASSANDRA-17429 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17429 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > While working on the latest CircleCI issues, we noticed some inconsistencies > in our config. > There were different images used in CircleCI for Java 8 and Java 11. > We need to use only the latest images everywhere, same as in Jenkins. > Also, we use specific date tag which is inconvenient as every time a new > image is published, we need to change the tag in config.yml on all Cassandra > branches. Better to switch to "latest" tag as we already use it successfully > in Jenkins. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17429) Use only one image for all CircleCI builds; Switch to "latest" tag
Ekaterina Dimitrova created CASSANDRA-17429: --- Summary: Use only one image for all CircleCI builds; Switch to "latest" tag Key: CASSANDRA-17429 URL: https://issues.apache.org/jira/browse/CASSANDRA-17429 Project: Cassandra Issue Type: Task Reporter: Ekaterina Dimitrova While working on the latest CircleCI issues, we noticed some inconsistencies in our config. There were different images used in CircleCI for Java 8 and Java 11. We need to use only the latest images everywhere, same as in Jenkins. Also, we use specific date tag which is inconvenient as every time a new image is published, we need to change the tag in config.yml on all Cassandra branches. Better to switch to "latest" tag as we already use it successfully in Jenkins. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17428) Fail build when Ant is not of a certain version
[ https://issues.apache.org/jira/browse/CASSANDRA-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504475#comment-17504475 ] Stefan Miklosovic commented on CASSANDRA-17428: --- Great! I will go with Brandon's stuff. > Fail build when Ant is not of a certain version > --- > > Key: CASSANDRA-17428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17428 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Low > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x > > > As of writing this ticket, trunk is known to be buildable with Ant 1.10 and > users have reported build failures on Ant 1.9 (see CASSANDRA-16831). > There should be a check which fails the build if Ant used to build Cassanra > source code was not at least 1.10. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17164) CEP-14: Paxos Improvements
[
https://issues.apache.org/jira/browse/CASSANDRA-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504438#comment-17504438
]
Benedict Elliott Smith commented on CASSANDRA-17164:
I'm about to commit.
FYI, this patch appears to break
{{write_failures_test.py::TestMultiDCWriteFailures::test_oversized_mutation}}
however this is a broken test. I have opted not to fix it as part of this work,
but will file a follow-up ticket to decide how to proceed. The test believed it
was checking whether hints were written, but since hints are written only at
expiration of the callback it was simply not witnessing them - introducing a
{{sleep(10)}} breaks the test on trunk. It may be that this is actually broken
behaviour in Cassandra that the test failed to detect.
> CEP-14: Paxos Improvements
> --
>
> Key: CASSANDRA-17164
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17164
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Coordination, Consistency/Repair
>Reporter: Benedict Elliott Smith
>Assignee: Benedict Elliott Smith
>Priority: Normal
> Fix For: 4.1
>
>
> This ticket encompasses work for [CEP-14|
> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-14%3A+Paxos+Improvements].
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504435#comment-17504435 ] Ekaterina Dimitrova commented on CASSANDRA-17351: - CircleCI run pushed [here|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1410/workflows/40d7c147-ad7d-4e51-8ee0-ddfa98959c33]. I will open a separate ticket and do the cleaning of our Circle config - what images and tags we use. > Pip doesn't install ccm every time > -- > > Key: CASSANDRA-17351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Urgent > Fix For: 4.1 > > > In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to > run without -e for ccm in order to address the moveable tag. That worked for > some time until last night. I successfully retagged and now ccm is not > re-installed in Circle CI. > Jenkins picked stuff though. But it was acting unreliably and weird so > rerunning now things there. Results pending. > Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still > pending results. I don't think this will be permanent solution and I am not > sure whether it will affect also the previous branches in a way. We need to > further investigate it and test. > For now I will ask people to test with -e until we figure it out. > CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17370) Add flag enabling operators to restrict use of ALLOW FILTERING in queries
[ https://issues.apache.org/jira/browse/CASSANDRA-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Rackliffe updated CASSANDRA-17370: Reviewers: Andres de la Peña, Joshua McKenzie (was: Andres de la Peña, Caleb Rackliffe, David Capwell) > Add flag enabling operators to restrict use of ALLOW FILTERING in queries > - > > Key: CASSANDRA-17370 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17370 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Semantics, Feature/Guardrails >Reporter: Savni Nagarkar >Assignee: Savni Nagarkar >Priority: Normal > Fix For: 4.x > > > This ticket adds the ability for operators to disallow use of ALLOW FILTERING > predicates in CQL SELECT statements. As queries that ALLOW FILTERING can > place additional load on the database, the flag enables operators to provide > tighter bounds on performance guarantees. The patch includes a new yaml > property, as well as a hot property enabling the value to be modified via JMX > at runtime. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504408#comment-17504408 ] Ekaterina Dimitrova edited comment on CASSANDRA-17351 at 3/10/22, 4:47 PM: --- For the record, further testing confirmed by Sam in Slack (details posted in the testing section), approvals to commit gathered. To [https://github.com/riptano/ccm.git] 0f9ae08..7e5ff6a master -> master Retagging done. I will push now CI test runs to double check again that CI is fine before sending update to the community. was (Author: e.dimitrova): For. the record, further testing confirmed by Sam in Slack, approval's gathered. To https://github.com/riptano/ccm.git 0f9ae08..7e5ff6a master -> master Retagging done. I will push now CI test runs to double check again that CI is fine before sending update to the community. > Pip doesn't install ccm every time > -- > > Key: CASSANDRA-17351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Urgent > Fix For: 4.1 > > > In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to > run without -e for ccm in order to address the moveable tag. That worked for > some time until last night. I successfully retagged and now ccm is not > re-installed in Circle CI. > Jenkins picked stuff though. But it was acting unreliably and weird so > rerunning now things there. Results pending. > Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still > pending results. I don't think this will be permanent solution and I am not > sure whether it will affect also the previous branches in a way. We need to > further investigate it and test. > For now I will ask people to test with -e until we figure it out. > CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17351: Fix Version/s: 4.1 (was: 4.x) > Pip doesn't install ccm every time > -- > > Key: CASSANDRA-17351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Urgent > Fix For: 4.1 > > > In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to > run without -e for ccm in order to address the moveable tag. That worked for > some time until last night. I successfully retagged and now ccm is not > re-installed in Circle CI. > Jenkins picked stuff though. But it was acting unreliably and weird so > rerunning now things there. Results pending. > Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still > pending results. I don't think this will be permanent solution and I am not > sure whether it will affect also the previous branches in a way. We need to > further investigate it and test. > For now I will ask people to test with -e until we figure it out. > CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17351: Source Control Link: https://github.com/riptano/ccm/commit/7e5ff6af02ac74c32c4380e1d1690b23e2a2c334 Resolution: Fixed Status: Resolved (was: Ready to Commit) > Pip doesn't install ccm every time > -- > > Key: CASSANDRA-17351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Urgent > Fix For: 4.1 > > > In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to > run without -e for ccm in order to address the moveable tag. That worked for > some time until last night. I successfully retagged and now ccm is not > re-installed in Circle CI. > Jenkins picked stuff though. But it was acting unreliably and weird so > rerunning now things there. Results pending. > Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still > pending results. I don't think this will be permanent solution and I am not > sure whether it will affect also the previous branches in a way. We need to > further investigate it and test. > For now I will ask people to test with -e until we figure it out. > CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17351: Reviewers: Ekaterina Dimitrova, Michael Semb Wever, Sam Tunnicliffe Status: Review In Progress (was: Patch Available) > Pip doesn't install ccm every time > -- > > Key: CASSANDRA-17351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Urgent > Fix For: 4.x > > > In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to > run without -e for ccm in order to address the moveable tag. That worked for > some time until last night. I successfully retagged and now ccm is not > re-installed in Circle CI. > Jenkins picked stuff though. But it was acting unreliably and weird so > rerunning now things there. Results pending. > Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still > pending results. I don't think this will be permanent solution and I am not > sure whether it will affect also the previous branches in a way. We need to > further investigate it and test. > For now I will ask people to test with -e until we figure it out. > CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[
https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17351:
Test and Documentation Plan:
[https://app.circleci.com/pipelines/github/beobal/cassandra?branch=cci%2Ftrunk&filter=all]
Pipeline 386 was run when the tag pointed at
{{{}dcce52eec82a912c3b799590229e332a42affd0b{}}}. If you drill into
{{j8_separate_tests -> j8_cqlsh-dtests-py38-no-vnodes (or one of the other
similar steps) -> Configure virtualenv and python Dependencies}} (edited)
We can see this:
{code:java}
Resolved https://github.com/beobal/ccm.git
to commit dcce52eec82a912c3b799590229e332a42affd0b
...
Successfully installed cassandra-driver-3.24.0 ccm-3.1.6.dev1290...{code}
Pipeline 387 was run after retagging, but without changing anything on the
Cassandra, Circle or dtest side. Following the same path shows:
{code:java}
Resolved https://github.com/beobal/ccm.git
to commit 180f2879ffce121f102f26d16883693c01f3c9c8{code}
...
Successfully installed cassandra-driver-3.24.0 ccm-3.1.6.dev1291...
so _just_ moving the tag causes the version bump from {{3.1.6.dev1290}} to
{{3.1.6.dev1291}}
was:
[https://app.circleci.com/pipelines/github/beobal/cassandra?branch=cci%2Ftrunk&filter=all]
[9:19|https://the-asf.slack.com/archives/C0369H83D1T/p1646921950420359]
pipeline 386 was run when the tag pointed at
{{{}dcce52eec82a912c3b799590229e332a42affd0b{}}}. If you drill into
{{j8_separate_tests -> j8_cqlsh-dtests-py38-no-vnodes (or one of the other
similar steps) -> Configure virtualenv and python Dependencies}} (edited)
[9:19|https://the-asf.slack.com/archives/C0369H83D1T/p1646921981105489]
you can see this:
[9:19|https://the-asf.slack.com/archives/C0369H83D1T/p1646921995076269]
Resolved [https://github.com/beobal/ccm.git]
to commit dcce52eec82a912c3b799590229e332a42affd0b
...
Successfully installed cassandra-driver-3.24.0 ccm-3.1.6.dev1290...
[9:20|https://the-asf.slack.com/archives/C0369H83D1T/p1646922009393759]
Pipeline 387 was run after retagging, but without changing anything on the C*,
Circle or dtest side. Following the same path shows:
[9:20|https://the-asf.slack.com/archives/C0369H83D1T/p1646922028259079]
Resolved [https://github.com/beobal/ccm.git]
to commit 180f2879ffce121f102f26d16883693c01f3c9c8
...
Successfully installed cassandra-driver-3.24.0 ccm-3.1.6.dev1291...
[9:22|https://the-asf.slack.com/archives/C0369H83D1T/p1646922124340229]
so _just_ moving the tag causes the version bump from {{3.1.6.dev1290}} to
{{3.1.6.dev1291}}
> Pip doesn't install ccm every time
> --
>
> Key: CASSANDRA-17351
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17351
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Urgent
> Fix For: 4.x
>
>
> In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to
> run without -e for ccm in order to address the moveable tag. That worked for
> some time until last night. I successfully retagged and now ccm is not
> re-installed in Circle CI.
> Jenkins picked stuff though. But it was acting unreliably and weird so
> rerunning now things there. Results pending.
> Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still
> pending results. I don't think this will be permanent solution and I am not
> sure whether it will affect also the previous branches in a way. We need to
> further investigate it and test.
> For now I will ask people to test with -e until we figure it out.
> CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17351: Status: Ready to Commit (was: Review In Progress) > Pip doesn't install ccm every time > -- > > Key: CASSANDRA-17351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Urgent > Fix For: 4.x > > > In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to > run without -e for ccm in order to address the moveable tag. That worked for > some time until last night. I successfully retagged and now ccm is not > re-installed in Circle CI. > Jenkins picked stuff though. But it was acting unreliably and weird so > rerunning now things there. Results pending. > Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still > pending results. I don't think this will be permanent solution and I am not > sure whether it will affect also the previous branches in a way. We need to > further investigate it and test. > For now I will ask people to test with -e until we figure it out. > CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[
https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17351:
Authors: Michael Semb Wever, Sam Tunnicliffe (was:
Ekaterina Dimitrova)
Test and Documentation Plan:
[https://app.circleci.com/pipelines/github/beobal/cassandra?branch=cci%2Ftrunk&filter=all]
[9:19|https://the-asf.slack.com/archives/C0369H83D1T/p1646921950420359]
pipeline 386 was run when the tag pointed at
{{{}dcce52eec82a912c3b799590229e332a42affd0b{}}}. If you drill into
{{j8_separate_tests -> j8_cqlsh-dtests-py38-no-vnodes (or one of the other
similar steps) -> Configure virtualenv and python Dependencies}} (edited)
[9:19|https://the-asf.slack.com/archives/C0369H83D1T/p1646921981105489]
you can see this:
[9:19|https://the-asf.slack.com/archives/C0369H83D1T/p1646921995076269]
Resolved [https://github.com/beobal/ccm.git]
to commit dcce52eec82a912c3b799590229e332a42affd0b
...
Successfully installed cassandra-driver-3.24.0 ccm-3.1.6.dev1290...
[9:20|https://the-asf.slack.com/archives/C0369H83D1T/p1646922009393759]
Pipeline 387 was run after retagging, but without changing anything on the C*,
Circle or dtest side. Following the same path shows:
[9:20|https://the-asf.slack.com/archives/C0369H83D1T/p1646922028259079]
Resolved [https://github.com/beobal/ccm.git]
to commit 180f2879ffce121f102f26d16883693c01f3c9c8
...
Successfully installed cassandra-driver-3.24.0 ccm-3.1.6.dev1291...
[9:22|https://the-asf.slack.com/archives/C0369H83D1T/p1646922124340229]
so _just_ moving the tag causes the version bump from {{3.1.6.dev1290}} to
{{3.1.6.dev1291}}
Status: Patch Available (was: In Progress)
> Pip doesn't install ccm every time
> --
>
> Key: CASSANDRA-17351
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17351
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Urgent
> Fix For: 4.x
>
>
> In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to
> run without -e for ccm in order to address the moveable tag. That worked for
> some time until last night. I successfully retagged and now ccm is not
> re-installed in Circle CI.
> Jenkins picked stuff though. But it was acting unreliably and weird so
> rerunning now things there. Results pending.
> Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still
> pending results. I don't think this will be permanent solution and I am not
> sure whether it will affect also the previous branches in a way. We need to
> further investigate it and test.
> For now I will ask people to test with -e until we figure it out.
> CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504408#comment-17504408 ] Ekaterina Dimitrova commented on CASSANDRA-17351: - For. the record, further testing confirmed by Sam in Slack, approval's gathered. To https://github.com/riptano/ccm.git 0f9ae08..7e5ff6a master -> master Retagging done. I will push now CI test runs to double check again that CI is fine before sending update to the community. > Pip doesn't install ccm every time > -- > > Key: CASSANDRA-17351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Urgent > Fix For: 4.x > > > In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to > run without -e for ccm in order to address the moveable tag. That worked for > some time until last night. I successfully retagged and now ccm is not > re-installed in Circle CI. > Jenkins picked stuff though. But it was acting unreliably and weird so > rerunning now things there. Results pending. > Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still > pending results. I don't think this will be permanent solution and I am not > sure whether it will affect also the previous branches in a way. We need to > further investigate it and test. > For now I will ask people to test with -e until we figure it out. > CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17188) Guardrails for consistency levels
[
https://issues.apache.org/jira/browse/CASSANDRA-17188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504332#comment-17504332
]
Andres de la Peña commented on CASSANDRA-17188:
---
Thanks for the review. I have just applied your suggestion on refactoring the
part about config in the new tests:
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/1392]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1347/workflows/5b4e4f04-f0ee-4cd3-98b3-52e509efcb2a]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1347/workflows/53a8ab2f-d4c5-437e-95df-e368f5d470e5]|
As for the serial CL, indeed the guardrail only checks the one specified by the
client.
> Guardrails for consistency levels
> -
>
> Key: CASSANDRA-17188
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17188
> 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: 1h 10m
> Remaining Estimate: 0h
>
> Add guardrails for read/write consistency levels, for example:
> {code:java}
> # Guardrail to warn about or reject read consistency levels.
> # By default all consistency levels are allowed.
> read_consistency_levels:
> warned: []
> disallowed: []
> # Guardrail to warn about or reject write consistency levels.
> # By default all consistency levels are allowed.
> write_consistency_levels:
> warned: []
> disallowed: []
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17405) Test failures: org.apache.cassandra.distributed.test.ring.BootstrapTest.bootstrapTest
[ https://issues.apache.org/jira/browse/CASSANDRA-17405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams reassigned CASSANDRA-17405: Assignee: Brandon Williams > Test failures: > org.apache.cassandra.distributed.test.ring.BootstrapTest.bootstrapTest > - > > Key: CASSANDRA-17405 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17405 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Ekaterina Dimitrova >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.x > > > I see one failure in Jenkins but it seems more flaky this week as I have it > failing in CircleCI with almost all my rung with Midres so seems like worth > to check what happened. > [https://ci-cassandra.apache.org/job/Cassandra-trunk/959/testReport/org.apache.cassandra.distributed.test.ring/BootstrapTest/bootstrapTest/] > https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1404/workflows/5bb5412a-87a9-4b5f-94bd-ab0cd618e0b9/jobs/9205 -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17337) Fix flaky test - dtest.secondary_indexes_test.TestSecondaryIndexes.test_6924_dropping_ks
[
https://issues.apache.org/jira/browse/CASSANDRA-17337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504271#comment-17504271
]
Brandon Williams commented on CASSANDRA-17337:
--
I think I've spent enough cycles on this, and the path left is not simple. If
it is a long running bug, it's not one of great importance to solve, so I feel
like this is going to be 99% effort for 1% gain.
> Fix flaky test -
> dtest.secondary_indexes_test.TestSecondaryIndexes.test_6924_dropping_ks
>
>
> Key: CASSANDRA-17337
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17337
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/2i Index
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.11.x, 4.0.x, 4.x
>
> Attachments: test.cql
>
>
> Failed 1 times in the last 30 runs. Flakiness: 6%, Stability: 96%
> Error Message
> cassandra.OperationTimedOut: errors={'127.0.0.2:9042': 'Client request
> timeout. See Session.execute[_async](timeout)'}, last_host=127.0.0.2:9042
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17337) Fix flaky test - dtest.secondary_indexes_test.TestSecondaryIndexes.test_6924_dropping_ks
[
https://issues.apache.org/jira/browse/CASSANDRA-17337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams reassigned CASSANDRA-17337:
Assignee: (was: Brandon Williams)
> Fix flaky test -
> dtest.secondary_indexes_test.TestSecondaryIndexes.test_6924_dropping_ks
>
>
> Key: CASSANDRA-17337
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17337
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/2i Index
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 3.11.x, 4.0.x, 4.x
>
> Attachments: test.cql
>
>
> Failed 1 times in the last 30 runs. Flakiness: 6%, Stability: 96%
> Error Message
> cassandra.OperationTimedOut: errors={'127.0.0.2:9042': 'Client request
> timeout. See Session.execute[_async](timeout)'}, last_host=127.0.0.2:9042
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15266) java internal exception on attempt to UPDATE a row using CONTAINS operator
[
https://issues.apache.org/jira/browse/CASSANDRA-15266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-15266:
--
Fix Version/s: 3.0.27
3.11.13
4.1
4.0.4
(was: 3.0.x)
(was: 3.11.x)
(was: 4.0.x)
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra/commit/c52b5ab95cf314a7983141f74c97744ff3ecbc81
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> java internal exception on attempt to UPDATE a row using CONTAINS operator
> --
>
> Key: CASSANDRA-15266
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15266
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/CQL
>Reporter: Konstantin
>Assignee: Maciej Sokol
>Priority: Normal
> Labels: lhf
> Fix For: 3.0.27, 3.11.13, 4.1, 4.0.4
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> kostja@atlas ~ % cqlsh -ucassandra -pcassandra
> Connected to My Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 3.11.4 | CQL spec 3.4.4 | Native protocol v4]
> Use HELP for help.
> cassandra@cqlsh> CREATE KEYSPACE t1 WITH replication =
> \{'class':'SimpleStrategy', 'replication_factor' : 1};
> cassandra@cqlsh> use t1;
> cassandra@cqlsh:t1> create table t (a int, b frozen>, c int,
> primary key (a, b));
> cassandra@cqlsh:t1> insert into t (a, b, c) values (1, \{1:1, 2:2}, 3);
> cassandra@cqlsh:t1> update t set c=3 where a=1 and b contains 1;
> ServerError: java.lang.UnsupportedOperationException
>
> Server log file:
> ```
> ERROR [Native-Transport-Requests-1] 2019-08-07 17:02:59,283
> QueryMessage.java:129 - Unexpected error during query
> java.lang.UnsupportedOperationException: null
> at
> org.apache.cassandra.cql3.restrictions.SingleColumnRestriction$ContainsRestriction.appendTo(SingleColumnRestriction.java:454)
> ~[a
> pache-cassandra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.cql3.restrictions.ClusteringColumnRestrictions.valuesAsClustering(ClusteringColumnRestrictions.java:109)
> ~[a
> pache-cassandra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.cql3.restrictions.StatementRestrictions.getClusteringColumns(StatementRestrictions.java:770)
> ~[apache-cassan
> dra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.createClustering(ModificationStatement.java:312)
> ~[apache-cassandra-3.
> 11.4.jar:3.11.4]
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.addUpdates(ModificationStatement.java:677)
> ~[apache-cassandra-3.11.4.j
> ar:3.11.4]
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.getMutations(ModificationStatement.java:635)
> ~[apache-cassandra-3.11.4
> .jar:3.11.4]
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithoutCondition(ModificationStatement.java:437)
> ~[apache-cassa
> ndra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:425)
> ~[apache-cassandra-3.11.4.jar:
> 3.11.4]
> at
> org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:225)
> ~[apache-cassandra-3.11.4.jar:3.11.4]
> at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:256)
> ~[apache-cassandra-3.11.4.jar:3.11.4]
> at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:241)
> ~[apache-cassandra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.transport.messages.QueryMessage.execute(QueryMessage.java:116)
> ~[apache-cassandra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:566)
> [apache-cassandra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:410)
> [apache-cassandra-3.11.4.jar:3.11.4]
> at
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
> [netty-all-4.0.44.Final.jar:4.0.44
> ...
> ```
> +Additional information for newcomers:+
> {{CONTAINS}} and {{CONTAINS KEY}} restrictions are not supported for
> {{UPDATE}} or {{DELETE}} operations but they should be properly rejected with
> a proper error message.
> To fix that problem a new check should be added in the
> {{StatementRestrictions}} constructor to thrown an
> {{InvalidRequestException}} if the relation operator is a {{CONTAINS}} or
> {{CONTAINS_KEY}} and the {{StatementType}} an {{UPDATE}} or a {{DELETION}}.
> Some unit tests should be added to {{UpdateTest}} an {{DeleteTest}} to test
> the behavior.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CASSANDRA-15266) java internal exception on attempt to UPDATE a row using CONTAINS operator
[
https://issues.apache.org/jira/browse/CASSANDRA-15266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504263#comment-17504263
]
Andres de la Peña commented on CASSANDRA-15266:
---
Committed to 3.0 as
[c52b5ab95cf314a7983141f74c97744ff3ecbc81|https://github.com/apache/cassandra/commit/c52b5ab95cf314a7983141f74c97744ff3ecbc81]
and merged to
[3.11|https://github.com/apache/cassandra/commit/fcdb3d154ed111dbeefe8283bf729d6bd172384a],
[4.0|https://github.com/apache/cassandra/commit/bdeafa0b79697b481ef4272fee606e70dad6764c]
and
[trunk|https://github.com/apache/cassandra/commit/eb960b19170e36bd9c52365ef15514a4d1ed9419].
Thanks for the patch.
> java internal exception on attempt to UPDATE a row using CONTAINS operator
> --
>
> Key: CASSANDRA-15266
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15266
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/CQL
>Reporter: Konstantin
>Assignee: Maciej Sokol
>Priority: Normal
> Labels: lhf
> Fix For: 3.0.x, 3.11.x, 4.0.x
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> kostja@atlas ~ % cqlsh -ucassandra -pcassandra
> Connected to My Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 3.11.4 | CQL spec 3.4.4 | Native protocol v4]
> Use HELP for help.
> cassandra@cqlsh> CREATE KEYSPACE t1 WITH replication =
> \{'class':'SimpleStrategy', 'replication_factor' : 1};
> cassandra@cqlsh> use t1;
> cassandra@cqlsh:t1> create table t (a int, b frozen>, c int,
> primary key (a, b));
> cassandra@cqlsh:t1> insert into t (a, b, c) values (1, \{1:1, 2:2}, 3);
> cassandra@cqlsh:t1> update t set c=3 where a=1 and b contains 1;
> ServerError: java.lang.UnsupportedOperationException
>
> Server log file:
> ```
> ERROR [Native-Transport-Requests-1] 2019-08-07 17:02:59,283
> QueryMessage.java:129 - Unexpected error during query
> java.lang.UnsupportedOperationException: null
> at
> org.apache.cassandra.cql3.restrictions.SingleColumnRestriction$ContainsRestriction.appendTo(SingleColumnRestriction.java:454)
> ~[a
> pache-cassandra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.cql3.restrictions.ClusteringColumnRestrictions.valuesAsClustering(ClusteringColumnRestrictions.java:109)
> ~[a
> pache-cassandra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.cql3.restrictions.StatementRestrictions.getClusteringColumns(StatementRestrictions.java:770)
> ~[apache-cassan
> dra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.createClustering(ModificationStatement.java:312)
> ~[apache-cassandra-3.
> 11.4.jar:3.11.4]
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.addUpdates(ModificationStatement.java:677)
> ~[apache-cassandra-3.11.4.j
> ar:3.11.4]
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.getMutations(ModificationStatement.java:635)
> ~[apache-cassandra-3.11.4
> .jar:3.11.4]
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithoutCondition(ModificationStatement.java:437)
> ~[apache-cassa
> ndra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:425)
> ~[apache-cassandra-3.11.4.jar:
> 3.11.4]
> at
> org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:225)
> ~[apache-cassandra-3.11.4.jar:3.11.4]
> at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:256)
> ~[apache-cassandra-3.11.4.jar:3.11.4]
> at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:241)
> ~[apache-cassandra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.transport.messages.QueryMessage.execute(QueryMessage.java:116)
> ~[apache-cassandra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:566)
> [apache-cassandra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:410)
> [apache-cassandra-3.11.4.jar:3.11.4]
> at
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
> [netty-all-4.0.44.Final.jar:4.0.44
> ...
> ```
> +Additional information for newcomers:+
> {{CONTAINS}} and {{CONTAINS KEY}} restrictions are not supported for
> {{UPDATE}} or {{DELETE}} operations but they should be properly rejected with
> a proper error message.
> To fix that problem a new check should be added in the
> {{StatementRestrictions}} constructor to thrown an
> {{InvalidRequestException}} if the relation operator is a {{CONTAINS}} or
> {{CONTAINS_KEY}} and the {{StatementType}} an {{UPDATE}} or a {{DELETION}}.
> Some unit tests should be added to {{UpdateTest}} an {{DeleteTest}} to test
> the behavior.
--
This message wa
[cassandra] branch trunk updated (852d7b6 -> eb960b1)
This is an automated email from the ASF dual-hosted git repository. adelapena pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 852d7b6 ninja: move nosetests.xml back to .jenkins/Jenkinsfile new c52b5ab Disallow CONTAINS for UPDATE and DELETE new fcdb3d1 Merge branch 'cassandra-3.0' into cassandra-3.11 new bdeafa0 Merge branch 'cassandra-3.11' into cassandra-4.0 new eb960b1 Merge branch 'cassandra-4.0' 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: CHANGES.txt| 1 + .../cql3/restrictions/StatementRestrictions.java | 6 .../validation/operations/CompactStorageTest.java | 10 +++ .../cql3/validation/operations/DeleteTest.java | 33 ++ .../cql3/validation/operations/UpdateTest.java | 31 5 files changed, 65 insertions(+), 16 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 (04c1289 -> bdeafa0)
This is an automated email from the ASF dual-hosted git repository. adelapena pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 04c1289 Merge branch 'cassandra-3.11' into cassandra-4.0 new c52b5ab Disallow CONTAINS for UPDATE and DELETE new fcdb3d1 Merge branch 'cassandra-3.0' into cassandra-3.11 new bdeafa0 Merge branch 'cassandra-3.11' into cassandra-4.0 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: CHANGES.txt| 1 + .../cql3/restrictions/StatementRestrictions.java | 6 .../validation/operations/CompactStorageTest.java | 10 +++ .../cql3/validation/operations/DeleteTest.java | 33 ++ .../cql3/validation/operations/UpdateTest.java | 31 5 files changed, 65 insertions(+), 16 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-3.0' into cassandra-3.11
This is an automated email from the ASF dual-hosted git repository. adelapena pushed a commit to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit fcdb3d154ed111dbeefe8283bf729d6bd172384a Merge: b18a9f0 c52b5ab Author: Andrés de la Peña AuthorDate: Thu Mar 10 13:08:38 2022 + Merge branch 'cassandra-3.0' into cassandra-3.11 CHANGES.txt| 1 + .../cql3/restrictions/StatementRestrictions.java | 6 .../cql3/validation/operations/DeleteTest.java | 33 ++ .../cql3/validation/operations/UpdateTest.java | 31 4 files changed, 60 insertions(+), 11 deletions(-) diff --cc CHANGES.txt index c6708f5,df0a734..3f17d5c --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,7 -1,5 +1,8 @@@ -3.0.27 +3.11.13 + * Validate existence of DCs when repairing (CASSANDRA-17407) + * dropping of a materialized view creates a snapshot with dropped- prefix (CASSANDRA-17415) +Merged from 3.0: + * Disallow CONTAINS for UPDATE and DELETE (CASSANDRA-15266) * filter out NULL_VERSION entries from peers table in ConfiguredLimit (CASSANDRA-16518) * Suppress inapplicable CVEs (CASSANDRA-17368) * Fix flaky test - test_cqlsh_completion.TestCqlshCompletion (CASSANDRA-17338) - 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 (b18a9f0 -> fcdb3d1)
This is an automated email from the ASF dual-hosted git repository. adelapena pushed a change to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git. from b18a9f0 Validate existence of DCs when repairing new c52b5ab Disallow CONTAINS for UPDATE and DELETE new fcdb3d1 Merge branch 'cassandra-3.0' into cassandra-3.11 The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt| 1 + .../cql3/restrictions/StatementRestrictions.java | 6 .../cql3/validation/operations/DeleteTest.java | 33 ++ .../cql3/validation/operations/UpdateTest.java | 31 4 files changed, 60 insertions(+), 11 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.0' into trunk
This is an automated email from the ASF dual-hosted git repository. adelapena pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit eb960b19170e36bd9c52365ef15514a4d1ed9419 Merge: 852d7b6 bdeafa0 Author: Andrés de la Peña AuthorDate: Thu Mar 10 13:28:47 2022 + Merge branch 'cassandra-4.0' into trunk CHANGES.txt| 1 + .../cql3/restrictions/StatementRestrictions.java | 6 .../validation/operations/CompactStorageTest.java | 10 +++ .../cql3/validation/operations/DeleteTest.java | 33 ++ .../cql3/validation/operations/UpdateTest.java | 31 5 files changed, 65 insertions(+), 16 deletions(-) diff --cc CHANGES.txt index 1b396b9,41c6574..8a7f5d5 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -153,19 -56,7 +153,20 @@@ Merged from 3.11 * Add key validation to ssstablescrub (CASSANDRA-16969) * Update Jackson from 2.9.10 to 2.12.5 (CASSANDRA-16851) * Make assassinate more resilient to missing tokens (CASSANDRA-16847) + * Validate SASI tokenizer options before adding index to schema (CASSANDRA-15135) + * Fixup scrub output when no data post-scrub and clear up old use of row, which really means partition (CASSANDRA-16835) + * Reduce thread contention in CommitLogSegment and HintsBuffer (CASSANDRA-16072) + * Make cqlsh use the same set of reserved keywords than the server uses (CASSANDRA-15663) + * Optimize bytes skipping when reading SSTable files (CASSANDRA-14415) + * Enable tombstone compactions when unchecked_tombstone_compaction is set in TWCS (CASSANDRA-14496) + * Read only the required SSTables for single partition queries (CASSANDRA-16737) Merged from 3.0: ++ * Disallow CONTAINS for UPDATE and DELETE (CASSANDRA-15266) + * Suppress inapplicable CVEs (CASSANDRA-17368) + * Fix flaky test - test_cqlsh_completion.TestCqlshCompletion (CASSANDRA-17338) + * Fixed TestCqlshOutput failing tests (CASSANDRA-17386) + * Lazy transaction log replica creation allows incorrect replica content divergence during anticompaction (CASSANDRA-17273) + * LeveledCompactionStrategy disk space check improvements (CASSANDRA-17272) * Fix conversion from megabits to bytes in streaming rate limiter (CASSANDRA-17243) * Upgrade logback to 1.2.9 (CASSANDRA-17204) * Avoid race in AbstractReplicationStrategy endpoint caching (CASSANDRA-16673) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-3.0 updated: Disallow CONTAINS for UPDATE and DELETE
This is an automated email from the ASF dual-hosted git repository.
adelapena pushed a commit to branch cassandra-3.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/cassandra-3.0 by this push:
new c52b5ab Disallow CONTAINS for UPDATE and DELETE
c52b5ab is described below
commit c52b5ab95cf314a7983141f74c97744ff3ecbc81
Author: Maciej Sokol
AuthorDate: Thu Mar 10 13:05:42 2022 +
Disallow CONTAINS for UPDATE and DELETE
patch by Maciej Sokol; reviewed by Andres de la Peña and Benjamin Lerer for
CASSANDRA-15266
---
CHANGES.txt| 1 +
.../cql3/restrictions/StatementRestrictions.java | 6
.../cql3/validation/operations/DeleteTest.java | 33 ++
.../cql3/validation/operations/UpdateTest.java | 31
4 files changed, 60 insertions(+), 11 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index 9de942c..df0a734 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
3.0.27
+ * Disallow CONTAINS for UPDATE and DELETE (CASSANDRA-15266)
* filter out NULL_VERSION entries from peers table in ConfiguredLimit
(CASSANDRA-16518)
* Suppress inapplicable CVEs (CASSANDRA-17368)
* Fix flaky test - test_cqlsh_completion.TestCqlshCompletion (CASSANDRA-17338)
diff --git
a/src/java/org/apache/cassandra/cql3/restrictions/StatementRestrictions.java
b/src/java/org/apache/cassandra/cql3/restrictions/StatementRestrictions.java
index d7d6f48..73d2810 100644
--- a/src/java/org/apache/cassandra/cql3/restrictions/StatementRestrictions.java
+++ b/src/java/org/apache/cassandra/cql3/restrictions/StatementRestrictions.java
@@ -150,9 +150,15 @@ public final class StatementRestrictions
* allow two IN for the same entity but that doesn't seem very
useful)
* - The value_alias cannot be restricted in any way (we don't
support wide rows with indexed value
* in CQL so far)
+ * - CONTAINS and CONTAINS_KEY cannot be used with UPDATE or DELETE
*/
for (Relation relation : whereClause.relations)
{
+if ((relation.isContains() || relation.isContainsKey()) &&
(type.isUpdate() || type.isDelete()))
+{
+throw invalidRequest("Cannot use %s with %s", type,
relation.operator());
+}
+
if (relation.operator() == Operator.IS_NOT)
{
if (!forView)
diff --git
a/test/unit/org/apache/cassandra/cql3/validation/operations/DeleteTest.java
b/test/unit/org/apache/cassandra/cql3/validation/operations/DeleteTest.java
index 9d495b3..a0ffada 100644
--- a/test/unit/org/apache/cassandra/cql3/validation/operations/DeleteTest.java
+++ b/test/unit/org/apache/cassandra/cql3/validation/operations/DeleteTest.java
@@ -162,6 +162,27 @@ public class DeleteTest extends CQLTester
row("abc", 4, "xyz", "some other value"));
}
+@Test
+public void testDeletionWithContainsAndContainsKey() throws Throwable
+{
+createTable("CREATE TABLE %s (a int, b frozen>, c int,
primary key (a, b))");
+
+Object[] row = row(1, map(1, 1, 2, 2), 3);
+execute("INSERT INTO %s (a, b, c) VALUES (?, ?, ?)", row);
+
+assertRows(execute("SELECT * FROM %s"), row);
+
+assertInvalidMessage("Cannot use DELETE with CONTAINS",
+ "DELETE FROM %s WHERE a=1 AND b CONTAINS 1");
+
+assertRows(execute("SELECT * FROM %s"), row);
+
+assertInvalidMessage("Cannot use DELETE with CONTAINS KEY",
+ "DELETE FROM %s WHERE a=1 AND b CONTAINS KEY 1");
+
+assertRows(execute("SELECT * FROM %s"), row);
+}
+
/**
* Test deletion by 'composite prefix' (range tombstones)
* migrated from cql_tests.py:TestCQL.range_tombstones_test()
@@ -468,7 +489,7 @@ public class DeleteTest extends CQLTester
assertInvalidMessage("Only EQ and IN relation are supported on the
partition key (unless you use the token() function)",
"DELETE FROM %s WHERE partitionKey > ? ", 0);
-assertInvalidMessage("Cannot use CONTAINS on non-collection column
partitionkey",
+assertInvalidMessage("Cannot use DELETE with CONTAINS",
"DELETE FROM %s WHERE partitionKey CONTAINS
?", 0);
// Non primary key in the where clause
@@ -560,7 +581,7 @@ public class DeleteTest extends CQLTester
assertInvalidMessage("Only EQ and IN relation are supported on the
partition key (unless you use the token() function)",
"DELETE FROM %s WHERE partitionKey > ? AND
clustering = ?", 0, 1);
-assertInvalidMessage("Cannot use CONTAINS on non-collection column
partitionkey",
+assertInvalidMessage("Cannot use DELETE with CONTAINS",
"DELE
[jira] [Commented] (CASSANDRA-17428) Fail build when Ant is not of a certain version
[ https://issues.apache.org/jira/browse/CASSANDRA-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504234#comment-17504234 ] Brandon Williams commented on CASSANDRA-17428: -- We could futureproof this a bit better by requiring _at least_ 1.10: https://github.com/driftx/cassandra/commit/0b49caa0f63ecb8c702fd21128c120e34cc5b9a0 > Fail build when Ant is not of a certain version > --- > > Key: CASSANDRA-17428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17428 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Low > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x > > > As of writing this ticket, trunk is known to be buildable with Ant 1.10 and > users have reported build failures on Ant 1.9 (see CASSANDRA-16831). > There should be a check which fails the build if Ant used to build Cassanra > source code was not at least 1.10. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17428) Fail build when Ant is not of a certain version
[ https://issues.apache.org/jira/browse/CASSANDRA-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504226#comment-17504226 ] Paulo Motta edited comment on CASSANDRA-17428 at 3/10/22, 12:45 PM: Did you test this locally? Can you paste a snippet of the check running for documentation purposes? -LGTM after CI passes.- Edit: check does not work to higher versions different from 1.10. was (Author: paulo): Did you test this locally? Can you paste a snippet of the check running for documentation purposes? LGTM after CI passes. > Fail build when Ant is not of a certain version > --- > > Key: CASSANDRA-17428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17428 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Low > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x > > > As of writing this ticket, trunk is known to be buildable with Ant 1.10 and > users have reported build failures on Ant 1.9 (see CASSANDRA-16831). > There should be a check which fails the build if Ant used to build Cassanra > source code was not at least 1.10. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14113) AssertionError while trying to upgrade 2.2.11 -> 3.11.1
[
https://issues.apache.org/jira/browse/CASSANDRA-14113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504231#comment-17504231
]
Benjamin Lerer commented on CASSANDRA-14113:
Sorry [~knbk]. The patch looked good to me. We just had some issue with CI at
that time and it was unclear to me if the patch was causing some regressions or
if the problems were coming from somewhere else. Then I got drag into other
problems. I will look into it.
> AssertionError while trying to upgrade 2.2.11 -> 3.11.1
> ---
>
> Key: CASSANDRA-14113
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14113
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core
> Environment: Tables have been created in 2.2.11 using thrift and have
> supercolumns
>Reporter: Guillaume Herail
>Assignee: Marten Kenbeek
>Priority: Normal
> Labels: supercolumns
> Attachments: 14113-3.0.txt, data.tar.gz
>
>
> We're trying to upgrade a test cluster from Cassandra 2.2.11 to Cassandra
> 3.11.1. The tables have been created using thrift and have supercolumns. When
> I try to run {{nodetool upgradesstables}} I get the following:
> {noformat}error: null
> -- StackTrace --
> java.lang.AssertionError
> at org.apache.cassandra.db.rows.BufferCell.(BufferCell.java:42)
> at
> org.apache.cassandra.db.LegacyLayout$CellGrouper.addCell(LegacyLayout.java:1242)
> at
> org.apache.cassandra.db.LegacyLayout$CellGrouper.addAtom(LegacyLayout.java:1185)
> at
> org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer$UnfilteredIterator.readRow(UnfilteredDeserializer.java:498)
> at
> org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer$UnfilteredIterator.hasNext(UnfilteredDeserializer.java:472)
> at
> org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer.hasNext(UnfilteredDeserializer.java:306)
> at
> org.apache.cassandra.io.sstable.SSTableSimpleIterator$OldFormatIterator.computeNext(SSTableSimpleIterator.java:188)
> at
> org.apache.cassandra.io.sstable.SSTableSimpleIterator$OldFormatIterator.computeNext(SSTableSimpleIterator.java:140)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at
> org.apache.cassandra.io.sstable.SSTableIdentityIterator.hasNext(SSTableIdentityIterator.java:122)
> at
> org.apache.cassandra.db.rows.LazilyInitializedUnfilteredRowIterator.computeNext(LazilyInitializedUnfilteredRowIterator.java:100)
> at
> org.apache.cassandra.db.rows.LazilyInitializedUnfilteredRowIterator.computeNext(LazilyInitializedUnfilteredRowIterator.java:32)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at
> org.apache.cassandra.utils.MergeIterator$TrivialOneToOne.computeNext(MergeIterator.java:484)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:499)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:359)
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> at org.apache.cassandra.db.transform.BaseRows.hasNext(BaseRows.java:133)
> at
> org.apache.cassandra.db.transform.UnfilteredRows.isEmpty(UnfilteredRows.java:74)
> at
> org.apache.cassandra.db.partitions.PurgeFunction.applyToPartition(PurgeFunction.java:75)
> at
> org.apache.cassandra.db.partitions.PurgeFunction.applyToPartition(PurgeFunction.java:26)
> at
> org.apache.cassandra.db.transform.BasePartitions.hasNext(BasePartitions.java:96)
> at
> org.apache.cassandra.db.compaction.CompactionIterator.hasNext(CompactionIterator.java:233)
> at
> org.apache.cassandra.db.compaction.CompactionTask.runMayThrow(CompactionTask.java:196)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at
> org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:85)
> at
> org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:61)
> at
> org.apache.cassandra.db.compaction.CompactionManager$5.execute(CompactionManager.java:428)
> at
> org.apache.cassandra.db.compaction.CompactionManager$2.call(CompactionManager.java:315)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
>
[jira] [Commented] (CASSANDRA-17425) Add new CQL function maxWritetime
[ https://issues.apache.org/jira/browse/CASSANDRA-17425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504230#comment-17504230 ] Benjamin Lerer commented on CASSANDRA-17425: [~yifanc] I am not against this functionality but is it not a work around. Would we need this functionality if CASSANDRA-8877 was fixed? I am always a bit relunctant to add new selectors as I often had to modify all of them to introduce new features. > Add new CQL function maxWritetime > - > > Key: CASSANDRA-17425 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17425 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Syntax >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > > The function "writetime" does not support multi-cell types, e.g. collections > and UDT. It would be useful to enable querying the latest modified timestamp > of a column value. > I'd like to propose to add a new function named "maxWritetime", which returns > the largest timestamp amongst the cells. When being applied to the single > cell types, it returns the same result as "writetime". -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17428) Fail build when Ant is not of a certain version
[
https://issues.apache.org/jira/browse/CASSANDRA-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504229#comment-17504229
]
Paulo Motta commented on CASSANDRA-17428:
-
Can you try *lower-than* operator instead of {*}contains{*}?
> Fail build when Ant is not of a certain version
> ---
>
> Key: CASSANDRA-17428
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17428
> Project: Cassandra
> Issue Type: Improvement
> Components: Build
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Low
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x
>
>
> As of writing this ticket, trunk is known to be buildable with Ant 1.10 and
> users have reported build failures on Ant 1.9 (see CASSANDRA-16831).
> There should be a check which fails the build if Ant used to build Cassanra
> source code was not at least 1.10.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17428) Fail build when Ant is not of a certain version
[
https://issues.apache.org/jira/browse/CASSANDRA-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504228#comment-17504228
]
Stefan Miklosovic edited comment on CASSANDRA-17428 at 3/10/22, 12:34 PM:
--
Yeah, if I put there 1.11, for example (because I am on 1.10 and I need to test
it fails), this is what I get
{code:java}
Buildfile:
/home/smiklosovic/dev/cassandra/cassandra-instaclustr/cassandra-3.0/build.xml
BUILD FAILED
/home/smiklosovic/dev/cassandra/cassandra-instaclustr/cassandra-3.0/build.xml:22:
You need to use Ant of version at least 1.11 to continue.
Total time: 0 seconds
{code}
Exit code is 1.
was (Author: smiklosovic):
Yeah, if I put there 1.11, for example (because I am on 1.10 and I need to test
it fails), this is what I get
{code:java}
Buildfile:
/home/smiklosovic/dev/cassandra/cassandra-instaclustr/cassandra-3.0/build.xml
BUILD FAILED
/home/smiklosovic/dev/cassandra/cassandra-instaclustr/cassandra-3.0/build.xml:22:
You need to use Ant of version at least 1.11 to continue.
Total time: 0 seconds
{code}
> Fail build when Ant is not of a certain version
> ---
>
> Key: CASSANDRA-17428
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17428
> Project: Cassandra
> Issue Type: Improvement
> Components: Build
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Low
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x
>
>
> As of writing this ticket, trunk is known to be buildable with Ant 1.10 and
> users have reported build failures on Ant 1.9 (see CASSANDRA-16831).
> There should be a check which fails the build if Ant used to build Cassanra
> source code was not at least 1.10.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17428) Fail build when Ant is not of a certain version
[ https://issues.apache.org/jira/browse/CASSANDRA-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paulo Motta updated CASSANDRA-17428: Reviewers: Paulo Motta > Fail build when Ant is not of a certain version > --- > > Key: CASSANDRA-17428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17428 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Low > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x > > > As of writing this ticket, trunk is known to be buildable with Ant 1.10 and > users have reported build failures on Ant 1.9 (see CASSANDRA-16831). > There should be a check which fails the build if Ant used to build Cassanra > source code was not at least 1.10. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17428) Fail build when Ant is not of a certain version
[
https://issues.apache.org/jira/browse/CASSANDRA-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504228#comment-17504228
]
Stefan Miklosovic commented on CASSANDRA-17428:
---
Yeah, if I put there 1.11, for example (because I am on 1.10 and I need to test
it fails), this is what I get
{code:java}
Buildfile:
/home/smiklosovic/dev/cassandra/cassandra-instaclustr/cassandra-3.0/build.xml
BUILD FAILED
/home/smiklosovic/dev/cassandra/cassandra-instaclustr/cassandra-3.0/build.xml:22:
You need to use Ant of version at least 1.11 to continue.
Total time: 0 seconds
{code}
> Fail build when Ant is not of a certain version
> ---
>
> Key: CASSANDRA-17428
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17428
> Project: Cassandra
> Issue Type: Improvement
> Components: Build
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Low
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x
>
>
> As of writing this ticket, trunk is known to be buildable with Ant 1.10 and
> users have reported build failures on Ant 1.9 (see CASSANDRA-16831).
> There should be a check which fails the build if Ant used to build Cassanra
> source code was not at least 1.10.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17428) Fail build when Ant is not of a certain version
[ https://issues.apache.org/jira/browse/CASSANDRA-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504226#comment-17504226 ] Paulo Motta commented on CASSANDRA-17428: - Did you test this locally? Can you paste a snippet of the check running for documentation purposes? LGTM after CI passes. > Fail build when Ant is not of a certain version > --- > > Key: CASSANDRA-17428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17428 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Low > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x > > > As of writing this ticket, trunk is known to be buildable with Ant 1.10 and > users have reported build failures on Ant 1.9 (see CASSANDRA-16831). > There should be a check which fails the build if Ant used to build Cassanra > source code was not at least 1.10. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17428) Fail build when Ant is not of a certain version
[ https://issues.apache.org/jira/browse/CASSANDRA-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504225#comment-17504225 ] Stefan Miklosovic commented on CASSANDRA-17428: --- I was trying to figure out where to put this check and the most straightforward place is just at the very top of build.xml so it is executed as the very first condition. Feel free to suggest other place to put it in if it is more appropriate. Running the build here: https://ci-cassandra.apache.org/job/Cassandra-devbranch/1485/ Will be applied across all (supported) branches afterwards once agreed on the approach. > Fail build when Ant is not of a certain version > --- > > Key: CASSANDRA-17428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17428 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Low > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x > > > As of writing this ticket, trunk is known to be buildable with Ant 1.10 and > users have reported build failures on Ant 1.9 (see CASSANDRA-16831). > There should be a check which fails the build if Ant used to build Cassanra > source code was not at least 1.10. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17428) Fail build when Ant is not of a certain version
[ https://issues.apache.org/jira/browse/CASSANDRA-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17428: -- Test and Documentation Plan: CI and manual build Status: Patch Available (was: In Progress) https://github.com/apache/cassandra/pull/1489 > Fail build when Ant is not of a certain version > --- > > Key: CASSANDRA-17428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17428 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Low > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x > > > As of writing this ticket, trunk is known to be buildable with Ant 1.10 and > users have reported build failures on Ant 1.9 (see CASSANDRA-16831). > There should be a check which fails the build if Ant used to build Cassanra > source code was not at least 1.10. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17428) Fail build when Ant is not of a certain version
[ https://issues.apache.org/jira/browse/CASSANDRA-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17428: -- Change Category: Quality Assurance Complexity: Low Hanging Fruit Fix Version/s: 3.0.x 3.11.x 4.0.x 4.x Priority: Low (was: Normal) Status: Open (was: Triage Needed) > Fail build when Ant is not of a certain version > --- > > Key: CASSANDRA-17428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17428 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Low > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x > > > As of writing this ticket, trunk is known to be buildable with Ant 1.10 and > users have reported build failures on Ant 1.9 (see CASSANDRA-16831). > There should be a check which fails the build if Ant used to build Cassanra > source code was not at least 1.10. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17428) Fail build when Ant is not of a certain version
[ https://issues.apache.org/jira/browse/CASSANDRA-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17428: -- Description: As of writing this ticket, trunk is known to be buildable with Ant 1.10 and users have reported build failures on Ant 1.9 (see CASSANDRA-16831). There should be a check which fails the build if Ant used to build Cassanra source code was not at least 1.10. was: As of writing this ticket, trunk is known to be buildable with Ant 1.10 and users have reported build failures on Ant 1.9 (see CASSANDRA-16831). There should be a check which fails the build if Ant used to build Cassanra source code was not at leats 1.10. > Fail build when Ant is not of a certain version > --- > > Key: CASSANDRA-17428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17428 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > > As of writing this ticket, trunk is known to be buildable with Ant 1.10 and > users have reported build failures on Ant 1.9 (see CASSANDRA-16831). > There should be a check which fails the build if Ant used to build Cassanra > source code was not at least 1.10. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17428) Fail build when Ant is not of a certain version
Stefan Miklosovic created CASSANDRA-17428: - Summary: Fail build when Ant is not of a certain version Key: CASSANDRA-17428 URL: https://issues.apache.org/jira/browse/CASSANDRA-17428 Project: Cassandra Issue Type: Improvement Components: Build Reporter: Stefan Miklosovic Assignee: Stefan Miklosovic As of writing this ticket, trunk is known to be buildable with Ant 1.10 and users have reported build failures on Ant 1.9 (see CASSANDRA-16831). There should be a check which fails the build if Ant used to build Cassanra source code was not at leats 1.10. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17409) WEBSITE - March 2022 blog "Can Apache Cassandra take my PEM keys?"
[ https://issues.apache.org/jira/browse/CASSANDRA-17409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504164#comment-17504164 ] Erick Ramirez commented on CASSANDRA-17409: --- The post is live in prod - https://cassandra.apache.org/_/blog/Can-Apache-Cassandra-take-my-PEM-keys.html > WEBSITE - March 2022 blog "Can Apache Cassandra take my PEM keys?" > -- > > Key: CASSANDRA-17409 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17409 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Maulin Vasavada >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17409-01-blog-index.png, c17409-02-blog-post.png, > c17409-03-blog-index-v2.png > > > This ticket is to capture the work associated with publishing the March 2022 > blog "Can Apache Cassandra take my PEM keys?" > If this blog cannot be published by the *March 10, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.1#820001) - 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 (cf79495 -> d161f23)
This is an automated email from the ASF dual-hosted git repository. erickramirezau pushed a change to branch asf-site in repository https://gitbox.apache.org/repos/asf/cassandra-website.git. discard cf79495 generate docs for d6db703d add 92077ce March 2022 blog "Can Apache Cassandra take my PEM keys?" add d161f23 generate docs for 92077ce1 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 (cf79495) \ N -- N -- N refs/heads/asf-site (d161f23) 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: ...ssandra-take-my-pem-keys-unsplash-tim-evans.jpg | Bin 0 -> 3223696 bytes content/_/blog.html| 24 + .../Can-Apache-Cassandra-take-my-PEM-keys.html | 626 + .../cassandra/configuration/cass_yaml_file.html| 25 + content/doc/4.1/cassandra/new/virtualtables.html | 119 +++- .../cassandra/configuration/cass_yaml_file.html| 25 + .../doc/latest/cassandra/new/virtualtables.html| 119 +++- .../cassandra/configuration/cass_yaml_file.html| 25 + content/doc/trunk/cassandra/new/virtualtables.html | 119 +++- content/search-index.js| 2 +- ...ssandra-take-my-pem-keys-unsplash-tim-evans.jpg | Bin 0 -> 3223696 bytes site-content/source/modules/ROOT/pages/blog.adoc | 23 + .../Can-Apache-Cassandra-take-my-PEM-keys.adoc | 334 +++ site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078 bytes 14 files changed, 1368 insertions(+), 73 deletions(-) create mode 100644 content/_/_images/blog/can-apache-cassandra-take-my-pem-keys-unsplash-tim-evans.jpg create mode 100644 content/_/blog/Can-Apache-Cassandra-take-my-PEM-keys.html create mode 100644 site-content/source/modules/ROOT/images/blog/can-apache-cassandra-take-my-pem-keys-unsplash-tim-evans.jpg create mode 100644 site-content/source/modules/ROOT/pages/blog/Can-Apache-Cassandra-take-my-PEM-keys.adoc - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17409) WEBSITE - March 2022 blog "Can Apache Cassandra take my PEM keys?"
[
https://issues.apache.org/jira/browse/CASSANDRA-17409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504159#comment-17504159
]
Erick Ramirez commented on CASSANDRA-17409:
---
The build is in staging:
||Branch||PR||Commit||Build||
|{{trunk}}|[#110|https://github.com/apache/cassandra-website/pull/110]|[92077ce|https://github.com/apache/cassandra-website/commit/92077ce16ba2ae19c004e462e97bcc1379c2bc9b]|[#162|https://ci-cassandra.apache.org/job/cassandra-website/162/]|
The blog post can be viewed here --
https://cassandra.staged.apache.org/_/blog/Can-Apache-Cassandra-take-my-PEM-keys.html
> WEBSITE - March 2022 blog "Can Apache Cassandra take my PEM keys?"
> --
>
> Key: CASSANDRA-17409
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17409
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Maulin Vasavada
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0.3
>
> Attachments: c17409-01-blog-index.png, c17409-02-blog-post.png,
> c17409-03-blog-index-v2.png
>
>
> This ticket is to capture the work associated with publishing the March 2022
> blog "Can Apache Cassandra take my PEM keys?"
> If this blog cannot be published by the *March 10, 2022 publish date*, please
> contact me, suggest changes, or correct the date when possible in the pull
> request for the appropriate time that the blog will go live (on both the
> blog.adoc and the blog post's file).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17153) Guardrails for collection items and size
[
https://issues.apache.org/jira/browse/CASSANDRA-17153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-17153:
Reviewers: Berenguer Blasi
Status: Review In Progress (was: Patch Available)
> Guardrails for collection items and size
>
>
> Key: CASSANDRA-17153
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17153
> 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: 20m
> Remaining Estimate: 0h
>
> Add guardrails for the number of items and size of collections. For example:
> {code}
> # Guardrail to warn or fail when encountering larger size of collection data
> than threshold.
> # The two thresholds default to 0KiB to disable.
> collection_size_warn_threshold: 0KiB
> collection_size_fail_threshold: 0KiB
> # Guardrail to warn or fail when encountering more elements in collection
> than threshold.
> # The two thresholds default to -1 to disable.
> items_per_collection_warn_threshold: -1
> items_per_collection_fail_threshold: -1
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
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 (cf79495 -> d161f23)
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 cf79495 generate docs for d6db703d add 92077ce March 2022 blog "Can Apache Cassandra take my PEM keys?" new d161f23 generate docs for 92077ce1 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 (cf79495) \ N -- N -- N refs/heads/asf-staging (d161f23) 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: ...ssandra-take-my-pem-keys-unsplash-tim-evans.jpg | Bin 0 -> 3223696 bytes content/_/blog.html| 24 + .../Can-Apache-Cassandra-take-my-PEM-keys.html | 626 + .../cassandra/configuration/cass_yaml_file.html| 25 + content/doc/4.1/cassandra/new/virtualtables.html | 119 +++- .../cassandra/configuration/cass_yaml_file.html| 25 + .../doc/latest/cassandra/new/virtualtables.html| 119 +++- .../cassandra/configuration/cass_yaml_file.html| 25 + content/doc/trunk/cassandra/new/virtualtables.html | 119 +++- content/search-index.js| 2 +- ...ssandra-take-my-pem-keys-unsplash-tim-evans.jpg | Bin 0 -> 3223696 bytes site-content/source/modules/ROOT/pages/blog.adoc | 23 + .../Can-Apache-Cassandra-take-my-PEM-keys.adoc | 334 +++ site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078 bytes 14 files changed, 1368 insertions(+), 73 deletions(-) create mode 100644 content/_/_images/blog/can-apache-cassandra-take-my-pem-keys-unsplash-tim-evans.jpg create mode 100644 content/_/blog/Can-Apache-Cassandra-take-my-PEM-keys.html create mode 100644 site-content/source/modules/ROOT/images/blog/can-apache-cassandra-take-my-pem-keys-unsplash-tim-evans.jpg create mode 100644 site-content/source/modules/ROOT/pages/blog/Can-Apache-Cassandra-take-my-PEM-keys.adoc - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch trunk updated: March 2022 blog "Can Apache Cassandra take my PEM keys?"
This is an automated email from the ASF dual-hosted git repository. erickramirezau 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 92077ce March 2022 blog "Can Apache Cassandra take my PEM keys?" 92077ce is described below commit 92077ce16ba2ae19c004e462e97bcc1379c2bc9b Author: Diogenese Topper AuthorDate: Fri Mar 4 15:03:44 2022 -0800 March 2022 blog "Can Apache Cassandra take my PEM keys?" patch by Maulin Vasavada, Diogenese Topper; reviewed by Erick Ramirez for CASSANDRA-17409 --- ...ssandra-take-my-pem-keys-unsplash-tim-evans.jpg | Bin 0 -> 3223696 bytes site-content/source/modules/ROOT/pages/blog.adoc | 23 ++ .../Can-Apache-Cassandra-take-my-PEM-keys.adoc | 334 + 3 files changed, 357 insertions(+) diff --git a/site-content/source/modules/ROOT/images/blog/can-apache-cassandra-take-my-pem-keys-unsplash-tim-evans.jpg b/site-content/source/modules/ROOT/images/blog/can-apache-cassandra-take-my-pem-keys-unsplash-tim-evans.jpg new file mode 100644 index 000..a375128 Binary files /dev/null and b/site-content/source/modules/ROOT/images/blog/can-apache-cassandra-take-my-pem-keys-unsplash-tim-evans.jpg differ diff --git a/site-content/source/modules/ROOT/pages/blog.adoc b/site-content/source/modules/ROOT/pages/blog.adoc index 6c9f8ac..0ec76c5 100644 --- a/site-content/source/modules/ROOT/pages/blog.adoc +++ b/site-content/source/modules/ROOT/pages/blog.adoc @@ -8,7 +8,30 @@ NOTES FOR CONTENT CREATORS - Replace post tile, date, description and link to you post. +//start card +[openblock,card shadow relative test] + +[openblock,card-header] +-- +[discrete] +=== Can Apache Cassandra take my PEM keys? +[discrete] + March 10, 2022 +-- +[openblock,card-content] +-- +Maulin Vasavada demonstrates how to use PEM-based security credentials like your private key, corresponding certificate chain, and trusted CA certificates. These credentials will have built-in support in Apache Cassandra 4.1 which will also introduce a pluggable configuration for customizing the SSL context for TLS encryption +[openblock,card-btn card-btn--blog] + + +[.btn.btn--alt] +xref:blog/Can-Apache-Cassandra-take-my-PEM-keys.adoc[Read More] + + +-- + +//end card //start card [openblock,card shadow relative test] diff --git a/site-content/source/modules/ROOT/pages/blog/Can-Apache-Cassandra-take-my-PEM-keys.adoc b/site-content/source/modules/ROOT/pages/blog/Can-Apache-Cassandra-take-my-PEM-keys.adoc new file mode 100644 index 000..c030c00 --- /dev/null +++ b/site-content/source/modules/ROOT/pages/blog/Can-Apache-Cassandra-take-my-PEM-keys.adoc @@ -0,0 +1,334 @@ += Can Apache Cassandra take my PEM keys? +:page-layout: single-post +:page-role: blog-post +:page-post-date: March 10, 2022 +:page-post-author: Maulin Vasavada +:description: The Apache Cassandra Community +:keywords: + +:!figure-caption: + +.Image credit: https://unsplash.com/@tjevans[Tim Evans on Unsplash^] +image::blog/can-apache-cassandra-take-my-pem-keys-unsplash-tim-evans.jpg[lockboxes] + +This article discusses how to configure Apache Cassandra 4.1 and beyond to use your PEM-encoded security credentials like your private key, corresponding certificate chain, and trusted CA certificates. + +=== What is PEM? + +PEM stands for https://en.wikipedia.org/wiki/Privacy-Enhanced_Mail[**P**rivacy **E**nhanced **M**ail^]. It is a popular data-formatting standard for your cryptographic keys, certificates, and other data. Being a text-based encoding standard, PEM makes it easier to https://datatracker.ietf.org/doc/html/rfc7468#page-12[transport, transfer, and even edit the data with simple text editors^]. It is easy to copy and paste and combine different PEM encoded artifacts (for example: build a certif [...] + +An Interesting fact about PEM is that—as the name suggests—it was designed to be used for electronic mail systems but became popular for encoding cryptographic data while other standards like https://en.wikipedia.org/wiki/S/MIME[S/MIME^] saw a better success with emails. Below is an https://www.ssl.com/guide/pem-der-crt-and-cer-x-509-encodings-and-conversions/[example from ssl.com^] of a X.509 Certificate represented in PEM format, + +``` +-BEGIN CERTIFICATE- +MIIH/TCCBeWgAwIBAgIQaBYE3/M08XHYCnNVmcFBcjANBgkqhkiG9w0BAQsFADBy +MQswCQYDVQQGEwJVUzEOMAwGA1UECAwFVGV4YXMxEDAOBgNVBAcMB0hvdXN0b24x +ETAPBgNVBAoMCFNTTCBDb3JwMS4wLAYDVQQDDCVTU0wuY29tIEVWIFNTTCBJbnRl +cm1lZGlhdGUgQ0EgUlNBIFIzMB4XDTIwMDQwMTAwNTgzM1oXDTIxMDcxNjAwNTgz +M1owgb0xCzAJBgNVBAYTAlVTMQ4wDAYDVQQIDAVUZXhhczEQMA4GA1UEBwwHSG91 +c3RvbjERMA8GA1UECgwIU1NMIENvcnAxFjAUBgNVBAUTDU5WMjAwODE2MTQyNDMx +FDASBgNVBAMMC3d3dy5zc2wuY29tMR0wGwYDVQQPDBRQcml2YXRlIE9yZ2FuaXph +dGlvbjEXMBUGCysGAQQBgjc8AgECDAZOZXZhZGExEzARBgsrBgEEAYI3PAIBAxMC +VVMwggEiMA0GCSqGSIb3DQEBAQU
[jira] [Updated] (CASSANDRA-17427) Improve unit tests performance
[ https://issues.apache.org/jira/browse/CASSANDRA-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacek Lewandowski updated CASSANDRA-17427: -- Test and Documentation Plan: run tests and build artifacts Status: Patch Available (was: In Progress) > Improve unit tests performance > -- > > Key: CASSANDRA-17427 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17427 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Jacek Lewandowski >Assignee: Jacek Lewandowski >Priority: Normal > > There a couple of small improvements to run unit tests a bit faster -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17427) Improve unit tests performance
[
https://issues.apache.org/jira/browse/CASSANDRA-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504079#comment-17504079
]
Jacek Lewandowski commented on CASSANDRA-17427:
---
[PR (trunk)|https://github.com/apache/cassandra/pull/1488]
As an example, I've compared times of running a random set of tests ({{time ant
testclasslist}}):
{noformat}
org/apache/cassandra/cql3/ViewFilteringComplexPKTest.java
org/apache/cassandra/cql3/PstmtPersistenceTest.java
org/apache/cassandra/cql3/ViewFilteringClustering1Test.java
org/apache/cassandra/cql3/MemtableSizeTest.java
org/apache/cassandra/cql3/GcCompactionTest.java
org/apache/cassandra/cql3/ViewRangesTest.java
org/apache/cassandra/cql3/ViewTimesTest.java
org/apache/cassandra/cql3/DurationTest.java
org/apache/cassandra/cql3/ViewTest.java
org/apache/cassandra/cql3/ViewComplexTest.java
{noformat}
It was ~ 3'55" vs 3'15" (40 seconds faster)
I also tried for a single test ({{ViewTest}}), it was 50" vs 35" (15 seconds
faster)
For a single run, we can safe around 12 seconds by avoiding {{checkstyle}},
{{rat-check}} and {{eclipse-warnings}} - it is enough for them to be executed
once for the whole build (when we generate artifacts).
Other changes include:
- using {{rm -r}} instead of iterating over directories and individual files in
Java when deleting stuff (we delete many files before each test) - this is
enabled only in unit tests by a system property
- setting grace period for driver shutdown to 0
- avoiding use of open ssl in unit tests
There is also a small change in {{workspace.xml}} for IntelliJ which increases
max meta space memory from 384M to 512M as it frequently happens for jvm dtests
to fail because of insufficient amount of that memory
> Improve unit tests performance
> --
>
> Key: CASSANDRA-17427
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17427
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/unit
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
>
> There a couple of small improvements to run unit tests a bit faster
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17409) WEBSITE - March 2022 blog "Can Apache Cassandra take my PEM keys?"
[ https://issues.apache.org/jira/browse/CASSANDRA-17409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17409: -- Fix Version/s: 4.0.3 (was: NA) Source Control Link: https://github.com/apache/cassandra-website/commit/92077ce16ba2ae19c004e462e97bcc1379c2bc9b Resolution: Fixed Status: Resolved (was: Ready to Commit) > WEBSITE - March 2022 blog "Can Apache Cassandra take my PEM keys?" > -- > > Key: CASSANDRA-17409 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17409 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Maulin Vasavada >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17409-01-blog-index.png, c17409-02-blog-post.png, > c17409-03-blog-index-v2.png > > > This ticket is to capture the work associated with publishing the March 2022 > blog "Can Apache Cassandra take my PEM keys?" > If this blog cannot be published by the *March 10, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
