[cassandra-website] branch asf-staging updated (a3f6c10c3 -> f02783e66)
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 a3f6c10c3 generate docs for 8e4e9469 new f02783e66 generate docs for 8e4e9469 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 (a3f6c10c3) \ N -- N -- N refs/heads/asf-staging (f02783e66) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4970139 -> 4970139 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17976) WEBSITE - Update What's New Page for 4.1 and trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628637#comment-17628637
]
Erick Ramirez edited comment on CASSANDRA-17976 at 11/4/22 5:04 AM:
Committed:
||Branch||PR||Commit||
|{{cassandra-4.1}}|[#1969|https://github.com/apache/cassandra/pull/1969]|[a4b90fb|https://github.com/apache/cassandra/commit/a4b90fbc011f2cfab464f375c564af67720a0a1d]|
|{{trunk}}|[#1970|https://github.com/apache/cassandra/pull/1970]|[e027229|https://github.com/apache/cassandra/commit/e027229238cafc105fd7913d0aab7e95b6930a34]|
For {{cassandra-4.1}} branch:
{noformat}
$ curl -L
https://github.com/apache/cassandra/commit/5140ca260260d053cb315d431a534746882462cc.patch
-o ~/17976-4.1.patch
$ git checkout cassandra-4.1
Switched to branch 'cassandra-4.1'
Your branch is up to date with 'origin/cassandra-4.1'.
$ git am -3 ~/17976-4.1.patch
Applying: WEBSITE - Updated What's New page for 4.1
$ git commit --amend
[cassandra-4.1 a4b90fbc01] WEBSITE - Updated What's New page for 4.1
Date: Fri Nov 4 11:33:04 2022 +1100
1 file changed, 20 insertions(+), 12 deletions(-)
rewrite doc/modules/cassandra/pages/new/index.adoc (99%)
$ git push origin cassandra-4.1
Enumerating objects: 15, done.
Counting objects: 100% (15/15), done.
Delta compression using up to 12 threads
Compressing objects: 100% (8/8), done.
Writing objects: 100% (8/8), 1.21 KiB | 1.21 MiB/s, done.
Total 8 (delta 5), reused 0 (delta 0)
remote: Resolving deltas: 100% (5/5), completed with 5 local objects.
To https://github.com/apache/cassandra.git
756aeed1f4..a4b90fbc01 cassandra-4.1 -> cassandra-4.1
{noformat}
For {{trunk}}:
{noformat}
$ curl -L
https://github.com/apache/cassandra/commit/7a116c170a2f65dd23aba269c85875dd84a56d6a.patch
-o ~/17976-trunk.patch
$ git checkout trunk
Switched to branch 'trunk'
Your branch is up to date with 'origin/trunk'.
$ git am -3 ~/17976-trunk.patch
Applying: WEBSITE - Updated What's New page for 5.0 in trunk
$ git commit --amend
[trunk e027229238] WEBSITE - Updated What's New page for 5.0 in trunk
Date: Fri Nov 4 11:58:12 2022 +1100
1 file changed, 11 insertions(+), 12 deletions(-)
rewrite doc/modules/cassandra/pages/new/index.adoc (99%)
$ git push origin trunk
Enumerating objects: 15, done.
Counting objects: 100% (15/15), done.
Delta compression using up to 12 threads
Compressing objects: 100% (8/8), done.
Writing objects: 100% (8/8), 1.02 KiB | 1.02 MiB/s, done.
Total 8 (delta 5), reused 0 (delta 0)
remote: Resolving deltas: 100% (5/5), completed with 5 local objects.
To https://github.com/apache/cassandra.git
7278db376e..e027229238 trunk -> trunk
{noformat}
was (Author: JIRAUSER285101):
Committed:
||Branch||PR||Commit||
|{{cassandra-4.1}}|[#1969|https://github.com/apache/cassandra/pull/1969]|[a4b90fb|https://github.com/apache/cassandra/commit/a4b90fbc011f2cfab464f375c564af67720a0a1d]|
|{{trunk}}|[#1970|https://github.com/apache/cassandra/pull/1970]|[e027229|https://github.com/apache/cassandra/commit/e027229238cafc105fd7913d0aab7e95b6930a34]|
> WEBSITE - Update What's New Page for 4.1 and trunk
> --
>
> Key: CASSANDRA-17976
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17976
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Ekaterina Dimitrova
>Assignee: Michael Semb Wever
>Priority: Low
> Fix For: 4.1.x, 4.x
>
> Attachments: Screenshot 2022-11-02 at 22.22.48.png, Screenshot
> 2022-11-02 at 22.40.13.png, c17976-01-doc-whats_new-4.1.png,
> c17976-02-doc-whats_new-trunk.png
>
>
> [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html]
> The page still says 4.0 and lists 4.0 new developments.
> We need to point to 4.1 and list latest developments blog posts, docs;
> probably we can also link NEWS.txt and CHANGES.txt
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18015) WEBSITE - Cleanup sub-pages of What's New section, fix version numbers
[
https://issues.apache.org/jira/browse/CASSANDRA-18015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-18015:
--
Change Category: Semantic
Complexity: Normal
Component/s: Documentation/Website
Fix Version/s: NA
Status: Open (was: Triage Needed)
> WEBSITE - Cleanup sub-pages of What's New section, fix version numbers
> --
>
> Key: CASSANDRA-18015
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18015
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: NA
>
> Attachments: c18015-01-new_index.png, c18015-02-subpages.png
>
>
> The [What's
> New|https://cassandra.apache.org/doc/latest/cassandra/new/index.html] section
> of the website needs a bit of TLC:
> * replace version number on landing page ({{new/index.adoc}})
> * cleanup sub-pages in {{/doc/latest/cassandra/new/}}
> This work needs to be done for both {{trunk}} and {{cassandra-4.1}} branches.
> !c18015-01-new_index.png|width=300!
> !c18015-02-subpages.png|width=300!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17976) WEBSITE - Update What's New Page for 4.1 and trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628670#comment-17628670 ] Erick Ramirez commented on CASSANDRA-17976: --- There's a bit more stuff to fix up with the *What's New* section which I'll deal with in CASSANDRA-18015. > WEBSITE - Update What's New Page for 4.1 and trunk > -- > > Key: CASSANDRA-17976 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17976 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Ekaterina Dimitrova >Assignee: Michael Semb Wever >Priority: Low > Fix For: 4.1.x, 4.x > > Attachments: Screenshot 2022-11-02 at 22.22.48.png, Screenshot > 2022-11-02 at 22.40.13.png, c17976-01-doc-whats_new-4.1.png, > c17976-02-doc-whats_new-trunk.png > > > [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html] > The page still says 4.0 and lists 4.0 new developments. > We need to point to 4.1 and list latest developments blog posts, docs; > probably we can also link NEWS.txt and CHANGES.txt -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18015) WEBSITE - Cleanup sub-pages of What's New section, fix version numbers
[
https://issues.apache.org/jira/browse/CASSANDRA-18015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-18015:
--
Description:
The [What's
New|https://cassandra.apache.org/doc/latest/cassandra/new/index.html] section
of the website needs a bit of TLC:
* replace version number on landing page ({{new/index.adoc}})
* cleanup sub-pages in {{/doc/latest/cassandra/new/}}
This work needs to be done for both {{trunk}} and {{cassandra-4.1}} branches.
!c18015-01-new_index.png|width=300!
!c18015-02-subpages.png|width=300!
was:
The [What's
New|https://cassandra.apache.org/doc/latest/cassandra/new/index.html] section
of the website needs a bit of TLC:
* replace version number on landing page ({{new/index.adoc}})
* cleanup sub-pages in {{/doc/latest/cassandra/new/}}
This work needs to be done for both {{trunk}} and {{cassandra-4.1}} branches.
!c18015-01-new_index.png!
!c18015-02-subpages.png!
> WEBSITE - Cleanup sub-pages of What's New section, fix version numbers
> --
>
> Key: CASSANDRA-18015
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18015
> Project: Cassandra
> Issue Type: Task
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Attachments: c18015-01-new_index.png, c18015-02-subpages.png
>
>
> The [What's
> New|https://cassandra.apache.org/doc/latest/cassandra/new/index.html] section
> of the website needs a bit of TLC:
> * replace version number on landing page ({{new/index.adoc}})
> * cleanup sub-pages in {{/doc/latest/cassandra/new/}}
> This work needs to be done for both {{trunk}} and {{cassandra-4.1}} branches.
> !c18015-01-new_index.png|width=300!
> !c18015-02-subpages.png|width=300!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18015) WEBSITE - Cleanup sub-pages of What's New section, fix version numbers
[
https://issues.apache.org/jira/browse/CASSANDRA-18015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-18015:
--
Description:
The [What's
New|https://cassandra.apache.org/doc/latest/cassandra/new/index.html] section
of the website needs a bit of TLC:
* replace version number on landing page ({{new/index.adoc}})
* cleanup sub-pages in {{/doc/latest/cassandra/new/}}
This work needs to be done for both {{trunk}} and {{cassandra-4.1}} branches.
!c18015-01-new_index.png!
!c18015-02-subpages.png!
was:
The [What's
New|https://cassandra.apache.org/doc/latest/cassandra/new/index.html] section
of the website needs a bit of TLC:
* replace version number on landing page ({{new/index.adoc}})
* cleanup sub-pages in {{/doc/latest/cassandra/new/}}
This work needs to be done for both {{trunk}} and {{cassandra-4.1}} branches.
!c18015-01-new_index.png!
> WEBSITE - Cleanup sub-pages of What's New section, fix version numbers
> --
>
> Key: CASSANDRA-18015
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18015
> Project: Cassandra
> Issue Type: Task
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Attachments: c18015-01-new_index.png, c18015-02-subpages.png
>
>
> The [What's
> New|https://cassandra.apache.org/doc/latest/cassandra/new/index.html] section
> of the website needs a bit of TLC:
> * replace version number on landing page ({{new/index.adoc}})
> * cleanup sub-pages in {{/doc/latest/cassandra/new/}}
> This work needs to be done for both {{trunk}} and {{cassandra-4.1}} branches.
> !c18015-01-new_index.png!
> !c18015-02-subpages.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18015) WEBSITE - Cleanup sub-pages of What's New section, fix version numbers
[
https://issues.apache.org/jira/browse/CASSANDRA-18015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-18015:
--
Attachment: c18015-02-subpages.png
c18015-01-new_index.png
> WEBSITE - Cleanup sub-pages of What's New section, fix version numbers
> --
>
> Key: CASSANDRA-18015
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18015
> Project: Cassandra
> Issue Type: Task
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Attachments: c18015-01-new_index.png, c18015-02-subpages.png
>
>
> The [What's
> New|https://cassandra.apache.org/doc/latest/cassandra/new/index.html] section
> of the website needs a bit of TLC:
> * replace version number on landing page ({{new/index.adoc}})
> * cleanup sub-pages in {{/doc/latest/cassandra/new/}}
> This work needs to be done for both {{trunk}} and {{cassandra-4.1}} branches.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18015) WEBSITE - Cleanup sub-pages of What's New section, fix version numbers
[
https://issues.apache.org/jira/browse/CASSANDRA-18015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-18015:
--
Description:
The [What's
New|https://cassandra.apache.org/doc/latest/cassandra/new/index.html] section
of the website needs a bit of TLC:
* replace version number on landing page ({{new/index.adoc}})
* cleanup sub-pages in {{/doc/latest/cassandra/new/}}
This work needs to be done for both {{trunk}} and {{cassandra-4.1}} branches.
!c18015-01-new_index.png!
was:
The [What's
New|https://cassandra.apache.org/doc/latest/cassandra/new/index.html] section
of the website needs a bit of TLC:
* replace version number on landing page ({{new/index.adoc}})
* cleanup sub-pages in {{/doc/latest/cassandra/new/}}
This work needs to be done for both {{trunk}} and {{cassandra-4.1}} branches.
> WEBSITE - Cleanup sub-pages of What's New section, fix version numbers
> --
>
> Key: CASSANDRA-18015
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18015
> Project: Cassandra
> Issue Type: Task
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Attachments: c18015-01-new_index.png, c18015-02-subpages.png
>
>
> The [What's
> New|https://cassandra.apache.org/doc/latest/cassandra/new/index.html] section
> of the website needs a bit of TLC:
> * replace version number on landing page ({{new/index.adoc}})
> * cleanup sub-pages in {{/doc/latest/cassandra/new/}}
> This work needs to be done for both {{trunk}} and {{cassandra-4.1}} branches.
> !c18015-01-new_index.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18015) WEBSITE - Cleanup sub-pages of What's New section, fix version numbers
Erick Ramirez created CASSANDRA-18015:
-
Summary: WEBSITE - Cleanup sub-pages of What's New section, fix
version numbers
Key: CASSANDRA-18015
URL: https://issues.apache.org/jira/browse/CASSANDRA-18015
Project: Cassandra
Issue Type: Task
Reporter: Erick Ramirez
Assignee: Erick Ramirez
The [What's
New|https://cassandra.apache.org/doc/latest/cassandra/new/index.html] section
of the website needs a bit of TLC:
* replace version number on landing page ({{new/index.adoc}})
* cleanup sub-pages in {{/doc/latest/cassandra/new/}}
This work needs to be done for both {{trunk}} and {{cassandra-4.1}} branches.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17976) WEBSITE - Update What's New Page for 4.1 and trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628663#comment-17628663
]
Erick Ramirez commented on CASSANDRA-17976:
---
The changes were [published to
production|https://github.com/apache/cassandra-website#merging-asf-staging-to-asf-site]
in CASSANDRA-18014.
The updated pages are now live on the site –
* 4.1 - [https://cassandra.apache.org/doc/latest/cassandra/new/index.html]
* {{trunk}} - [https://cassandra.apache.org/doc/trunk/cassandra/new/index.html]
> WEBSITE - Update What's New Page for 4.1 and trunk
> --
>
> Key: CASSANDRA-17976
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17976
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Ekaterina Dimitrova
>Assignee: Michael Semb Wever
>Priority: Low
> Fix For: 4.1.x, 4.x
>
> Attachments: Screenshot 2022-11-02 at 22.22.48.png, Screenshot
> 2022-11-02 at 22.40.13.png, c17976-01-doc-whats_new-4.1.png,
> c17976-02-doc-whats_new-trunk.png
>
>
> [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html]
> The page still says 4.0 and lists 4.0 new developments.
> We need to point to 4.1 and list latest developments blog posts, docs;
> probably we can also link NEWS.txt and CHANGES.txt
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18014) WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
[
https://issues.apache.org/jira/browse/CASSANDRA-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628664#comment-17628664
]
Erick Ramirez commented on CASSANDRA-18014:
---
I’ve completed final verification in staging and [published to
production|https://github.com/apache/cassandra-website#merging-asf-staging-to-asf-site]:
{noformat}
$ git branch
* trunk
$ git fetch origin
$ git checkout asf-site
Branch ‘asf-site’ set up to track remote branch ‘asf-site’ from ‘origin’.
Switched to a new branch ‘asf-site’
$ git branch
* asf-site
trunk
$ git reset --hard origin/asf-staging
HEAD is now at a3f6c10c generate docs for 8e4e9469
$ git push -f origin asf-site
Total 0 (delta 0), reused 0 (delta 0)
To [https://github.com/apache/cassandra-website.git]
+ 4603a308...a3f6c10c asf-site -> asf-site (forced update)
{noformat}
The blog post is now live on the site –
https://cassandra.apache.org/_/blog/Apache-Cassandra-Changelog-20-November-2022.html
> WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
> -
>
> Key: CASSANDRA-18014
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18014
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Chris Thornett
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
> Attachments: c18014-01-blog-index.png, c18014-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the November
> 2022 blog "Apache Cassandra Changelog #20"
> If this blog cannot be published by the November 3, 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
> page card and the post).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-site updated (4603a308f -> a3f6c10c3)
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 4603a308f generate docs for 4f4137af
add 8e4e94694 BLOG - Changelog #20, November 2022
add a3f6c10c3 generate docs for 8e4e9469
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 (4603a308f)
\
N -- N -- N refs/heads/asf-site (a3f6c10c3)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
content/_/_images/blog/Ayushi-Signh-ACNA22.jpg | Bin 0 -> 343991 bytes
content/_/blog.html| 24 +++
...ache-Cassandra-Changelog-20-November-2022.html} | 168 ++---
content/doc/4.1/cassandra/new/index.html | 47 --
content/doc/4.2/cassandra/new/index.html | 23 ++-
content/doc/latest/cassandra/new/index.html| 47 --
content/doc/trunk/cassandra/new/index.html | 23 ++-
content/search-index.js| 2 +-
.../ROOT/images/blog/Ayushi-Signh-ACNA22.jpg | Bin 0 -> 343991 bytes
site-content/source/modules/ROOT/pages/blog.adoc | 24 +++
...pache-Cassandra-Changelog-20-November-2022.adoc | 165
site-ui/build/ui-bundle.zip| Bin 4970139 -> 4970139
bytes
12 files changed, 416 insertions(+), 107 deletions(-)
create mode 100644 content/_/_images/blog/Ayushi-Signh-ACNA22.jpg
copy content/_/blog/{Apache-Cassandra-Changelog-18-August-2022.html =>
Apache-Cassandra-Changelog-20-November-2022.html} (54%)
create mode 100644
site-content/source/modules/ROOT/images/blog/Ayushi-Signh-ACNA22.jpg
create mode 100644
site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-20-November-2022.adoc
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17976) WEBSITE - Update What's New Page for 4.1 and trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17976: -- Attachment: c17976-02-doc-whats_new-trunk.png > WEBSITE - Update What's New Page for 4.1 and trunk > -- > > Key: CASSANDRA-17976 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17976 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Ekaterina Dimitrova >Assignee: Michael Semb Wever >Priority: Low > Fix For: 4.1.x, 4.x > > Attachments: Screenshot 2022-11-02 at 22.22.48.png, Screenshot > 2022-11-02 at 22.40.13.png, c17976-01-doc-whats_new-4.1.png, > c17976-02-doc-whats_new-trunk.png > > > [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html] > The page still says 4.0 and lists 4.0 new developments. > We need to point to 4.1 and list latest developments blog posts, docs; > probably we can also link NEWS.txt and CHANGES.txt -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17976) WEBSITE - Update What's New Page for 4.1 and trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628636#comment-17628636 ] Erick Ramirez edited comment on CASSANDRA-17976 at 11/4/22 4:16 AM: Reviewed and ready to commit. !c17976-01-doc-whats_new-4.1.png|width=300! !c17976-02-doc-whats_new-trunk.png|width=300! was (Author: JIRAUSER285101): Reviewed and ready to commit. > WEBSITE - Update What's New Page for 4.1 and trunk > -- > > Key: CASSANDRA-17976 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17976 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Ekaterina Dimitrova >Assignee: Michael Semb Wever >Priority: Low > Fix For: 4.1.x, 4.x > > Attachments: Screenshot 2022-11-02 at 22.22.48.png, Screenshot > 2022-11-02 at 22.40.13.png, c17976-01-doc-whats_new-4.1.png, > c17976-02-doc-whats_new-trunk.png > > > [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html] > The page still says 4.0 and lists 4.0 new developments. > We need to point to 4.1 and list latest developments blog posts, docs; > probably we can also link NEWS.txt and CHANGES.txt -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17976) WEBSITE - Update What's New Page for 4.1 and trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17976: -- Attachment: c17976-01-doc-whats_new-4.1.png > WEBSITE - Update What's New Page for 4.1 and trunk > -- > > Key: CASSANDRA-17976 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17976 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Ekaterina Dimitrova >Assignee: Michael Semb Wever >Priority: Low > Fix For: 4.1.x, 4.x > > Attachments: Screenshot 2022-11-02 at 22.22.48.png, Screenshot > 2022-11-02 at 22.40.13.png, c17976-01-doc-whats_new-4.1.png, > c17976-02-doc-whats_new-trunk.png > > > [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html] > The page still says 4.0 and lists 4.0 new developments. > We need to point to 4.1 and list latest developments blog posts, docs; > probably we can also link NEWS.txt and CHANGES.txt -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (65558618b -> a3f6c10c3)
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git
discard 65558618b generate docs for 4f4137af
add 8e4e94694 BLOG - Changelog #20, November 2022
new a3f6c10c3 generate docs for 8e4e9469
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 (65558618b)
\
N -- N -- N refs/heads/asf-staging (a3f6c10c3)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
content/_/_images/blog/Ayushi-Signh-ACNA22.jpg | Bin 0 -> 343991 bytes
content/_/blog.html| 24 +++
...ache-Cassandra-Changelog-20-November-2022.html} | 168 ++---
content/search-index.js| 2 +-
.../ROOT/images/blog/Ayushi-Signh-ACNA22.jpg | Bin 0 -> 343991 bytes
site-content/source/modules/ROOT/pages/blog.adoc | 24 +++
...pache-Cassandra-Changelog-20-November-2022.adoc | 165
site-ui/build/ui-bundle.zip| Bin 4970139 -> 4970139
bytes
8 files changed, 324 insertions(+), 59 deletions(-)
create mode 100644 content/_/_images/blog/Ayushi-Signh-ACNA22.jpg
copy content/_/blog/{Apache-Cassandra-Changelog-18-August-2022.html =>
Apache-Cassandra-Changelog-20-November-2022.html} (54%)
create mode 100644
site-content/source/modules/ROOT/images/blog/Ayushi-Signh-ACNA22.jpg
create mode 100644
site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-20-November-2022.adoc
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18014) WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
[
https://issues.apache.org/jira/browse/CASSANDRA-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628653#comment-17628653
]
Erick Ramirez commented on CASSANDRA-18014:
---
The website content is getting built in staging:
||Branch||PR||Commit||Build||
|{{trunk}}|[#191|https://github.com/apache/cassandra-website/pull/191]|[8e4e946|https://github.com/apache/cassandra-website/commit/8e4e94694d5be7d3019f66bfff98ca40668bc1f3]|[#715|https://ci-cassandra.apache.org/job/cassandra-website/715/]|
> WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
> -
>
> Key: CASSANDRA-18014
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18014
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Chris Thornett
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
> Attachments: c18014-01-blog-index.png, c18014-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the November
> 2022 blog "Apache Cassandra Changelog #20"
> If this blog cannot be published by the November 3, 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
> page card and the post).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18014) WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
[
https://issues.apache.org/jira/browse/CASSANDRA-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-18014:
--
Fix Version/s: NA
Source Control Link:
https://github.com/apache/cassandra-website/commit/8e4e94694d5be7d3019f66bfff98ca40668bc1f3
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed:
||Branch||PR||Commit||
|{{trunk}}|[#191|https://github.com/apache/cassandra-website/pull/191]|[8e4e946|https://github.com/apache/cassandra-website/commit/8e4e94694d5be7d3019f66bfff98ca40668bc1f3]|
> WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
> -
>
> Key: CASSANDRA-18014
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18014
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Chris Thornett
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
> Attachments: c18014-01-blog-index.png, c18014-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the November
> 2022 blog "Apache Cassandra Changelog #20"
> If this blog cannot be published by the November 3, 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
> page card and the post).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18014) WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
[ https://issues.apache.org/jira/browse/CASSANDRA-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18014: -- Status: Ready to Commit (was: Review In Progress) I've reviewed the PR and it is ready to commit. !c18014-01-blog-index.png|width=300! !c18014-02-blog-post.png|width=300! > WEBSITE - November 2022 blog "Apache Cassandra Changelog #20" > - > > Key: CASSANDRA-18014 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18014 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Chris Thornett >Priority: Normal > Labels: pull-request-available > Attachments: c18014-01-blog-index.png, c18014-02-blog-post.png > > > This ticket is to capture the work associated with publishing the November > 2022 blog "Apache Cassandra Changelog #20" > If this blog cannot be published by the November 3, 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 > page card and the post). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18014) WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
[ https://issues.apache.org/jira/browse/CASSANDRA-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18014: -- Attachment: c18014-02-blog-post.png c18014-01-blog-index.png > WEBSITE - November 2022 blog "Apache Cassandra Changelog #20" > - > > Key: CASSANDRA-18014 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18014 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Chris Thornett >Priority: Normal > Labels: pull-request-available > Attachments: c18014-01-blog-index.png, c18014-02-blog-post.png > > > This ticket is to capture the work associated with publishing the November > 2022 blog "Apache Cassandra Changelog #20" > If this blog cannot be published by the November 3, 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 > page card and the post). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18014) WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
[ https://issues.apache.org/jira/browse/CASSANDRA-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18014: -- Reviewers: Erick Ramirez Status: Review In Progress (was: Patch Available) > WEBSITE - November 2022 blog "Apache Cassandra Changelog #20" > - > > Key: CASSANDRA-18014 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18014 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Chris Thornett >Priority: Normal > Labels: pull-request-available > Attachments: c18014-01-blog-index.png, c18014-02-blog-post.png > > > This ticket is to capture the work associated with publishing the November > 2022 blog "Apache Cassandra Changelog #20" > If this blog cannot be published by the November 3, 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 > page card and the post). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch trunk updated: BLOG - Changelog #20, November 2022
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 8e4e94694 BLOG - Changelog #20, November 2022 8e4e94694 is described below commit 8e4e94694d5be7d3019f66bfff98ca40668bc1f3 Author: Diogenese Topper AuthorDate: Thu Nov 3 13:37:50 2022 -0700 BLOG - Changelog #20, November 2022 patch by Chris Thornett, Diogenese Topper; reviewed by Erick Ramirez for CASSANDRA-18014 Co-authored by: Chris Thornett Co-authored by: Diogenese Topper --- .../ROOT/images/blog/Ayushi-Signh-ACNA22.jpg | Bin 0 -> 343991 bytes site-content/source/modules/ROOT/pages/blog.adoc | 24 +++ ...pache-Cassandra-Changelog-20-November-2022.adoc | 165 + 3 files changed, 189 insertions(+) diff --git a/site-content/source/modules/ROOT/images/blog/Ayushi-Signh-ACNA22.jpg b/site-content/source/modules/ROOT/images/blog/Ayushi-Signh-ACNA22.jpg new file mode 100644 index 0..383a963b9 Binary files /dev/null and b/site-content/source/modules/ROOT/images/blog/Ayushi-Signh-ACNA22.jpg differ diff --git a/site-content/source/modules/ROOT/pages/blog.adoc b/site-content/source/modules/ROOT/pages/blog.adoc index 7e8b16ef8..7e87f1e83 100644 --- a/site-content/source/modules/ROOT/pages/blog.adoc +++ b/site-content/source/modules/ROOT/pages/blog.adoc @@ -8,6 +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] +=== Apache Cassandra Changelog #20 +[discrete] + November 3, 2022 +-- +[openblock,card-content] +-- +We announce Cassandra 4.1-beta1 and a host of city-based Cassandra Days from Santa Clara to Hanoi, Jakarta and Singapore. + +[openblock,card-btn card-btn--blog] + +[.btn.btn--alt] +xref:blog/Apache-Cassandra-Changelog-20-November-2022.adoc[Read More] + + +-- + +//end card + //start card [openblock,card shadow relative test] diff --git a/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-20-November-2022.adoc b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-20-November-2022.adoc new file mode 100644 index 0..96876464d --- /dev/null +++ b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-20-November-2022.adoc @@ -0,0 +1,165 @@ += Apache Cassandra Changelog #20 +:page-layout: single-post +:page-role: blog-post +:page-post-date: November 3, 2022 +:page-post-author: Chris Thornett +:description: Apache Cassandra Changelog +:keywords: Cassandra, changelog, updates, news, release notes, community, + +:!figure-caption: + +.Our monthly roundup of key activities and knowledge to keep the community informed. +image::blog/changelog_header.jpg[Apache Cassandra Changelog] + +== Release Notes + +The first beta version of Apache Cassandra 4.1 (https://downloads.apache.org/cassandra/4.1-beta1/[4.1-beta1^]) has been released. This is another milestone that brings us closer to the next major release of Cassandra. + +Please read the https://github.com/apache/cassandra/blob/cassandra-4.1-beta1/NEWS.txt[release notes^] and feed back any problems you encounter. + +In the interim, the latest release of Apache Cassandra is https://www.apache.org/dyn/closer.lua/cassandra/4.0.7/apache-cassandra-4.0.7-bin.tar.gz[4.0.7^](https://downloads.apache.org/cassandra/4.0.7/apache-cassandra-4.0.7-bin.tar.gz.asc[pgp^], https://downloads.apache.org/cassandra/4.0.7/apache-cassandra-4.0.7-bin.tar.gz.sha256[sha256^], https://downloads.apache.org/cassandra/4.0.7/apache-cassandra-4.0.7-bin.tar.gz.sha512[sha512^]), which was announced on 23 October 2022. + +Please read the https://github.com/apache/cassandra/blob/cassandra-4.0.7/NEWS.txt[4.0.7 release notes^] and let us know if you encounter any problems. + +The other latest supported releases are Apache Cassandra https://www.apache.org/dyn/closer.lua/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz[3.11.14^] (https://downloads.apache.org/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz.asc[pgp^], https://downloads.apache.org/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz.sha256[sha256^], https://downloads.apache.org/cassandra/3.11.14/apache-cassandra-3.11.14-bin.tar.gz.sha512[sha512^]) and https://www.apache.org/dyn/closer [...] + +Please read the https://github.com/apache/cassandra/blob/cassandra-3.11.14/NEWS.txt[3.11.14^] and https://github.com/apache/cassandra/blob/cassandra-3.0.28/NEWS.txt[3.0.28 release notes^] and contact us if you experience any issues. + +*Note:* For this release cycle only, we will continue to support Cassandra 3.0. as well as the latest patch versions of 3.11 and 4.0. See
[cassandra-website] branch asf-staging updated (4d2366c20 -> 65558618b)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 4d2366c20 generate docs for 4f4137af new 65558618b generate docs for 4f4137af 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 (4d2366c20) \ N -- N -- N refs/heads/asf-staging (65558618b) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/doc/4.1/cassandra/new/index.html| 47 +--- content/doc/4.2/cassandra/new/index.html| 23 ++ content/doc/latest/cassandra/new/index.html | 47 +--- content/doc/trunk/cassandra/new/index.html | 23 ++ content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4970139 -> 4970139 bytes 6 files changed, 93 insertions(+), 49 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17976) WEBSITE - Update What's New Page for 4.1 and trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628639#comment-17628639
]
Erick Ramirez commented on CASSANDRA-17976:
---
Waiting for builds to complete:
||Branch||PR||Commit||Build||
|{{cassandra-4.1}}|[#1969|https://github.com/apache/cassandra/pull/1969]|[a4b90fb|https://github.com/apache/cassandra/commit/a4b90fbc011f2cfab464f375c564af67720a0a1d]|[#197|https://ci-cassandra.apache.org/job/Cassandra-4.1/197/]|
|{{trunk}}|[#1970|https://github.com/apache/cassandra/pull/1970]|[e027229|https://github.com/apache/cassandra/commit/e027229238cafc105fd7913d0aab7e95b6930a34]|[#1362|https://ci-cassandra.apache.org/job/Cassandra-trunk/1362/]|
> WEBSITE - Update What's New Page for 4.1 and trunk
> --
>
> Key: CASSANDRA-17976
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17976
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Ekaterina Dimitrova
>Assignee: Michael Semb Wever
>Priority: Low
> Fix For: 4.1.x, 4.x
>
> Attachments: Screenshot 2022-11-02 at 22.22.48.png, Screenshot
> 2022-11-02 at 22.40.13.png
>
>
> [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html]
> The page still says 4.0 and lists 4.0 new developments.
> We need to point to 4.1 and list latest developments blog posts, docs;
> probably we can also link NEWS.txt and CHANGES.txt
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17976) WEBSITE - Update What's New Page for 4.1 and trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17976:
--
Source Control Link:
https://github.com/apache/cassandra/commit/a4b90fbc011f2cfab464f375c564af67720a0a1d
https://github.com/apache/cassandra/commit/e027229238cafc105fd7913d0aab7e95b6930a34
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed:
||Branch||PR||Commit||
|{{cassandra-4.1}}|[#1969|https://github.com/apache/cassandra/pull/1969]|[a4b90fb|https://github.com/apache/cassandra/commit/a4b90fbc011f2cfab464f375c564af67720a0a1d]|
|{{trunk}}|[#1970|https://github.com/apache/cassandra/pull/1970]|[e027229|https://github.com/apache/cassandra/commit/e027229238cafc105fd7913d0aab7e95b6930a34]|
> WEBSITE - Update What's New Page for 4.1 and trunk
> --
>
> Key: CASSANDRA-17976
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17976
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Ekaterina Dimitrova
>Assignee: Michael Semb Wever
>Priority: Low
> Fix For: 4.1.x, 4.x
>
> Attachments: Screenshot 2022-11-02 at 22.22.48.png, Screenshot
> 2022-11-02 at 22.40.13.png
>
>
> [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html]
> The page still says 4.0 and lists 4.0 new developments.
> We need to point to 4.1 and list latest developments blog posts, docs;
> probably we can also link NEWS.txt and CHANGES.txt
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17976) WEBSITE - Update What's New Page for 4.1 and trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628636#comment-17628636 ] Erick Ramirez commented on CASSANDRA-17976: --- Reviewed and ready to commit. > WEBSITE - Update What's New Page for 4.1 and trunk > -- > > Key: CASSANDRA-17976 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17976 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Ekaterina Dimitrova >Assignee: Michael Semb Wever >Priority: Low > Fix For: 4.1.x, 4.x > > Attachments: Screenshot 2022-11-02 at 22.22.48.png, Screenshot > 2022-11-02 at 22.40.13.png > > > [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html] > The page still says 4.0 and lists 4.0 new developments. > We need to point to 4.1 and list latest developments blog posts, docs; > probably we can also link NEWS.txt and CHANGES.txt -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17976) WEBSITE - Update What's New Page for 4.1 and trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17976: -- Status: Review In Progress (was: Patch Available) > WEBSITE - Update What's New Page for 4.1 and trunk > -- > > Key: CASSANDRA-17976 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17976 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Ekaterina Dimitrova >Assignee: Michael Semb Wever >Priority: Low > Fix For: 4.1.x, 4.x > > Attachments: Screenshot 2022-11-02 at 22.22.48.png, Screenshot > 2022-11-02 at 22.40.13.png > > > [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html] > The page still says 4.0 and lists 4.0 new developments. > We need to point to 4.1 and list latest developments blog posts, docs; > probably we can also link NEWS.txt and CHANGES.txt -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17976) WEBSITE - Update What's New Page for 4.1 and trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17976: -- Status: Ready to Commit (was: Review In Progress) > WEBSITE - Update What's New Page for 4.1 and trunk > -- > > Key: CASSANDRA-17976 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17976 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Ekaterina Dimitrova >Assignee: Michael Semb Wever >Priority: Low > Fix For: 4.1.x, 4.x > > Attachments: Screenshot 2022-11-02 at 22.22.48.png, Screenshot > 2022-11-02 at 22.40.13.png > > > [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html] > The page still says 4.0 and lists 4.0 new developments. > We need to point to 4.1 and list latest developments blog posts, docs; > probably we can also link NEWS.txt and CHANGES.txt -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: WEBSITE - Updated What's New page for 5.0 in trunk
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.git The following commit(s) were added to refs/heads/trunk by this push: new e027229238 WEBSITE - Updated What's New page for 5.0 in trunk e027229238 is described below commit e027229238cafc105fd7913d0aab7e95b6930a34 Author: Erick Ramirez AuthorDate: Fri Nov 4 11:58:12 2022 +1100 WEBSITE - Updated What's New page for 5.0 in trunk patch by Michael Semb Wever, Erick Ramirez; reviewed by Ekaterina Dimitrova, Berenguer Blasi, Erick Ramirez for CASSANDRA-17976 Co-authored by: Mick Semb Wever Co-authored by: Erick Ramirez --- doc/modules/cassandra/pages/new/index.adoc | 19 +-- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/doc/modules/cassandra/pages/new/index.adoc b/doc/modules/cassandra/pages/new/index.adoc index 5bf6cc7862..3945fe1105 100644 --- a/doc/modules/cassandra/pages/new/index.adoc +++ b/doc/modules/cassandra/pages/new/index.adoc @@ -1,12 +1,11 @@ -= New Features in Apache Cassandra 4.0 += New Features in Apache Cassandra 5.0 -This section covers the new features in Apache Cassandra 4.0. +This section covers the new features in Apache Cassandra 5.0. -* xref:new/java11.adoc[Java 11] -* xref:new/virtualtables.adoc[Virtual tables] -* xref:new/auditlogging.adoc[Audit logging] -* xref:new/fqllogging.adoc[Full query logging] -* xref:new/messaging.adoc[Messaging] -* xref:new/streaming.adoc[Streaming] -* xref:new/transientreplication.adoc[Transient replication] -* xref:configuration/configuration.adoc[Configuration] +* https://cwiki.apache.org/confluence/x/FQRACw[ACID Transactions (Accord)] +* https://issues.apache.org/jira/browse/CASSANDRA-16052[Storage Attached Indexes] +* https://issues.apache.org/jira/browse/CASSANDRA-17240[Trie Memtables] +* https://github.com/apache/cassandra/blob/trunk/NEWS.txt[More Guardrails] +* https://issues.apache.org/jira/browse/CASSANDRA-8877[TTL and writetime on collections and UDTs] +* https://cwiki.apache.org/confluence/x/YyD1D[Transactional Cluster Metadata] +* https://issues.apache.org/jira/browse/CASSANDRA-16895[JDK 17] - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.1 updated: WEBSITE - Updated What's New page for 4.1
This is an automated email from the ASF dual-hosted git repository. erickramirezau pushed a commit to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/cassandra-4.1 by this push: new a4b90fbc01 WEBSITE - Updated What's New page for 4.1 a4b90fbc01 is described below commit a4b90fbc011f2cfab464f375c564af67720a0a1d Author: Erick Ramirez AuthorDate: Fri Nov 4 11:33:04 2022 +1100 WEBSITE - Updated What's New page for 4.1 patch by Michael Semb Wever, Erick Ramirez; reviewed by Ekaterina Dimitrova, Berenguer Blasi, Erick Ramirez for CASSANDRA-17976 Co-authored by: Mick Semb Wever Co-authored by: Erick Ramirez --- doc/modules/cassandra/pages/new/index.adoc | 28 ++-- 1 file changed, 18 insertions(+), 10 deletions(-) diff --git a/doc/modules/cassandra/pages/new/index.adoc b/doc/modules/cassandra/pages/new/index.adoc index 5bf6cc7862..a6545a74bc 100644 --- a/doc/modules/cassandra/pages/new/index.adoc +++ b/doc/modules/cassandra/pages/new/index.adoc @@ -1,12 +1,20 @@ -= New Features in Apache Cassandra 4.0 += New Features in Apache Cassandra 4.1 -This section covers the new features in Apache Cassandra 4.0. +This section covers the new features in Apache Cassandra 4.1. -* xref:new/java11.adoc[Java 11] -* xref:new/virtualtables.adoc[Virtual tables] -* xref:new/auditlogging.adoc[Audit logging] -* xref:new/fqllogging.adoc[Full query logging] -* xref:new/messaging.adoc[Messaging] -* xref:new/streaming.adoc[Streaming] -* xref:new/transientreplication.adoc[Transient replication] -* xref:configuration/configuration.adoc[Configuration] + +* https://issues.apache.org/jira/browse/CASSANDRA-17164[Paxos v2] +* link:/_/blog/Apache-Cassandra-4.1-Features-Guardrails-Framework.html[Guardrails] +* link:/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html[New and Improved Configuration Format] +* link:/_/blog/Apache-Cassandra-4.1-Features-Client-side-Password-Hashing.html[Client-side Password Hashing] +* link:/_/blog/Apache-Cassandra-4.1-Denylisting-Partitions.html[Partition Denylist] +* Lots of CQL improvements +* link:/_/blog/Apache-Cassandra-4.1-New-SSTable-Identifiers.html[New SSTable Identifiers] +* https://issues.apache.org/jira/browse/CASSANDRA-17423[Native Transport rate limiting] +* https://issues.apache.org/jira/browse/CASSANDRA-16310[Top partition tracking per table] +* https://issues.apache.org/jira/browse/CASSANDRA-14309[Hint Window consistency] +* https://issues.apache.org/jira/browse/CASSANDRA-17044[Pluggability] +** link:/_/blog/Apache-Cassandra-4.1-Features-Pluggable-Memtable-Implementations.html[Memtable] +** Encryption +** link:/_/blog/Apache-Cassandra-4.1-Features-Authentication-Plugin-Support-for-CQLSH.html[CQLSH Authentication] +* and much link:https://github.com/apache/cassandra/blob/cassandra-4.1/NEWS.txt[more] - 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 (31d5fa947 -> 4d2366c20)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 31d5fa947 generate docs for 4f4137af new 4d2366c20 generate docs for 4f4137af 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 (31d5fa947) \ N -- N -- N refs/heads/asf-staging (4d2366c20) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4970139 -> 4970139 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17976) WEBSITE - Update What's New Page for 4.1 and trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17976: -- Authors: Berenguer Blasi, Ekaterina Dimitrova, Erick Ramirez, Michael Semb Wever (was: Erick Ramirez, Michael Semb Wever) > WEBSITE - Update What's New Page for 4.1 and trunk > -- > > Key: CASSANDRA-17976 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17976 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Ekaterina Dimitrova >Assignee: Michael Semb Wever >Priority: Low > Fix For: 4.1.x, 4.x > > Attachments: Screenshot 2022-11-02 at 22.22.48.png, Screenshot > 2022-11-02 at 22.40.13.png > > > [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html] > The page still says 4.0 and lists 4.0 new developments. > We need to point to 4.1 and list latest developments blog posts, docs; > probably we can also link NEWS.txt and CHANGES.txt -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17976) WEBSITE - Update What's New Page for 4.1 and trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17976: -- Reviewers: Berenguer Blasi, Ekaterina Dimitrova, Erick Ramirez (was: Erick Ramirez) > WEBSITE - Update What's New Page for 4.1 and trunk > -- > > Key: CASSANDRA-17976 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17976 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Ekaterina Dimitrova >Assignee: Michael Semb Wever >Priority: Low > Fix For: 4.1.x, 4.x > > Attachments: Screenshot 2022-11-02 at 22.22.48.png, Screenshot > 2022-11-02 at 22.40.13.png > > > [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html] > The page still says 4.0 and lists 4.0 new developments. > We need to point to 4.1 and list latest developments blog posts, docs; > probably we can also link NEWS.txt and CHANGES.txt -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17976) WEBSITE - Update What's New Page for 4.1 and trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17976: -- Authors: Erick Ramirez, Michael Semb Wever (was: Berenguer Blasi, Ekaterina Dimitrova, Erick Ramirez, Michael Semb Wever) > WEBSITE - Update What's New Page for 4.1 and trunk > -- > > Key: CASSANDRA-17976 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17976 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Ekaterina Dimitrova >Assignee: Michael Semb Wever >Priority: Low > Fix For: 4.1.x, 4.x > > Attachments: Screenshot 2022-11-02 at 22.22.48.png, Screenshot > 2022-11-02 at 22.40.13.png > > > [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html] > The page still says 4.0 and lists 4.0 new developments. > We need to point to 4.1 and list latest developments blog posts, docs; > probably we can also link NEWS.txt and CHANGES.txt -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17976) WEBSITE - Update What's New Page for 4.1 and trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-17976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17976:
--
Authors: Erick Ramirez, Michael Semb Wever (was:
Michael Semb Wever)
Test and Documentation Plan: Stage locally and verify updates render as
expected (was: manual preview)
Status: Patch Available (was: In Progress)
Updated patches:
||Branch||PR||
|{{cassandra-4.1}}|[#1969|https://github.com/apache/cassandra/pull/1969]|
|{{trunk}}|[#1970|https://github.com/apache/cassandra/pull/1970]|
> WEBSITE - Update What's New Page for 4.1 and trunk
> --
>
> Key: CASSANDRA-17976
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17976
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Ekaterina Dimitrova
>Assignee: Michael Semb Wever
>Priority: Low
> Fix For: 4.1.x, 4.x
>
> Attachments: Screenshot 2022-11-02 at 22.22.48.png, Screenshot
> 2022-11-02 at 22.40.13.png
>
>
> [https://cassandra.apache.org/doc/4.1/cassandra/new/index.html]
> The page still says 4.0 and lists 4.0 new developments.
> We need to point to 4.1 and list latest developments blog posts, docs;
> probably we can also link NEWS.txt and CHANGES.txt
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (73d35b9b8 -> 31d5fa947)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 73d35b9b8 generate docs for 4f4137af new 31d5fa947 generate docs for 4f4137af 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 (73d35b9b8) \ N -- N -- N refs/heads/asf-staging (31d5fa947) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: site-ui/build/ui-bundle.zip | Bin 4970139 -> 4970139 bytes 1 file changed, 0 insertions(+), 0 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17178) CEP-10: Simulator Java11 Support
[
https://issues.apache.org/jira/browse/CASSANDRA-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628564#comment-17628564
]
David Capwell edited comment on CASSANDRA-17178 at 11/3/22 11:27 PM:
-
Testing this out on j8 to make sure I can run things before doing j11, and here
is what I see
Warnings about serialVersionUID; should these be build failures?
{code}
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.security.ThreadAwareSecurityManager$1
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.utils.concurrent.Semaphore$Standard
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.metrics.Sampler$Sample
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.distributed.shared.VersionedApplicationState
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.net.ForwardingInfo
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.distributed.impl.MessageImpl
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.distributed.impl.UnsafeGossipHelper$HostInfo
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.service.paxos.ContentionStrategy$TimeLimitedLatencySupplier
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.utils.concurrent.FutureCombiner$Listener
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.streaming.SessionInfo
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.streaming.StreamState
{code}
Tests run differently than normal tests, and this is due to the need for the
agent... ATM the tests don't take a long time so this is fine, but if we start
to add more simulator tests or want to run them longer we may want to switch to
testclasslist to simplify CI... that would require we rethink about a few
things...
{code}
$ ant test-simulator-dtest
...
BUILD SUCCESSFUL
Total time: 1 minute 23 seconds
{code}
Doesn't work on M1 Mac's
{code}
[junit-timeout] The stack size specified is too small, Specify at least 384k
[junit-timeout] Error: Could not create the Java Virtual Machine.
[junit-timeout] Error: A fatal exception has occurred. Program will exit.
{code}
was (Author: dcapwell):
Testing this out on j8 to make sure I can run things before doing j11, and here
is what I see
Warnings about serialVersionUID; should these be build failures?
{code}
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.security.ThreadAwareSecurityManager$1
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.utils.concurrent.Semaphore$Standard
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.metrics.Sampler$Sample
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.distributed.shared.VersionedApplicationState
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.net.ForwardingInfo
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.distributed.impl.MessageImpl
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.distributed.impl.UnsafeGossipHelper$HostInfo
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.service.paxos.ContentionStrategy$TimeLimitedLatencySupplier
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.utils.concurrent.FutureCombiner$Listener
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.streaming.SessionInfo
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.streaming.StreamState
{code}
Tests run differently than normal tests, and this is due to the need for the
agent... ATM the tests don't take a long time so this is fine, but if we start
to add more simulator tests or want to run them longer we may want to switch to
testclasslist to simplify CI... that would require we rethink about a few
things...
{code}
$ ant test-simulator-dtest
...
BUILD SUCCESSFUL
Total time: 1 minute 23 seconds
{code}
> CEP-10: Simulator Java11 Support
>
>
> Key: CASSANDRA-17178
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17178
> Project: Cassandra
> Issue Type: Task
> Components: Test/fuzz
>Reporter: Benedict Elliott Smith
>Assignee: David Capwell
>Priority: Normal
> Fix For: NA
>
>
> Java11
[jira] [Commented] (CASSANDRA-17178) CEP-10: Simulator Java11 Support
[
https://issues.apache.org/jira/browse/CASSANDRA-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628564#comment-17628564
]
David Capwell commented on CASSANDRA-17178:
---
Testing this out on j8 to make sure I can run things before doing j11, and here
is what I see
Warnings about serialVersionUID; should these be build failures?
{code}
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.security.ThreadAwareSecurityManager$1
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.utils.concurrent.Semaphore$Standard
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.metrics.Sampler$Sample
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.distributed.shared.VersionedApplicationState
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.concurrent.SingleThreadExecutorPlus$AtLeastOnce
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.net.ForwardingInfo
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.distributed.impl.MessageImpl
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.distributed.impl.UnsafeGossipHelper$HostInfo
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.service.paxos.ContentionStrategy$TimeLimitedLatencySupplier
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.utils.concurrent.FutureCombiner$Listener
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.streaming.SessionInfo
[junit-timeout] No serialVersionUID on Serializable class
org.apache.cassandra.streaming.StreamState
{code}
Tests run differently than normal tests, and this is due to the need for the
agent... ATM the tests don't take a long time so this is fine, but if we start
to add more simulator tests or want to run them longer we may want to switch to
testclasslist to simplify CI... that would require we rethink about a few
things...
{code}
$ ant test-simulator-dtest
...
BUILD SUCCESSFUL
Total time: 1 minute 23 seconds
{code}
> CEP-10: Simulator Java11 Support
>
>
> Key: CASSANDRA-17178
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17178
> Project: Cassandra
> Issue Type: Task
> Components: Test/fuzz
>Reporter: Benedict Elliott Smith
>Assignee: David Capwell
>Priority: Normal
> Fix For: NA
>
>
> Java11 introduces new protection domains for package private methods, so that
> classes loaded with different class loaders may not access each others’
> package private methods, regardless of the package they are declared within.
> There are differences within the JDK also, and there may be byte weaving
> targets that need updating (ThreadLocalRandom was one that has been handled)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17178) CEP-10: Simulator Java11 Support
[ https://issues.apache.org/jira/browse/CASSANDRA-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-17178: -- Change Category: Quality Assurance Complexity: Challenging Fix Version/s: NA Status: Open (was: Triage Needed) > CEP-10: Simulator Java11 Support > > > Key: CASSANDRA-17178 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17178 > Project: Cassandra > Issue Type: Task > Components: Test/fuzz >Reporter: Benedict Elliott Smith >Assignee: David Capwell >Priority: Normal > Fix For: NA > > > Java11 introduces new protection domains for package private methods, so that > classes loaded with different class loaders may not access each others’ > package private methods, regardless of the package they are declared within. > There are differences within the JDK also, and there may be byte weaving > targets that need updating (ThreadLocalRandom was one that has been handled) -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17178) CEP-10: Simulator Java11 Support
[ https://issues.apache.org/jira/browse/CASSANDRA-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell reassigned CASSANDRA-17178: - Assignee: David Capwell > CEP-10: Simulator Java11 Support > > > Key: CASSANDRA-17178 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17178 > Project: Cassandra > Issue Type: Task > Components: Test/fuzz >Reporter: Benedict Elliott Smith >Assignee: David Capwell >Priority: Normal > > Java11 introduces new protection domains for package private methods, so that > classes loaded with different class loaders may not access each others’ > package private methods, regardless of the package they are declared within. > There are differences within the JDK also, and there may be byte weaving > targets that need updating (ThreadLocalRandom was one that has been handled) -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17912) Fix CircleCI config for running Python upgrade tests on 3.0 and 3.11
[ https://issues.apache.org/jira/browse/CASSANDRA-17912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628550#comment-17628550 ] Ekaterina Dimitrova commented on CASSANDRA-17912: - * 3.0 - 3304 tests have been run and there are two failures which matches Jenkins last runs. The two failures already have tickets opened and linked in Butler(CASSANDRA-17313 and CASSANDRA-17329). * 3.11 - 3676 tests have been run and 1 failed. Again this is matching Jenkins. There is already a ticket open for the failure and linked in Butler (CASSANDRA-17329). [~mck] , do you want to take a final look now when we are ready also with 3.11 before I commit? > Fix CircleCI config for running Python upgrade tests on 3.0 and 3.11 > > > Key: CASSANDRA-17912 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17912 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 3.0.x, 3.11.x > > > It was noticed that Circle CI pushes to run irrelevant for 3.0 and 3.11 > Python upgrade tests. Those are properly skipped in Jenkins. > Example runs: > [CircleCI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1931/workflows/39ef5261-a6bf-4e77-a412-e750e322a231/jobs/15293] > - 3.0 run > [Jenkins|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/] > - while typing this I actually noticed [one > test|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/testReport/junit/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_parallel_upgrade_with_internode_ssl/] > only looking suspicious in Jenkins as it ends the upgrade in 3.11 when we > test 3.0... > This is good to be fixed for two reasons - reduce the noise so we do not miss > legit failures and we should not spend resources to try to run those tests. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17964) Some tests are never executed due to naming violation - fix it and add checkstyle where applicable
[
https://issues.apache.org/jira/browse/CASSANDRA-17964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628517#comment-17628517
]
David Capwell edited comment on CASSANDRA-17964 at 11/3/22 10:13 PM:
-
Looking at https://github.com/instaclustr/cassandra/tree/CASSANDRA-17964-4.1-2
I have concerns that this renames things that were already running, or renames
things that are just fine (such as what class all jvm-dtest extend...)
The issue with checkstyle is that we don't have the full ability to understand
the context and if this is correct or not...
I wrote a quick test to find all bad named tests
{code}
/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.cassandra.distributed.test;
import java.lang.reflect.Method;
import java.lang.reflect.Modifier;
import java.util.List;
import java.util.Set;
import java.util.stream.Collectors;
import java.util.stream.Stream;
import org.junit.Test;
import org.reflections.Reflections;
import org.reflections.scanners.Scanners;
import org.reflections.util.ConfigurationBuilder;
public class DidYouNameThingsRightTest
{
private static final Reflections reflections = new Reflections(new
ConfigurationBuilder().forPackage("org.apache.cassandra").setScanners(Scanners.MethodsAnnotated,
Scanners.SubTypes).setExpandSuperTypes(true));
@Test
public void test()
{
Set methodsAnnotatedWith =
reflections.getMethodsAnnotatedWith(Test.class);
List testFiles =
methodsAnnotatedWith.stream().map(Method::getDeclaringClass).distinct()
//.filter(c ->
c.getPackage().getName().contains("org.apache.cassandra.distributed.test")) //
uncomment to filter to jvm-dtest
.flatMap(DidYouNameThingsRightTest::expand)
.map(DidYouNameThingsRightTest::normalize)
.map(Class::getCanonicalName)
.filter(s ->
!s.endsWith("Test"))
.distinct().sorted()
.collect(Collectors.toList());
throw new AssertionError("Detected tests that have a bad naming
convension: \n" + String.join("\n", testFiles));
}
private static Class normalize(Class klass)
{
for (; klass.getEnclosingClass() != null; klass =
klass.getEnclosingClass())
{
}
return klass;
}
private static Stream> expand(Class klass)
{
Set> subTypes = reflections.getSubTypesOf(klass);
if (subTypes == null || subTypes.isEmpty())
return Stream.of(klass);
Stream> subs = (Stream>) subTypes.stream();
// assume we include if not abstract
if (!Modifier.isAbstract(klass.getModifiers()))
subs = Stream.concat(Stream.of(klass), subs);
return subs;
}
}
{code}
Which finds
{code}
org.apache.cassandra.auth.CassandraAuthorizerTruncatingTests
org.apache.cassandra.cql3.BatchTests
org.apache.cassandra.cql3.CachingBench
org.apache.cassandra.cql3.GcCompactionBench
org.apache.cassandra.cql3.KeywordTestSplit1
org.apache.cassandra.cql3.KeywordTestSplit2
org.apache.cassandra.db.guardrails.GuardrailAllowUncompressedTables
org.apache.cassandra.db.guardrails.GuardrailSecondaryIndexTester
org.apache.cassandra.db.guardrails.GuardrailSecondaryIndexesPerTable
org.apache.cassandra.distributed.test.ByteBuddyExamples
org.apache.cassandra.distributed.test.PaxosRepairTest2
org.apache.cassandra.distributed.test.ReprepareTestOldBehaviour
org.apache.cassandra.distributed.test.VirtualTableFromInternode
org.apache.cassandra.utils.UUIDTests
{code}
Can we limit the changes to just these classes? Would it make sense to
leverage the above code for test discovery? maybe adding something like
{code}
$ ant find-tests-unit
$ ant find-tests-jvm-dtest
$ ant find-tests-jvm-dtest-upgrade
{code}
was (Author: dcapwell):
Looking at https://github.com/instaclustr/cassandra/tree/CASSANDRA-17964-4.1-2
I have
[jira] [Commented] (CASSANDRA-17964) Some tests are never executed due to naming violation - fix it and add checkstyle where applicable
[ https://issues.apache.org/jira/browse/CASSANDRA-17964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628538#comment-17628538 ] David Capwell commented on CASSANDRA-17964: --- We chatted on Slack, history can be found here https://the-asf.slack.com/archives/CK23JSY2K/p1667507316662959 > Some tests are never executed due to naming violation - fix it and add > checkstyle where applicable > -- > > Key: CASSANDRA-17964 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17964 > Project: Cassandra > Issue Type: Task > Components: Test/unit >Reporter: Ruslan Fomkin >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 4.x > > Time Spent: 1h 10m > Remaining Estimate: 0h > > [BatchTests|https://github.com/apache/cassandra/blob/trunk/test/unit/org/apache/cassandra/cql3/BatchTests.java] > doesn't follow naming convention to be run as unit tests and, thus, is never > run. > The rule in build expects names as `*Test`. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17964) Some tests are never executed due to naming violation - fix it and add checkstyle where applicable
[ https://issues.apache.org/jira/browse/CASSANDRA-17964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628531#comment-17628531 ] Stefan Miklosovic edited comment on CASSANDRA-17964 at 11/3/22 9:19 PM: I am fine with abandoning checkstyle if we need something more robust. It seems to me checkstyle module is quite hard to use right with all stuff we need. Talking with [~dcapwell] about this outside of this ticket, we would like to introduce an Ant task which is checking this in more depth and we would fail the build if Ant task fails. I will spend more time on trying to introduce Ant task with the logic pretty similar to David's (if not the same and I just retrofit that code to Ant task). was (Author: smiklosovic): I am fine with abandoning checkstyle if we need something more robust. It seems to me checkstyle module is quite hard to use right with all stuff we need. Talking with [~dcapwell] about this outside of this ticket, we would like to introduce an Ant task which is checking this in more depth and we would fail the build if Ant task fails. I will spend more time on trying to introduce Ant task with the logic pretty similar to David's (if not the same and I just retrofit that code to And task). > Some tests are never executed due to naming violation - fix it and add > checkstyle where applicable > -- > > Key: CASSANDRA-17964 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17964 > Project: Cassandra > Issue Type: Task > Components: Test/unit >Reporter: Ruslan Fomkin >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 4.x > > Time Spent: 1h 10m > Remaining Estimate: 0h > > [BatchTests|https://github.com/apache/cassandra/blob/trunk/test/unit/org/apache/cassandra/cql3/BatchTests.java] > doesn't follow naming convention to be run as unit tests and, thus, is never > run. > The rule in build expects names as `*Test`. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17964) Some tests are never executed due to naming violation - fix it and add checkstyle where applicable
[ https://issues.apache.org/jira/browse/CASSANDRA-17964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628531#comment-17628531 ] Stefan Miklosovic commented on CASSANDRA-17964: --- I am fine with abandoning checkstyle if we need something more robust. It seems to me checkstyle module is quite hard to use right with all stuff we need. Talking with [~dcapwell] about this outside of this ticket, we would like to introduce an Ant task which is checking this in more depth and we would fail the build if Ant task fails. I will spend more time on trying to introduce Ant task with the logic pretty similar to David's (if not the same and I just retrofit that code to And task). > Some tests are never executed due to naming violation - fix it and add > checkstyle where applicable > -- > > Key: CASSANDRA-17964 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17964 > Project: Cassandra > Issue Type: Task > Components: Test/unit >Reporter: Ruslan Fomkin >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 4.x > > Time Spent: 1h 10m > Remaining Estimate: 0h > > [BatchTests|https://github.com/apache/cassandra/blob/trunk/test/unit/org/apache/cassandra/cql3/BatchTests.java] > doesn't follow naming convention to be run as unit tests and, thus, is never > run. > The rule in build expects names as `*Test`. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17964) Some tests are never executed due to naming violation - fix it and add checkstyle where applicable
[
https://issues.apache.org/jira/browse/CASSANDRA-17964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628517#comment-17628517
]
David Capwell edited comment on CASSANDRA-17964 at 11/3/22 9:15 PM:
Looking at https://github.com/instaclustr/cassandra/tree/CASSANDRA-17964-4.1-2
I have concerns that this renames things that were already running, or renames
things that are just fine (such as what class all jvm-dtest extend...)
The issue with checkstyle is that we don't have the full ability to understand
the context and if this is correct or not...
I wrote a quick test to find all bad named tests
{code}
/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.cassandra.distributed.test;
import java.lang.reflect.Method;
import java.util.List;
import java.util.Set;
import java.util.stream.Collectors;
import java.util.stream.Stream;
import org.junit.Test;
import org.reflections.Reflections;
import org.reflections.scanners.Scanners;
import org.reflections.util.ConfigurationBuilder;
public class DidYouNameThingsRightTest
{
private static final Reflections reflections = new Reflections(new
ConfigurationBuilder().forPackage("org.apache.cassandra").setScanners(Scanners.MethodsAnnotated,
Scanners.SubTypes).setExpandSuperTypes(true));
@Test
public void test2()
{
Set methodsAnnotatedWith =
reflections.getMethodsAnnotatedWith(Test.class);
List testFiles =
methodsAnnotatedWith.stream().map(Method::getDeclaringClass).distinct()
//.filter(c ->
c.getPackage().getName().contains("org.apache.cassandra.distributed.test")) //
uncomment to filter to jvm-dtest
.flatMap(DidYouNameThingsRightTest::expand)
.map(DidYouNameThingsRightTest::normalize)
.map(Class::getCanonicalName)
.filter(s ->
!s.endsWith("Test"))
.distinct().sorted()
.collect(Collectors.toList());
System.out.println(String.join("\n", testFiles));
}
private static Class normalize(Class klass)
{
for (; klass.getEnclosingClass() != null; klass =
klass.getEnclosingClass())
{
}
return klass;
}
private static Stream> expand(Class klass)
{
Set> subTypes = reflections.getSubTypesOf(klass);
if (subTypes == null || subTypes.isEmpty())
return Stream.of(klass);
Stream> subs = (Stream>) subTypes.stream();
// assume we include if not abstract
if (!Modifier.isAbstract(klass.getModifiers()))
subs = Stream.concat(Stream.of(klass), subs);
return subs;
}
}
{code}
Which finds
{code}
org.apache.cassandra.auth.CassandraAuthorizerTruncatingTests
org.apache.cassandra.cql3.BatchTests
org.apache.cassandra.cql3.CachingBench
org.apache.cassandra.cql3.GcCompactionBench
org.apache.cassandra.cql3.KeywordTestSplit1
org.apache.cassandra.cql3.KeywordTestSplit2
org.apache.cassandra.db.guardrails.GuardrailAllowUncompressedTables
org.apache.cassandra.db.guardrails.GuardrailSecondaryIndexTester
org.apache.cassandra.db.guardrails.GuardrailSecondaryIndexesPerTable
org.apache.cassandra.distributed.test.ByteBuddyExamples
org.apache.cassandra.distributed.test.PaxosRepairTest2
org.apache.cassandra.distributed.test.ReprepareTestOldBehaviour
org.apache.cassandra.distributed.test.VirtualTableFromInternode
org.apache.cassandra.utils.UUIDTests
{code}
Can we limit the changes to just these classes? Would it make sense to
leverage the above code for test discovery? maybe adding something like
{code}
$ ant find-tests-unit
$ ant find-tests-jvm-dtest
$ ant find-tests-jvm-dtest-upgrade
{code}
was (Author: dcapwell):
Looking at https://github.com/instaclustr/cassandra/tree/CASSANDRA-17964-4.1-2
I have concerns that this renames things that were already running, or renames
things that are just fine (such as
[cassandra-website] branch asf-staging updated (5755f86e3 -> 73d35b9b8)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 5755f86e3 generate docs for 4f4137af new 73d35b9b8 generate docs for 4f4137af 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 (5755f86e3) \ N -- N -- N refs/heads/asf-staging (73d35b9b8) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: site-ui/build/ui-bundle.zip | Bin 4970139 -> 4970139 bytes 1 file changed, 0 insertions(+), 0 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18004) CEP-15: (C*/Accord) - remove futures
[ https://issues.apache.org/jira/browse/CASSANDRA-18004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628525#comment-17628525 ] Josh McKenzie commented on CASSANDRA-18004: --- bq. how we solve the ongoing inefficiencies around governance related to libraries, as each minor update requires a release vote prior to committing the patch that depends upon it. Great point. This is something that's likely to become more pressing in the relatively near future as other things come into the ecosystem under the project umbrella; let's follow up offline about it (us being the pmc) and I'll update here when / if we have some resolution that'll help make this kind of workflow sustainable. > CEP-15: (C*/Accord) - remove futures > > > Key: CASSANDRA-18004 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18004 > Project: Cassandra > Issue Type: Improvement > Components: Accord >Reporter: Blake Eggleston >Assignee: Blake Eggleston >Priority: Normal > > Remove futures in favor of async chain -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18014) WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
[ https://issues.apache.org/jira/browse/CASSANDRA-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper reassigned CASSANDRA-18014: Assignee: Chris Thornett > WEBSITE - November 2022 blog "Apache Cassandra Changelog #20" > - > > Key: CASSANDRA-18014 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18014 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Chris Thornett >Priority: Normal > Labels: pull-request-available > > This ticket is to capture the work associated with publishing the November > 2022 blog "Apache Cassandra Changelog #20" > If this blog cannot be published by the November 3, 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 > page card and the post). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18014) WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
[ https://issues.apache.org/jira/browse/CASSANDRA-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628519#comment-17628519 ] Diogenese Topper commented on CASSANDRA-18014: -- Text reviewed, translated to .adoc format - need someone for final check in staging and commit. > WEBSITE - November 2022 blog "Apache Cassandra Changelog #20" > - > > Key: CASSANDRA-18014 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18014 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > > This ticket is to capture the work associated with publishing the November > 2022 blog "Apache Cassandra Changelog #20" > If this blog cannot be published by the November 3, 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 > page card and the post). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18014) WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
[ https://issues.apache.org/jira/browse/CASSANDRA-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-18014: - Authors: Chris Thornett Test and Documentation Plan: * Add blog post titled "Apache Cassandra Changelog #20" * Modify blog index page * Add image for blog: "Ayushi-Signh-ACNA22.jpg" Status: Patch Available (was: Open) https://github.com/apache/cassandra-website/pull/191 > WEBSITE - November 2022 blog "Apache Cassandra Changelog #20" > - > > Key: CASSANDRA-18014 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18014 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > > This ticket is to capture the work associated with publishing the November > 2022 blog "Apache Cassandra Changelog #20" > If this blog cannot be published by the November 3, 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 > page card and the post). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17964) Some tests are never executed due to naming violation - fix it and add checkstyle where applicable
[
https://issues.apache.org/jira/browse/CASSANDRA-17964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628517#comment-17628517
]
David Capwell commented on CASSANDRA-17964:
---
Looking at https://github.com/instaclustr/cassandra/tree/CASSANDRA-17964-4.1-2
I have concerns that this renames things that were already running, or renames
things that are just fine (such as what class all jvm-dtest extend...)
The issue with checkstyle is that we don't have the full ability to understand
the context and if this is correct or not...
I wrote a quick test to find all bad named tests
{code}
/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.cassandra.distributed.test;
import java.lang.reflect.Method;
import java.util.List;
import java.util.Set;
import java.util.stream.Collectors;
import java.util.stream.Stream;
import org.junit.Test;
import org.reflections.Reflections;
import org.reflections.scanners.Scanners;
import org.reflections.util.ConfigurationBuilder;
public class DidYouNameThingsRightTest
{
private static final Reflections reflections = new Reflections(new
ConfigurationBuilder().forPackage("org.apache.cassandra").setScanners(Scanners.MethodsAnnotated,
Scanners.SubTypes).setExpandSuperTypes(true));
@Test
public void test2()
{
Set methodsAnnotatedWith =
reflections.getMethodsAnnotatedWith(Test.class);
List testFiles =
methodsAnnotatedWith.stream().map(Method::getDeclaringClass).distinct()
//.filter(c ->
c.getPackage().getName().contains("org.apache.cassandra.distributed.test")) //
uncomment to filter to jvm-dtest
.flatMap(DidYouNameThingsRightTest::expand)
.map(DidYouNameThingsRightTest::normalize)
.map(Class::getCanonicalName)
.filter(s ->
!s.endsWith("Test"))
.distinct().sorted()
.collect(Collectors.toList());
System.out.println(String.join("\n", testFiles));
}
private static Class normalize(Class klass)
{
for (; klass.getEnclosingClass() != null; klass =
klass.getEnclosingClass())
{
}
return klass;
}
private static Stream> expand(Class klass)
{
Set> subTypes = reflections.getSubTypesOf(klass);
if (subTypes == null || subTypes.isEmpty())
return Stream.of(klass);
return (Stream>) subTypes.stream();
}
}
{code}
Which finds
{code}
org.apache.cassandra.auth.CassandraAuthorizerTruncatingTests
org.apache.cassandra.cql3.BatchTests
org.apache.cassandra.cql3.CachingBench
org.apache.cassandra.cql3.GcCompactionBench
org.apache.cassandra.cql3.KeywordTestSplit1
org.apache.cassandra.cql3.KeywordTestSplit2
org.apache.cassandra.db.guardrails.GuardrailAllowUncompressedTables
org.apache.cassandra.db.guardrails.GuardrailSecondaryIndexTester
org.apache.cassandra.db.guardrails.GuardrailSecondaryIndexesPerTable
org.apache.cassandra.distributed.test.ByteBuddyExamples
org.apache.cassandra.distributed.test.PaxosRepairTest2
org.apache.cassandra.distributed.test.ReprepareTestOldBehaviour
org.apache.cassandra.distributed.test.VirtualTableFromInternode
org.apache.cassandra.utils.UUIDTests
{code}
Can we limit the changes to just these classes? Would it make sense to
leverage the above code for test discovery? maybe adding something like
{code}
$ ant find-tests-unit
$ ant find-tests-jvm-dtest
$ ant find-tests-jvm-dtest-upgrade
{code}
> Some tests are never executed due to naming violation - fix it and add
> checkstyle where applicable
> --
>
> Key: CASSANDRA-17964
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17964
> Project: Cassandra
> Issue Type: Task
> Components: Test/unit
>Reporter: Ruslan
[jira] [Updated] (CASSANDRA-17964) Some tests are never executed due to naming violation - fix it and add checkstyle where applicable
[ https://issues.apache.org/jira/browse/CASSANDRA-17964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-17964: -- Reviewers: Berenguer Blasi, David Capwell (was: Berenguer Blasi) > Some tests are never executed due to naming violation - fix it and add > checkstyle where applicable > -- > > Key: CASSANDRA-17964 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17964 > Project: Cassandra > Issue Type: Task > Components: Test/unit >Reporter: Ruslan Fomkin >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 4.x > > Time Spent: 1h 10m > Remaining Estimate: 0h > > [BatchTests|https://github.com/apache/cassandra/blob/trunk/test/unit/org/apache/cassandra/cql3/BatchTests.java] > doesn't follow naming convention to be run as unit tests and, thus, is never > run. > The rule in build expects names as `*Test`. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18014) WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
[ https://issues.apache.org/jira/browse/CASSANDRA-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-18014: - Change Category: Semantic Complexity: Normal Status: Open (was: Triage Needed) > WEBSITE - November 2022 blog "Apache Cassandra Changelog #20" > - > > Key: CASSANDRA-18014 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18014 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > > This ticket is to capture the work associated with publishing the November > 2022 blog "Apache Cassandra Changelog #20" > If this blog cannot be published by the November 3, 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 > page card and the post). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18014) WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
[ https://issues.apache.org/jira/browse/CASSANDRA-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-18014: --- Labels: pull-request-available (was: ) > WEBSITE - November 2022 blog "Apache Cassandra Changelog #20" > - > > Key: CASSANDRA-18014 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18014 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > > This ticket is to capture the work associated with publishing the November > 2022 blog "Apache Cassandra Changelog #20" > If this blog cannot be published by the November 3, 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 > page card and the post). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17991) Possible data inconsistency during bootstrap/decommission
[
https://issues.apache.org/jira/browse/CASSANDRA-17991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628507#comment-17628507
]
Jaydeepkumar Chovatia commented on CASSANDRA-17991:
---
[~jjirsa] [~brandon.williams] If you could take a look at it in detail and
provide your opinion. Thank You!
> Possible data inconsistency during bootstrap/decommission
> -
>
> Key: CASSANDRA-17991
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17991
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Bootstrap and Decommission
>Reporter: Jaydeepkumar Chovatia
>Priority: Normal
>
> I am facing one corner case in which the deleted data resurrects.
> tl;dr: This could be because when we stream all the SSTables for a given
> token range to the new owner, then they are not sent atomically, so the new
> owner could do compaction on the partially received SSTables, which might
> remove the tombstones.
>
> Here are the reproducible steps:
> +*Prerequisite*+ # Three nodes Cassandra cluster n1, n2, and n3 (C* version
> 3.0.27)
> #
> {code:java}
> CREATE KEYSPACE KS1 WITH replication = {'class': 'NetworkTopologyStrategy',
> 'dc1': '3'};
> CREATE TABLE KS1.T1 (
> key int,
> c1 int,
> c2 int,
> c3 int
> PRIMARY KEY (key)
> ) WITH CLUSTERING ORDER BY (key ASC)
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND gc_grace_seconds = 864000;
> {code}
>
> *Reproducible Steps*
> * Day1: Insert a new record followed by {_}nodetool flush on n1, n2, and
> n3{_}. A new SSTable ({_}SSTable1{_}) will be created.
> {code:java}
> INSERT INTO KS1.T1 (key, c1, c2, c3) values (1, 10, 20, 30){code}
> * Day2: Insert the same record again followed by _nodetool flush_ {_}on n1,
> n2, and n3{_}{_}.{_} A new SSTable ({_}SSTable2{_}) will be created
> {code:java}
> INSERT INTO KS1.T1 (key, c1, c2, c3) values (1, 10, 20, 30){code}
> * Day3: Here is the data layout on SSTables on n1, n2, and n3
> {code:java}
> SSTable1:
> {
> "partition" : {
> "key" : [ "1" ],
> "position" : 900
> },
> "rows" : [
> "type" : "row",
> "position" : 10,
> "liveness_info" : { "tstamp" : "2022-10-15T00:00:00.01Z"},
> "cells" : [
> { "name" : "c1", "value" : 10 },
> { "name" : "c2", "value" : 20 },
> { "name" : "c3", "value" : 30 },
> ]
> }
> .
> SSTable2:
> {
> "partition" : {
> "key" : [ "1" ],
> "position" : 900
> },
> "rows" : [
> "type" : "row",
> "position" : 10,
> "liveness_info" : { "tstamp" : "2022-10-16T00:00:00.01Z"},
> "cells" : [
> { "name" : "c1", "value" : 10 },
> { "name" : "c2", "value" : 20 },
> { "name" : "c3", "value" : 30 },
> ]
> }
> {code}
> * Day4: Delete the record followed by _nodetool flush_ on n1, n2, and n3
> {code:java}
> CONSISTENCY ALL; DELETE FROM KS1.T1 WHERE key = 1; {code}
> * Day5: Here is the data layout on SSTables on n1, n2, and n3
> {code:java}
> SSTable1:
> {
> "partition" : {
> "key" : [ "1" ],
> "position" : 900
> },
> "rows" : [
> "type" : "row",
> "position" : 10,
> "liveness_info" : { "tstamp" : "2022-10-15T00:00:00.01Z"},
> "cells" : [
> { "name" : "c1", "value" : 10 },
> { "name" : "c2", "value" : 20 },
> { "name" : "c3", "value" : 30 },
> ]
> }
> .
> SSTable2:
> {
> "partition" : {
> "key" : [ "1" ],
> "position" : 900
> },
> "rows" : [
> "type" : "row",
> "position" : 10,
> "liveness_info" : { "tstamp" : "2022-10-16T00:00:00.01Z"},
> "cells" : [
> { "name" : "c1", "value" : 10 },
> { "name" : "c2", "value" : 20 },
> { "name" : "c3", "value" : 30 },
> ]
> }
> .
> SSTable3 (Tombstone):
> {
> "partition" : {
> "key" : [ "1" ],
> "position" : 900
> },
> "rows" : [
> "type" : "row",
> "position" : 10,
> "deletion_info" : { "marked_deleted" : "2022-10-19T00:00:00.01Z",
> "local_delete_time" : "2022-10-19T00:00:00.01Z" },
> "cells" : [ ]
> }
> {code}
> * Day20: Nothing happens for more than 10 days. Let's say the data layout on
> SSTables on n1, n2, and n3 is the same as Day5
> * Day20: A new node (n4) joins the ring, and it is going to be responsible
> for key "1". Let's say it streams the data from n3. The node _n3_ is supposed
> to stream out SSTable1, SSTable2, and SSTable3, but it does not happen
> atomically as per the streaming algorithm.
[jira] [Commented] (CASSANDRA-17912) Fix CircleCI config for running Python upgrade tests on 3.0 and 3.11
[ https://issues.apache.org/jira/browse/CASSANDRA-17912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628498#comment-17628498 ] Ekaterina Dimitrova commented on CASSANDRA-17912: - Thank you for the ping [~adelapena] ! Patch rebased and CI started for 3.0 and 3.11. The other branches do not need CI as the only change will be to add the -a flag in the CircleCI ReadMe. Pending commit on CI results and final confirmation with what we see in Jenkins (plus squash of the three commits as the rebase and updates required separate steps): ||Patch||Upgrade tests running|| |[3.0|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:cassandra:17912-3.0-2?expand=1]|[CircleCI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2021/workflows/3dcf7f43-1ba1-40e1-b89e-0113837489eb]| |[3.11|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:cassandra:17912-3.11]|[CircleCI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2020/workflows/70412fe4-f058-4435-aba4-b28d14eb258a]| |[4.0|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:cassandra:17912-4.0?expand=1]| | |[4.1|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:cassandra:17912-4.1?expand=1]| | |[trunk|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:cassandra:trunk-17912?expand=1]| | > Fix CircleCI config for running Python upgrade tests on 3.0 and 3.11 > > > Key: CASSANDRA-17912 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17912 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 3.0.x, 3.11.x > > > It was noticed that Circle CI pushes to run irrelevant for 3.0 and 3.11 > Python upgrade tests. Those are properly skipped in Jenkins. > Example runs: > [CircleCI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1931/workflows/39ef5261-a6bf-4e77-a412-e750e322a231/jobs/15293] > - 3.0 run > [Jenkins|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/] > - while typing this I actually noticed [one > test|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/testReport/junit/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_parallel_upgrade_with_internode_ssl/] > only looking suspicious in Jenkins as it ends the upgrade in 3.11 when we > test 3.0... > This is good to be fixed for two reasons - reduce the noise so we do not miss > legit failures and we should not spend resources to try to run those tests. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (9545693f -> 5755f86e)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 9545693f generate docs for 4f4137af new 5755f86e generate docs for 4f4137af 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 (9545693f) \ N -- N -- N refs/heads/asf-staging (5755f86e) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4970139 -> 4970139 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18000) CircleCI: Skip checkstyle in the Ant-based repeated tests
[
https://issues.apache.org/jira/browse/CASSANDRA-18000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628481#comment-17628481
]
Andres de la Peña commented on CASSANDRA-18000:
---
Here are the patches for all branches, CI is running:
||Patch||CI||
|[3.0
|https://github.com/apache/cassandra/compare/cassandra-3.0...adelapena:18000-3.0]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/2411/workflows/13f03ad4-4362-4224-af01-71f1aa468656]|
|[3.11
|https://github.com/apache/cassandra/compare/cassandra-3.11...adelapena:18000-3.11]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/2410/workflows/19893b77-8587-4588-8780-516aba9becb8]|
|[4.0
|https://github.com/apache/cassandra/compare/cassandra-4.0...adelapena:18000-4.0]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/2412/workflows/7657837c-8aca-4fcb-a880-b9b9c78c7e84]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/2412/workflows/f6b5d930-bbff-4aac-b759-91454a3194a4]|
|[4.1
|https://github.com/apache/cassandra/compare/cassandra-4.1...adelapena:18000-4.11]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/2409/workflows/93be17d4-f3ee-47fd-916b-eff885ce207f]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/2409/workflows/e0ff6861-ef84-41bb-af42-7009d43e536b]|
|[trunk|https://github.com/apache/cassandra/compare/trunk...adelapena:18000-trunk]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/2408/workflows/be507a78-97a7-44aa-8eed-84a1f955f9ae]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/2408/workflows/a146ebc3-9cde-4017-953c-1cac2fcb7931]|
> CircleCI: Skip checkstyle in the Ant-based repeated tests
> -
>
> Key: CASSANDRA-18000
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18000
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>
> The CircleCI jobs for repeating Ant-based tests include the {{checkstyle}}
> and {{checkstyle-test}} targets. Those targets are skipped for Java 11 but
> not for Java 8.
> Including those targets on every test iteration produces a significant
> difference in the run times of repeated test jobs for j8 and j11:
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/122d58b9-b454-4a99-8c46-fb7ef225/jobs/23225]
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/50f33d9b-c7c6-4aa9-bac9-22ac78ad6b8c/jobs/23224]
> We should use the {{no-checkstyle}} flag in the iterations done by those
> jobs. That should significantly speed up the jobs and save resources.
>
> Thanks to [~bereng] , who detected the difference in the running times
> between j8 and j11.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17412) CEP-15: (Accord) Initial Cassandra Integration
[ https://issues.apache.org/jira/browse/CASSANDRA-17412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628432#comment-17628432 ] David Capwell commented on CASSANDRA-17412: --- [~bdeggleston] should we close this now that cep-15-accord branch exists from the metadata-persistence branch? That includes this patch > CEP-15: (Accord) Initial Cassandra Integration > -- > > Key: CASSANDRA-17412 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17412 > Project: Cassandra > Issue Type: New Feature > Components: Accord >Reporter: Blake Eggleston >Assignee: Blake Eggleston >Priority: Normal > > Integrate the accord messages into Cassandra and implement a basic Cassandra > to accord topology mapping. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18014) WEBSITE - November 2022 blog "Apache Cassandra Changelog #20"
Diogenese Topper created CASSANDRA-18014: Summary: WEBSITE - November 2022 blog "Apache Cassandra Changelog #20" Key: CASSANDRA-18014 URL: https://issues.apache.org/jira/browse/CASSANDRA-18014 Project: Cassandra Issue Type: Task Components: Documentation/Blog Reporter: Diogenese Topper This ticket is to capture the work associated with publishing the November 2022 blog "Apache Cassandra Changelog #20" If this blog cannot be published by the November 3, 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 page card and the post). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18013) Splitter sometimes creates different number of splits than requested
[
https://issues.apache.org/jira/browse/CASSANDRA-18013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628405#comment-17628405
]
Jacek Lewandowski commented on CASSANDRA-18013:
---
https://github.com/apache/cassandra/pull/1968 (3.11)
> Splitter sometimes creates different number of splits than requested
>
>
> Key: CASSANDRA-18013
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18013
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 3.11.x, 4.1, 4.2, 4.x
>
>
> {{Splitter}} in some cases may produce one split more than requested. When it
> happens, it fails with assertion error when assertions are enabled.
> Test to reproduce the issue:
> {code:java}
> Splitter splitter = getSplitter(Murmur3Partitioner.instance);
> long lt = 0;
> long rt = 31;
> Range range = new
> Range<>(getWrappedToken(Murmur3Partitioner.instance, BigInteger.valueOf(lt)),
>
> getWrappedToken(Murmur3Partitioner.instance, BigInteger.valueOf(rt)));
> for (int i = 1; i <= (rt - lt); i++)
> {
> List splits = splitter.splitOwnedRanges(i,
> Arrays.asList(new Splitter.WeightedRange(1.0d, range)), false);
> logger.info("{} splits of {} are: {}", i, range, splits);
> Assertions.assertThat(splits).hasSize(i);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18013) Splitter sometimes creates different number of splits than requested
[
https://issues.apache.org/jira/browse/CASSANDRA-18013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacek Lewandowski updated CASSANDRA-18013:
--
Test and Documentation Plan: run regressions
Status: Patch Available (was: In Progress)
> Splitter sometimes creates different number of splits than requested
>
>
> Key: CASSANDRA-18013
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18013
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 3.11.x, 4.1, 4.2, 4.x
>
>
> {{Splitter}} in some cases may produce one split more than requested. When it
> happens, it fails with assertion error when assertions are enabled.
> Test to reproduce the issue:
> {code:java}
> Splitter splitter = getSplitter(Murmur3Partitioner.instance);
> long lt = 0;
> long rt = 31;
> Range range = new
> Range<>(getWrappedToken(Murmur3Partitioner.instance, BigInteger.valueOf(lt)),
>
> getWrappedToken(Murmur3Partitioner.instance, BigInteger.valueOf(rt)));
> for (int i = 1; i <= (rt - lt); i++)
> {
> List splits = splitter.splitOwnedRanges(i,
> Arrays.asList(new Splitter.WeightedRange(1.0d, range)), false);
> logger.info("{} splits of {} are: {}", i, range, splits);
> Assertions.assertThat(splits).hasSize(i);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18013) Splitter sometimes creates different number of splits than requested
[
https://issues.apache.org/jira/browse/CASSANDRA-18013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacek Lewandowski updated CASSANDRA-18013:
--
Bug Category: Parent values: Correctness(12982)Level 1 values:
Consistency(12989)
Complexity: Normal
Discovered By: Adhoc Test
Severity: Normal
Status: Open (was: Triage Needed)
> Splitter sometimes creates different number of splits than requested
>
>
> Key: CASSANDRA-18013
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18013
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 3.11.x, 4.1, 4.2, 4.x
>
>
> {{Splitter}} in some cases may produce one split more than requested. When it
> happens, it fails with assertion error when assertions are enabled.
> Test to reproduce the issue:
> {code:java}
> Splitter splitter = getSplitter(Murmur3Partitioner.instance);
> long lt = 0;
> long rt = 31;
> Range range = new
> Range<>(getWrappedToken(Murmur3Partitioner.instance, BigInteger.valueOf(lt)),
>
> getWrappedToken(Murmur3Partitioner.instance, BigInteger.valueOf(rt)));
> for (int i = 1; i <= (rt - lt); i++)
> {
> List splits = splitter.splitOwnedRanges(i,
> Arrays.asList(new Splitter.WeightedRange(1.0d, range)), false);
> logger.info("{} splits of {} are: {}", i, range, splits);
> Assertions.assertThat(splits).hasSize(i);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18013) Splitter sometimes creates different number of splits than requested
[
https://issues.apache.org/jira/browse/CASSANDRA-18013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacek Lewandowski updated CASSANDRA-18013:
--
Fix Version/s: 3.11.x
> Splitter sometimes creates different number of splits than requested
>
>
> Key: CASSANDRA-18013
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18013
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 3.11.x, 4.1, 4.2, 4.x
>
>
> {{Splitter}} in some cases may produce one split more than requested. When it
> happens, it fails with assertion error when assertions are enabled.
> Test to reproduce the issue:
> {code:java}
> Splitter splitter = getSplitter(Murmur3Partitioner.instance);
> long lt = 0;
> long rt = 31;
> Range range = new
> Range<>(getWrappedToken(Murmur3Partitioner.instance, BigInteger.valueOf(lt)),
>
> getWrappedToken(Murmur3Partitioner.instance, BigInteger.valueOf(rt)));
> for (int i = 1; i <= (rt - lt); i++)
> {
> List splits = splitter.splitOwnedRanges(i,
> Arrays.asList(new Splitter.WeightedRange(1.0d, range)), false);
> logger.info("{} splits of {} are: {}", i, range, splits);
> Assertions.assertThat(splits).hasSize(i);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18013) Splitter sometimes creates different number of splits than requested
[
https://issues.apache.org/jira/browse/CASSANDRA-18013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacek Lewandowski updated CASSANDRA-18013:
--
Fix Version/s: 4.1
4.2
4.x
> Splitter sometimes creates different number of splits than requested
>
>
> Key: CASSANDRA-18013
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18013
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.1, 4.2, 4.x
>
>
> {{Splitter}} in some cases may produce one split more than requested. When it
> happens, it fails with assertion error when assertions are enabled.
> Test to reproduce the issue:
> {code:java}
> Splitter splitter = getSplitter(Murmur3Partitioner.instance);
> long lt = 0;
> long rt = 31;
> Range range = new
> Range<>(getWrappedToken(Murmur3Partitioner.instance, BigInteger.valueOf(lt)),
>
> getWrappedToken(Murmur3Partitioner.instance, BigInteger.valueOf(rt)));
> for (int i = 1; i <= (rt - lt); i++)
> {
> List splits = splitter.splitOwnedRanges(i,
> Arrays.asList(new Splitter.WeightedRange(1.0d, range)), false);
> logger.info("{} splits of {} are: {}", i, range, splits);
> Assertions.assertThat(splits).hasSize(i);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18013) Splitter sometimes creates different number of splits than requested
Jacek Lewandowski created CASSANDRA-18013:
-
Summary: Splitter sometimes creates different number of splits
than requested
Key: CASSANDRA-18013
URL: https://issues.apache.org/jira/browse/CASSANDRA-18013
Project: Cassandra
Issue Type: Bug
Components: Local/Compaction
Reporter: Jacek Lewandowski
Assignee: Jacek Lewandowski
{{Splitter}} in some cases may produce one split more than requested. When it
happens, it fails with assertion error when assertions are enabled.
Test to reproduce the issue:
{code:java}
Splitter splitter = getSplitter(Murmur3Partitioner.instance);
long lt = 0;
long rt = 31;
Range range = new
Range<>(getWrappedToken(Murmur3Partitioner.instance, BigInteger.valueOf(lt)),
getWrappedToken(Murmur3Partitioner.instance, BigInteger.valueOf(rt)));
for (int i = 1; i <= (rt - lt); i++)
{
List splits = splitter.splitOwnedRanges(i, Arrays.asList(new
Splitter.WeightedRange(1.0d, range)), false);
logger.info("{} splits of {} are: {}", i, range, splits);
Assertions.assertThat(splits).hasSize(i);
}
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17972) nodetool resetlocalschema does not sync schema
[
https://issues.apache.org/jira/browse/CASSANDRA-17972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628376#comment-17628376
]
Brandon Williams commented on CASSANDRA-17972:
--
Unfortunately now your test runs are not against the latest commits. That
said, everything looks okay to me, it should just be a matter of checking with
CI.
> nodetool resetlocalschema does not sync schema
> --
>
> Key: CASSANDRA-17972
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17972
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
>Reporter: Cameron Zemek
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 3.0.x, 3.11.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Steps to reproduce:
> {code:java}
> $ ccm create -n 2 -v 3.11.13 -s resettest
> $ ccm node1 cqlsh -e "CREATE KEYSPACE test WITH replication =
> {'class':'NetworkTopologyStrategy', 'datacenter1': 2}"
> $ ccm node1 cqlsh -e "CREATE TABLE test.messages(id int primary key, message
> text)"
> $ ccm node1 nodetool describecluster
> Cluster Information:
> Name: resettest
> Snitch: org.apache.cassandra.locator.SimpleSnitch
> DynamicEndPointSnitch: enabled
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> 5172094b-dee2-3967-b5f0-dfd81d572a74: [127.0.0.1, 127.0.0.2]
> $ ccm node2 nodetool resetlocalschema
> $ ccm node2 cqlsh -e 'describe full schema'
> $ find ~/.ccm/resettest/node2/data0/system_schema/ -maxdepth 2 -type f
> $ ccm node2 nodetool describecluster
> Cluster Information:
> Name: resettest
> Snitch: org.apache.cassandra.locator.SimpleSnitch
> DynamicEndPointSnitch: enabled
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> 5172094b-dee2-3967-b5f0-dfd81d572a74: [127.0.0.1]
> 59adb24e-f3cd-3e02-97f0-5b395827453f: [127.0.0.2]
> $ ccm node2 stop
> $ ccm node2 start
> $ ccm node2 nodetool describecluster
> Cluster Information:
> Name: jpmctest
> Snitch: org.apache.cassandra.locator.SimpleSnitch
> DynamicEndPointSnitch: enabled
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> 5172094b-dee2-3967-b5f0-dfd81d572a74: [127.0.0.1, 127.0.0.2]
> {code}
> Its not resyncing the schema until after restarting the node.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18000) CircleCI: Skip checkstyle in the Ant-based repeated tests
[
https://issues.apache.org/jira/browse/CASSANDRA-18000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628347#comment-17628347
]
Andres de la Peña edited comment on CASSANDRA-18000 at 11/3/22 2:51 PM:
Ah, that one indeed takes longer. It's probably due to the use of the
[RepeatableRunner
|https://github.com/bereng/cassandra/commit/87ace66b11279dffc9a06f4f08c38512da9fc62f]
used in combination with the multiplexer, yielding -5- 25 million test
iterations and thereof larger result files.
{quote}Iirc there was some option to store test results or skip that.
{quote}
That would be not storing things in the {{store_test_results}} phase. But that
is used also for both comparing with previous runs and for building the results
view in the GUI, as I understand from
[this|https://circleci.com/docs/collect-test-data/#overview]. What we would
need is a way to have the results way without the comparison with previous
results. That seems like a question for CircleCI support. In any case, I would
do that on a separate ticket.
was (Author: adelapena):
Ah, that one indeed takes longer. It's probably due to the use of the
[RepeatableRunner
|https://github.com/bereng/cassandra/commit/87ace66b11279dffc9a06f4f08c38512da9fc62f]
used in combination with the multiplexer, yielding 5 million test iterations
and thereof larger result files.
{quote}Iirc there was some option to store test results or skip that.
{quote}
That would be not storing things in the {{store_test_results}} phase. But that
is used also for both comparing with previous runs and for building the results
view in the GUI, as I understand from
[this|https://circleci.com/docs/collect-test-data/#overview]. What we would
need is a way to have the results way without the comparison with previous
results. That seems like a question for CircleCI support. In any case, I would
do that on a separate ticket.
> CircleCI: Skip checkstyle in the Ant-based repeated tests
> -
>
> Key: CASSANDRA-18000
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18000
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>
> The CircleCI jobs for repeating Ant-based tests include the {{checkstyle}}
> and {{checkstyle-test}} targets. Those targets are skipped for Java 11 but
> not for Java 8.
> Including those targets on every test iteration produces a significant
> difference in the run times of repeated test jobs for j8 and j11:
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/122d58b9-b454-4a99-8c46-fb7ef225/jobs/23225]
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/50f33d9b-c7c6-4aa9-bac9-22ac78ad6b8c/jobs/23224]
> We should use the {{no-checkstyle}} flag in the iterations done by those
> jobs. That should significantly speed up the jobs and save resources.
>
> Thanks to [~bereng] , who detected the difference in the running times
> between j8 and j11.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-8675) COPY TO/FROM broken for newline characters
[
https://issues.apache.org/jira/browse/CASSANDRA-8675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628350#comment-17628350
]
Michael Shuler commented on CASSANDRA-8675:
---
Hi Vincenzo, would you be so kind as to verify the bug still affects trunk/4.x?
If the behavior does indeed still present itself, edit the bug and adjust the
fixver from 3.0.x to also include: 3.11., 4.x, 5.x. If it is important to you,
as it sounds that it is, please bring this up on the cassandra-dev mailing list
and see if you can find an active committer to review and offer feedback. (I
would suggest that a patch that also includes test(s) would be an improvement
to the current patch.)
As it sits, this bug likely won't be seen by other devs outside of the few
ticket "watchers", which is how I was notified. The squeaky wheel is going to
get noticed.
> COPY TO/FROM broken for newline characters
> --
>
> Key: CASSANDRA-8675
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8675
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Tools
> Environment: [cqlsh 5.0.1 | Cassandra 2.1.2 | CQL spec 3.2.0 | Native
> protocol v3]
> Ubuntu 14.04 64-bit
>Reporter: Lex Lythius
>Priority: Normal
> Labels: cqlsh, remove-reopen
> Fix For: 3.0.x
>
> Attachments: CASSANDRA-8675.patch, copytest.csv
>
>
> Exporting/importing does not preserve contents when texts containing newline
> (and possibly other) characters are involved:
> {code:sql}
> cqlsh:test> create table if not exists copytest (id int primary key, t text);
> cqlsh:test> insert into copytest (id, t) values (1, 'This has a newline
> ... character');
> cqlsh:test> insert into copytest (id, t) values (2, 'This has a quote "
> character');
> cqlsh:test> insert into copytest (id, t) values (3, 'This has a fake tab \t
> character (typed backslash, t)');
> cqlsh:test> select * from copytest;
> id | t
> +-
> 1 | This has a newline\ncharacter
> 2 |This has a quote " character
> 3 | This has a fake tab \t character (entered slash-t text)
> (3 rows)
> cqlsh:test> copy copytest to '/tmp/copytest.csv';
> 3 rows exported in 0.034 seconds.
> cqlsh:test> copy copytest from '/tmp/copytest.csv';
> 3 rows imported in 0.005 seconds.
> cqlsh:test> select * from copytest;
> id | t
> +---
> 1 | This has a newlinencharacter
> 2 | This has a quote " character
> 3 | This has a fake tab \t character (typed backslash, t)
> (3 rows)
> {code}
> I tried replacing \n in the CSV file with \\n, which just expands to \n in
> the table; and with an actual newline character, which fails with error since
> it prematurely terminates the record.
> It seems backslashes are only used to take the following character as a
> literal
> Until this is fixed, what would be the best way to refactor an old table with
> a new, incompatible structure maintaining its content and name, since we
> can't rename tables?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18000) CircleCI: Skip checkstyle in the Ant-based repeated tests
[
https://issues.apache.org/jira/browse/CASSANDRA-18000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628347#comment-17628347
]
Andres de la Peña commented on CASSANDRA-18000:
---
Ah, that one indeed takes longer. It's probably due to the use of the
[RepeatableRunner
|https://github.com/bereng/cassandra/commit/87ace66b11279dffc9a06f4f08c38512da9fc62f]
used in combination with the multiplexer, yielding 5 million test iterations
and thereof larger result files.
{quote}Iirc there was some option to store test results or skip that.
{quote}
That would be not storing things in the {{store_test_results}} phase. But that
is used also for both comparing with previous runs and for building the results
view in the GUI, as I understand from
[this|https://circleci.com/docs/collect-test-data/#overview]. What we would
need is a way to have the results way without the comparison with previous
results. That seems like a question for CircleCI support. In any case, I would
do that on a separate ticket.
> CircleCI: Skip checkstyle in the Ant-based repeated tests
> -
>
> Key: CASSANDRA-18000
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18000
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>
> The CircleCI jobs for repeating Ant-based tests include the {{checkstyle}}
> and {{checkstyle-test}} targets. Those targets are skipped for Java 11 but
> not for Java 8.
> Including those targets on every test iteration produces a significant
> difference in the run times of repeated test jobs for j8 and j11:
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/122d58b9-b454-4a99-8c46-fb7ef225/jobs/23225]
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/50f33d9b-c7c6-4aa9-bac9-22ac78ad6b8c/jobs/23224]
> We should use the {{no-checkstyle}} flag in the iterations done by those
> jobs. That should significantly speed up the jobs and save resources.
>
> Thanks to [~bereng] , who detected the difference in the running times
> between j8 and j11.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17854) Add JDK17 to our test docker images
[ https://issues.apache.org/jira/browse/CASSANDRA-17854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628334#comment-17628334 ] Brandon Williams commented on CASSANDRA-17854: -- cassandra-builds is now ready to go with j17 images. > Add JDK17 to our test docker images > --- > > Key: CASSANDRA-17854 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17854 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > In preparation to support JDK 17 I want to add JDK 17 to our test images to > enable our CIs for testing with JDK 17 > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17871) Update debian packages for bullseye
[ https://issues.apache.org/jira/browse/CASSANDRA-17871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17871: - Fix Version/s: 2.2.20 3.0.29 3.11.15 4.0.8 4.1-beta2 4.2 (was: 2.2.x) (was: 3.0.x) (was: 3.11.x) (was: 4.0.x) (was: 4.1.x) Source Control Link: https://github.com/apache/cassandra/commit/bba519501cbc7f47577fd7ba4d08969ff8e1d90c Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed this, Mick's fix, and my 17854 branch. > Update debian packages for bullseye > --- > > Key: CASSANDRA-17871 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17871 > Project: Cassandra > Issue Type: Task > Components: Packaging >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 2.2.20, 3.0.29, 3.11.15, 4.0.8, 4.1-beta2, 4.2 > > > We are updating the buster docker image used to build debian packages to > bullseye (which is probably a bit overdue) in CASSANDRA-17854 Package build > dependencies for versions using python2 need to be updated for this to work. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-builds] 02/02: Add j17 to images; upgrade buster to bullseye
This is an automated email from the ASF dual-hosted git repository.
brandonwilliams pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-builds.git
commit f59c8bf8c2c504475d85b261a60b5d48c9c14983
Author: Brandon Williams
AuthorDate: Tue Aug 30 11:40:11 2022 -0500
Add j17 to images; upgrade buster to bullseye
Patch by brandonwilliams; reviewed by edimitrova for CASSANDRA-17854
---
README.md | 10 ++--
build-scripts/cassandra-deb-packaging.sh | 8 ++--
docker/almalinux-image.docker | 1 +
docker/build-debs.sh | 2 +-
.../{buster-image.docker => bullseye-image.docker} | 13 --
docker/centos7-image.docker| 6 +++
docker/centos8-image.docker| 54 --
docker/jessie-image.docker | 49
8 files changed, 25 insertions(+), 118 deletions(-)
diff --git a/README.md b/README.md
index 2d79a87..c2f6758 100644
--- a/README.md
+++ b/README.md
@@ -28,16 +28,14 @@ Prior to release, make sure to edit:
```docker build -t cass-build-rpms -f docker/almalinux-image.docker
docker/```
The image will contain a clone of the Apache git repository by default.
Using a different repository is possible by adding the `--build-arg
CASSANDRA_GIT_URL=https://github.com/myuser/cassandra.git` parameter. All
successive builds will be executed based on the repository cloned during docker
image creation.
2. Run build script through docker (specify branch, e.g. cassandra-3.0 and
version, e.g. 3.0.11):
- * Debian Jessie:
-```docker run --rm -v `pwd`/dist:/dist `docker images -f
label=org.cassandra.buildenv=jessie -q` /home/build/build-debs.sh
```
- * Debian Buster
-```docker run --rm -v `pwd`/dist:/dist `docker images -f
label=org.cassandra.buildenv=buster -q` /home/build/build-debs.sh
```
+ * Debian Bullseye
+```docker run --rm -v `pwd`/dist:/dist `docker images -f
label=org.cassandra.buildenv=bullseye -q` /home/build/build-debs.sh
```
* RPM:
```docker run --rm -v `pwd`/dist:/dist `docker images -f
label=org.cassandra.buildenv=almalinux -q` /home/build/build-rpms.sh
```
-For the build by Debian Buster, you have the possibility to build Cassandra
either by Java 8 (default) or by Java 11. You control the Java version like
following. If you want to build with Java 8, just omit that last option.
+For the build by Debian Bullseye, you have the possibility to build Cassandra
either by Java 8 (default) or by Java 11. You control the Java version like
following. If you want to build with Java 8, just omit that last option.
-```docker run --rm -v `pwd`/dist:/dist `docker images -f
label=org.cassandra.buildenv=buster -q` /home/build/build-debs.sh
11```
+```docker run --rm -v `pwd`/dist:/dist `docker images -f
label=org.cassandra.buildenv=bullseye -q` /home/build/build-debs.sh
11```
You should find newly created Debian and RPM packages in the `dist` directory.
diff --git a/build-scripts/cassandra-deb-packaging.sh
b/build-scripts/cassandra-deb-packaging.sh
index a1483f0..980e9a5 100755
--- a/build-scripts/cassandra-deb-packaging.sh
+++ b/build-scripts/cassandra-deb-packaging.sh
@@ -26,18 +26,18 @@ java_version=$2
command -v docker >/dev/null 2>&1 || { echo >&2 "docker needs to be
installed"; exit 1; }
(docker info >/dev/null 2>&1) || { echo >&2 "docker needs to running"; exit 1;
}
[ -d "${cassandra_builds_dir}" ] || { echo >&2 "cassandra-builds directory
must exist"; exit 1; }
-[ -f "${cassandra_builds_dir}/docker/buster-image.docker" ] || { echo >&2
"docker/buster-image.docker must exist"; exit 1; }
+[ -f "${cassandra_builds_dir}/docker/bullseye-image.docker" ] || { echo >&2
"docker/bullseye-image.docker must exist"; exit 1; }
[ -f "${cassandra_builds_dir}/docker/build-debs.sh" ] || { echo >&2
"docker/build-debs.sh must exist"; exit 1; }
# remove any previous older built images
-docker image prune --all --force --filter label=org.cassandra.buildenv=buster
--filter "until=4h" || true
+docker image prune --all --force --filter
label=org.cassandra.buildenv=bullseye --filter "until=4h" || true
pushd $cassandra_builds_dir
# Create build images containing the build tool-chain, Java and an Apache
Cassandra git working directory
-docker build --build-arg CASSANDRA_GIT_URL=$CASSANDRA_GIT_URL --build-arg
UID_ARG=`id -u` --build-arg GID_ARG=`id -g` -t
cassandra-artifacts-buster:${sha} -f docker/buster-image.docker docker/
+docker build --build-arg CASSANDRA_GIT_URL=$CASSANDRA_GIT_URL --build-arg
UID_ARG=`id -u` --build-arg GID_ARG=`id -g` -t
cassandra-artifacts-bullseye:${sha} -f docker/bullseye-image.docker docker/
# Run build script through docker (specify branch, tag, or sha)
-docker run --rm -v "${deb_dir}":/dist -v
~/.m2/repository/:/home/build/.m2/repository/ cassandra-artifacts-buster:${sha}
[cassandra-builds] 01/02: ninja-fix building cassandra-2.2 artefacts
This is an automated email from the ASF dual-hosted git repository.
brandonwilliams pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-builds.git
commit 32d110a0896f8748670775202d6050da9d451981
Author: Mick Semb Wever
AuthorDate: Mon Oct 31 21:34:34 2022 +0100
ninja-fix building cassandra-2.2 artefacts
---
docker/build-debs.sh | 3 ++-
docker/build-rpms.sh | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/docker/build-debs.sh b/docker/build-debs.sh
index 4484d98..52e323a 100755
--- a/docker/build-debs.sh
+++ b/docker/build-debs.sh
@@ -118,7 +118,8 @@ javac -version
# Pre-download dependencies, loop to prevent failures
set +e
for x in $(seq 1 3); do
-ant clean resolver-dist-lib
+# maven-ant-tasks-retrieve-build is for cassandra-2.2 support
+ant realclean clean resolver-dist-lib || ant realclean
maven-ant-tasks-retrieve-build
RETURN="$?"
if [ "${RETURN}" -eq "0" ]; then break ; fi
sleep 3
diff --git a/docker/build-rpms.sh b/docker/build-rpms.sh
index 7382228..651a7e4 100755
--- a/docker/build-rpms.sh
+++ b/docker/build-rpms.sh
@@ -107,7 +107,8 @@ javac -version
# Pre-download dependencies, loop to prevent failures
set +e
for x in $(seq 1 3); do
-ant clean resolver-dist-lib
+# maven-ant-tasks-retrieve-build is for cassandra-2.2 support
+ant realclean clean resolver-dist-lib || ant realclean
maven-ant-tasks-retrieve-build
RETURN="$?"
if [ "${RETURN}" -eq "0" ]; then break ; fi
sleep 3
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-builds] branch trunk updated (c07e472 -> f59c8bf)
This is an automated email from the ASF dual-hosted git repository.
brandonwilliams pushed a change to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-builds.git
from c07e472 When cutting a release, and having built rpm noboolean
packages, copy files separately
new 32d110a ninja-fix building cassandra-2.2 artefacts
new f59c8bf Add j17 to images; upgrade buster to bullseye
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:
README.md | 10 ++--
build-scripts/cassandra-deb-packaging.sh | 8 ++--
docker/almalinux-image.docker | 1 +
docker/build-debs.sh | 5 +-
docker/build-rpms.sh | 3 +-
.../{buster-image.docker => bullseye-image.docker} | 13 --
docker/centos7-image.docker| 6 +++
docker/centos8-image.docker| 54 --
docker/jessie-image.docker | 49
9 files changed, 29 insertions(+), 120 deletions(-)
rename docker/{buster-image.docker => bullseye-image.docker} (79%)
delete mode 100644 docker/centos8-image.docker
delete mode 100644 docker/jessie-image.docker
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18000) CircleCI: Skip checkstyle in the Ant-based repeated tests
[
https://issues.apache.org/jira/browse/CASSANDRA-18000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628331#comment-17628331
]
Berenguer Blasi commented on CASSANDRA-18000:
-
Take a look at
[this|https://app.circleci.com/pipelines/github/bereng/cassandra/796/workflows/be470790-e5bc-4fe7-97bc-bc2aaff554d1/jobs/7232]
one: 4GB and 3m. Iirc there was some option to store test results or skip
that. In fact you can see some circle jobs have it while others are missing it.
I'll try to pin it down.
Jenkins looks good. If the comment I added to the PR gets addressed I think
work on the rest of the branches can start.
> CircleCI: Skip checkstyle in the Ant-based repeated tests
> -
>
> Key: CASSANDRA-18000
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18000
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>
> The CircleCI jobs for repeating Ant-based tests include the {{checkstyle}}
> and {{checkstyle-test}} targets. Those targets are skipped for Java 11 but
> not for Java 8.
> Including those targets on every test iteration produces a significant
> difference in the run times of repeated test jobs for j8 and j11:
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/122d58b9-b454-4a99-8c46-fb7ef225/jobs/23225]
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/50f33d9b-c7c6-4aa9-bac9-22ac78ad6b8c/jobs/23224]
> We should use the {{no-checkstyle}} flag in the iterations done by those
> jobs. That should significantly speed up the jobs and save resources.
>
> Thanks to [~bereng] , who detected the difference in the running times
> between j8 and j11.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.1 updated (1d1866b86d -> 756aeed1f4)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 1d1866b86d Merge branch 'cassandra-4.0' into cassandra-4.1 new bba519501c add python2-dev to build-deps new e0331f631e Merge branch 'cassandra-2.2' into cassandra-3.0 new b82dca6f81 Merge branch 'cassandra-3.0' into cassandra-3.11 new 8f06ec372e Merge branch 'cassandra-3.11' into cassandra-4.0 new 756aeed1f4 Merge branch 'cassandra-4.0' into cassandra-4.1 The 5 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.1' into trunk
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 7278db376e8b933e5ae67ecb7c8b8c7ce5a263f0 Merge: 6f801d4232 756aeed1f4 Author: Brandon Williams AuthorDate: Thu Nov 3 08:08:49 2022 -0500 Merge branch 'cassandra-4.1' into trunk - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-3.0' into cassandra-3.11
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit b82dca6f81f67994af2e62f4cfd74a74ddbb45ca Merge: 7df905a429 e0331f631e Author: Brandon Williams AuthorDate: Thu Nov 3 08:07:57 2022 -0500 Merge branch 'cassandra-3.0' into cassandra-3.11 - 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-2.2' into cassandra-3.0
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-3.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit e0331f631e419d82977d94b561cac2411860f279 Merge: 116ce3bc05 bba519501c Author: Brandon Williams AuthorDate: Thu Nov 3 08:07:29 2022 -0500 Merge branch 'cassandra-2.2' into cassandra-3.0 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-3.0 updated (116ce3bc05 -> e0331f631e)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch cassandra-3.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 116ce3bc05 CircleCI: Add jobs for missing specialized unit tests new bba519501c add python2-dev to build-deps new e0331f631e Merge branch 'cassandra-2.2' into cassandra-3.0 The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-2.2 updated: add python2-dev to build-deps
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-2.2 in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/cassandra-2.2 by this push: new bba519501c add python2-dev to build-deps bba519501c is described below commit bba519501cbc7f47577fd7ba4d08969ff8e1d90c Author: Brandon Williams AuthorDate: Wed Aug 31 13:30:31 2022 -0500 add python2-dev to build-deps Patch by brandonwilliams; reviewed by edimitrova for CASSANDRA-17871 --- debian/control | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/control b/debian/control index 95c3c07970..e94057aefd 100644 --- a/debian/control +++ b/debian/control @@ -3,7 +3,7 @@ Section: misc Priority: extra Maintainer: Eric Evans Uploaders: Sylvain Lebresne -Build-Depends: debhelper (>= 5), openjdk-8-jdk | java8-jdk, ant (>= 1.9), ant-optional (>= 1.9), dh-python, python-dev (>= 2.7), dpatch, bash-completion +Build-Depends: debhelper (>= 5), openjdk-8-jdk | java8-jdk, ant (>= 1.9), ant-optional (>= 1.9), dh-python, python-dev (>= 2.7) | python2-dev (>= 2.7), dpatch, bash-completion Homepage: http://cassandra.apache.org Vcs-Git: http://git-wip-us.apache.org/repos/asf/cassandra.git Vcs-Browser: https://git-wip-us.apache.org/repos/asf?p=cassandra.git - 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 (6152cb08db -> 8f06ec372e)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 6152cb08db Merge branch 'cassandra-3.11' into cassandra-4.0 new bba519501c add python2-dev to build-deps new e0331f631e Merge branch 'cassandra-2.2' into cassandra-3.0 new b82dca6f81 Merge branch 'cassandra-3.0' into cassandra-3.11 new 8f06ec372e Merge branch 'cassandra-3.11' into cassandra-4.0 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: - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (6f801d4232 -> 7278db376e)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 6f801d4232 Merge branch 'cassandra-4.1' into trunk new bba519501c add python2-dev to build-deps new e0331f631e Merge branch 'cassandra-2.2' into cassandra-3.0 new b82dca6f81 Merge branch 'cassandra-3.0' into cassandra-3.11 new 8f06ec372e Merge branch 'cassandra-3.11' into cassandra-4.0 new 756aeed1f4 Merge branch 'cassandra-4.0' into cassandra-4.1 new 7278db376e Merge branch 'cassandra-4.1' into trunk The 6 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.0' into cassandra-4.1
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 756aeed1f4cf70ae2515da1914c9892b6ac08cd9 Merge: 1d1866b86d 8f06ec372e Author: Brandon Williams AuthorDate: Thu Nov 3 08:08:39 2022 -0500 Merge branch 'cassandra-4.0' into cassandra-4.1 - 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 (7df905a429 -> b82dca6f81)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 7df905a429 Merge branch 'cassandra-3.0' into cassandra-3.11 new bba519501c add python2-dev to build-deps new e0331f631e Merge branch 'cassandra-2.2' into cassandra-3.0 new b82dca6f81 Merge branch 'cassandra-3.0' into cassandra-3.11 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: - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-3.11' into cassandra-4.0
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 8f06ec372e20c55b85a083e43aa3b8e0993b648d Merge: 6152cb08db b82dca6f81 Author: Brandon Williams AuthorDate: Thu Nov 3 08:08:27 2022 -0500 Merge branch 'cassandra-3.11' into cassandra-4.0 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18000) CircleCI: Skip checkstyle in the Ant-based repeated tests
[
https://issues.apache.org/jira/browse/CASSANDRA-18000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628322#comment-17628322
]
Andres de la Peña commented on CASSANDRA-18000:
---
{quote}In the spirit of removing unnecessary steps we should also remove the
'Downloading previous tests results' for multiplexed circle jobs as these can
hide massive downloads, consume time and are unnecessary. Wdyt?
{quote}
That step is automatically added by CircleCI. I don't know if or how we can
disable it. But for reference, [this massive
run|https://app.circleci.com/pipelines/github/adelapena/cassandra/2387/workflows/c713a919-330f-49c3-a8ab-e55aa9966bac/jobs/23722/parallel-runs/2]
with 50K iterations and a run time of 3h has downloaded the results of [this
other previous
run|https://app.circleci.com/pipelines/github/adelapena/cassandra/2387/workflows/c713a919-330f-49c3-a8ab-e55aa9966bac/jobs/23686],
of the same size, and it has only downloaded 7.5MiB in a reported time of 0s.
{quote}Will this only go to trunk?
{quote}
No, this is for all branches. I've only prepared a brunch for trunk to get some
feedback/validation for the approach. I'll prepare the patches for the other
branches and post them in a bit. I don't expect big differences in those
branches.
> CircleCI: Skip checkstyle in the Ant-based repeated tests
> -
>
> Key: CASSANDRA-18000
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18000
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>
> The CircleCI jobs for repeating Ant-based tests include the {{checkstyle}}
> and {{checkstyle-test}} targets. Those targets are skipped for Java 11 but
> not for Java 8.
> Including those targets on every test iteration produces a significant
> difference in the run times of repeated test jobs for j8 and j11:
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/122d58b9-b454-4a99-8c46-fb7ef225/jobs/23225]
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/50f33d9b-c7c6-4aa9-bac9-22ac78ad6b8c/jobs/23224]
> We should use the {{no-checkstyle}} flag in the iterations done by those
> jobs. That should significantly speed up the jobs and save resources.
>
> Thanks to [~bereng] , who detected the difference in the running times
> between j8 and j11.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17912) Fix CircleCI config for running Python upgrade tests on 3.0 and 3.11
[ https://issues.apache.org/jira/browse/CASSANDRA-17912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628311#comment-17628311 ] Andres de la Peña commented on CASSANDRA-17912: --- Just committed CASSANDRA-17987. > Fix CircleCI config for running Python upgrade tests on 3.0 and 3.11 > > > Key: CASSANDRA-17912 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17912 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 3.0.x, 3.11.x > > > It was noticed that Circle CI pushes to run irrelevant for 3.0 and 3.11 > Python upgrade tests. Those are properly skipped in Jenkins. > Example runs: > [CircleCI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1931/workflows/39ef5261-a6bf-4e77-a412-e750e322a231/jobs/15293] > - 3.0 run > [Jenkins|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/] > - while typing this I actually noticed [one > test|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/testReport/junit/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_parallel_upgrade_with_internode_ssl/] > only looking suspicious in Jenkins as it ends the upgrade in 3.11 when we > test 3.0... > This is good to be fixed for two reasons - reduce the noise so we do not miss > legit failures and we should not spend resources to try to run those tests. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17999) Bug fix for WriteTimeoutException when using Paxos v2 in LWT performance test
[ https://issues.apache.org/jira/browse/CASSANDRA-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628297#comment-17628297 ] Marianne Lyne Manaog commented on CASSANDRA-17999: -- Hi [~dcapwell], please note I have added a new PR for Cassandra 4.1.0 as per these links: [dtest|https://github.com/apache/cassandra/pull/1966] and [bug fix|https://github.com/apache/cassandra/pull/1967] > Bug fix for WriteTimeoutException when using Paxos v2 in LWT performance test > - > > Key: CASSANDRA-17999 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17999 > Project: Cassandra > Issue Type: Bug > Components: Feature/Lightweight Transactions >Reporter: Marianne Lyne Manaog >Assignee: Marianne Lyne Manaog >Priority: Normal > Time Spent: 50m > Remaining Estimate: 0h > > A WriteTimeoutException is encountered when using Paxos v2 in > an LWT performance test that only has a single datacenter because Paxos was > still waiting for a response from another datacenter during the > Commit/Acknowledge phase even though we were running with LOCAL_SERIAL. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17928) Test Failure: org.apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest.testCommitLogInitWithException-compression
[
https://issues.apache.org/jira/browse/CASSANDRA-17928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628296#comment-17628296
]
Benedict Elliott Smith commented on CASSANDRA-17928:
So it is not expressly discussed in that ticket, but AFAICT there is no reason
to invoke {{Thread.stop}} in the JVMKiller. Since the real JVMKiller does not
invoke Thread.stop this cannot be a critical part of the test. So a simple
condition that is signalled by the JVMKiller, that the test waits on for some
predetermined period (perhaps 10s) to confirm the JVMKiller has been invoked
seems sufficient.
However, it might be nice to confirm with the original authors [~gzh1992n],
[~djoshi], [~jwest]
> Test Failure:
> org.apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest.testCommitLogInitWithException-compression
> -
>
> Key: CASSANDRA-17928
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17928
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.1-rc
>
>
> [Link|https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/org.apache.cassandra.db.commitlog/CommitLogInitWithExceptionTest/testCommitLogInitWithException_compression/]
> Failed 1 times in the last 14 runs. Flakiness: 7%, Stability: 92%
> Stacktrace
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest.testCommitLogInitWithException(CommitLogInitWithExceptionTest.java:93)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at java.base/java.lang.Thread.run(Thread.java:829)
> {code}
> {code:java}
> Standard Output
> INFO [main] 2022-09-25 11:43:16,512 Reflections.java:219 - Reflections took
> 1221 ms to scan 8 urls, producing 1756 keys and 6922 values
> INFO [main] 2022-09-25 11:43:17,480 Reflections.java:219 - Reflections took
> 907 ms to scan 8 urls, producing 1756 keys and 6922 values
> INFO [main] 2022-09-25 11:43:17,573 YamlConfigurationLoader.java:104 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2022-09-25 11:43:17,574 YamlConfigurationLoader
> ...[truncated 35568 chars]...
> .apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest$MockCommitLogSegmentMgr.createSegment(CommitLogInitWithExceptionTest.java:106)
> at
> org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager$AllocatorRunnable.run(AbstractCommitLogSegmentManager.java:155)
> at
> org.apache.cassandra.concurrent.InfiniteLoopExecutor.loop(InfiniteLoopExecutor.java:121)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17987) CircleCI: Add jobs for running specialized unit tests with Java 11
[ https://issues.apache.org/jira/browse/CASSANDRA-17987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña updated CASSANDRA-17987: -- Fix Version/s: 3.0.29 3.11.15 4.0.8 4.1-beta2 4.2 Source Control Link: https://github.com/apache/cassandra/commit/116ce3bc0562f69e698f569db0904debd9f87cd0 Resolution: Fixed Status: Resolved (was: Ready to Commit) > CircleCI: Add jobs for running specialized unit tests with Java 11 > -- > > Key: CASSANDRA-17987 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17987 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Andres de la Peña >Assignee: Andres de la Peña >Priority: Normal > Fix For: 3.0.29, 3.11.15, 4.0.8, 4.1-beta2, 4.2 > > > CircleCI has a set of jobs for running specialiazed unit tests that are only > run with Java 8: > * utests_compression > * utests_system_keyspace_directory > * utests_trie > * utests_stress > * utests_long > * utests_fqltool > It should probably be possible to run these tests with Java 11 tool. > Rather than creating a ticket for every job, it's probably easier to use a > single ticket for all of them. This should give us an overall vision for > deciding job names, approval steps, etc. Also, the required config changes > should be quite minimal and doing all of them at once should save us both > effort and test runs. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17987) CircleCI: Add jobs for running specialized unit tests with Java 11
[ https://issues.apache.org/jira/browse/CASSANDRA-17987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628285#comment-17628285 ] Andres de la Peña commented on CASSANDRA-17987: --- Thanks, committed to 3.0 as [116ce3bc0562f69e698f569db0904debd9f87cd0|https://github.com/apache/cassandra/commit/116ce3bc0562f69e698f569db0904debd9f87cd0] and merged to [3.11|https://github.com/apache/cassandra/commit/7df905a4293af692b793b9364f2011f1c0a3a0d9], [4.0|https://github.com/apache/cassandra/commit/6152cb08dba770f46496d84cde067c6776c66fa0], [4.1|https://github.com/apache/cassandra/commit/1d1866b86d524bcaf10cd9d5f547c9ca57a184c6] and [trunk|https://github.com/apache/cassandra/commit/6f801d42324e24cc6a57274b57705e724501eb98]. > CircleCI: Add jobs for running specialized unit tests with Java 11 > -- > > Key: CASSANDRA-17987 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17987 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Andres de la Peña >Assignee: Andres de la Peña >Priority: Normal > > CircleCI has a set of jobs for running specialiazed unit tests that are only > run with Java 8: > * utests_compression > * utests_system_keyspace_directory > * utests_trie > * utests_stress > * utests_long > * utests_fqltool > It should probably be possible to run these tests with Java 11 tool. > Rather than creating a ticket for every job, it's probably easier to use a > single ticket for all of them. This should give us an overall vision for > deciding job names, approval steps, etc. Also, the required config changes > should be quite minimal and doing all of them at once should save us both > effort and test runs. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (0bde8a2e20 -> 6f801d4232)
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 0bde8a2e20 Fix BootstrapTest failure on vnodes new 116ce3bc05 CircleCI: Add jobs for missing specialized unit tests new 7df905a429 Merge branch 'cassandra-3.0' into cassandra-3.11 new 6152cb08db Merge branch 'cassandra-3.11' into cassandra-4.0 new 1d1866b86d Merge branch 'cassandra-4.0' into cassandra-4.1 new 6f801d4232 Merge branch 'cassandra-4.1' into trunk The 5 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .circleci/config-2_1.yml| 621 - .circleci/config-2_1.yml.high_res.patch | 13 +- .circleci/config-2_1.yml.mid_res.patch | 39 +- .circleci/config.yml| 4431 -- .circleci/config.yml.HIGHRES| 4541 ++- .circleci/config.yml.LOWRES | 4537 +- .circleci/config.yml.MIDRES | 4451 +- .circleci/generate.sh | 21 +- 8 files changed, 13188 insertions(+), 5466 deletions(-) - 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 (deede44af5 -> 7df905a429)
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 deede44af5 Merge branch 'cassandra-3.0' into cassandra-3.11 new 116ce3bc05 CircleCI: Add jobs for missing specialized unit tests new 7df905a429 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: .circleci/config-2_1.yml| 70 -- .circleci/config-2_1.yml.high_res.patch | 6 +- .circleci/config-2_1.yml.mid_res.patch | 12 +- .circleci/config.yml| 403 +-- .circleci/config.yml.HIGHRES| 413 ++-- .circleci/config.yml.LOWRES | 413 ++-- .circleci/config.yml.MIDRES | 413 ++-- .circleci/generate.sh | 1 + 8 files changed, 1606 insertions(+), 125 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.1 updated (b7ef579703 -> 1d1866b86d)
This is an automated email from the ASF dual-hosted git repository. adelapena pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from b7ef579703 Merge branch 'cassandra-4.0' into cassandra-4.1 new 116ce3bc05 CircleCI: Add jobs for missing specialized unit tests new 7df905a429 Merge branch 'cassandra-3.0' into cassandra-3.11 new 6152cb08db Merge branch 'cassandra-3.11' into cassandra-4.0 new 1d1866b86d Merge branch 'cassandra-4.0' into cassandra-4.1 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: .circleci/config-2_1.yml| 541 - .circleci/config-2_1.yml.high_res.patch | 13 +- .circleci/config-2_1.yml.mid_res.patch | 39 +- .circleci/config.yml| 3315 +++ .circleci/config.yml.HIGHRES| 3709 +- .circleci/config.yml.LOWRES | 3703 +- .circleci/config.yml.MIDRES | 3713 ++- .circleci/generate.sh | 18 +- 8 files changed, 10865 insertions(+), 4186 deletions(-) - 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: CircleCI: Add jobs for missing specialized unit tests
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 116ce3bc05 CircleCI: Add jobs for missing specialized unit tests
116ce3bc05 is described below
commit 116ce3bc0562f69e698f569db0904debd9f87cd0
Author: Andrés de la Peña
AuthorDate: Thu Nov 3 11:30:38 2022 +
CircleCI: Add jobs for missing specialized unit tests
Fix run_repeated_utests for non-testsome targets
patch by Andrés de la Peña; reviewed by Ekaterina Dimitrova and Berenguer
Blasi for CASSANDRA-17987
---
.circleci/config-2_1.yml | 13 +++--
.circleci/config.yml | 65 ++--
.circleci/config.yml.HIGHRES | 65 ++--
.circleci/config.yml.LOWRES | 65 ++--
.circleci/config.yml.MIDRES | 65 ++--
5 files changed, 210 insertions(+), 63 deletions(-)
diff --git a/.circleci/config-2_1.yml b/.circleci/config-2_1.yml
index 0b22f29349..48bce92a3a 100644
--- a/.circleci/config-2_1.yml
+++ b/.circleci/config-2_1.yml
@@ -1004,6 +1004,13 @@ commands:
# Put manually specified tests and automatically detected tests
together, removing duplicates
tests=$(echo <> | sed -e "s///" | sed -e
"s/ //" | tr "," "\n" | tr " " "\n" | sort -n | uniq -u)
echo "Tests to be repeated: ${tests}"
+
+# Prepare the testtag for the target, used by the test macro in
build.xml to group the output files
+target=<>
+testtag=""
+if [[ $target == "test-compression" ]]; then
+ testtag="compression"
+fi
# Run each test class as many times as requested.
exit_code="$?"
@@ -1031,7 +1038,7 @@ commands:
fi
# Prepare the -Dtest.methods argument, which is optional
-if [ $method == "" ]; then
+if [[ $method == "" ]]; then
methods_arg=""
else
methods_arg="-Dtest.methods=$method"
@@ -1056,7 +1063,7 @@ commands:
mv stdout.txt $dest/${test}.txt
# move the XML output files
- source=build/test/output
+ source=build/test/output/${testtag}
dest=/tmp/results/repeated_utests/output/${status}/${i}
mkdir -p $dest
if [[ -d $source && -n "$(ls $source)" ]]; then
@@ -1064,7 +1071,7 @@ commands:
fi
# move the log files
- source=build/test/logs
+ source=build/test/logs/${testtag}
dest=/tmp/results/repeated_utests/logs/${status}/${i}
mkdir -p $dest
if [[ -d $source && -n "$(ls $source)" ]]; then
diff --git a/.circleci/config.yml b/.circleci/config.yml
index 43a507ba9f..84da5cfb0a 100644
--- a/.circleci/config.yml
+++ b/.circleci/config.yml
@@ -181,6 +181,13 @@ jobs:
tests=$(echo ${REPEATED_UTESTS} | sed -e "s///" | sed -e "s/
//" | tr "," "\n" | tr " " "\n" | sort -n | uniq -u)
echo "Tests to be repeated: ${tests}"
+ # Prepare the testtag for the target, used by the test macro in
build.xml to group the output files
+ target=test-compression
+ testtag=""
+ if [[ $target == "test-compression" ]]; then
+testtag="compression"
+ fi
+
# Run each test class as many times as requested.
exit_code="$?"
for test in $tests; do
@@ -207,7 +214,7 @@ jobs:
fi
# Prepare the -Dtest.methods argument, which is optional
- if [ $method == "" ]; then
+ if [[ $method == "" ]]; then
methods_arg=""
else
methods_arg="-Dtest.methods=$method"
@@ -232,7 +239,7 @@ jobs:
mv stdout.txt $dest/${test}.txt
# move the XML output files
-source=build/test/output
+source=build/test/output/${testtag}
dest=/tmp/results/repeated_utests/output/${status}/${i}
mkdir -p $dest
if [[ -d $source && -n "$(ls $source)" ]]; then
@@ -240,7 +247,7 @@ jobs:
fi
# move the log files
-source=build/test/logs
+source=build/test/logs/${testtag}
dest=/tmp/results/repeated_utests/logs/${status}/${i}
mkdir -p $dest
if [[ -d $source && -n "$(ls $source)" ]]; then
@@ -353,6 +360,13 @@ jobs:
tests=$(echo ${REPEATED_UTESTS_LONG} | sed -e "s///" | sed -e
"s/ //" | tr "," "\n" |
[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 7df905a4293af692b793b9364f2011f1c0a3a0d9
Merge: deede44af5 116ce3bc05
Author: Andrés de la Peña
AuthorDate: Thu Nov 3 11:36:22 2022 +
Merge branch 'cassandra-3.0' into cassandra-3.11
.circleci/config-2_1.yml| 70 --
.circleci/config-2_1.yml.high_res.patch | 6 +-
.circleci/config-2_1.yml.mid_res.patch | 12 +-
.circleci/config.yml| 403 +--
.circleci/config.yml.HIGHRES| 413 ++--
.circleci/config.yml.LOWRES | 413 ++--
.circleci/config.yml.MIDRES | 413 ++--
.circleci/generate.sh | 1 +
8 files changed, 1606 insertions(+), 125 deletions(-)
diff --cc .circleci/config-2_1.yml
index c3703d699d,48bce92a3a..92dd98d332
--- a/.circleci/config-2_1.yml
+++ b/.circleci/config-2_1.yml
@@@ -109,7 -101,7 +109,6 @@@ default_env_vars: _env_var
# REPEATED_ANT_TEST_TARGET: test-jvm-dtest-some
# REPEATED_ANT_TEST_TARGET: test-cdc
# REPEATED_ANT_TEST_TARGET: test-compression
--# REPEATED_ANT_TEST_TARGET: test-system-keyspace-directory
REPEATED_ANT_TEST_TARGET: testsome
# The name of JUnit class to be run multiple times, for example:
# REPEATED_ANT_TEST_CLASS: org.apache.cassandra.cql3.ViewTest
@@@ -199,7 -191,7 +198,7 @@@ separate_jobs: _job
requires:
- start_j8_jvm_dtests_repeat
- build
--# specialized unit tests (all run using Java 8)
++# specialized unit tests (all run on request)
- start_utests_long:
type: approval
- utests_long:
@@@ -212,6 -204,6 +211,18 @@@
requires:
- start_utests_long_repeat
- build
++- start_utests_cdc:
++type: approval
++- utests_cdc:
++requires:
++ - start_utests_cdc
++ - build
++- start_utests_cdc_repeat:
++type: approval
++- utests_cdc_repeat:
++requires:
++ - start_utests_cdc_repeat
++ - build
- start_utests_compression:
type: approval
- utests_compression:
@@@ -320,7 -301,7 +331,7 @@@ pre-commit_jobs: _job
- j8_jvm_dtests_repeat:
requires:
- build
--# specialized unit tests (all run on request using Java 8)
++# specialized unit tests (all run on request)
- start_utests_long:
type: approval
- utests_long:
@@@ -331,6 -312,6 +342,16 @@@
requires:
- start_utests_long
- build
++- start_utests_cdc:
++type: approval
++- utests_cdc:
++requires:
++ - start_utests_cdc
++ - build
++- utests_cdc_repeat:
++requires:
++ - start_utests_cdc
++ - build
- start_utests_compression:
type: approval
- utests_compression:
@@@ -481,6 -448,6 +502,16 @@@ jobs
- run_junit_tests:
target: long-test
++ utests_cdc:
++<<: *j8_par_executor
++steps:
++ - attach_workspace:
++ at: /home/cassandra
++ - create_junit_containers
++ - log_environment
++ - run_parallel_junit_tests:
++ target: testclasslist-cdc
++
utests_compression:
<<: *j8_par_executor
steps:
@@@ -552,21 -511,21 +583,21 @@@
- log_environment
- run_unit_tests_repeat
-- utests_compression_repeat:
++ utests_cdc_repeat:
<<: *j8_repeated_utest_executor
steps:
- attach_workspace:
at: /home/cassandra
- log_environment
-- - run_utests_compression_repeat
++ - run_utests_cdc_repeat
-- utests_system_keyspace_directory_repeat:
++ utests_compression_repeat:
<<: *j8_repeated_utest_executor
steps:
- attach_workspace:
at: /home/cassandra
- log_environment
-- - run_utests_system_keyspace_directory_repeat
++ - run_utests_compression_repeat
utests_long_repeat:
<<: *j8_repeated_utest_executor
@@@ -984,18 -932,18 +1015,18 @@@ commands
count: ${REPEATED_UTESTS_COUNT}
stop_on_failure: ${REPEATED_TESTS_STOP_ON_FAILURE}
-- run_utests_compression_repeat:
++ run_utests_cdc_repeat:
steps:
- run_repeated_utests:
-- target: test-compression
++ target: test-cdc
tests: ${REPEATED_UTESTS}
count: ${REPEATED_UTESTS_COUNT}
stop_on_failure: ${REPEATED_TESTS_STOP_ON_FAILURE}
-- run_utests_system_keyspace_directory_repeat:
++ run_utests_compression_repeat:
steps:
- run_repeated_utests:
-- target: test-system-keyspace-directory
++ target: test-compression
tests: ${REPEATED_UTESTS}
count:
[cassandra] branch cassandra-4.0 updated (0db0b8f781 -> 6152cb08db)
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 0db0b8f781 Update NetBeans project file for dependency changes since 7th July 2021 new 116ce3bc05 CircleCI: Add jobs for missing specialized unit tests new 7df905a429 Merge branch 'cassandra-3.0' into cassandra-3.11 new 6152cb08db 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: .circleci/config-2_1.yml| 539 ++- .circleci/config-2_1.yml.high_res.patch | 13 +- .circleci/config-2_1.yml.mid_res.patch | 49 +- .circleci/config.yml| 5913 +-- .circleci/config.yml.HIGHRES| 5499 .circleci/config.yml.LOWRES | 5501 .circleci/config.yml.MIDRES | 5493 .circleci/generate.sh | 17 +- 8 files changed, 16443 insertions(+), 6581 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
