[cassandra-website] branch asf-staging updated (9a496617 -> bf3ad100)

[git-site-role]

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 9a496617 generate docs for 521906f9
 new bf3ad100 generate docs for 521906f9

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   (9a496617)
\
 N -- N -- N   refs/heads/asf-staging (bf3ad100)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17836) WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"

[Erick Ramirez (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17582249#comment-17582249
 ] 

Erick Ramirez commented on CASSANDRA-17836:
---

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 9a496617 generate docs for 521906f9

$ git push -f origin asf-site
Username for ‘https://github.com’: erickramirezau
Password for ‘https://erickramire...@github.com’: 
Total 0 (delta 0), reused 0 (delta 0) 
To https://github.com/apache/cassandra-website.git
 + bc24893c...9a496617 asf-site -> asf-site (forced update)
{noformat}
The blog post is now live on the site – 
https://cassandra.apache.org/_/blog/Apache-Cassandra-Changelog-18-August-2022.html

> WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"
> ---
>
> Key: CASSANDRA-17836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17836
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
>  Labels: pull-request-available
> Fix For: 4.0.x
>
> Attachments: CASSANDRA-17836v2.patch, c17836-01-blog-index.png, 
> c17836-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the July 2022 
> blog "Apache Cassandra Changelog #18"
> If this blog cannot be published by the *August 19, 2022 publish date*, 
> please contact me, suggest changes, or correct the date when possible in the 
> pull request for the appropriate time that the blog will go live (on both the 
> blog.adoc and the blog post's file).



--
This message was sent by Atlassian Jira
(v8.20.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 (bc24893c -> 9a496617)

[erickramirezau]

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 bc24893c generate docs for b1be68c0
 add 521906f9 BLOG - Apache Cassandra Changelog #18
 add 9a496617 generate docs for 521906f9

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   (bc24893c)
\
 N -- N -- N   refs/heads/asf-site (9a496617)

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:
 ...he-cassandra-4.x-cassandra-world-party-2022.jpg | Bin 0 -> 72233 bytes
 content/_/blog.html|  24 
 ...Apache-Cassandra-Changelog-18-August-2022.html} | 112 ++
 content/search-index.js|   2 +-
 ...he-cassandra-4.x-cassandra-world-party-2022.jpg | Bin 0 -> 72233 bytes
 site-content/source/modules/ROOT/pages/blog.adoc   |  25 
 .../Apache-Cassandra-Changelog-18-August-2022.adoc | 126 +
 site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078 
bytes
 8 files changed, 241 insertions(+), 48 deletions(-)
 create mode 100644 
content/_/_images/blog/what-is-netflix-waiting-for-in-apache-cassandra-4.x-cassandra-world-party-2022.jpg
 copy content/_/blog/{Apache-Cassandra-Changelog-17-July-2022.html => 
Apache-Cassandra-Changelog-18-August-2022.html} (59%)
 create mode 100644 
site-content/source/modules/ROOT/images/blog/what-is-netflix-waiting-for-in-apache-cassandra-4.x-cassandra-world-party-2022.jpg
 create mode 100644 
site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-18-August-2022.adoc


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17836) WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"

[Erick Ramirez (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17582248#comment-17582248
 ] 

Erick Ramirez commented on CASSANDRA-17836:
---

The blog post is now in staging – 
https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-Changelog-18-August-2022.html

> WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"
> ---
>
> Key: CASSANDRA-17836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17836
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
>  Labels: pull-request-available
> Fix For: 4.0.x
>
> Attachments: CASSANDRA-17836v2.patch, c17836-01-blog-index.png, 
> c17836-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the July 2022 
> blog "Apache Cassandra Changelog #18"
> If this blog cannot be published by the *August 19, 2022 publish date*, 
> please contact me, suggest changes, or correct the date when possible in the 
> pull request for the appropriate time that the blog will go live (on both the 
> blog.adoc and the blog post's file).



--
This message was sent by Atlassian Jira
(v8.20.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 (8fb75274 -> 9a496617)

[git-site-role]

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 8fb75274 generate docs for b1be68c0
 add 521906f9 BLOG - Apache Cassandra Changelog #18
 new 9a496617 generate docs for 521906f9

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   (8fb75274)
\
 N -- N -- N   refs/heads/asf-staging (9a496617)

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:
 ...he-cassandra-4.x-cassandra-world-party-2022.jpg | Bin 0 -> 72233 bytes
 content/_/blog.html|  24 
 ...Apache-Cassandra-Changelog-18-August-2022.html} | 112 ++
 content/search-index.js|   2 +-
 ...he-cassandra-4.x-cassandra-world-party-2022.jpg | Bin 0 -> 72233 bytes
 site-content/source/modules/ROOT/pages/blog.adoc   |  25 
 .../Apache-Cassandra-Changelog-18-August-2022.adoc | 126 +
 site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078 
bytes
 8 files changed, 241 insertions(+), 48 deletions(-)
 create mode 100644 
content/_/_images/blog/what-is-netflix-waiting-for-in-apache-cassandra-4.x-cassandra-world-party-2022.jpg
 copy content/_/blog/{Apache-Cassandra-Changelog-17-July-2022.html => 
Apache-Cassandra-Changelog-18-August-2022.html} (59%)
 create mode 100644 
site-content/source/modules/ROOT/images/blog/what-is-netflix-waiting-for-in-apache-cassandra-4.x-cassandra-world-party-2022.jpg
 create mode 100644 
site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-18-August-2022.adoc


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17836) WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"

[Erick Ramirez (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17582245#comment-17582245
 ] 

Erick Ramirez commented on CASSANDRA-17836:
---

The website content is getting built in staging:

||Branch||PR||Commit||Build||
|{{trunk}}|[#166|https://github.com/apache/cassandra-website/pull/166]|[521906f 
|https://github.com/apache/cassandra-website/commit/521906f97ce6b3925b69b572b69e74ec46f4883e]|[#537|https://ci-cassandra.apache.org/job/cassandra-website/537/]|

> WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"
> ---
>
> Key: CASSANDRA-17836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17836
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
>  Labels: pull-request-available
> Fix For: 4.0.x
>
> Attachments: CASSANDRA-17836v2.patch, c17836-01-blog-index.png, 
> c17836-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the July 2022 
> blog "Apache Cassandra Changelog #18"
> If this blog cannot be published by the *August 19, 2022 publish date*, 
> please contact me, suggest changes, or correct the date when possible in the 
> pull request for the appropriate time that the blog will go live (on both the 
> blog.adoc and the blog post's file).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17836) WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17836:
--
  Fix Version/s: 4.0.x
Source Control Link: 
https://github.com/apache/cassandra-website/commit/521906f97ce6b3925b69b572b69e74ec46f4883e
 Resolution: Fixed
 Status: Resolved  (was: Ready to Commit)

h2. Committed
||Branch||PR||Commit||
|{{trunk}}|[#166|https://github.com/apache/cassandra-website/pull/166]|[521906f 
|https://github.com/apache/cassandra-website/commit/521906f97ce6b3925b69b572b69e74ec46f4883e]|

> WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"
> ---
>
> Key: CASSANDRA-17836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17836
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
>  Labels: pull-request-available
> Fix For: 4.0.x
>
> Attachments: CASSANDRA-17836v2.patch, c17836-01-blog-index.png, 
> c17836-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the July 2022 
> blog "Apache Cassandra Changelog #18"
> If this blog cannot be published by the *August 19, 2022 publish date*, 
> please contact me, suggest changes, or correct the date when possible in the 
> pull request for the appropriate time that the blog will go live (on both the 
> blog.adoc and the blog post's file).



--
This message was sent by Atlassian Jira
(v8.20.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 - Apache Cassandra Changelog #18

[erickramirezau]

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 521906f9 BLOG - Apache Cassandra Changelog #18
521906f9 is described below

commit 521906f97ce6b3925b69b572b69e74ec46f4883e
Author: Diogenese Topper 
AuthorDate: Thu Aug 18 18:37:58 2022 -0700

BLOG - Apache Cassandra Changelog #18

patch by Chris Thornett, Diogenese Topper; reviewed by Erick Ramirez for 
CASSANDRA-17836

Co-authored by: Chris Thornett 
Co-authored by: Diogenese Topper 
---
 ...he-cassandra-4.x-cassandra-world-party-2022.jpg | Bin 0 -> 72233 bytes
 site-content/source/modules/ROOT/pages/blog.adoc   |  25 
 .../Apache-Cassandra-Changelog-18-August-2022.adoc | 126 +
 3 files changed, 151 insertions(+)

diff --git 
a/site-content/source/modules/ROOT/images/blog/what-is-netflix-waiting-for-in-apache-cassandra-4.x-cassandra-world-party-2022.jpg
 
b/site-content/source/modules/ROOT/images/blog/what-is-netflix-waiting-for-in-apache-cassandra-4.x-cassandra-world-party-2022.jpg
new file mode 100644
index ..5bec4c52
Binary files /dev/null and 
b/site-content/source/modules/ROOT/images/blog/what-is-netflix-waiting-for-in-apache-cassandra-4.x-cassandra-world-party-2022.jpg
 differ
diff --git a/site-content/source/modules/ROOT/pages/blog.adoc 
b/site-content/source/modules/ROOT/pages/blog.adoc
index 78d39a1e..2820f57b 100644
--- a/site-content/source/modules/ROOT/pages/blog.adoc
+++ b/site-content/source/modules/ROOT/pages/blog.adoc
@@ -8,6 +8,31 @@ 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 #18
+[discrete]
+ August 19, 2022
+--
+[openblock,card-content]
+--
+Cassandra 4.0.5 is released, we say thank you to everyone for their help on 
Cassandra World Party and to Nate McCall, who is stepping down as PMC Chair.
+
+[openblock,card-btn card-btn--blog]
+
+
+[.btn.btn--alt]
+xref:blog/Apache-Cassandra-Changelog-18-August-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-18-August-2022.adoc
 
b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-18-August-2022.adoc
new file mode 100644
index ..b04f4a70
--- /dev/null
+++ 
b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-18-August-2022.adoc
@@ -0,0 +1,126 @@
+= Apache Cassandra Changelog #18
+:page-layout: single-post
+:page-role: blog-post
+:page-post-date: August 19, 2022
+:page-post-author: Chris Thornett
+:description: Apache Cassandra Changelog
+:keywords: Cassandra, changelog, updates, news, release notes, community,
+
+image::blog/changelog_header.jpg[Apache Cassandra Changelog]
+Our monthly roundup of key activities and knowledge to keep the community 
informed.
+
+== Release Notes
+
+=== Released
+
+The latest release of Apache Cassandra is 
https://www.apache.org/dyn/closer.lua/cassandra/4.0.5/apache-cassandra-4.0.5-bin.tar.gz[4.0.5^]
 
(https://downloads.apache.org/cassandra/4.0.5/apache-cassandra-4.0.5-bin.tar.gz.asc[pgp^],
 
https://downloads.apache.org/cassandra/4.0.5/apache-cassandra-4.0.5-bin.tar.gz.sha256[sha256^],
 
https://downloads.apache.org/cassandra/4.0.5/apache-cassandra-4.0.5-bin.tar.gz.sha512[sha512^]),
 which we announced on 18 August 2022. Crucially, this release contains [...]
+
+While this is the Changelog highlight activities for July, we want to 
acknowledge the CentOS 7 issue, which will be resolved in Apache Cassandra 
4.0.6. This will soon be out and will re-add support for CentOS 7.
+
+Please read the 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0.5[4.0.5
 release notes^] and let us know if you encounter any problems.
+
+Our focus remains on the tickets that block the beta release and release 
candidate for Apache Cassandra 4.1. We have only a handful of unassigned 
tickets left and these would be a great introduction for someone new to 
contributing to the project (see details, below, on how to help).
+
+The other supported releases remain Apache Cassandra 3.11 
(https://www.apache.org/dyn/closer.lua/cassandra/3.11.13/apache-cassandra-3.11.13-bin.tar.gz[3.11.13^],
 
https://downloads.apache.org/cassandra/3.11.13/apache-cassandra-3.11.13-bin.tar.gz.asc[pgp^],
 
https://downloads.apache.org/cassandra/3.11.13/apache-cassandra-3.11.13-bin.tar.gz.sha256[sha256^],
 
https://downloads.apache.org/cassandra/3.11.13/apache-cassandra-3.11.13-bin.tar.gz.sha512[sha512^])
 and 3.0 series (https://www.apache.o [...]
+
+Please read the release notes for 

[jira] [Updated] (CASSANDRA-17836) WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17836:
--
Status: Ready to Commit  (was: Changes Suggested)

h2. Ready to commit

I've made the necessary changes so the PR is ready to commit. Details in  
[^CASSANDRA-17836v2.patch].

 !c17836-01-blog-index.png|width=300!
 !c17836-02-blog-post.png|width=300! 

> WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"
> ---
>
> Key: CASSANDRA-17836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17836
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
>  Labels: pull-request-available
> Attachments: CASSANDRA-17836v2.patch, c17836-01-blog-index.png, 
> c17836-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the July 2022 
> blog "Apache Cassandra Changelog #18"
> If this blog cannot be published by the *August 19, 2022 publish date*, 
> please contact me, suggest changes, or correct the date when possible in the 
> pull request for the appropriate time that the blog will go live (on both the 
> blog.adoc and the blog post's file).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17836) WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17836:
--
Attachment: c17836-02-blog-post.png
c17836-01-blog-index.png

> WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"
> ---
>
> Key: CASSANDRA-17836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17836
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
>  Labels: pull-request-available
> Attachments: CASSANDRA-17836v2.patch, c17836-01-blog-index.png, 
> c17836-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the July 2022 
> blog "Apache Cassandra Changelog #18"
> If this blog cannot be published by the *August 19, 2022 publish date*, 
> please contact me, suggest changes, or correct the date when possible in the 
> pull request for the appropriate time that the blog will go live (on both the 
> blog.adoc and the blog post's file).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17836) WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17836:
--
Attachment: CASSANDRA-17836v2.patch

> WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"
> ---
>
> Key: CASSANDRA-17836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17836
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
>  Labels: pull-request-available
> Attachments: CASSANDRA-17836v2.patch
>
>
> This ticket is to capture the work associated with publishing the July 2022 
> blog "Apache Cassandra Changelog #18"
> If this blog cannot be published by the *August 19, 2022 publish date*, 
> please contact me, suggest changes, or correct the date when possible in the 
> pull request for the appropriate time that the blog will go live (on both the 
> blog.adoc and the blog post's file).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17836) WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17836:
--
Status: Changes Suggested  (was: Review In Progress)

h2. Suggested changes

h3. In {{pages/blog.adoc}}

* The version number in the card summary has an extra dot:

bq. Cassandra {color:#DE350B}4..0.5{color} is released, we say thank you to 
everyone for their help on Cassandra World Party and to Nate McCall, who is 
stepping down as PMC Chair.

h3. In {{pagesblog/Apache-Cassandra-Changelog-18-August-2022.adoc}}

* Dot notation of version numbers in the *Release Notes* section are either 
missing a dot or has a redundant dot.
* Incorrect link to *architecture overview* doc:

bq. We would also recommend reading the [overview of the C* 
architecture|xref:doc/latest/cassandra/architecture/overview.adoc].

* Use of "conversion" instead of "conversation" in:

bq. The {color:#DE350B}conversion{color} covers Apache Cassandra’s role in 
powering your entertainment and Jeff’s experience of supporting Cassandra at a 
global scale.

* Remove link to register for World Party:

bq. Last Chance to Register: Schedule & Moderators Announced - Cassandra 
Community

> WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"
> ---
>
> Key: CASSANDRA-17836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17836
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
>  Labels: pull-request-available
>
> This ticket is to capture the work associated with publishing the July 2022 
> blog "Apache Cassandra Changelog #18"
> If this blog cannot be published by the *August 19, 2022 publish date*, 
> please contact me, suggest changes, or correct the date when possible in the 
> pull request for the appropriate time that the blog will go live (on both the 
> blog.adoc and the blog post's file).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17836) WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17836:
--
Authors: Chris Thornett, Diogenese Topper  (was: Erick Ramirez)

> WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"
> ---
>
> Key: CASSANDRA-17836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17836
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
>  Labels: pull-request-available
>
> This ticket is to capture the work associated with publishing the July 2022 
> blog "Apache Cassandra Changelog #18"
> If this blog cannot be published by the *August 19, 2022 publish date*, 
> please contact me, suggest changes, or correct the date when possible in the 
> pull request for the appropriate time that the blog will go live (on both the 
> blog.adoc and the blog post's file).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Assigned] (CASSANDRA-17836) WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez reassigned CASSANDRA-17836:
-

 Authors: Chris Thornett, Diogenese Topper
Assignee: Erick Ramirez

> WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"
> ---
>
> Key: CASSANDRA-17836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17836
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
>  Labels: pull-request-available
>
> This ticket is to capture the work associated with publishing the July 2022 
> blog "Apache Cassandra Changelog #18"
> If this blog cannot be published by the *August 19, 2022 publish date*, 
> please contact me, suggest changes, or correct the date when possible in the 
> pull request for the appropriate time that the blog will go live (on both the 
> blog.adoc and the blog post's file).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17836) WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17836:
--
Reviewers: Erick Ramirez
   Status: Review In Progress  (was: Patch Available)

> WEBSITE - August 2022 blog "Apache Cassandra Changelog #18"
> ---
>
> Key: CASSANDRA-17836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17836
> 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 July 2022 
> blog "Apache Cassandra Changelog #18"
> If this blog cannot be published by the *August 19, 2022 publish date*, 
> please contact me, suggest changes, or correct the date when possible in the 
> pull request for the appropriate time that the blog will go live (on both the 
> blog.adoc and the blog post's file).



--
This message was sent by Atlassian Jira
(v8.20.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-17843) Fix test/distributed/org/apache/cassandra/distributed/test/IncRepairCoordinatorErrorTest

[Stefan Miklosovic (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17582216#comment-17582216
 ] 

Stefan Miklosovic edited comment on CASSANDRA-17843 at 8/20/22 1:11 PM:


trunk: [https://github.com/apache/cassandra/pull/1803]

4.1 [https://github.com/apache/cassandra/pull/1802]

build trunk: 
[https://app.circleci.com/pipelines/github/instaclustr/cassandra/1222/workflows/283f03b5-702a-47a0-8a8f-f3eec1351524]

build 4.1: 
[https://app.circleci.com/pipelines/github/instaclustr/cassandra/1220/workflows/c15b13a6-1d58-444a-a8f0-6e278ce2b616]


was (Author: smiklosovic):
trunk: [https://github.com/apache/cassandra/pull/1803]

4.1 [https://github.com/apache/cassandra/pull/1802]

build trunk: 
[https://app.circleci.com/pipelines/github/instaclustr/cassandra?branch=CASSANDRA-17843-trunk]

build 4.1: 
[https://app.circleci.com/pipelines/github/instaclustr/cassandra?branch=CASSANDRA-17843]

> Fix 
> test/distributed/org/apache/cassandra/distributed/test/IncRepairCoordinatorErrorTest
> 
>
> Key: CASSANDRA-17843
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17843
> Project: Cassandra
>  Issue Type: Bug
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.1-beta, 4.1.x, 4.x
>
>
> test/distributed/org/apache/cassandra/distributed/test/IncRepairCoordinatorErrorTest
> needs to be fixed on 4.1 and trunk
> [https://app.circleci.com/pipelines/github/yifan-c/cassandra/394/workflows/0079ce49-a851-4bf9-b6cd-3f9b76e9667c/jobs/3786/tests#failed-test-0]
> {code:java}
> java.lang.ClassCastException: class org.apache.cassandra.utils.TimeUUID 
> cannot be cast to class java.util.UUID (org.apache.cassandra.utils.TimeUUID 
> is in unnamed module of loader 'app'; java.util.UUID is in module java.base 
> of loader 'bootstrap') at 
> org.apache.cassandra.distributed.test.IncRepairCoordinatorErrorTest.errorTest(IncRepairCoordinatorErrorTest.java:50)
>  at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method) at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43){code}



--
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-17843) Fix test/distributed/org/apache/cassandra/distributed/test/IncRepairCoordinatorErrorTest

[Stefan Miklosovic (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-17843:
--
Test and Documentation Plan: fixed jvm dtest test
 Status: Patch Available  (was: In Progress)

> Fix 
> test/distributed/org/apache/cassandra/distributed/test/IncRepairCoordinatorErrorTest
> 
>
> Key: CASSANDRA-17843
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17843
> Project: Cassandra
>  Issue Type: Bug
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.1-beta, 4.1.x, 4.x
>
>
> test/distributed/org/apache/cassandra/distributed/test/IncRepairCoordinatorErrorTest
> needs to be fixed on 4.1 and trunk
> [https://app.circleci.com/pipelines/github/yifan-c/cassandra/394/workflows/0079ce49-a851-4bf9-b6cd-3f9b76e9667c/jobs/3786/tests#failed-test-0]
> {code:java}
> java.lang.ClassCastException: class org.apache.cassandra.utils.TimeUUID 
> cannot be cast to class java.util.UUID (org.apache.cassandra.utils.TimeUUID 
> is in unnamed module of loader 'app'; java.util.UUID is in module java.base 
> of loader 'bootstrap') at 
> org.apache.cassandra.distributed.test.IncRepairCoordinatorErrorTest.errorTest(IncRepairCoordinatorErrorTest.java:50)
>  at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method) at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43){code}



--
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-17843) Fix test/distributed/org/apache/cassandra/distributed/test/IncRepairCoordinatorErrorTest

[Stefan Miklosovic (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17582216#comment-17582216
 ] 

Stefan Miklosovic commented on CASSANDRA-17843:
---

trunk: [https://github.com/apache/cassandra/pull/1803]

4.1 [https://github.com/apache/cassandra/pull/1802]

build trunk: 
[https://app.circleci.com/pipelines/github/instaclustr/cassandra?branch=CASSANDRA-17843-trunk]

build 4.1: 
[https://app.circleci.com/pipelines/github/instaclustr/cassandra?branch=CASSANDRA-17843]

> Fix 
> test/distributed/org/apache/cassandra/distributed/test/IncRepairCoordinatorErrorTest
> 
>
> Key: CASSANDRA-17843
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17843
> Project: Cassandra
>  Issue Type: Bug
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.1-beta, 4.1.x, 4.x
>
>
> test/distributed/org/apache/cassandra/distributed/test/IncRepairCoordinatorErrorTest
> needs to be fixed on 4.1 and trunk
> [https://app.circleci.com/pipelines/github/yifan-c/cassandra/394/workflows/0079ce49-a851-4bf9-b6cd-3f9b76e9667c/jobs/3786/tests#failed-test-0]
> {code:java}
> java.lang.ClassCastException: class org.apache.cassandra.utils.TimeUUID 
> cannot be cast to class java.util.UUID (org.apache.cassandra.utils.TimeUUID 
> is in unnamed module of loader 'app'; java.util.UUID is in module java.base 
> of loader 'bootstrap') at 
> org.apache.cassandra.distributed.test.IncRepairCoordinatorErrorTest.errorTest(IncRepairCoordinatorErrorTest.java:50)
>  at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method) at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43){code}



--
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-17843) Fix test/distributed/org/apache/cassandra/distributed/test/IncRepairCoordinatorErrorTest

[Stefan Miklosovic (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic reassigned CASSANDRA-17843:
-

Assignee: Stefan Miklosovic

> Fix 
> test/distributed/org/apache/cassandra/distributed/test/IncRepairCoordinatorErrorTest
> 
>
> Key: CASSANDRA-17843
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17843
> Project: Cassandra
>  Issue Type: Bug
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.1-beta, 4.1.x, 4.x
>
>
> test/distributed/org/apache/cassandra/distributed/test/IncRepairCoordinatorErrorTest
> needs to be fixed on 4.1 and trunk
> [https://app.circleci.com/pipelines/github/yifan-c/cassandra/394/workflows/0079ce49-a851-4bf9-b6cd-3f9b76e9667c/jobs/3786/tests#failed-test-0]
> {code:java}
> java.lang.ClassCastException: class org.apache.cassandra.utils.TimeUUID 
> cannot be cast to class java.util.UUID (org.apache.cassandra.utils.TimeUUID 
> is in unnamed module of loader 'app'; java.util.UUID is in module java.base 
> of loader 'bootstrap') at 
> org.apache.cassandra.distributed.test.IncRepairCoordinatorErrorTest.errorTest(IncRepairCoordinatorErrorTest.java:50)
>  at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method) at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43){code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-13010) nodetool compactionstats should say which disk a compaction is writing to

[Stefan Miklosovic (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-13010:
--
Status: Ready to Commit  (was: Review In Progress)

> nodetool compactionstats should say which disk a compaction is writing to
> -
>
> Key: CASSANDRA-13010
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13010
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Local/Compaction, Tool/nodetool
>Reporter: Jon Haddad
>Assignee: Stefan Miklosovic
>Priority: Normal
>  Labels: 4.0-feature-freeze-review-requested
> Fix For: 4.x
>
> Attachments: cleanup.png, multiple operations.png
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-13010) nodetool compactionstats should say which disk a compaction is writing to

[Stefan Miklosovic (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-13010:
--
  Fix Version/s: 4.2
 (was: 4.x)
Source Control Link: 
https://github.com/apache/cassandra/commit/e7c9ac05f99cc8a5ee958169c49326e85ab4b25b
 Resolution: Fixed
 Status: Resolved  (was: Ready to Commit)

> nodetool compactionstats should say which disk a compaction is writing to
> -
>
> Key: CASSANDRA-13010
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13010
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Local/Compaction, Tool/nodetool
>Reporter: Jon Haddad
>Assignee: Stefan Miklosovic
>Priority: Normal
>  Labels: 4.0-feature-freeze-review-requested
> Fix For: 4.2
>
> Attachments: cleanup.png, multiple operations.png
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
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 (c4b1c0614e -> e7c9ac05f9)

[smiklosovic]

This is an automated email from the ASF dual-hosted git repository.

smiklosovic pushed a change to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git


from c4b1c0614e Read/Write/Truncate throw RequestFailure in a race 
condition with callback timeouts, should return Timeout instead
 add e7c9ac05f9 Introduce target directory to vtable output for 
sstable_tasks and for compactionstats

No new revisions were added by this update.

Summary of changes:
 CHANGES.txt|   1 +
 .../apache/cassandra/cache/AutoSavingCache.java|   3 +-
 .../cassandra/db/compaction/CompactionInfo.java|  52 ++--
 .../db/compaction/CompactionIterator.java  |  12 +-
 .../cassandra/db/compaction/CompactionManager.java |   4 +
 .../cassandra/db/compaction/CompactionTask.java|   1 +
 .../apache/cassandra/db/compaction/Scrubber.java   |   4 +-
 .../apache/cassandra/db/compaction/Upgrader.java   |   1 +
 .../compaction/writers/CompactionAwareWriter.java  |  11 +-
 .../writers/DefaultCompactionWriter.java   |   2 +
 .../writers/MajorLeveledCompactionWriter.java  |   3 +-
 .../compaction/writers/MaxSSTableSizeWriter.java   |   1 -
 .../SplittingSizeTieredCompactionWriter.java   |   6 +-
 .../cassandra/db/virtual/SSTableTasksTable.java|   5 +-
 .../cassandra/index/sasi/SASIIndexBuilder.java |   7 +-
 .../cassandra/tools/nodetool/CompactionStats.java  |   9 +-
 .../db/lifecycle/RealTransactionsTest.java |   1 +
 .../db/virtual/SSTableTasksTableTest.java  |   7 +-
 .../tools/nodetool/CompactionStatsTest.java| 146 +
 19 files changed, 193 insertions(+), 83 deletions(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17461) Test Failure: org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation

[Benedict Elliott Smith (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17582186#comment-17582186
 ] 

Benedict Elliott Smith commented on CASSANDRA-17461:


bq. other tests still hit CAS timeouts

Some of these at least are probably similar situations to this test. I will try 
to take a look at these, but probably not until the end of the coming week or 
so.

> Test Failure: 
> org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
> -
>
> Key: CASSANDRA-17461
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17461
> Project: Cassandra
>  Issue Type: Bug
>  Components: Test/dtest/java
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.1-beta, 4.x
>
>
> Intermittent failures on {{org.apache.cassandra.distributed.test.CASTest}} 
> for trunk:
> * 
> [testConflictingWritesWithStaleRingInformation|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.distributed.test/CASTest/testConflictingWritesWithStaleRingInformation_3/]
> * 
> [testSuccessfulWriteBeforeRangeMovement|https://ci-cassandra.apache.org/job/Cassandra-trunk/1025/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteBeforeRangeMovement/]
> * 
> [testSuccessfulWriteDuringRangeMovementFollowedByConflicting|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteDuringRangeMovementFollowedByConflicting/]
> * 
> [testSucccessfulWriteDuringRangeMovementFollowedByRead|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSucccessfulWriteDuringRangeMovementFollowedByRead/]
> All four seem to have the same aspect:
> {code}
> Failed 2 times in the last 5 runs. Flakiness: 50%, Stability: 60%
> Error Message
> CAS operation timed out: received 1 of 2 required responses after 0 
> contention retries
> Stacktrace
> org.apache.cassandra.exceptions.CasWriteTimeoutException: CAS operation timed 
> out: received 1 of 2 required responses after 0 contention retries
>   at 
> org.apache.cassandra.service.paxos.Paxos$MaybeFailure.markAndThrowAsTimeoutOrFailure(Paxos.java:547)
>   at org.apache.cassandra.service.paxos.Paxos.begin(Paxos.java:1048)
>   at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:659)
>   at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:618)
>   at org.apache.cassandra.service.StorageProxy.cas(StorageProxy.java:307)
>   at 
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithCondition(ModificationStatement.java:500)
>   at 
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:467)
>   at 
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
>   at 
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
>   at 
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
>   at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:47)
>   at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:57)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>   at 
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
>   at java.base/java.lang.Thread.run(Thread.java:829)
> Standard Output
> DEBUG [main] 2022-03-19 16:20:42,868 Reflections.java:198 - going to scan 
> these urls: 
> [jar:file:/home/cassandra/cassandra/build/apache-cassandra-4.1-SNAPSHOT.jar!/,
>  
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/simulator-bootstrap.jar!/,
>  
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/dtest-api-0.0.12.jar!/,
>  file:/home/cassandra/cassandra/build/classes/fqltool/, 
> file:/home/cassandra/cassandra/build/test/classes/, 
> file:/home/cassandra/cassandra/build/classes/main/, file:/home/cass
> ...[truncated 4929659 chars]...
> gService.java:519 - Waiting for messaging service to quiesce
> INFO  [node1_isolatedExecutor:10] 2022-03-19 16:21:55,223 
> SubstituteLogger.java:169 - INFO  [node1_isolatedExecutor:10] node1 
> 2022-03-19 16:21:55,221 MessagingService.java:519 - Waiting for messaging 
> service to quiesce
> INFO  [node2_isolatedExecutor:8] 2022-03-19 16:21:55,223 
> SubstituteLogger.java:169 - INFO  [node2_isolatedExecutor:8] node2 2022-03-19 
> 16:21:55,222 MessagingService.java:519 - Waiting for messaging service to 

[cassandra-website] branch asf-staging updated (bc24893c -> 8fb75274)

[git-site-role]

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 bc24893c generate docs for b1be68c0
 new 8fb75274 generate docs for b1be68c0

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   (bc24893c)
\
 N -- N -- N   refs/heads/asf-staging (8fb75274)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17599) Update how_to_commit documentation with lost updates from in-tree repo

[Michael Semb Wever (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17582177#comment-17582177
 ] 

Michael Semb Wever commented on CASSANDRA-17599:


is live.

> Update how_to_commit documentation with lost updates from in-tree repo
> --
>
> Key: CASSANDRA-17599
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17599
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation
>Reporter: Michael Semb Wever
>Assignee: Claude Warren
>Priority: Normal
>  Labels: pull-request-available
> Fix For: NA
>
> Attachments: how_to_commit.patch
>
>
> When the 
> [how_to_commit.rst|https://github.com/apache/cassandra/blob/1fce84f9833bd62227dbf8f5d063935457dbc18e/doc/source/development/how_to_commit.rst]
>  page got migrated and moved to the 
> [cassandra-website|https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc]
>  repo, new edits were not carried over. 
> cassandra-website/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc
>  
> needs to be updated so it reads like 
> https://github.com/apache/cassandra/blob/1fce84f9833bd62227dbf8f5d063935457dbc18e/doc/source/development/how_to_commit.rst
> It should also be updated to include latest release branches (ref: 
> CASSANDRA-17589 )



--
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 (08728742 -> bc24893c)

[mck]

This is an automated email from the ASF dual-hosted git repository.

mck pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git


 discard 08728742 generate docs for 8f277185
 add 11349c1a Fix broken link to "existing documents" in 
development/documentation.html
 add b1be68c0 Update how_to_commit documentation with lost updates from 
in-tree repo
 add bc24893c generate docs for b1be68c0

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   (08728742)
\
 N -- N -- N   refs/heads/asf-site (bc24893c)

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/_/development/documentation.html   |   4 +-
 content/_/development/how_to_commit.html   | 317 +---
 content/_/development/index.html   | 318 ++---
 .../cassandra/configuration}/configuration.html|  71 +++--
 content/doc/4.1/cassandra/new/index.html   |   3 +
 .../doc/4.1/cassandra/operating/bulk_loading.html  |  18 +-
 .../4.1/cassandra/tools/sstable/sstableloader.html |  25 +-
 .../cassandra/configuration}/configuration.html|  69 +++--
 content/doc/4.2/cassandra/new/index.html   |   3 +
 .../doc/4.2/cassandra/operating/bulk_loading.html  |  18 +-
 .../4.2/cassandra/tools/nodetool/profileload.html  |  18 +-
 .../cassandra/tools/nodetool/toppartitions.html|  18 +-
 .../4.2/cassandra/tools/sstable/sstableloader.html |  25 +-
 .../cassandra/configuration}/configuration.html|  71 +++--
 content/doc/latest/cassandra/new/index.html|   3 +
 .../latest/cassandra/operating/bulk_loading.html   |  18 +-
 .../cassandra/tools/sstable/sstableloader.html |  25 +-
 .../cassandra/configuration}/configuration.html|  69 +++--
 content/doc/trunk/cassandra/new/index.html |   3 +
 .../trunk/cassandra/operating/bulk_loading.html|  18 +-
 .../cassandra/tools/nodetool/profileload.html  |  18 +-
 .../cassandra/tools/nodetool/toppartitions.html|  18 +-
 .../cassandra/tools/sstable/sstableloader.html |  25 +-
 content/search-index.js|   2 +-
 .../ROOT/pages/development/documentation.adoc  |   5 +-
 .../ROOT/pages/development/how_to_commit.adoc  | 187 +---
 site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078 
bytes
 27 files changed, 1130 insertions(+), 239 deletions(-)
 rename content/doc/{latest/cassandra/new => 
4.1/cassandra/configuration}/configuration.html (96%)
 rename content/doc/{trunk/cassandra/new => 
4.2/cassandra/configuration}/configuration.html (96%)
 rename content/doc/{4.1/cassandra/new => 
latest/cassandra/configuration}/configuration.html (96%)
 rename content/doc/{4.2/cassandra/new => 
trunk/cassandra/configuration}/configuration.html (96%)


-
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 (ec673ed8 -> bc24893c)

[git-site-role]

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 ec673ed8 generate docs for 11349c1a
 add b1be68c0 Update how_to_commit documentation with lost updates from 
in-tree repo
 new bc24893c generate docs for b1be68c0

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   (ec673ed8)
\
 N -- N -- N   refs/heads/asf-staging (bc24893c)

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/_/development/how_to_commit.html   | 317 ++---
 content/_/development/index.html   | 314 +---
 content/search-index.js|   2 +-
 .../ROOT/pages/development/how_to_commit.adoc  | 187 +---
 site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078 
bytes
 5 files changed, 693 insertions(+), 127 deletions(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Assigned] (CASSANDRA-17599) Update how_to_commit documentation with lost updates from in-tree repo

[Michael Semb Wever (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Semb Wever reassigned CASSANDRA-17599:
--

  Fix Version/s: NA
  Reviewers: Michael Semb Wever
Source Control Link: 
https://github.com/apache/cassandra-website/commit/b1be68c0d9b9e610dd14315c9d42044fe62ec910
   Assignee: Claude Warren

> Update how_to_commit documentation with lost updates from in-tree repo
> --
>
> Key: CASSANDRA-17599
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17599
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation
>Reporter: Michael Semb Wever
>Assignee: Claude Warren
>Priority: Normal
>  Labels: pull-request-available
> Fix For: NA
>
> Attachments: how_to_commit.patch
>
>
> When the 
> [how_to_commit.rst|https://github.com/apache/cassandra/blob/1fce84f9833bd62227dbf8f5d063935457dbc18e/doc/source/development/how_to_commit.rst]
>  page got migrated and moved to the 
> [cassandra-website|https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc]
>  repo, new edits were not carried over. 
> cassandra-website/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc
>  
> needs to be updated so it reads like 
> https://github.com/apache/cassandra/blob/1fce84f9833bd62227dbf8f5d063935457dbc18e/doc/source/development/how_to_commit.rst
> It should also be updated to include latest release branches (ref: 
> CASSANDRA-17589 )



--
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-17599) Update how_to_commit documentation with lost updates from in-tree repo

[Michael Semb Wever (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Semb Wever updated CASSANDRA-17599:
---
Resolution: Fixed
Status: Resolved  (was: Open)

Committed as 
[b1be68c0d9b9e610dd14315c9d42044fe62ec910|https://github.com/apache/cassandra-website/commit/b1be68c0d9b9e610dd14315c9d42044fe62ec910].

Thanks [~claude]! This was tripping a number of new contributors up, fantastic 
to have this page back in its updated form.

> Update how_to_commit documentation with lost updates from in-tree repo
> --
>
> Key: CASSANDRA-17599
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17599
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation
>Reporter: Michael Semb Wever
>Priority: Normal
>  Labels: pull-request-available
> Attachments: how_to_commit.patch
>
>
> When the 
> [how_to_commit.rst|https://github.com/apache/cassandra/blob/1fce84f9833bd62227dbf8f5d063935457dbc18e/doc/source/development/how_to_commit.rst]
>  page got migrated and moved to the 
> [cassandra-website|https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc]
>  repo, new edits were not carried over. 
> cassandra-website/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc
>  
> needs to be updated so it reads like 
> https://github.com/apache/cassandra/blob/1fce84f9833bd62227dbf8f5d063935457dbc18e/doc/source/development/how_to_commit.rst
> It should also be updated to include latest release branches (ref: 
> CASSANDRA-17589 )



--
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: Update how_to_commit documentation with lost updates from in-tree repo

[mck]

This is an automated email from the ASF dual-hosted git repository.

mck pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git


The following commit(s) were added to refs/heads/trunk by this push:
 new b1be68c0 Update how_to_commit documentation with lost updates from 
in-tree repo
b1be68c0 is described below

commit b1be68c0d9b9e610dd14315c9d42044fe62ec910
Author: Claude Warren, Jr 
AuthorDate: Tue Aug 16 07:59:14 2022 +0100

Update how_to_commit documentation with lost updates from in-tree repo

Updates were made to the in-tree version of this page that were not 
included to the rewrite from rst to adoc

 patch by Claude Warren; reviewed by Mick Semb Wever for CASSANDRA-17599
---
 .../ROOT/pages/development/how_to_commit.adoc  | 187 -
 1 file changed, 145 insertions(+), 42 deletions(-)

diff --git 
a/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc 
b/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc
index 5a9cf5a7..319a4f0e 100644
--- a/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc
+++ b/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc
@@ -1,63 +1,156 @@
 :page-layout: basic
 
-== How-to Commit
+= How-to Commit
 
 If you are a committer, feel free to pick any process that works for you
 - so long as you are planning to commit the work yourself.
 
-Here is how committing and merging typically look for merging and
-pushing for tickets that follow the convention (if patch-based).
-A hypothetical CASSANDRA-12345 ticket used in the example is a cassandra-3.0
-based bug fix that requires different code for cassandra-3.3, and trunk.
-Contributor Jackie is supplying a patch for the root branch (12345-3.0.patch),
-and patches for the remaining branches (12345-3.3.patch, 12345-trunk.patch).
+== Patch based Contribution
+
+Here is how committing and merging will usually look for merging and
+pushing for tickets that follow the convention (if patch-based):
+
+Hypothetical CASSANDRA-12345 ticket is a cassandra-3.0 based bug fix
+that requires different code for cassandra-3.11, cassandra-4.0, and
+trunk. Contributor Jackie supplied a patch for the root branch
+(12345-3.0.patch), and patches for the remaining branches
+(12345-3.11.patch, 12345-4.0.patch, 12345-trunk.patch).
 
 On cassandra-3.0:::
-  . `git am -3 12345-3.0.patch` (if we have a problem b/c of CHANGES.txt
-  not merging anymore, we modify it ourselves, in place)
-On cassandra-3.3:::
-  . `git merge cassandra-3.0 -s ours`
-  . `git apply -3 12345-3.3.patch` (likely to have an issue with
-  CHANGES.txt here: modify it ourselves, then `git add CHANGES.txt`)
-  . `git commit -amend`
+  . `+git am -3 12345-3.0.patch+` (any problem b/c of CHANGES.txt not
+  merging anymore, fix it in place)
+  . `+ant realclean && ant jar build-test+` (rebuild to make sure code
+  compiles)
+On cassandra-3.11:::
+  . `+git merge cassandra-3.0 -s ours+`
+  . `+git apply -3 12345-3.11.patch+` (any issue with CHANGES.txt : fix
+  and [.title-ref]#git add CHANGES.txt#)
+  . `+ant realclean && ant jar build-test+` (rebuild to make sure code
+  compiles)
+  . `+git commit --amend+` (Notice this will squash the 3.11 applied
+  patch into the forward merge commit)
+On cassandra-4.0:::
+  . `+git merge cassandra-3.11 -s ours+`
+  . `+git apply -3 12345-4.0.patch+` (any issue with CHANGES.txt : fix
+  and [.title-ref]#git add CHANGES.txt#)
+  . `+ant realclean && ant jar build-test+` (rebuild to make sure code
+  compiles)
+  . `+git commit --amend+` (Notice this will squash the 4.0 applied
+  patch into the forward merge commit)
 On trunk:::
-  . `git merge cassandra-3.3 -s ours`
-  . `git apply -3 12345-trunk.patch` (likely to have an issue with
-  CHANGES.txt here: modify it ourselves, then `git add CHANGES.txt`)
-  . `git commit -amend`
+  . `+git merge cassandra-4.0 -s ours+`
+  . `+git apply -3 12345-trunk.patch+` (any issue with CHANGES.txt : fix
+  and [.title-ref]#git add CHANGES.txt#)
+  . `+ant realclean && ant jar build-test+` (rebuild to make sure code
+  compiles)
+  . `+git commit --amend+` (Notice this will squash the trunk applied
+  patch into the forward merge commit)
 On any branch:::
-  . `git push origin cassandra-3.0 cassandra-3.3 trunk -atomic`
+  . `+git push origin cassandra-3.0 cassandra-3.11 cassandra-4.0 trunk 
--atomic -n+`
+  (dryrun check)
+  . `+git push origin cassandra-3.0 cassandra-3.11 cassandra-4.0 trunk 
--atomic+`
+
+== Git branch based Contribution
 
 Same scenario, but a branch-based contribution:
 
 On cassandra-3.0:::
-  . `git cherry-pick ` (if we have a problem b/c of
-  CHANGES.txt not merging anymore, we modify it ourselves, in place)
-On cassandra-3.3:::
-  . `git merge cassandra-3.0 -s ours`
-  . `git format-patch -1 `
-  . `git apply -3 .patch` (likely to have an issue
-  with CHANGES.txt here: modify it ourselves, then `git add CHANGES.txt`)
-  . `git 

[jira] [Comment Edited] (CASSANDRA-17753) Include GitSHA in nodetool version output

[Michael Semb Wever (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17579250#comment-17579250
 ] 

Michael Semb Wever edited comment on CASSANDRA-17753 at 8/20/22 7:49 AM:
-

{quote}In -src, this file is excluded: 
[https://github.com/apache/cassandra/blob/a45e70a860e9d68745f463f5a06aa7b870ff69df/build.xml#L1321]
{quote}
That is correct. And you cannot (are not allowed to) put the version.properties 
into the -src tarball.

The -src tarball is a snapshot of our source, from version control from a 
stated SHA, nothing generated or custom added.

It needs to be possible to do {{`tar xvf *-src.tar.gz ; cd apache-cassandra* ; 
ant artifacts`}} without git or the generated version.properties being present.


was (Author: michaelsembwever):
{quote}In -src, this file is excluded: 
[https://github.com/apache/cassandra/blob/a45e70a860e9d68745f463f5a06aa7b870ff69df/build.xml#L1321]
{quote}
That is correct. And you cannot (are not allowed to) put the version.properties 
into the -src tarball.

The -src tarball is a snapshot of our source, from version control from a 
stated SHA, nothing generated or custom added.

It needs to be possible to do {{`tar xvf {*}-src.tar.gz ; cd 
apache-cassandra{*} ; ant artifacts`}} without git or the generated 
version.properties being present.

> Include GitSHA in nodetool version output
> -
>
> Key: CASSANDRA-17753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17753
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Tool/nodetool
>Reporter: Abe Ratnofsky
>Assignee: Abe Ratnofsky
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> It can be useful to see specifically which Git SHA a running instance of 
> Cassandra was built with, especially when running clusters in development for 
> soak testing.
>  
> I have a patch ready for this, and am preparing it now.



--
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-17753) Include GitSHA in nodetool version output

[Michael Semb Wever (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17579250#comment-17579250
 ] 

Michael Semb Wever edited comment on CASSANDRA-17753 at 8/20/22 7:49 AM:
-

{quote}In -src, this file is excluded: 
[https://github.com/apache/cassandra/blob/a45e70a860e9d68745f463f5a06aa7b870ff69df/build.xml#L1321]
{quote}
That is correct. And you cannot (are not allowed to) put the version.properties 
into the -src tarball.

The -src tarball is a snapshot of our source, from version control from a 
stated SHA, nothing generated or custom added.

It needs to be possible to do {{`tar xvf *{*}-src.tar.gz ; cd 
apache-cassandra*{*} ; ant artifacts`}} without git or the generated 
version.properties being present.


was (Author: michaelsembwever):
{quote}In -src, this file is excluded: 
[https://github.com/apache/cassandra/blob/a45e70a860e9d68745f463f5a06aa7b870ff69df/build.xml#L1321]
{quote}
That is correct. And you cannot (are not allowed to) put the version.properties 
into the -src tarball.

The -src tarball is a snapshot of our source, from version control from a 
stated SHA, nothing generated or custom added.

It needs to be possible to do {{`tar xvf *-src.tar.gz ; cd apache-cassandra* ; 
ant artifacts`}} without git or the generated version.properties being present.

> Include GitSHA in nodetool version output
> -
>
> Key: CASSANDRA-17753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17753
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Tool/nodetool
>Reporter: Abe Ratnofsky
>Assignee: Abe Ratnofsky
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> It can be useful to see specifically which Git SHA a running instance of 
> Cassandra was built with, especially when running clusters in development for 
> soak testing.
>  
> I have a patch ready for this, and am preparing it now.



--
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-17753) Include GitSHA in nodetool version output

[Michael Semb Wever (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17579250#comment-17579250
 ] 

Michael Semb Wever edited comment on CASSANDRA-17753 at 8/20/22 7:49 AM:
-

{quote}In -src, this file is excluded: 
[https://github.com/apache/cassandra/blob/a45e70a860e9d68745f463f5a06aa7b870ff69df/build.xml#L1321]
{quote}
That is correct. And you cannot (are not allowed to) put the version.properties 
into the -src tarball.

The -src tarball is a snapshot of our source, from version control from a 
stated SHA, nothing generated or custom added.

It needs to be possible to do {{`tar xvf \*-src.tar.gz ; cd apache-cassandra\* 
; ant artifacts`}} without git or the generated version.properties being 
present.


was (Author: michaelsembwever):
{quote}In -src, this file is excluded: 
[https://github.com/apache/cassandra/blob/a45e70a860e9d68745f463f5a06aa7b870ff69df/build.xml#L1321]
{quote}
That is correct. And you cannot (are not allowed to) put the version.properties 
into the -src tarball.

The -src tarball is a snapshot of our source, from version control from a 
stated SHA, nothing generated or custom added.

It needs to be possible to do {{`tar xvf *-src.tar.gz ; cd apache-cassandra* ; 
ant artifacts`}} without git or the generated version.properties being present.

> Include GitSHA in nodetool version output
> -
>
> Key: CASSANDRA-17753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17753
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Tool/nodetool
>Reporter: Abe Ratnofsky
>Assignee: Abe Ratnofsky
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> It can be useful to see specifically which Git SHA a running instance of 
> Cassandra was built with, especially when running clusters in development for 
> soak testing.
>  
> I have a patch ready for this, and am preparing it now.



--
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-17753) Include GitSHA in nodetool version output

[Michael Semb Wever (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17579250#comment-17579250
 ] 

Michael Semb Wever edited comment on CASSANDRA-17753 at 8/20/22 7:49 AM:
-

{quote}In -src, this file is excluded: 
[https://github.com/apache/cassandra/blob/a45e70a860e9d68745f463f5a06aa7b870ff69df/build.xml#L1321]
{quote}
That is correct. And you cannot (are not allowed to) put the version.properties 
into the -src tarball.

The -src tarball is a snapshot of our source, from version control from a 
stated SHA, nothing generated or custom added.

It needs to be possible to do {{`tar xvf {*}-src.tar.gz ; cd 
apache-cassandra{*} ; ant artifacts`}} without git or the generated 
version.properties being present.


was (Author: michaelsembwever):
{quote}In -src, this file is excluded: 
[https://github.com/apache/cassandra/blob/a45e70a860e9d68745f463f5a06aa7b870ff69df/build.xml#L1321]
{quote}
That is correct. And you cannot (are not allowed to) put the version.properties 
into the -src tarball.

The -src tarball is a snapshot of our source, from version control from a 
stated SHA, nothing generated or custom added.

It needs to be possible to do {{`tar xvf *{*}-src.tar.gz ; cd 
apache-cassandra*{*} ; ant artifacts`}} without git or the generated 
version.properties being present.

> Include GitSHA in nodetool version output
> -
>
> Key: CASSANDRA-17753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17753
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Tool/nodetool
>Reporter: Abe Ratnofsky
>Assignee: Abe Ratnofsky
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> It can be useful to see specifically which Git SHA a running instance of 
> Cassandra was built with, especially when running clusters in development for 
> soak testing.
>  
> I have a patch ready for this, and am preparing it now.



--
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 (f1618fae -> ec673ed8)

[git-site-role]

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 f1618fae generate docs for 11349c1a
 new ec673ed8 generate docs for 11349c1a

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   (f1618fae)
\
 N -- N -- N   refs/heads/asf-staging (ec673ed8)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 content/search-index.js |   2 +-
 site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes
 2 files changed, 1 insertion(+), 1 deletion(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17750) Remove dependency on Maven Ant Tasks

[Michael Semb Wever (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17582158#comment-17582158
 ] 

Michael Semb Wever commented on CASSANDRA-17750:


+1

the patch is against cassandra-4.1, but it looks like we are only going to 
apply this to trunk (i.e. 4.2)

> Remove dependency on Maven Ant Tasks
> 
>
> Key: CASSANDRA-17750
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17750
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Build, Dependencies, Packaging
>Reporter: Abe Ratnofsky
>Assignee: Abe Ratnofsky
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10h
>  Remaining Estimate: 0h
>
> Apache Cassandra depends on Maven Ant Tasks (MAT) during build, for declaring 
> dependencies and generating POM files from within build.xml. MAT has long 
> been retired (no commits since maintenance in 2015), has registered CVEs in 
> dependencies (CVE-2017-1000487), and encourages migration to its successor, 
> Maven Artifact Resolver Ant Tasks (MARAT).
> As part of CASSANDRA-16391 
> , mck migrated 
> dependency resolution to MARAT, but MAT is still included in our build for 
> generating POMs since MARAT does not have an alternative to the writepom task 
> provided by MAT. I have a patch ready that removes MAT completely, with a 
> workaround for POM generation.
> I am not advocating for any kind of migration away from Ant to an alternative 
> like Gradle or Maven, just to be extra clear.



--
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