[jira] [Commented] (CASSANDRA-18705) Create release branch cassandra-5.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751339#comment-17751339
]
Michael Semb Wever commented on CASSANDRA-18705:
For (1), (2) and (2a):
- trunk:
https://github.com/apache/cassandra/compare/trunk...michaelsembwever:cassandra:mck/18705/trunk
- cassandra-5.0:
https://github.com/apache/cassandra/compare/trunk...michaelsembwever:cassandra:mck/18705/5.0
CI
- trunk:
https://app.circleci.com/pipelines/github/michaelsembwever/cassandra?branch=mck%2F18705%2Ftrunk
- 5.0:
https://app.circleci.com/pipelines/github/michaelsembwever/cassandra?branch=mck%2F18705%2F5.0
> Create release branch cassandra-5.0
> ---
>
> Key: CASSANDRA-18705
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18705
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 5.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-5.0 trunk
> git push --set-upstream origin cassandra-5.0
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 5.1
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths, and dtest jar generation (both
> circleci and in-tree scripts)
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> -
> https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> - https://github.com/apache/cassandra/blob/trunk/.build/run-tests.sh#L85
> 3. Add `5.0-alpha`, `5.0-alpha1`, `5.0-beta`, `5.0-rc`, `5.0.x` and `5.1.x`
> to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 5.x to what is appropriate…)
> 4. Update docker images to include cassandra-5.0
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
> -
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
> -
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
> https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc
> 8. Update website CI to trigger off cassandra-5.0 builds
> -
> https://github.com/apache/cassandra-builds/commit/1fc9b5ee71dc37e1145f276ead5c680c6b3fe3db
--
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-18705) Create release branch cassandra-5.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-18705:
---
Description:
Figure out what needs to be done beyond the following…
1. Create release branch
{code}
git switch -c cassandra-5.0 trunk
git push --set-upstream origin cassandra-5.0
{code}
2. Bump trunk's version
{code}
git switch trunk
# increment version to 5.1
edit build.xml debian/changelog CHANGES.txt NEWS.txt
{code}
2a. Update jvm-dtest supported upgrade paths, and dtest jar generation (both
circleci and in-tree scripts)
-
https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
-
https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
- https://github.com/apache/cassandra/blob/trunk/.build/run-tests.sh#L85
3. Add `5.0-alpha`, `5.0-alpha1`, `5.0-beta`, `5.0-rc`, `5.0.x` and `5.1.x` to
jira versions
(no existing tickets will be changed - assignees need to change appropriate
bugs from 5.x to what is appropriate…)
4. Update docker images to include cassandra-5.0
(Docker images also need to be deployed)
5. Add pipeline to ci-cassandra
https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
6. Add dtest version and upgrade paths
-
https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
-
https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
7. Update how_to_commit documentation
https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc
8. Update website CI to trigger off cassandra-5.0 builds
-
https://github.com/apache/cassandra-builds/commit/1fc9b5ee71dc37e1145f276ead5c680c6b3fe3db
was:
Figure out what needs to be done beyond the following…
1. Create release branch
{code}
git switch -c cassandra-5.0 trunk
git push --set-upstream origin cassandra-5.0
{code}
2. Bump trunk's version
{code}
git switch trunk
# increment version to 5.1
edit build.xml debian/changelog CHANGES.txt NEWS.txt
{code}
2a. Update jvm-dtest supported upgrade paths, and circleci dtest jar generation
-
https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
-
https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
3. Add `5.0-alpha`, `5.0-alpha1`, `5.0-beta`, `5.0-rc`, `5.0.x` and `5.1.x` to
jira versions
(no existing tickets will be changed - assignees need to change appropriate
bugs from 5.x to what is appropriate…)
4. Update docker images to include cassandra-5.0
(Docker images also need to be deployed)
5. Add pipeline to ci-cassandra
https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
6. Add dtest version and upgrade paths
-
https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
-
https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
7. Update how_to_commit documentation
https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc
> Create release branch cassandra-5.0
> ---
>
> Key: CASSANDRA-18705
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18705
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 5.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-5.0 trunk
> git push --set-upstream origin cassandra-5.0
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 5.1
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths, and dtest jar generation (both
> circleci and in-tree scripts)
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> -
> https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> - https://github.com/apache/cassandra/blob/trunk/.build/run-tests.sh#L85
> 3. Add `5.0-alpha`, `5.0-alpha1`, `5.0-beta`, `5.0-rc`, `5.0.x` and `5.1.x`
> to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 5.x to what is appropriate…)
> 4. Update docker images to include cassandra-5.0
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6.
[jira] [Updated] (CASSANDRA-18705) Create release branch cassandra-5.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-18705:
---
Description:
Figure out what needs to be done beyond the following…
1. Create release branch
{code}
git switch -c cassandra-5.0 trunk
git push --set-upstream origin cassandra-5.0
{code}
2. Bump trunk's version
{code}
git switch trunk
# increment version to 5.1
edit build.xml debian/changelog CHANGES.txt NEWS.txt
{code}
2a. Update jvm-dtest supported upgrade paths, and circleci dtest jar generation
-
https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
-
https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
3. Add `5.0-alpha`, `5.0-alpha1`, `5.0-beta`, `5.0-rc`, `5.0.x` and `5.1.x` to
jira versions
(no existing tickets will be changed - assignees need to change appropriate
bugs from 5.x to what is appropriate…)
4. Update docker images to include cassandra-5.0
(Docker images also need to be deployed)
5. Add pipeline to ci-cassandra
https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
6. Add dtest version and upgrade paths
-
https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
-
https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
7. Update how_to_commit documentation
https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc
was:
Figure out what needs to be done beyond the following…
1. Create release branch
{code}
git switch -c cassandra-5.0 trunk
git push --set-upstream origin cassandra-5.0
{code}
2. Bump trunk's version
{code}
git switch trunk
# increment version to 5.1
edit build.xml debian/changelog CHANGES.txt NEWS.txt
{code}
2a. Update jvm-dtest supported upgrade paths, and circleci dtest jar generation
-
https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
-
https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
3. Add `5.0-alpha`, `5.0-alpha1`, `5.0-beta`, `5.0-rc`, `5.0.x` and `5.1.x` to
jira versions
(no existing tickets will be changed - assignees need to change appropriate
bugs from 5.x to what is appropriate…)
4. Update docker images to include cassandra-5.0
(Docker images also need to be deployed)
5. Add pipeline to ci-cassandra
https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
6. Add dtest version and upgrade paths
-
https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
-
https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
7. Update how_to_commit documentation
https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
> Create release branch cassandra-5.0
> ---
>
> Key: CASSANDRA-18705
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18705
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 5.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-5.0 trunk
> git push --set-upstream origin cassandra-5.0
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 5.1
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths, and circleci dtest jar
> generation
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> -
> https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> 3. Add `5.0-alpha`, `5.0-alpha1`, `5.0-beta`, `5.0-rc`, `5.0.x` and `5.1.x`
> to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 5.x to what is appropriate…)
> 4. Update docker images to include cassandra-5.0
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
> -
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
> -
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
>
[jira] [Updated] (CASSANDRA-18705) Create release branch cassandra-5.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-18705:
---
Description:
Figure out what needs to be done beyond the following…
1. Create release branch
{code}
git switch -c cassandra-5.0 trunk
git push --set-upstream origin cassandra-5.0
{code}
2. Bump trunk's version
{code}
git switch trunk
# increment version to 5.1
edit build.xml debian/changelog CHANGES.txt NEWS.txt
{code}
2a. Update jvm-dtest supported upgrade paths, and circleci dtest jar generation
-
https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
-
https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
3. Add `5.0-alpha`, `5.0-alpha1`, `5.0-beta`, `5.0-rc`, `5.0.x` and `5.1.x` to
jira versions
(no existing tickets will be changed - assignees need to change appropriate
bugs from 5.x to what is appropriate…)
4. Update docker images to include cassandra-5.0
(Docker images also need to be deployed)
5. Add pipeline to ci-cassandra
https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
6. Add dtest version and upgrade paths
-
https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
-
https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
7. Update how_to_commit documentation
https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
was:
Figure out what needs to be done beyond the following…
1. Create release branch
{code}
git switch -c cassandra-5.0 trunk
git push --set-upstream origin cassandra-5.0
{code}
2. Bump trunk's version
{code}
git switch trunk
# increment version to 5.1
edit build.xml debian/changelog CHANGES.txt NEWS.txt
{code}
2a. Update jvm-dtest supported upgrade paths, and circleci dtest jar generation
-
https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
-
https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
3. Add `5.0-alpha`, `5.0-alpha1`, `5.0-beta`, `5.0-rc`, `5.0.x` and `5.1.x` to
jira versions
(no existing tickets will be changed - assignees need to change appropriate
bugs from 5.x to what is appropriate…)
4. Update docker images to include cassandra-5.0
(Docker images also need to be deployed)
5. Add pipeline to ci-cassandra
https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
6. Add dtest version and upgrade paths
-
https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
- https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
-
https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
7. Update how_to_commit documentation
https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
> Create release branch cassandra-5.0
> ---
>
> Key: CASSANDRA-18705
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18705
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 5.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-5.0 trunk
> git push --set-upstream origin cassandra-5.0
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 5.1
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths, and circleci dtest jar
> generation
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> -
> https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> 3. Add `5.0-alpha`, `5.0-alpha1`, `5.0-beta`, `5.0-rc`, `5.0.x` and `5.1.x`
> to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 5.x to what is appropriate…)
> 4. Update docker images to include cassandra-5.0
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
> -
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
> -
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
>
[jira] [Updated] (CASSANDRA-18705) Create release branch cassandra-5.0
[
https://issues.apache.org/jira/browse/CASSANDRA-18705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-18705:
---
Description:
Figure out what needs to be done beyond the following…
1. Create release branch
{code}
git switch -c cassandra-5.0 trunk
git push --set-upstream origin cassandra-5.0
{code}
2. Bump trunk's version
{code}
git switch trunk
# increment version to 5.1
edit build.xml debian/changelog CHANGES.txt NEWS.txt
{code}
2a. Update jvm-dtest supported upgrade paths, and circleci dtest jar generation
-
https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
-
https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
3. Add `5.0-alpha`, `5.0-alpha1`, `5.0-beta`, `5.0-rc`, `5.0.x` and `5.1.x` to
jira versions
(no existing tickets will be changed - assignees need to change appropriate
bugs from 5.x to what is appropriate…)
4. Update docker images to include cassandra-5.0
(Docker images also need to be deployed)
5. Add pipeline to ci-cassandra
https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
6. Add dtest version and upgrade paths
-
https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
- https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
-
https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
7. Update how_to_commit documentation
https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
was:
Figure out what needs to be done beyond the following…
1. Create release branch
{code}
git switch -c cassandra-5.0 trunk
git push --set-upstream origin cassandra-5.0
{code}
2. Bump trunk's version
{code}
git switch trunk
# increment version to 5.1
edit build.xml debian/changelog CHANGES.txt NEWS.txt
{code}
2a. Update jvm-dtest supported upgrade paths
-
https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
3. Add `5.0-alpha`, `5.0-alpha1`, `5.0-beta`, `5.0-rc`, `5.0.x` and `5.1.x` to
jira versions
(no existing tickets will be changed - assignees need to change appropriate
bugs from 5.x to what is appropriate…)
4. Update docker images to include cassandra-5.0
(Docker images also need to be deployed)
5. Add pipeline to ci-cassandra
https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
6. Add dtest version and upgrade paths
-
https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
- https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
-
https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
7. Update how_to_commit documentation
https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
> Create release branch cassandra-5.0
> ---
>
> Key: CASSANDRA-18705
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18705
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 5.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-5.0 trunk
> git push --set-upstream origin cassandra-5.0
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 5.1
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths, and circleci dtest jar
> generation
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> -
> https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> 3. Add `5.0-alpha`, `5.0-alpha1`, `5.0-beta`, `5.0-rc`, `5.0.x` and `5.1.x`
> to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 5.x to what is appropriate…)
> 4. Update docker images to include cassandra-5.0
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
> -
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
> - https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> -
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
>
[cassandra] branch cassandra-5.0 created (now 53d1644ff4)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch cassandra-5.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git at 53d1644ff4 Upgraded to Netty 4.1.96 No new revisions were added by this update. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18726) Simplify helptopics.py using associative array
[ https://issues.apache.org/jira/browse/CASSANDRA-18726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18726: - Status: Needs Committer (was: Review In Progress) > Simplify helptopics.py using associative array > -- > > Key: CASSANDRA-18726 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18726 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Vineet Gali >Assignee: Vineet Gali >Priority: Normal > Fix For: 5.x > > > The ~200 lines of code in helptopics.py can be greatly simplified using an > associative array to map topics to HTML anchors instead of class reflection. > This will halve the lines of code and improve readability. > Functionality will not be changed. -- 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-18726) Simplify helptopics.py using associative array
[ https://issues.apache.org/jira/browse/CASSANDRA-18726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751298#comment-17751298 ] Brandon Williams commented on CASSANDRA-18726: -- CI is clean with a small fix, +1 from me. > Simplify helptopics.py using associative array > -- > > Key: CASSANDRA-18726 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18726 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Vineet Gali >Assignee: Vineet Gali >Priority: Normal > Fix For: 5.x > > > The ~200 lines of code in helptopics.py can be greatly simplified using an > associative array to map topics to HTML anchors instead of class reflection. > This will halve the lines of code and improve readability. > Functionality will not be changed. -- 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-8272) 2ndary indexes can return stale data
[
https://issues.apache.org/jira/browse/CASSANDRA-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751279#comment-17751279
]
Manish Khandelwal commented on CASSANDRA-8272:
--
Hi, reading the comments on this ticket indicates a performance hit for people
using queries with "ALLOW FILTERING" with CL above One or Local_ONE. But I see
this ticket fixed in Cassandra 3.11.7. When I upgraded to Cassandra 3.11.13, I
did not see the dip in performance but after upgrading to Cassandra 4.0.x , I
am seeing test cases using "ALLOW FILTERING" with CL LOCAL_QUORUM taking a hit.
Is there something which only went in Cassandra 4.0.x and not in 3.11.7+.
> 2ndary indexes can return stale data
>
>
> Key: CASSANDRA-8272
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8272
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/2i Index
>Reporter: Sylvain Lebresne
>Assignee: Andres de la Peña
>Priority: Normal
> Labels: pull-request-available
> Fix For: 3.0.21, 3.11.7, 4.0-beta1, 4.0
>
> Time Spent: 7h
> Remaining Estimate: 0h
>
> When replica return 2ndary index results, it's possible for a single replica
> to return a stale result and that result will be sent back to the user,
> potentially failing the CL contract.
> For instance, consider 3 replicas A, B and C, and the following situation:
> {noformat}
> CREATE TABLE test (k int PRIMARY KEY, v text);
> CREATE INDEX ON test(v);
> INSERT INTO test(k, v) VALUES (0, 'foo');
> {noformat}
> with every replica up to date. Now, suppose that the following queries are
> done at {{QUORUM}}:
> {noformat}
> UPDATE test SET v = 'bar' WHERE k = 0;
> SELECT * FROM test WHERE v = 'foo';
> {noformat}
> then, if A and B acknowledge the insert but C respond to the read before
> having applied the insert, then the now stale result will be returned (since
> C will return it and A or B will return nothing).
> A potential solution would be that when we read a tombstone in the index (and
> provided we make the index inherit the gcGrace of it's parent CF), instead of
> skipping that tombstone, we'd insert in the result a corresponding range
> tombstone.
--
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
