[jira] [Commented] (CASSANDRA-16621) Replace spinAsserts code with Awaitility code
[ https://issues.apache.org/jira/browse/CASSANDRA-16621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379626#comment-17379626 ] Jogesh Anand commented on CASSANDRA-16621: -- [~bereng] - thanks! that's very considerate of you :) Yeah I have been following the email updates on 4.0.0 release. :) > Replace spinAsserts code with Awaitility code > - > > Key: CASSANDRA-16621 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16621 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Jogesh Anand >Priority: Normal > Labels: low-hanging-fruit > Fix For: 4.0.x > > > Currently spinAsserts does a similar thing to Awaitility which is being used > more and more. We have now 2 ways of doing the same thing so it would be good > to consolidate -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16621) Replace spinAsserts code with Awaitility code
[ https://issues.apache.org/jira/browse/CASSANDRA-16621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379591#comment-17379591 ] Berenguer Blasi commented on CASSANDRA-16621: - I'm not forgetting about this. I am just waiting on the 4.0.0 cut test upgrade issues to resolve. Thx for your patience. > Replace spinAsserts code with Awaitility code > - > > Key: CASSANDRA-16621 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16621 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Jogesh Anand >Priority: Normal > Labels: low-hanging-fruit > Fix For: 4.0.x > > > Currently spinAsserts does a similar thing to Awaitility which is being used > more and more. We have now 2 ways of doing the same thing so it would be good > to consolidate -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-16797) Incompatible constants related to forwarded writes
Yongkang Li created CASSANDRA-16797: --- Summary: Incompatible constants related to forwarded writes Key: CASSANDRA-16797 URL: https://issues.apache.org/jira/browse/CASSANDRA-16797 Project: Cassandra Issue Type: Bug Reporter: Yongkang Li The header for forwarded writes changed from 3.x.x->4.0. In C* 3.x.x headers are "FWD_TO" or "FWD_FROM" while in C* 4.0 headers are "FORWARD_TO" or "FORWARD_FROM". Therefore, I suppose that there will be a failure during rolling upgrade from 3.x.x to 4.0. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14811) RPC_READY flag handled inconsistently
[
https://issues.apache.org/jira/browse/CASSANDRA-14811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379466#comment-17379466
]
Rens Groothuijsen commented on CASSANDRA-14811:
---
Unit tests have been added.
> RPC_READY flag handled inconsistently
> -
>
> Key: CASSANDRA-14811
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14811
> Project: Cassandra
> Issue Type: Bug
>Reporter: Tibor Repasi
>Assignee: Rens Groothuijsen
>Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> With version 3.0.17 we experience an inconsistent handling of the RPC_READY
> flag. We identified 3 scenarios with an unexpected behaviour.
> # Using {{nodetool disablebinary}} on a node in normal operation
> ** Observed behaviour:
> *** (/) the CQL listener is closed and Netty shut down
> *** (x) gossipinfo still contain the {{RPC_READY}} *true* advertisement.
> ** Expected behaviour: gossip announcement of the {{RPC_READY}} flag should
> switch to *false.* This is what we observe with version 2.2.13
> # Starting up a node with JVM option
> {{-Dcassandra.start_native_transport=false}}
> ** Observed behaviour:
> *** (/) Netty is not started to listen for CQL clients
> *** (/) logging {{cassandra[1765]: INFO 13:58:46 Not starting native
> transport as requested. Use JMX (StorageService->startNativeTransport()) or
> nodetool (enablebinary) to start it}}
> *** (?) the gossipinfo does not contain the {{RPC_READY}} flag at all,
> however, this is also observed on 2.2.13.
> # Issuing {{nodetool enablebinary}} command on a node started with
> {{-Dcassandra.start_native_transport=false}}
> ** Observed behaviour:
> *** (/) Netty is started up and open the CQL port for listening
> *** (x) the {{RPC_READY}} flag is not announced for this node any more,
> causing clients to not consider this node up and not trying to connect.
> ** Expected behaviour: gossip flag {{RPC_READY}} should be added to announce
> *true*, as observed with version 2.2.13.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15210) Streaming with CDC does not honor cdc_enabled
[
https://issues.apache.org/jira/browse/CASSANDRA-15210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379460#comment-17379460
]
Aleksei Zotov commented on CASSANDRA-15210:
---
[~blerer]
I briefly read about CDC feature in Cassandra and this ticket makes sense to
me. As per my understanding, non-CDC node should not care about CDC tables and
enforce writing corresponding mutations to commit log. The patch also looks
good to me. Two questions to you:
# Despite the problem exists, it does not affect anything rather than
performance (with unnecessary writing to commit log for CDC table on non-CDC
nodes). I feel it is not so critical to make it mandatory for 4.0 release. WDYT?
# Even though the patch looks good, there are no unit tests for the change.
Moreover, currently the affected class is not covered by tests. I trier to find
a simple reference test, but looks like streaming tests are quite complicated.
Do we need to have a test developed to get these changes merged? Even though it
is 1 line patch, my belief that having a test is mandatory. Could you please
share a reference test that can be used to cover CDC functionality in
{{CassandraStreamReceiver}}?
> Streaming with CDC does not honor cdc_enabled
> -
>
> Key: CASSANDRA-15210
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15210
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Streaming, Feature/Change Data Capture
>Reporter: Andrew Prudhomme
>Assignee: Andrew Prudhomme
>Priority: Normal
>
> When SSTables are streamed for a CDC enabled table, the updates are processed
> through the write path to ensure they are made available through the commit
> log. However, currently only the CDC state of the table is checked. Since CDC
> is enabled at both the node and table level, a node with CDC disabled (with
> cdc_enabled: false) will unnecessarily send updates through the write path if
> CDC is enabled on the table. This seems like an oversight.
> I'd imagine the fix would be something like
>
> {code:java}
> - hasCDC = cfs.metadata.params.cdc;
> + hasCDC = cfs.metadata.params.cdc &&
> DatabaseDescriptor.isCDCEnabled();{code}
> in
> org.apache.cassandra.db.streaming.CassandraStreamReceiver (4)
> org.apache.cassandra.streaming.StreamReceiveTask (3.11)
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-12922) Bloom filter miss counts are not measured correctly
[
https://issues.apache.org/jira/browse/CASSANDRA-12922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379453#comment-17379453
]
Aleksei Zotov commented on CASSANDRA-12922:
---
[~blambov]
I know you've already confirmed that the patch looks good, but I want to
confirm one use case is valid. I analyzed the code and I see the following
valid exit paths for {{getPosition}} method:
||Use Case||Behavior||
|key is not present in NF|addTrueNegative and exit|
|key is present in Key Cache|addTruePositive and exit|
|key is not within sstable's keys range|addFalsePositive and exit|
|there is no index file|exit|
|key is not present in index file|*addFalsePositive (that's what we're fixing)*
and exit|
|key is present in index file|addTruePositive and exit|
|else|addFalsePositive and exit|
The question is: don't we need to track "false positive" if there is no index
file? I know that having no index file is not smth expected, but from BF
perspective, I see no difference between "key is not present in index file" and
"there is no index file" use cases. Please, let me know your thoughts.
cc: [~blerer]
-
> Bloom filter miss counts are not measured correctly
> ---
>
> Key: CASSANDRA-12922
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12922
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
>Reporter: Branimir Lambov
>Assignee: Benjamin Lerer
>Priority: Normal
> Labels: lhf
> Fix For: 4.x
>
> Attachments: 12922-trunk.txt
>
>
> Bloom filter hits and misses are evaluated incorrectly in
> {{BigTableReader.getPosition}}: we properly record hits, but not misses. In
> particular, if we don't find a match for a key in the index, which is where
> almost all non-matches will be rejected, [we don't record a bloom filter
> false
> positive|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/io/sstable/format/big/BigTableReader.java#L228].
> This leads to very misleading output from e.g. {{nodetool tablestats}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16760) JMXTimer exposes attributes in inconsistent time units
[ https://issues.apache.org/jira/browse/CASSANDRA-16760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379431#comment-17379431 ] Yifan Cai commented on CASSANDRA-16760: --- Thanks for the review. Updated the dtest PR. CI is green https://app.circleci.com/pipelines/github/yifan-c/cassandra/254/workflows/664834fc-da38-4d46-b182-6d4b5f3bdc90 > JMXTimer exposes attributes in inconsistent time units > -- > > Key: CASSANDRA-16760 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16760 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/Observability >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Fix For: 4.x > > Time Spent: 0.5h > Remaining Estimate: 0h > > JMXTimer objects are constructed with a duration time unit, which is fixed to > MICROSECONDS in the codebase. According to that, we should expect the time > values returned from the JXMTimer are in micros. > However, the time unit is inconsistent among the JMXTimer attributes. > Most of the attributes such as percentiles and mean values returned are in > micros, except Values and RecentValues. > Those 2 attributes expose the raw histogram values of the underlying Timer > (CodaHale) and the values are fixed to be based on nanos. > The inconsistency leads to confusion and mis-interpretation of the values, if > the end user is not familiar with the implementation details. One may > consider the Values and RecentValues are also in micros. > Besides the confusion, given the intention is to record the time values in > the micros resolution, we do not need to allocate 165 buckets in the > DecayingEstimatedHistogramReservoir. 165 buckets is necessary for nanos, but > not for micros. We can only allocate 90 buckets and it should reduce ~50% > memory footprint used by the Timers. > I'd like to propose an approach to scale the values being recorded in the > reservoirs used by Timers and reduce the allocation. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15402) Make incremental backup configurable per keyspace and table
[ https://issues.apache.org/jira/browse/CASSANDRA-15402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-15402: --- Reviewers: Marcus Eriksson, Michael Semb Wever (was: Marcus Eriksson) > Make incremental backup configurable per keyspace and table > --- > > Key: CASSANDRA-15402 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15402 > Project: Cassandra > Issue Type: Improvement > Components: Local/Other, Tool/nodetool >Reporter: maxwellguo >Assignee: maxwellguo >Priority: Normal > Labels: pull-request-available > Fix For: 4.x > > Time Spent: 10m > Remaining Estimate: 0h > > We know that when we do backup for cassandra, we can do full bakcup with > snapshot, when we need to backup incremental data , incremental_backup can do > some help . > For snapshot we can just make snapshot for some keyspace/table. but > incremental backup will do all data backup(make hard link for all sstable > that flush from memtable or streaming ). we also know that commitlog's replay > can do some keyspace /table 's filter. > So I think for incremental backup we also need some filter for it.After all > not all keyspace/table is so important to do backup. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16536) BLOG - Post about Cassandra & Kubernetes - SIG Update #2
[ https://issues.apache.org/jira/browse/CASSANDRA-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379417#comment-17379417 ] Michael Semb Wever commented on CASSANDRA-16536: What's happening here? Is the blog post still intended? > BLOG - Post about Cassandra & Kubernetes - SIG Update #2 > > > Key: CASSANDRA-16536 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16536 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Rahul Singh >Assignee: Michael Semb Wever >Priority: High > Labels: pull-request-available > Fix For: 4.0.x > > Attachments: image-2021-03-24-18-57-08-450.png > > > We're getting another update up for the Cassandra & Kubernetes SIG > > [https://github.com/Anant/cassandra-website/blob/master/src/_posts/2021-03-26-cassandra-and-kubernetes-sig-update.markdown] > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16642) Create release branch cassandra-4.0
[
https://issues.apache.org/jira/browse/CASSANDRA-16642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-16642:
---
Fix Version/s: (was: 4.0.x)
(was: 4.x)
4.1
4.0.1
> Create release branch cassandra-4.0
> ---
>
> Key: CASSANDRA-16642
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16642
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0.1, 4.1
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-4.0 trunk
> git push --set-upstream origin cassandra-4.0
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 4.1
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 3. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> -4. Update website versions-
> (it not needed until a release is made)
> 5. 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#L31
> 6. Update how_to_commit documentation
> https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16642) Create release branch cassandra-4.0
[
https://issues.apache.org/jira/browse/CASSANDRA-16642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-16642:
---
Resolution: Fixed
Status: Resolved (was: Open)
All (sub) issues resolved.
> Create release branch cassandra-4.0
> ---
>
> Key: CASSANDRA-16642
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16642
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-4.0 trunk
> git push --set-upstream origin cassandra-4.0
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 4.1
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 3. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> -4. Update website versions-
> (it not needed until a release is made)
> 5. 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#L31
> 6. Update how_to_commit documentation
> https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16649) Add Versions.Major.v4X to Java DTests (after cassandra-4.0 branch was created)
[ https://issues.apache.org/jira/browse/CASSANDRA-16649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379413#comment-17379413 ] Michael Semb Wever commented on CASSANDRA-16649: Committed as [b3f99218815c318eaf60e950300163463d2bdba4|https://github.com/apache/cassandra/commit/b3f99218815c318eaf60e950300163463d2bdba4]. > Add Versions.Major.v4X to Java DTests (after cassandra-4.0 branch was created) > -- > > Key: CASSANDRA-16649 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16649 > Project: Cassandra > Issue Type: Sub-task > Components: Test/dtest/java >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 2.2.20, 3.0.25, 3.11.11, 4.0.1, 4.1 > > > - > https://github.com/apache/cassandra-in-jvm-dtest-api/compare/trunk...thelastpickle:mck/16649 > - > https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/16649/trunk > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.0 updated (51f16a3 -> 4dcf7d9)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 51f16a3 Merge branch 'cassandra-4.0.0' into cassandra-4.0 new b3f9921 Introduce SemVer4j for version representation, parsing and handling. And correct supported upgrade paths. Add v4X to Java DTests (after cassandra-4.0 branch was created) new 0a84dda Merge branch 'cassandra-2.2' into cassandra-3.0 new 0c1e1cc Merge branch 'cassandra-3.0' into cassandra-3.11 new 4dcf7d9 Merge branch 'cassandra-3.11' into cassandra-4.0 The 4 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: build.xml | 2 +- .../distributed/impl/AbstractCluster.java | 2 +- .../cassandra/distributed/impl/InstanceConfig.java | 18 +++-- .../upgrade/CompactStorage3to4UpgradeTest.java | 2 +- .../upgrade/CompactStorageUpgradeTest.java | 10 +-- .../cassandra/distributed/upgrade/GroupByTest.java | 2 +- .../upgrade/MixedModeAvailabilityTestBase.java | 17 +++-- .../upgrade/MixedModeAvailabilityV22Test.java | 4 +- .../upgrade/MixedModeAvailabilityV30Test.java | 10 +-- .../upgrade/MixedModeAvailabilityV3XTest.java | 4 +- .../upgrade/MixedModeBatchTestBase.java| 12 +++- .../upgrade/MixedModeConsistencyTestBase.java | 12 +++- .../upgrade/MixedModeConsistencyV22Test.java | 4 +- .../upgrade/MixedModeConsistencyV30Test.java | 10 +-- .../upgrade/MixedModeConsistencyV3XTest.java | 4 +- .../upgrade/MixedModeFrom2LoggedBatchTest.java | 4 +- .../upgrade/MixedModeFrom2ReplicationTest.java | 4 +- .../upgrade/MixedModeFrom2UnloggedBatchTest.java | 4 +- .../upgrade/MixedModeFrom3LoggedBatchTest.java | 12 +--- .../upgrade/MixedModeFrom3ReplicationTest.java | 12 +--- .../upgrade/MixedModeFrom3UnloggedBatchTest.java | 12 +--- .../distributed/upgrade/MixedModeGossipTest.java | 10 +-- .../distributed/upgrade/MixedModeReadTest.java | 5 +- .../distributed/upgrade/MixedModeRepairTest.java | 4 +- .../upgrade/MixedModeReplicationTestBase.java | 12 +++- .../cassandra/distributed/upgrade/PagingTest.java | 2 +- .../upgrade/Pre40MessageFilterTest.java| 5 +- .../ReadRepairCompactStorageUpgradeTest.java | 4 +- .../cassandra/distributed/upgrade/UpgradeTest.java | 2 +- .../distributed/upgrade/UpgradeTestBase.java | 84 ++ 30 files changed, 152 insertions(+), 137 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16649) Add Versions.Major.v4X to Java DTests (after cassandra-4.0 branch was created)
[ https://issues.apache.org/jira/browse/CASSANDRA-16649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16649: --- Fix Version/s: (was: 4.0.x) (was: 3.11.x) (was: 4.x) (was: 3.0.x) (was: 2.2.x) 4.1 4.0.1 3.11.11 3.0.25 2.2.20 Source Control Link: https://github.com/apache/cassandra-in-jvm-dtest-api/commit/8b17c8dfe3fa0d062af1e861b8b204c7bbeb275b https://github.com/apache/cassandra-in-jvm-dtest-api/commit/0a13871f9dc8261b3defc1183eb4eee92d9c4f72 https://github.com/apache/cassandra/commit/b3f992188 (was: https://github.com/apache/cassandra-in-jvm-dtest-api/commit/8b17c8dfe3fa0d062af1e861b8b204c7bbeb275b https://github.com/apache/cassandra-in-jvm-dtest-api/commit/0a13871f9dc8261b3defc1183eb4eee92d9c4f72) Resolution: Fixed Status: Resolved (was: Ready to Commit) > Add Versions.Major.v4X to Java DTests (after cassandra-4.0 branch was created) > -- > > Key: CASSANDRA-16649 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16649 > Project: Cassandra > Issue Type: Sub-task > Components: Test/dtest/java >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 2.2.20, 3.0.25, 3.11.11, 4.0.1, 4.1 > > > - > https://github.com/apache/cassandra-in-jvm-dtest-api/compare/trunk...thelastpickle:mck/16649 > - > https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/16649/trunk > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.0' into trunk
This is an automated email from the ASF dual-hosted git repository.
mck pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit f9a220c1100d9f6deaca0ec20e7481576deb5b36
Merge: 25b75df 4dcf7d9
Author: Mick Semb Wever
AuthorDate: Mon Jul 12 22:39:19 2021 +0200
Merge branch 'cassandra-4.0' into trunk
build.xml | 2 +-
.../distributed/impl/AbstractCluster.java | 2 +-
.../cassandra/distributed/impl/InstanceConfig.java | 18 ++---
.../upgrade/CompactStorage3to4UpgradeTest.java | 2 +-
.../upgrade/CompactStorageUpgradeTest.java | 10 +--
.../cassandra/distributed/upgrade/GroupByTest.java | 2 +-
.../upgrade/MixedModeAvailabilityTestBase.java | 17 +++--
.../upgrade/MixedModeAvailabilityV22Test.java | 4 +-
.../upgrade/MixedModeAvailabilityV30Test.java | 10 +--
.../upgrade/MixedModeAvailabilityV3XTest.java | 4 +-
.../upgrade/MixedModeBatchTestBase.java| 12 ++-
.../upgrade/MixedModeConsistencyTestBase.java | 12 ++-
.../upgrade/MixedModeConsistencyV22Test.java | 4 +-
.../upgrade/MixedModeConsistencyV30Test.java | 10 +--
.../upgrade/MixedModeConsistencyV3XTest.java | 4 +-
.../upgrade/MixedModeFrom2LoggedBatchTest.java | 4 +-
.../upgrade/MixedModeFrom2ReplicationTest.java | 4 +-
.../upgrade/MixedModeFrom2UnloggedBatchTest.java | 4 +-
.../upgrade/MixedModeFrom3LoggedBatchTest.java | 12 +--
.../upgrade/MixedModeFrom3ReplicationTest.java | 12 +--
.../upgrade/MixedModeFrom3UnloggedBatchTest.java | 12 +--
.../distributed/upgrade/MixedModeGossipTest.java | 10 ++-
.../distributed/upgrade/MixedModeReadTest.java | 5 +-
.../distributed/upgrade/MixedModeRepairTest.java | 4 +-
.../upgrade/MixedModeReplicationTestBase.java | 12 ++-
.../cassandra/distributed/upgrade/PagingTest.java | 2 +-
.../upgrade/Pre40MessageFilterTest.java| 5 +-
.../ReadRepairCompactStorageUpgradeTest.java | 4 +-
.../cassandra/distributed/upgrade/UpgradeTest.java | 2 +-
.../distributed/upgrade/UpgradeTestBase.java | 86 ++
30 files changed, 154 insertions(+), 137 deletions(-)
diff --cc
test/distributed/org/apache/cassandra/distributed/upgrade/MixedModeGossipTest.java
index 83e911d,e706bda..f62936c
---
a/test/distributed/org/apache/cassandra/distributed/upgrade/MixedModeGossipTest.java
+++
b/test/distributed/org/apache/cassandra/distributed/upgrade/MixedModeGossipTest.java
@@@ -50,8 -50,9 +50,9 @@@ public class MixedModeGossipTest extend
.withConfig(c -> c.with(Feature.GOSSIP, Feature.NETWORK))
.nodes(3)
.nodesToUpgradeOrdered(1, 2, 3)
- .upgrade(Versions.Major.v30, Versions.Major.v4)
- .upgrade(Versions.Major.v3X, Versions.Major.v4)
-// all upgrades from v30 up, excluding v30->v3X
++// all upgrades from v30 up, excluding v30->v3X and from v40
+ .singleUpgrade(v30, v40)
-.upgradesFrom(v3X)
++.singleUpgrade(v3X, v40)
.setup(c -> {})
.runAfterNodeUpgrade((cluster, node) -> {
if (node == 1) {
@@@ -85,8 -86,9 +86,9 @@@
.withConfig(c -> c.with(Feature.GOSSIP, Feature.NETWORK))
.nodes(3)
.nodesToUpgradeOrdered(1, 2, 3)
- .upgrade(Versions.Major.v30, Versions.Major.v4)
- .upgrade(Versions.Major.v3X, Versions.Major.v4)
-// all upgrades from v30 up, excluding v30->v3X
++// all upgrades from v30 up, excluding v30->v3X and from v40
+ .singleUpgrade(v30, v40)
-.upgradesFrom(v3X)
++.singleUpgrade(v3X, v40)
.setup(cluster -> {
// node2 and node3 gossiper cannot talk with each other
cluster.filters().verbs(Verb.GOSSIP_DIGEST_SYN.id).from(2).to(3).drop();
diff --cc
test/distributed/org/apache/cassandra/distributed/upgrade/MixedModeReadTest.java
index f1883b0,c95aede..631f65a
---
a/test/distributed/org/apache/cassandra/distributed/upgrade/MixedModeReadTest.java
+++
b/test/distributed/org/apache/cassandra/distributed/upgrade/MixedModeReadTest.java
@@@ -39,8 -39,9 +39,9 @@@ public class MixedModeReadTest extends
.withConfig(c -> c.with(Feature.GOSSIP, Feature.NETWORK))
.nodes(2)
.nodesToUpgrade(1)
- .upgrade(Versions.Major.v30, Versions.Major.v4)
- .upgrade(Versions.Major.v3X, Versions.Major.v4)
-// all upgrades from v30 up, excluding v30->v3X
++// all upgrades from v30 up, excluding v30->v3X and from v40
+ .singleUpgrade(v30, v40)
-.upgradesFrom(v3X)
++.singleUpgrade(v3X, v40)
.setup(cluster -> {
cluster.schemaChange(CREATE_TABLE);
insertData(cluster.coordinator(1));
diff --cc
test/distributed/org/apache/cassandra/distributed/upgrade/MixedModeRepairTest.java
index 39f6c95,adcfd1f..478a1b7
---
a/test/distribut
[cassandra] 01/01: Merge branch 'cassandra-3.11' into cassandra-4.0
This is an automated email from the ASF dual-hosted git repository.
mck pushed a commit to branch cassandra-4.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit 4dcf7d9ebd5c330b0dc438054d595fe63fe60bbe
Merge: 51f16a3 0c1e1cc
Author: Mick Semb Wever
AuthorDate: Mon Jul 12 22:31:23 2021 +0200
Merge branch 'cassandra-3.11' into cassandra-4.0
build.xml | 2 +-
.../distributed/impl/AbstractCluster.java | 2 +-
.../cassandra/distributed/impl/InstanceConfig.java | 18 +++--
.../upgrade/CompactStorage3to4UpgradeTest.java | 2 +-
.../upgrade/CompactStorageUpgradeTest.java | 10 +--
.../cassandra/distributed/upgrade/GroupByTest.java | 2 +-
.../upgrade/MixedModeAvailabilityTestBase.java | 17 +++--
.../upgrade/MixedModeAvailabilityV22Test.java | 4 +-
.../upgrade/MixedModeAvailabilityV30Test.java | 10 +--
.../upgrade/MixedModeAvailabilityV3XTest.java | 4 +-
.../upgrade/MixedModeBatchTestBase.java| 12 +++-
.../upgrade/MixedModeConsistencyTestBase.java | 12 +++-
.../upgrade/MixedModeConsistencyV22Test.java | 4 +-
.../upgrade/MixedModeConsistencyV30Test.java | 10 +--
.../upgrade/MixedModeConsistencyV3XTest.java | 4 +-
.../upgrade/MixedModeFrom2LoggedBatchTest.java | 4 +-
.../upgrade/MixedModeFrom2ReplicationTest.java | 4 +-
.../upgrade/MixedModeFrom2UnloggedBatchTest.java | 4 +-
.../upgrade/MixedModeFrom3LoggedBatchTest.java | 12 +---
.../upgrade/MixedModeFrom3ReplicationTest.java | 12 +---
.../upgrade/MixedModeFrom3UnloggedBatchTest.java | 12 +---
.../distributed/upgrade/MixedModeGossipTest.java | 10 +--
.../distributed/upgrade/MixedModeReadTest.java | 5 +-
.../distributed/upgrade/MixedModeRepairTest.java | 4 +-
.../upgrade/MixedModeReplicationTestBase.java | 12 +++-
.../cassandra/distributed/upgrade/PagingTest.java | 2 +-
.../upgrade/Pre40MessageFilterTest.java| 5 +-
.../ReadRepairCompactStorageUpgradeTest.java | 4 +-
.../cassandra/distributed/upgrade/UpgradeTest.java | 2 +-
.../distributed/upgrade/UpgradeTestBase.java | 84 ++
30 files changed, 152 insertions(+), 137 deletions(-)
diff --cc build.xml
index 6d15381,a2a59d8..d93992d
--- a/build.xml
+++ b/build.xml
@@@ -521,39 -406,43 +521,39 @@@
-
-
-
-
-
+
+
+
+
-
-
-
+
+
+
+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
++
+
+
+
+
+
+
+
+
-
-
+
+
+
-
+
-
-
+
+
-
-
-
-
+
+
+
+
diff --cc
test/distributed/org/apache/cassandra/distributed/impl/AbstractCluster.java
index 8026357,4de6fcd..240f080
---
a/test/distributed/org/apache/cassandra/distributed/impl/AbstractCluster.java
+++
b/test/distributed/org/apache/cassandra/distributed/impl/AbstractCluster.java
@@@ -215,8 -178,8 +215,8 @@@ public abstract class AbstractCluster<
ClassLoader classLoader = new InstanceClassLoader(generation,
config.num(), version.classpath, sharedClassLoader, SHARED_PREDICATE);
if (instanceInitializer != null)
instanceInitializer.accept(classLoader, config.num());
-return
Instance.transferAdhoc((SerializableBiFunction)Instance::new, classLoader)
-.apply(config, classLoader);
+return
Instance.transferAdhoc((SerializableBiFunction)Instance::new, classLoader)
-
.apply(config.forVersion(version.major), classLoader);
++
.apply(config.forVersion(version.version), classLoader);
}
public IInstanceConfig config()
diff --cc
test/distributed/org/apache/cassandra/distributed/impl/InstanceConfig.java
index 895f2a7,b6b402b..1bbdd0b
--- a/test/distributed/org/apache/cassandra/distributed/impl/InstanceConfig.java
+++ b/test/distributed/org/apache/cassandra/distributed/impl/InstanceConfig.java
@@@ -284,15 -264,11 +282,15 @@@ public class InstanceConfig implements
return datadirs;
}
- public InstanceConfig forVersion(Versions.Major major)
+ public InstanceConfig forVersion(Semver version)
{
-
[cassandra] 01/01: Merge branch 'cassandra-3.0' into cassandra-3.11
This is an automated email from the ASF dual-hosted git repository.
mck pushed a commit to branch cassandra-3.11
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit 0c1e1ccfadacf59e6a45e013e598830c8b637f4d
Merge: f49b86d 0a84dda
Author: Mick Semb Wever
AuthorDate: Mon Jul 12 22:20:10 2021 +0200
Merge branch 'cassandra-3.0' into cassandra-3.11
build.xml | 2 +-
.../cassandra/distributed/impl/InstanceConfig.java | 14 ++--
.../upgrade/CompactStorage2to3UpgradeTest.java | 8 +--
.../upgrade/DropCompactStorageTest.java| 7 +-
.../distributed/upgrade/MigrateDropColumns.java| 20 +++---
.../upgrade/MigrateDropColumns22To30To311Test.java | 2 +-
.../upgrade/MigrateDropColumns22To311Test.java | 2 +-
.../upgrade/MigrateDropColumns30To311Test.java | 2 +-
.../upgrade/MixedModeRangeTombstoneTest.java | 2 +-
.../upgrade/MixedModeReadRepairTest.java | 4 +-
.../distributed/upgrade/MixedModeReadTest.java | 2 +-
.../cassandra/distributed/upgrade/PagingTest.java | 2 +-
.../cassandra/distributed/upgrade/UpgradeTest.java | 26 +--
.../distributed/upgrade/UpgradeTestBase.java | 80 +++---
14 files changed, 92 insertions(+), 81 deletions(-)
diff --cc build.xml
index e40d62b,87851b8..a2a59d8
--- a/build.xml
+++ b/build.xml
@@@ -416,9 -390,9 +416,9 @@@
-
+
-
+
diff --cc
test/distributed/org/apache/cassandra/distributed/upgrade/CompactStorage2to3UpgradeTest.java
index b0bbe64,9ea54c3..7235c72
---
a/test/distributed/org/apache/cassandra/distributed/upgrade/CompactStorage2to3UpgradeTest.java
+++
b/test/distributed/org/apache/cassandra/distributed/upgrade/CompactStorage2to3UpgradeTest.java
@@@ -118,8 -118,9 +118,8 @@@ public class CompactStorage2to3UpgradeT
final ResultsRecorder recorder = new ResultsRecorder();
new TestCase()
-
.nodes(2)
- .upgrade(Versions.Major.v22, Versions.Major.v3X)
+ .upgradesFrom(v22)
.withConfig(config -> config.with(GOSSIP, NETWORK, NATIVE_PROTOCOL))
.setup(cluster -> {
cluster.schemaChange(String.format(
@@@ -208,121 -210,119 +208,121 @@@
final int additionalParititons = 5;
new TestCase()
-.nodes(2)
-.upgradesFrom(v22)
-.withConfig(config -> config.with(GOSSIP, NETWORK,
NATIVE_PROTOCOL).set("enable_drop_compact_storage", true))
-.setup(cluster -> {
-cluster.schemaChange(String.format(
-"CREATE TABLE %s.%s (key int, c1 int, c2 int, c3
int, PRIMARY KEY (key, c1, c2)) WITH COMPACT STORAGE",
-KEYSPACE, table));
-ICoordinator coordinator = cluster.coordinator(1);
-
-for (int i = 1; i <= partitions; i++)
-{
-for (int j = 1; j <= rowsPerPartition; j++)
-{
-coordinator.execute(String.format("INSERT INTO
%s.%s (key, c1, c2, c3) VALUES (%d, %d, 1, 1)",
-KEYSPACE, table, i, j),
ConsistencyLevel.ALL);
-coordinator.execute(String.format("INSERT INTO
%s.%s (key, c1, c2, c3) VALUES (%d, %d, 2, 2)",
- KEYSPACE,
table, i, j), ConsistencyLevel.ALL);
-coordinator.execute(String.format("INSERT INTO
%s.%s (key, c1, c2, c3) VALUES (%d, %d, 3, 3)",
- KEYSPACE,
table, i, j), ConsistencyLevel.ALL);
-}
-}
-})
-.runAfterClusterUpgrade(cluster -> {
-cluster.forEach(n -> n.nodetoolResult("upgradesstables",
KEYSPACE).asserts().success());
-Thread.sleep(1000);
-// drop compact storage on only one node before
performing writes
-IMessageFilters.Filter filter =
cluster.verbs().allVerbs().to(2).drop();
-cluster.schemaChange(String.format("ALTER TABLE %s.%s
DROP COMPACT STORAGE", KEYSPACE, table), 1);
-filter.off();
-
-// add new partitions and delete some of the old ones
-ICoordinator coordinator = cluster.coordinator(1);
-for (int i = 0; i < additionalParititons; i++)
-{
-for (int j = 1; j <= rowsPerPartition; j++)
-{
-coordinator.execute(String.format("INSERT INTO
%s.%s (key, c1, c2, c3) VALUES (%d, %d, 1, 1)",
-KEYSPACE, t
[cassandra] branch cassandra-2.2 updated: Introduce SemVer4j for version representation, parsing and handling. And correct supported upgrade paths. Add v4X to Java DTests (after cassandra-4.0 branch w
This is an automated email from the ASF dual-hosted git repository.
mck pushed a commit to branch cassandra-2.2
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/cassandra-2.2 by this push:
new b3f9921 Introduce SemVer4j for version representation, parsing and
handling. And correct supported upgrade paths. Add v4X to Java DTests (after
cassandra-4.0 branch was created)
b3f9921 is described below
commit b3f99218815c318eaf60e950300163463d2bdba4
Author: Mick Semb Wever
AuthorDate: Sun May 2 17:54:00 2021 +0200
Introduce SemVer4j for version representation, parsing and handling. And
correct supported upgrade paths. Add v4X to Java DTests (after cassandra-4.0
branch was created)
Change upgrades from testing only a single path, to testing all upgrade
paths that are defined as supported within the specified from-to range.
Change all upgrades to v40 and v4X to be open ended (i.e. implicit CURRENT
version).
patch by Mick Semb Wever; reviewed by Alex Petrov for CASSANDRA-16649
---
build.xml | 2 +-
.../cassandra/distributed/impl/InstanceConfig.java | 15 ++---
.../upgrade/MixedModeReadRepairTest.java | 2 +-
.../cassandra/distributed/upgrade/PagingTest.java | 2 +-
.../cassandra/distributed/upgrade/UpgradeTest.java | 2 +-
.../distributed/upgrade/UpgradeTestBase.java | 73 +++---
6 files changed, 60 insertions(+), 36 deletions(-)
diff --git a/build.xml b/build.xml
index 064d16d..7d1cc58 100644
--- a/build.xml
+++ b/build.xml
@@ -393,7 +393,7 @@
-
+
diff --git
a/test/distributed/org/apache/cassandra/distributed/impl/InstanceConfig.java
b/test/distributed/org/apache/cassandra/distributed/impl/InstanceConfig.java
index b71f22c..f4ef623 100644
--- a/test/distributed/org/apache/cassandra/distributed/impl/InstanceConfig.java
+++ b/test/distributed/org/apache/cassandra/distributed/impl/InstanceConfig.java
@@ -19,10 +19,8 @@
package org.apache.cassandra.distributed.impl;
import java.io.File;
-import java.lang.reflect.Field;
import java.net.InetSocketAddress;
import java.net.UnknownHostException;
-import java.util.Arrays;
import java.util.Collections;
import java.util.EnumSet;
import java.util.Map;
@@ -30,15 +28,16 @@ import java.util.TreeMap;
import java.util.UUID;
import java.util.function.Function;
-import org.apache.cassandra.config.YamlConfigurationLoader;
+import com.vdurmont.semver4j.Semver;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
+import org.apache.cassandra.config.YamlConfigurationLoader;
import org.apache.cassandra.distributed.api.Feature;
import org.apache.cassandra.distributed.api.IInstanceConfig;
import org.apache.cassandra.distributed.shared.NetworkTopology;
import org.apache.cassandra.distributed.shared.Shared;
-import org.apache.cassandra.distributed.shared.Versions;
+import org.apache.cassandra.distributed.upgrade.UpgradeTestBase;
import org.apache.cassandra.locator.InetAddressAndPort;
import org.apache.cassandra.locator.SimpleSeedProvider;
@@ -266,15 +265,11 @@ public class InstanceConfig implements IInstanceConfig
return datadirs;
}
-public InstanceConfig forVersion(Versions.Major major)
+public InstanceConfig forVersion(Semver version)
{
-switch (major)
-{
-case v4: return this;
-default: return new InstanceConfig(this)
+return new InstanceConfig(this)
.set("seed_provider", new
ParameterizedClass(SimpleSeedProvider.class.getName(),
Collections.singletonMap("seeds", "127.0.0.1")));
-}
}
public String toString()
diff --git
a/test/distributed/org/apache/cassandra/distributed/upgrade/MixedModeReadRepairTest.java
b/test/distributed/org/apache/cassandra/distributed/upgrade/MixedModeReadRepairTest.java
index fabf172..549596b 100644
---
a/test/distributed/org/apache/cassandra/distributed/upgrade/MixedModeReadRepairTest.java
+++
b/test/distributed/org/apache/cassandra/distributed/upgrade/MixedModeReadRepairTest.java
@@ -32,7 +32,7 @@ public class MixedModeReadRepairTest extends UpgradeTestBase
{
new TestCase()
.nodes(2)
-.upgrade(Versions.Major.v22, Versions.Major.v30)
+.upgradesFrom(v22)
.setup((cluster) -> cluster.schemaChange("CREATE TABLE " +
DistributedTestBase.KEYSPACE + ".tbl (pk ascii, b boolean, v blob, PRIMARY KEY
(pk)) WITH COMPACT STORAGE"))
.runAfterNodeUpgrade((cluster, node) -> {
if (node != 1)
diff --git
a/test/distributed/org/apache/cassandra/distributed/upgrade/PagingTest.java
b/test/distributed/org/apache/cassandra/distributed/upgrade/PagingTest.java
index 1af5856..7b958a7 100644
--- a/test/distribu
[cassandra] 01/01: Merge branch 'cassandra-2.2' into cassandra-3.0
This is an automated email from the ASF dual-hosted git repository.
mck pushed a commit to branch cassandra-3.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit 0a84dda36a2ec971681f0002b45a00c3432a8024
Merge: eadb171 b3f9921
Author: Mick Semb Wever
AuthorDate: Mon Jul 12 22:14:13 2021 +0200
Merge branch 'cassandra-2.2' into cassandra-3.0
build.xml | 2 +-
.../cassandra/distributed/impl/InstanceConfig.java | 14 ++--
.../upgrade/CompactStorage2to3UpgradeTest.java | 23 +++
.../upgrade/DropCompactStorageTest.java| 7 +-
.../upgrade/MigrateDropColumnsTest.java| 3 +-
.../upgrade/MixedModeRangeTombstoneTest.java | 2 +-
.../upgrade/MixedModeReadRepairTest.java | 4 +-
.../cassandra/distributed/upgrade/PagingTest.java | 2 +-
.../cassandra/distributed/upgrade/UpgradeTest.java | 27 +---
.../distributed/upgrade/UpgradeTestBase.java | 77 +++---
10 files changed, 83 insertions(+), 78 deletions(-)
diff --cc build.xml
index 8dc7dfd,7d1cc58..87851b8
--- a/build.xml
+++ b/build.xml
@@@ -392,9 -393,8 +392,9 @@@
-
+
+
diff --cc
test/distributed/org/apache/cassandra/distributed/impl/InstanceConfig.java
index dfd842d,f4ef623..b97cb75
--- a/test/distributed/org/apache/cassandra/distributed/impl/InstanceConfig.java
+++ b/test/distributed/org/apache/cassandra/distributed/impl/InstanceConfig.java
@@@ -33,7 -32,7 +32,6 @@@ import com.vdurmont.semver4j.Semver
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
--import org.apache.cassandra.config.YamlConfigurationLoader;
import org.apache.cassandra.distributed.api.Feature;
import org.apache.cassandra.distributed.api.IInstanceConfig;
import org.apache.cassandra.distributed.shared.NetworkTopology;
diff --cc
test/distributed/org/apache/cassandra/distributed/upgrade/CompactStorage2to3UpgradeTest.java
index 37e8bb4,000..9ea54c3
mode 100644,00..100644
---
a/test/distributed/org/apache/cassandra/distributed/upgrade/CompactStorage2to3UpgradeTest.java
+++
b/test/distributed/org/apache/cassandra/distributed/upgrade/CompactStorage2to3UpgradeTest.java
@@@ -1,363 -1,0 +1,364 @@@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.cassandra.distributed.upgrade;
+
+import java.util.HashMap;
+import java.util.Map;
+
+import org.junit.Test;
+
+import org.apache.cassandra.distributed.UpgradeableCluster;
+import org.apache.cassandra.distributed.api.ConsistencyLevel;
+import org.apache.cassandra.distributed.api.ICoordinator;
+import org.apache.cassandra.distributed.api.IMessageFilters;
+import org.apache.cassandra.distributed.api.NodeToolResult;
+import org.apache.cassandra.distributed.shared.Versions;
+
+import static org.apache.cassandra.distributed.shared.AssertUtils.assertRows;
+import static org.apache.cassandra.distributed.shared.AssertUtils.row;
+import static org.junit.Assert.assertEquals;
+import static org.apache.cassandra.distributed.api.Feature.GOSSIP;
+import static org.apache.cassandra.distributed.api.Feature.NATIVE_PROTOCOL;
+import static org.apache.cassandra.distributed.api.Feature.NETWORK;
+
+
+public class CompactStorage2to3UpgradeTest extends UpgradeTestBase
+{
+@Test
+public void multiColumn() throws Throwable
+{
+new TestCase()
- .upgrade(Versions.Major.v22, Versions.Major.v30)
++.upgradesFrom(v22)
+.setup(cluster -> {
+assert cluster.size() == 3;
+int rf = cluster.size() - 1;
+assert rf == 2;
+cluster.schemaChange("CREATE KEYSPACE ks WITH replication =
{'class': 'SimpleStrategy', 'replication_factor': " + (cluster.size() - 1) +
"};");
+cluster.schemaChange("CREATE TABLE ks.tbl (pk int, v1 int, v2
text, PRIMARY KEY (pk)) WITH COMPACT STORAGE");
+ICoordinator coordinator = cluster.coordinator(1);
+// these shouldn't be replicated by the 3rd node
+coordinator.execute("INSERT INTO ks.tbl (pk, v1, v2)
[cassandra] branch trunk updated (25b75df -> f9a220c)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 25b75df Merge branch 'cassandra-4.0' into trunk new b3f9921 Introduce SemVer4j for version representation, parsing and handling. And correct supported upgrade paths. Add v4X to Java DTests (after cassandra-4.0 branch was created) new 0a84dda Merge branch 'cassandra-2.2' into cassandra-3.0 new 0c1e1cc Merge branch 'cassandra-3.0' into cassandra-3.11 new 4dcf7d9 Merge branch 'cassandra-3.11' into cassandra-4.0 new f9a220c Merge branch 'cassandra-4.0' into trunk The 5 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: build.xml | 2 +- .../distributed/impl/AbstractCluster.java | 2 +- .../cassandra/distributed/impl/InstanceConfig.java | 18 ++--- .../upgrade/CompactStorage3to4UpgradeTest.java | 2 +- .../upgrade/CompactStorageUpgradeTest.java | 10 +-- .../cassandra/distributed/upgrade/GroupByTest.java | 2 +- .../upgrade/MixedModeAvailabilityTestBase.java | 17 +++-- .../upgrade/MixedModeAvailabilityV22Test.java | 4 +- .../upgrade/MixedModeAvailabilityV30Test.java | 10 +-- .../upgrade/MixedModeAvailabilityV3XTest.java | 4 +- .../upgrade/MixedModeBatchTestBase.java| 12 ++- .../upgrade/MixedModeConsistencyTestBase.java | 12 ++- .../upgrade/MixedModeConsistencyV22Test.java | 4 +- .../upgrade/MixedModeConsistencyV30Test.java | 10 +-- .../upgrade/MixedModeConsistencyV3XTest.java | 4 +- .../upgrade/MixedModeFrom2LoggedBatchTest.java | 4 +- .../upgrade/MixedModeFrom2ReplicationTest.java | 4 +- .../upgrade/MixedModeFrom2UnloggedBatchTest.java | 4 +- .../upgrade/MixedModeFrom3LoggedBatchTest.java | 12 +-- .../upgrade/MixedModeFrom3ReplicationTest.java | 12 +-- .../upgrade/MixedModeFrom3UnloggedBatchTest.java | 12 +-- .../distributed/upgrade/MixedModeGossipTest.java | 10 ++- .../distributed/upgrade/MixedModeReadTest.java | 5 +- .../distributed/upgrade/MixedModeRepairTest.java | 4 +- .../upgrade/MixedModeReplicationTestBase.java | 12 ++- .../cassandra/distributed/upgrade/PagingTest.java | 2 +- .../upgrade/Pre40MessageFilterTest.java| 5 +- .../ReadRepairCompactStorageUpgradeTest.java | 4 +- .../cassandra/distributed/upgrade/UpgradeTest.java | 2 +- .../distributed/upgrade/UpgradeTestBase.java | 86 ++ 30 files changed, 154 insertions(+), 137 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-3.11 updated (f49b86d -> 0c1e1cc)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git. from f49b86d Optimize bytes skipping when reading SSTables new b3f9921 Introduce SemVer4j for version representation, parsing and handling. And correct supported upgrade paths. Add v4X to Java DTests (after cassandra-4.0 branch was created) new 0a84dda Merge branch 'cassandra-2.2' into cassandra-3.0 new 0c1e1cc Merge branch 'cassandra-3.0' into cassandra-3.11 The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: build.xml | 2 +- .../cassandra/distributed/impl/InstanceConfig.java | 14 ++-- .../upgrade/CompactStorage2to3UpgradeTest.java | 8 +-- .../upgrade/DropCompactStorageTest.java| 7 +- .../distributed/upgrade/MigrateDropColumns.java| 20 +++--- .../upgrade/MigrateDropColumns22To30To311Test.java | 2 +- .../upgrade/MigrateDropColumns22To311Test.java | 2 +- .../upgrade/MigrateDropColumns30To311Test.java | 2 +- .../upgrade/MixedModeRangeTombstoneTest.java | 2 +- .../upgrade/MixedModeReadRepairTest.java | 4 +- .../distributed/upgrade/MixedModeReadTest.java | 2 +- .../cassandra/distributed/upgrade/PagingTest.java | 2 +- .../cassandra/distributed/upgrade/UpgradeTest.java | 26 +-- .../distributed/upgrade/UpgradeTestBase.java | 80 +++--- 14 files changed, 92 insertions(+), 81 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-3.0 updated (eadb171 -> 0a84dda)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch cassandra-3.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git. from eadb171 Handle correctly the exceptions thrown by custom QueryHandler constructors new b3f9921 Introduce SemVer4j for version representation, parsing and handling. And correct supported upgrade paths. Add v4X to Java DTests (after cassandra-4.0 branch was created) new 0a84dda Merge branch 'cassandra-2.2' into cassandra-3.0 The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: build.xml | 2 +- .../cassandra/distributed/impl/InstanceConfig.java | 14 ++-- .../upgrade/CompactStorage2to3UpgradeTest.java | 23 +++ .../upgrade/DropCompactStorageTest.java| 7 +- .../upgrade/MigrateDropColumnsTest.java| 3 +- .../upgrade/MixedModeRangeTombstoneTest.java | 2 +- .../upgrade/MixedModeReadRepairTest.java | 4 +- .../cassandra/distributed/upgrade/PagingTest.java | 2 +- .../cassandra/distributed/upgrade/UpgradeTest.java | 27 +--- .../distributed/upgrade/UpgradeTestBase.java | 77 +++--- 10 files changed, 83 insertions(+), 78 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16649) Add Versions.Major.v4X to Java DTests (after cassandra-4.0 branch was created)
[ https://issues.apache.org/jira/browse/CASSANDRA-16649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16649: --- Status: Ready to Commit (was: Review In Progress) > Add Versions.Major.v4X to Java DTests (after cassandra-4.0 branch was created) > -- > > Key: CASSANDRA-16649 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16649 > Project: Cassandra > Issue Type: Sub-task > Components: Test/dtest/java >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 2.2.x, 3.0.x, 3.11.x, 4.0.x, 4.x > > > - > https://github.com/apache/cassandra-in-jvm-dtest-api/compare/trunk...thelastpickle:mck/16649 > - > https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/16649/trunk > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16649) Add Versions.Major.v4X to Java DTests (after cassandra-4.0 branch was created)
[ https://issues.apache.org/jira/browse/CASSANDRA-16649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379384#comment-17379384 ] Michael Semb Wever commented on CASSANDRA-16649: CI full pipelines using the released 0.0.8: - 3.0 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/930/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/930/] - 3.11 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/931/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/931/] - 4.0 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/932/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/932/] - trunk [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/933/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/933/] > Add Versions.Major.v4X to Java DTests (after cassandra-4.0 branch was created) > -- > > Key: CASSANDRA-16649 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16649 > Project: Cassandra > Issue Type: Sub-task > Components: Test/dtest/java >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 2.2.x, 3.0.x, 3.11.x, 4.0.x, 4.x > > > - > https://github.com/apache/cassandra-in-jvm-dtest-api/compare/trunk...thelastpickle:mck/16649 > - > https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/16649/trunk > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16761) New Cassandra Website and Documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-16761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379345#comment-17379345 ] Michael Semb Wever commented on CASSANDRA-16761: Feedback on things still to fix: * change antora's component name from "Project" to "_" (and fix nav links accordingly) * remove duplicated previous adoc files (e.g. index.adoc, download-old.adoc, …) * rename home.html to index.html * add latest blog page * new version 4.0-rc2 on download page * "Learn more" button appears twice on front page * links to /Cassandra/ need to be replaced with /doc/latest/ * the links to the Community pages don't work (from top nav) * create a .htaccess file to map legacy URLs to new URL ( and / into /_/index.html ) * copying site-content/build/html/* into content/ (while keeping the /doc/ folder ) > New Cassandra Website and Documentation > --- > > Key: CASSANDRA-16761 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16761 > Project: Cassandra > Issue Type: Epic > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Anthony Grasso >Priority: High > Fix For: 4.0.x > > > This epic captures the work associated with the development of the new > Cassandra website and documentation. > Work to create the new website and documentation will be broken up as follows: > * Proof of concept - CASSANDRA-16029 > * Website concept and design - CASSANDRA-16115 > * Develop tooling to render new website and documentation - CASSANDRA-16066 > * Create website content that will be rendered by new tooling - > CASSANDRA-16762 > * Create Cassandra documentation content that will be rendered by new > tooling - CASSANDRA-16763 > It is expected that the new website and documentation will be in asciidoc > format and rendered using Antora. > Antora is purpose built for rendering versioned documentation to HTML. In > addition it allows rendering customisations via Java Script which may be > useful when rending the website. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.0.0 updated (b428552 -> 69b8cc5)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch cassandra-4.0.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git. from b428552 Fix CassandraVersion::compareTo add 69b8cc5 Prepare debian changelog for 4.0.0 No new revisions were added by this update. Summary of changes: debian/changelog | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.0.0' into cassandra-4.0
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 51f16a30b010151d55b53065c009ab8c4c77567c Merge: 330cde6 69b8cc5 Author: Mick Semb Wever AuthorDate: Mon Jul 12 20:33:48 2021 +0200 Merge branch 'cassandra-4.0.0' into cassandra-4.0 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (58515c2 -> 25b75df)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 58515c2 Merge branch cassandra-4.0 into trunk add 69b8cc5 Prepare debian changelog for 4.0.0 new 51f16a3 Merge branch 'cassandra-4.0.0' into cassandra-4.0 new 25b75df Merge branch 'cassandra-4.0' into trunk The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.0' into trunk
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 25b75dfe64e350443afa020cfa9d226dd520a8c4 Merge: 58515c2 51f16a3 Author: Mick Semb Wever AuthorDate: Mon Jul 12 20:36:10 2021 +0200 Merge branch 'cassandra-4.0' into trunk - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.0 updated (330cde6 -> 51f16a3)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 330cde6 Merge branch cassandra-4.0.0 into cassandra-4.0 add 69b8cc5 Prepare debian changelog for 4.0.0 new 51f16a3 Merge branch 'cassandra-4.0.0' into cassandra-4.0 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: - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r48799 - in /dev/cassandra/4.0.0/redhat: ./ repodata/
Author: mck Date: Mon Jul 12 18:28:05 2021 New Revision: 48799 Log: staging cassandra rpm packages for 4.0.0 Added: dev/cassandra/4.0.0/redhat/ dev/cassandra/4.0.0/redhat/cassandra-4.0.0-1.noarch.rpm (with props) dev/cassandra/4.0.0/redhat/cassandra-4.0.0-1.src.rpm (with props) dev/cassandra/4.0.0/redhat/cassandra-tools-4.0.0-1.noarch.rpm (with props) dev/cassandra/4.0.0/redhat/repodata/ dev/cassandra/4.0.0/redhat/repodata/12830058a70d01bf0f5325525e6dcfbe300dc2ecaa84e9d1108d935c3b6acf43-primary.sqlite.bz2 (with props) dev/cassandra/4.0.0/redhat/repodata/12830058a70d01bf0f5325525e6dcfbe300dc2ecaa84e9d1108d935c3b6acf43-primary.sqlite.bz2.asc dev/cassandra/4.0.0/redhat/repodata/256c67edf33d5c312281dfa1c0270c93cd0ba1fa07279f01e971036110579f78-filelists.sqlite.bz2 (with props) dev/cassandra/4.0.0/redhat/repodata/256c67edf33d5c312281dfa1c0270c93cd0ba1fa07279f01e971036110579f78-filelists.sqlite.bz2.asc dev/cassandra/4.0.0/redhat/repodata/43e55dabb06e6e564906e63b0a640df1eed6dbca4e0a28781fdbdf4425e787a3-other.xml.gz (with props) dev/cassandra/4.0.0/redhat/repodata/43e55dabb06e6e564906e63b0a640df1eed6dbca4e0a28781fdbdf4425e787a3-other.xml.gz.asc dev/cassandra/4.0.0/redhat/repodata/53a136435776ecb487d8ffe6bae5410f1d6308b06b59aeee35cf357bfb392515-primary.xml.gz (with props) dev/cassandra/4.0.0/redhat/repodata/53a136435776ecb487d8ffe6bae5410f1d6308b06b59aeee35cf357bfb392515-primary.xml.gz.asc dev/cassandra/4.0.0/redhat/repodata/d9fe92c9093b6d56622b2ad041b29490237055501d56a24b105719da06cba17c-filelists.xml.gz (with props) dev/cassandra/4.0.0/redhat/repodata/d9fe92c9093b6d56622b2ad041b29490237055501d56a24b105719da06cba17c-filelists.xml.gz.asc dev/cassandra/4.0.0/redhat/repodata/dc0a406573f6daf718d6ea2570fe53356618deaaaf3bd819468a7c06f9c9a0dc-other.sqlite.bz2 (with props) dev/cassandra/4.0.0/redhat/repodata/dc0a406573f6daf718d6ea2570fe53356618deaaaf3bd819468a7c06f9c9a0dc-other.sqlite.bz2.asc dev/cassandra/4.0.0/redhat/repodata/repomd.xml dev/cassandra/4.0.0/redhat/repodata/repomd.xml.asc Added: dev/cassandra/4.0.0/redhat/cassandra-4.0.0-1.noarch.rpm == Binary file - no diff available. Propchange: dev/cassandra/4.0.0/redhat/cassandra-4.0.0-1.noarch.rpm -- svn:mime-type = application/octet-stream Added: dev/cassandra/4.0.0/redhat/cassandra-4.0.0-1.src.rpm == Binary file - no diff available. Propchange: dev/cassandra/4.0.0/redhat/cassandra-4.0.0-1.src.rpm -- svn:mime-type = application/octet-stream Added: dev/cassandra/4.0.0/redhat/cassandra-tools-4.0.0-1.noarch.rpm == Binary file - no diff available. Propchange: dev/cassandra/4.0.0/redhat/cassandra-tools-4.0.0-1.noarch.rpm -- svn:mime-type = application/octet-stream Added: dev/cassandra/4.0.0/redhat/repodata/12830058a70d01bf0f5325525e6dcfbe300dc2ecaa84e9d1108d935c3b6acf43-primary.sqlite.bz2 == Binary file - no diff available. Propchange: dev/cassandra/4.0.0/redhat/repodata/12830058a70d01bf0f5325525e6dcfbe300dc2ecaa84e9d1108d935c3b6acf43-primary.sqlite.bz2 -- svn:mime-type = application/octet-stream Added: dev/cassandra/4.0.0/redhat/repodata/12830058a70d01bf0f5325525e6dcfbe300dc2ecaa84e9d1108d935c3b6acf43-primary.sqlite.bz2.asc == --- dev/cassandra/4.0.0/redhat/repodata/12830058a70d01bf0f5325525e6dcfbe300dc2ecaa84e9d1108d935c3b6acf43-primary.sqlite.bz2.asc (added) +++ dev/cassandra/4.0.0/redhat/repodata/12830058a70d01bf0f5325525e6dcfbe300dc2ecaa84e9d1108d935c3b6acf43-primary.sqlite.bz2.asc Mon Jul 12 18:28:05 2021 @@ -0,0 +1,16 @@ +-BEGIN PGP SIGNATURE- + +iQIzBAABCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmDsiZ0ACgkQ6RM1134+ +h8s5RQ/8CGxPqhyVC3I7+Fffb5ed64CoefHphAuy0ebkMtdxQ2oRqIkFhZ+WuIt4 +giph3a0DdBLKq61a++5wPP3nTWEPJ9V8JhHy5uHCLg/UgCOvj9Qmitvi0BQsVZaH +UfuRszMnF2C+lUT3yKRz6xXbsQfm7e7UQwbUXPzAXOQlFjxP1Uz/7H6kwU7le87n +9bvNNe3VFzaA1BbJW2z3+tyg+Ia1B8PEyI4tuChk52WIDumNrw9DF36RjYmfVxle +8TJr+6yX2NMy0pbvo1lKdN3/wrlBBRFziK8SOWZ5BqlY0igR1MhKSsp8ay4KTmdC +kXmiMizN/RRX94aIyRa1Tk2sB+WieXYQT/wcKXApbV19v/jnF0sVaYccCBiV615M +WDtkcIYlmCcsl5BtBiA1ucRM4HO4MBu+WVgfLj/QDcQTFfMOK9EBq8xz8WyBmUUT +efTQbt7bmkYHxOKfrRpdBi0qVN1e7HSeYKUVP4DHOBmisdkvkJdRXE/IelDjapIO ++KtdXjRdK7mXfrSOn8YE1D9UILZ1mfDRW1LKTXwEpKOEGGnmdGOXkAZuvUQYO6xu +8kIPoZf3mpaR1lTBRFKL35Z6Ur/A7uipinyBFxPp4o/3iD7ljH
svn commit: r48798 - in /dev/cassandra/4.0.0/debian: ./ dists/ dists/40x/ dists/40x/main/ dists/40x/main/binary-amd64/ dists/40x/main/binary-arm64/ dists/40x/main/binary-i386/ dists/40x/main/source/ p
Author: mck Date: Mon Jul 12 18:15:41 2021 New Revision: 48798 Log: staging cassandra debian packages for 4.0.0 Added: dev/cassandra/4.0.0/debian/ dev/cassandra/4.0.0/debian/cassandra-tools_4.0.0_all.deb (with props) dev/cassandra/4.0.0/debian/cassandra_4.0.0.dsc dev/cassandra/4.0.0/debian/cassandra_4.0.0.tar.gz (with props) dev/cassandra/4.0.0/debian/cassandra_4.0.0_all.deb (with props) dev/cassandra/4.0.0/debian/cassandra_4.0.0_amd64.buildinfo dev/cassandra/4.0.0/debian/cassandra_4.0.0_amd64.changes dev/cassandra/4.0.0/debian/dists/ dev/cassandra/4.0.0/debian/dists/40x/ dev/cassandra/4.0.0/debian/dists/40x/InRelease dev/cassandra/4.0.0/debian/dists/40x/Release dev/cassandra/4.0.0/debian/dists/40x/Release.gpg dev/cassandra/4.0.0/debian/dists/40x/main/ dev/cassandra/4.0.0/debian/dists/40x/main/binary-amd64/ dev/cassandra/4.0.0/debian/dists/40x/main/binary-amd64/Packages dev/cassandra/4.0.0/debian/dists/40x/main/binary-amd64/Packages.gz (with props) dev/cassandra/4.0.0/debian/dists/40x/main/binary-amd64/Release dev/cassandra/4.0.0/debian/dists/40x/main/binary-arm64/ dev/cassandra/4.0.0/debian/dists/40x/main/binary-arm64/Packages dev/cassandra/4.0.0/debian/dists/40x/main/binary-arm64/Packages.gz (with props) dev/cassandra/4.0.0/debian/dists/40x/main/binary-arm64/Release dev/cassandra/4.0.0/debian/dists/40x/main/binary-i386/ dev/cassandra/4.0.0/debian/dists/40x/main/binary-i386/Packages dev/cassandra/4.0.0/debian/dists/40x/main/binary-i386/Packages.gz (with props) dev/cassandra/4.0.0/debian/dists/40x/main/binary-i386/Release dev/cassandra/4.0.0/debian/dists/40x/main/source/ dev/cassandra/4.0.0/debian/dists/40x/main/source/Release dev/cassandra/4.0.0/debian/dists/40x/main/source/Sources.gz (with props) dev/cassandra/4.0.0/debian/pool/ dev/cassandra/4.0.0/debian/pool/main/ dev/cassandra/4.0.0/debian/pool/main/c/ dev/cassandra/4.0.0/debian/pool/main/c/cassandra/ dev/cassandra/4.0.0/debian/pool/main/c/cassandra/cassandra-tools_4.0.0_all.deb (with props) dev/cassandra/4.0.0/debian/pool/main/c/cassandra/cassandra_4.0.0.dsc dev/cassandra/4.0.0/debian/pool/main/c/cassandra/cassandra_4.0.0.tar.gz (with props) dev/cassandra/4.0.0/debian/pool/main/c/cassandra/cassandra_4.0.0_all.deb (with props) Added: dev/cassandra/4.0.0/debian/cassandra-tools_4.0.0_all.deb == Binary file - no diff available. Propchange: dev/cassandra/4.0.0/debian/cassandra-tools_4.0.0_all.deb -- svn:mime-type = application/octet-stream Added: dev/cassandra/4.0.0/debian/cassandra_4.0.0.dsc == --- dev/cassandra/4.0.0/debian/cassandra_4.0.0.dsc (added) +++ dev/cassandra/4.0.0/debian/cassandra_4.0.0.dsc Mon Jul 12 18:15:41 2021 @@ -0,0 +1,41 @@ +-BEGIN PGP SIGNED MESSAGE- +Hash: SHA512 + +Format: 1.0 +Source: cassandra +Binary: cassandra, cassandra-tools +Architecture: all +Version: 4.0.0 +Maintainer: Eric Evans +Uploaders: Sylvain Lebresne +Homepage: http://cassandra.apache.org +Standards-Version: 3.8.3 +Vcs-Browser: https://gitbox.apache.org/repos/asf?p=cassandra.git +Vcs-Git: https://gitbox.apache.org/repos/asf/cassandra.git +Build-Depends: debhelper (>= 11), openjdk-8-jdk | java8-jdk, ant (>= 1.9), ant-optional (>= 1.9), dh-python, python3-dev (>= 3.6), quilt, bash-completion +Package-List: + cassandra deb misc extra arch=all + cassandra-tools deb misc extra arch=all +Checksums-Sha1: + 8e6f362f474817263c20376494c3b53edac7543c 237422573 cassandra_4.0.0.tar.gz +Checksums-Sha256: + 1d624df471c81a0c606bb45dc0da903f0e892c2181d0d4c6a4b450a95a184879 237422573 cassandra_4.0.0.tar.gz +Files: + 2ca27fd79a978cebf8ddfd739e2798de 237422573 cassandra_4.0.0.tar.gz + +-BEGIN PGP SIGNATURE- + +iQIzBAEBCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmDshgUACgkQ6RM1134+ +h8unCQ//VU46Y+Peu5fy+X5G8t/5mZQBxC4/A9RGpe5ZmojNXm6m3trjGXeD9XKy +TnnnrGXTRw3teQMhSUrCWudKEuegME78xoBxQYYeWH+PILtnKJ2ByWmc+D8aC7T4 +ULYWhFnewZGxNylJnRgrwuyaybZo5lWx2UuiYnUf+BRwa3YyIBaPmPy3TUmyvjFu +MH+Z8cHyK/DyREP5jA8yySzkHaRQlwZAvQz9b5Ym6tVnk+VpKzJOq24Te+CbNpQ+ +mGlui12pFCZWcu9lsbgYxk68TcnaAfckAZEba2fbU2LH0NnFAkIIBQpcJ6BkWBF0 +xoZvlJeEuilA9UVtf4BeIxcC8u6NspbiJDMGSlfSwlMlJ7LOASP51jPd2dpUB2c7 +xVj4QwERwZHNjA+tzgAiluqEKMtmhwjXFhTGoE8dHGulYL2DdQtdMqBpQwsqN5Y2 +sC3Xt+BStkwSGXty3PblzD5VPiw0zhHsOUtJQOQxER1WQbuLnyrOb+0XaGwQiiZQ +bc9qaqF8fFuk5FFIwBWvXbakLZYfBsNOmGh2ZRxrEtrH9jbozxjW0QMCMV0AQpWT +vQvLfcItU3mUcgAxYj5LC31oAi+IGP8XtBTJWDr8FDVDZM8ki8hgM88v9UwzBUnc ++jzmuPv6viZ5N78hco7048uEsVQm1RL6wCZoC9XLm/0Dc2IwsW8= +=M41C +-END PGP SIGNATURE- Added: dev/cassandra/4.0.0/debian/cassandra_4.0.0.tar.gz == Binary file - no diff
svn commit: r48796 - /dev/cassandra/4.0.0/
Author: mck Date: Mon Jul 12 17:56:59 2021 New Revision: 48796 Log: staging cassandra 4.0.0 Added: dev/cassandra/4.0.0/ dev/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz (with props) dev/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz.asc dev/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz.sha256 dev/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz.sha512 dev/cassandra/4.0.0/apache-cassandra-4.0.0-src.tar.gz (with props) dev/cassandra/4.0.0/apache-cassandra-4.0.0-src.tar.gz.asc dev/cassandra/4.0.0/apache-cassandra-4.0.0-src.tar.gz.sha256 dev/cassandra/4.0.0/apache-cassandra-4.0.0-src.tar.gz.sha512 Added: dev/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz == Binary file - no diff available. Propchange: dev/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz -- svn:mime-type = application/octet-stream Added: dev/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz.asc == --- dev/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz.asc (added) +++ dev/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz.asc Mon Jul 12 17:56:59 2021 @@ -0,0 +1,16 @@ +-BEGIN PGP SIGNATURE- + +iQIzBAABCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmDsgfwACgkQ6RM1134+ +h8sB1Q//UXMmZbiP4cQKhXBW6zPVqYzqSUSEsVoB9200QDZjFF5Cv4MSq0K6NNB8 +6wPxPVUFPdMdvMF3o4VXpjoN7ANk+LmfG2KUzU9npSv4i+SOUqvYHSh1tUQFGWRo +ommn5D/7bzPYYd5c3OaSvinzYXd0IByyQHS4FO8MNvyR/5TyuTVJ3y6Tb5CIkvMR +lRBbYYy6e/l8Bm1DKTmCllmfXAbJRbKLh611gk/OrqKNFKEznfLu2LiH2QUdxh3k +m6n4YpUE0nOTjs89hiZjaL2zjkLskjiNSe7QcIpj7tRBpd9rm5S7RIKW6fJbtGFU +n6brdaw9m8284LunXLc7ShlBvDYvoZs/PhsVkYpK/LsolC3aKPY2sqVhUs1J7QAj +Ozzhwmbi2YW4rXhAQPfdSKEWu/8ZImCOOwWVqkh4aKBYT5UX1A2CwMx7CNxgeCWk +C1qofvEQEN6fWLyv0f8tDxbqCrz+Si3ic8hx+688zInzl5WL4PQbNe6EPW5/wPtW +Ms5CBXYzqhVL15JQLSZ5FIAmdU9C+cDUAwEqazAm8R0gawS6KN6L8hFfeRhnYLiV +h6rP4FmZ4jaa2aQuUsq/tTmcV2JiD9Hb/Z3Qb1KtfFWjMPN1zROv1S2zMLoCfwvN +waq92SoaIl0IQKFHYOz1RBJTYSMZFb/UN4IRuYpvGRlIUfDjvtw= +=4XE+ +-END PGP SIGNATURE- Added: dev/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz.sha256 == --- dev/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz.sha256 (added) +++ dev/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz.sha256 Mon Jul 12 17:56:59 2021 @@ -0,0 +1 @@ +73a07db76169bb3902aa0781e78a1344c1c87a8ecb1ed0ea80b1f832066dfd73 Added: dev/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz.sha512 == --- dev/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz.sha512 (added) +++ dev/cassandra/4.0.0/apache-cassandra-4.0.0-bin.tar.gz.sha512 Mon Jul 12 17:56:59 2021 @@ -0,0 +1 @@ +de11fd549c2d45ade2414b08f42becfc806fbe973168f96d65a21e91caffd5a0d716ad3173278c4d24045d5f6fd9e8cc7fb08cc97087532f9a2684397e7dd424 Added: dev/cassandra/4.0.0/apache-cassandra-4.0.0-src.tar.gz == Binary file - no diff available. Propchange: dev/cassandra/4.0.0/apache-cassandra-4.0.0-src.tar.gz -- svn:mime-type = application/octet-stream Added: dev/cassandra/4.0.0/apache-cassandra-4.0.0-src.tar.gz.asc == --- dev/cassandra/4.0.0/apache-cassandra-4.0.0-src.tar.gz.asc (added) +++ dev/cassandra/4.0.0/apache-cassandra-4.0.0-src.tar.gz.asc Mon Jul 12 17:56:59 2021 @@ -0,0 +1,16 @@ +-BEGIN PGP SIGNATURE- + +iQIzBAABCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmDsggAACgkQ6RM1134+ +h8sYvQ/9FOgkQxH2TJEAUn9+IpnmDNpFVlzbcySuzcs46AqWqBHUdNJc7yJiyvAb +2QG/T040igc4DgFTrEw9A/bC1PswCH0GAIKIouEao0aM8arZhm0ogKLH4PWuFwO7 +NYf6w4KhrwRd1JHjtoS9japh9C0QTP4CDYAa9zLjH+yDEWCUkJOQGd53zm5LNO0g +/9HyLIFt0rLM9OSc5Od8MZQA63gmXIfuZ94vrhFpCP4I1CVAWvpGP7buciJyQJry ++OwqgXVUFBO7ShfZeeOmnxsXHU6gVEkvbkpANGk5w+XNx6j6yhUefdGScPp3AueB +0DHCg8Igy/5bAlGqK7XWHniIf7pQUQ7mcCAIYaTRVUhntF83SHe+L+wBcP/Ua+rZ +noTm7bVhkrCY5EPeiy+6zJIXLdbVHs0oaFVfNr4gVNYzxbqTxCnh/daZ8YcS4a/M +qznJescwPn7TusaOVznWt2D+sFWlqwTJc1BHvS+euvN/ft16b5K5bJsKvmcx/kP2 +yIVPlbcQtKQYbnkPTD1Q3PMpLVGEmviQhfoaR/uz7P9Y3rkoq+F84OR3CZI2WKqt +EOol7McuKJFehnEDniRfcp6/Pyxk6bPgq5KRztupMK99E6UotXzcc+vqQnoJjbWE +SeP+zet4++yTPCKQQcJyag6KFHt3UQUX6E7jJybm1CBzSur0tf4= +=70rA +-END PGP SIGNATURE- Added: dev/cassandra/4.0.0/apache-cassandra-4.0.0-src.tar.gz.sha256 == --- dev/cassandra/4.0.0/apache-cassandra-4.0.0-src.tar.gz.sha256 (added) +++ dev/cassandra/4.0.0/apache-cassandra-4.0.0-src.tar.gz.sha256 Mon Jul 12 17:56:59 2021 @@ -0,0 +1 @@ +a69d13660dee1c98536f9f723fee46f2d62d64a20544c7d92b0134d7bc7ffbd9 Added: dev/cassandra/4.0.0/apache-
[cassandra] tag 4.0.0-tentative created (now 69b8cc5)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to tag 4.0.0-tentative in repository https://gitbox.apache.org/repos/asf/cassandra.git. at 69b8cc5 (commit) This tag includes the following new commits: new 69b8cc5 Prepare debian changelog for 4.0.0 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. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Prepare debian changelog for 4.0.0
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to tag 4.0.0-tentative in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 69b8cc5cecc196fddb549f2edf01d962e7ef2dae Author: Mick Semb Wever AuthorDate: Mon Jul 12 19:48:49 2021 +0200 Prepare debian changelog for 4.0.0 --- debian/changelog | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index 12f38ca..c8ee807 100644 --- a/debian/changelog +++ b/debian/changelog @@ -2,7 +2,7 @@ cassandra (4.0.0) unstable; urgency=medium * New release - -- Mick Thu, 08 Jul 2021 23:49:23 +0200 + -- Mick Semb Wever Mon, 12 Jul 2021 19:48:05 +0200 cassandra (4.0~rc2) unstable; urgency=medium - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-14162) Backport 7950 (Output of nodetool compactionstats and compactionhistory does not work well with long keyspace and column family names)
[ https://issues.apache.org/jira/browse/CASSANDRA-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379255#comment-17379255 ] Ekaterina Dimitrova edited comment on CASSANDRA-14162 at 7/12/21, 5:41 PM: --- As it is only sorted representation, probably it is fine but normally we don't backport new behaviors. I think that was the reason also to discuss initially whether this patch should be really backported at all. Cassandra has that behavior of having pain in the leg when you slap her in the face even after smallest changes, so I felt it's worth mentioning that change before any commit. Thank you both was (Author: e.dimitrova): As it is only sorted representation, probably it is fine but normally we don't backport new behaviors. I think that was the reason also to discuss initially whether this patch should be really backported at all. Cassandra has that behavior of having pain in the leg wen you slap her in the face even after smallest changes, so I felt it's worth mentioning that change before any commit. Thank you both > Backport 7950 (Output of nodetool compactionstats and compactionhistory does > not work well with long keyspace and column family names) > -- > > Key: CASSANDRA-14162 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14162 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Tools >Reporter: Kurt Greaves >Assignee: Stefan Miklosovic >Priority: Low > Fix For: 3.0.25 > > Attachments: 14162-3.0.patch, Screenshot from 2018-01-11 > 01-02-02.png, Screenshot from 2018-01-11 01-02-46.png, Screenshot from > 2018-01-11 01-02-51.png > > > Colleagues have had issues with output of listsnapshots/compactionstats > because of things with really long names. Mostly cosmetic but I see no reason > we shouldn't backport CASSANDRA-7950 to 3.0. It's practically a bugfix. I've > attached a patch and a bunch of images to show the relevant commands working > as intended after applying the patch. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16796) Clear pending ranges for a SHUTDOWN peer
[ https://issues.apache.org/jira/browse/CASSANDRA-16796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-16796: Description: If a node involved in a MOVE operation should fail, peers can sometimes maintain pending ranges for it even when it has left the ring and/or been replaced (in practice until the peer is next bounced). This in turn can lead to bogus unavailable responses to clients if a replica for the any of the pending ranges should go down. If the moving node crashes hard, a subsequent replacement will correctly fail as long as cassandra.consistent.rangemovement is set to true because the new node will learn the MOVING status from the remaining peers. A graceful shutdown, however, causes that status to be replaced with SHUTDOWN, but doesn't update TokenMetadata, so pending ranges remain for the down node, even after it has been removed from the ring. was: If a node involved in a MOVE operation should fail, peers can sometimes maintain pending ranges even when it has left the ring and/or been replaced (in practice until the peer is next bounced). This in turn can lead to bogus unavailable responses to clients if a replica for the any of the pending ranges should go down. If the moving node crashes hard, a subsequent replacement will correctly fail as long as cassandra.consistent.rangemovement is set to true because the new node will learn the MOVING status from the remaining peers. A graceful shutdown, however, causes that status to be replaced with SHUTDOWN, but doesn't update TokenMetadata, so pending ranges remain for the down node, even after it has been removed from the ring. > Clear pending ranges for a SHUTDOWN peer > > > Key: CASSANDRA-16796 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16796 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Membership >Reporter: Sam Tunnicliffe >Assignee: Sam Tunnicliffe >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x > > > If a node involved in a MOVE operation should fail, peers can sometimes > maintain pending ranges for it even when it has left the ring and/or been > replaced (in practice until the peer is next bounced). This in turn can lead > to bogus unavailable responses to clients if a replica for the any of the > pending ranges should go down. > If the moving node crashes hard, a subsequent replacement will correctly fail > as long as cassandra.consistent.rangemovement is set to true because the new > node will learn the MOVING status from the remaining peers. A graceful > shutdown, however, causes that status to be replaced with SHUTDOWN, but > doesn't update TokenMetadata, so pending ranges remain for the down node, > even after it has been removed from the ring. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16796) Clear pending ranges for a SHUTDOWN peer
[ https://issues.apache.org/jira/browse/CASSANDRA-16796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-16796: Test and Documentation Plan: new dtest added Status: Patch Available (was: Open) ||branch||Circle CI|| |[16796-3.0|https://github.com/beobal/cassandra/tree/16796-3.0]|[circle|https://circleci.com/gh/beobal/cassandra?branch=16796-3.0]| |[16796-3.11|https://github.com/beobal/cassandra/tree/16796-3.11]|[circle|https://circleci.com/gh/beobal/cassandra?branch=16796-3.11]| |[16796-4.0|https://github.com/beobal/cassandra/tree/16796-4.0]|[circle|https://circleci.com/gh/beobal/cassandra?branch=16796-4.0]| |[16796-trunk|https://github.com/beobal/cassandra/tree/16796-trunk]|[circle|https://circleci.com/gh/beobal/cassandra?branch=16796-trunk]| The 3.0/3.11 & 4.0/trunk patches are basically the same, so I've only kicked off ci-c jobs for [3.0|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/936] and [4.0|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/936] > Clear pending ranges for a SHUTDOWN peer > > > Key: CASSANDRA-16796 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16796 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Membership >Reporter: Sam Tunnicliffe >Assignee: Sam Tunnicliffe >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x > > > If a node involved in a MOVE operation should fail, peers can sometimes > maintain pending ranges even when it has left the ring and/or been replaced > (in practice until the peer is next bounced). This in turn can lead to bogus > unavailable responses to clients if a replica for the any of the pending > ranges should go down. > If the moving node crashes hard, a subsequent replacement will correctly fail > as long as cassandra.consistent.rangemovement is set to true because the new > node will learn the MOVING status from the remaining peers. A graceful > shutdown, however, causes that status to be replaced with SHUTDOWN, but > doesn't update TokenMetadata, so pending ranges remain for the down node, > even after it has been removed from the ring. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16796) Clear pending ranges for a SHUTDOWN peer
[ https://issues.apache.org/jira/browse/CASSANDRA-16796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-16796: Bug Category: Parent values: Availability(12983)Level 1 values: Unavailable(12994) Complexity: Normal Discovered By: User Report Fix Version/s: 4.0.x 3.11.x 3.0.x Severity: Normal Status: Open (was: Triage Needed) > Clear pending ranges for a SHUTDOWN peer > > > Key: CASSANDRA-16796 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16796 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Membership >Reporter: Sam Tunnicliffe >Assignee: Sam Tunnicliffe >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x > > > If a node involved in a MOVE operation should fail, peers can sometimes > maintain pending ranges even when it has left the ring and/or been replaced > (in practice until the peer is next bounced). This in turn can lead to bogus > unavailable responses to clients if a replica for the any of the pending > ranges should go down. > If the moving node crashes hard, a subsequent replacement will correctly fail > as long as cassandra.consistent.rangemovement is set to true because the new > node will learn the MOVING status from the remaining peers. A graceful > shutdown, however, causes that status to be replaced with SHUTDOWN, but > doesn't update TokenMetadata, so pending ranges remain for the down node, > even after it has been removed from the ring. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-14162) Backport 7950 (Output of nodetool compactionstats and compactionhistory does not work well with long keyspace and column family names)
[ https://issues.apache.org/jira/browse/CASSANDRA-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379255#comment-17379255 ] Ekaterina Dimitrova edited comment on CASSANDRA-14162 at 7/12/21, 4:36 PM: --- As it is only sorted representation, probably it is fine but normally we don't backport new behaviors. I think that was the reason also to discuss initially whether this patch should be really backported at all. Cassandra has that behavior of having pain in the leg wen you slap her in the face even after smallest changes, so I felt it's worth mentioning that change before any commit. Thank you both was (Author: e.dimitrova): As it is only sorted representation, probably it is fine but normally we don't backport new behaviors. I think that was the reason also to discuss initially whether this patch should be really backported at all. Cassandra has that behavior of having pain in the leg wen you slap her in the face even after smallest changes, so I felt worth mentioning that change before any commit. Thank you both > Backport 7950 (Output of nodetool compactionstats and compactionhistory does > not work well with long keyspace and column family names) > -- > > Key: CASSANDRA-14162 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14162 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Tools >Reporter: Kurt Greaves >Assignee: Stefan Miklosovic >Priority: Low > Fix For: 3.0.25 > > Attachments: 14162-3.0.patch, Screenshot from 2018-01-11 > 01-02-02.png, Screenshot from 2018-01-11 01-02-46.png, Screenshot from > 2018-01-11 01-02-51.png > > > Colleagues have had issues with output of listsnapshots/compactionstats > because of things with really long names. Mostly cosmetic but I see no reason > we shouldn't backport CASSANDRA-7950 to 3.0. It's practically a bugfix. I've > attached a patch and a bunch of images to show the relevant commands working > as intended after applying the patch. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-14162) Backport 7950 (Output of nodetool compactionstats and compactionhistory does not work well with long keyspace and column family names)
[ https://issues.apache.org/jira/browse/CASSANDRA-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379255#comment-17379255 ] Ekaterina Dimitrova edited comment on CASSANDRA-14162 at 7/12/21, 4:36 PM: --- As it is only sorted representation, probably it is fine but normally we don't backport new behaviors. I think that was the reason also to discuss initially whether this patch should be really backported at all. Cassandra has that behavior of having pain in the leg wen you slap her in the face even after smallest changes, so I felt worth mentioning that change before any commit. Thank you both was (Author: e.dimitrova): As it is only sorted representation, probably it is fine but normally we don't backport new behaviors. I think that was the reason also to discuss initially whether this patch should be really backported at all. Cassandra has that behavior of having pain in the leg wen you slap her in the face, so I felt worth mentioning that change before any commit. Thank you both > Backport 7950 (Output of nodetool compactionstats and compactionhistory does > not work well with long keyspace and column family names) > -- > > Key: CASSANDRA-14162 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14162 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Tools >Reporter: Kurt Greaves >Assignee: Stefan Miklosovic >Priority: Low > Fix For: 3.0.25 > > Attachments: 14162-3.0.patch, Screenshot from 2018-01-11 > 01-02-02.png, Screenshot from 2018-01-11 01-02-46.png, Screenshot from > 2018-01-11 01-02-51.png > > > Colleagues have had issues with output of listsnapshots/compactionstats > because of things with really long names. Mostly cosmetic but I see no reason > we shouldn't backport CASSANDRA-7950 to 3.0. It's practically a bugfix. I've > attached a patch and a bunch of images to show the relevant commands working > as intended after applying the patch. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14162) Backport 7950 (Output of nodetool compactionstats and compactionhistory does not work well with long keyspace and column family names)
[ https://issues.apache.org/jira/browse/CASSANDRA-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379255#comment-17379255 ] Ekaterina Dimitrova commented on CASSANDRA-14162: - As it is only sorted representation, probably it is fine but normally we don't backport new behaviors. I think that was the reason also to discuss initially whether this patch should be really backported at all. Cassandra has that behavior of having pain in the leg wen you slap her in the face, so I felt worth mentioning that change before any commit. Thank you both > Backport 7950 (Output of nodetool compactionstats and compactionhistory does > not work well with long keyspace and column family names) > -- > > Key: CASSANDRA-14162 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14162 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Tools >Reporter: Kurt Greaves >Assignee: Stefan Miklosovic >Priority: Low > Fix For: 3.0.25 > > Attachments: 14162-3.0.patch, Screenshot from 2018-01-11 > 01-02-02.png, Screenshot from 2018-01-11 01-02-46.png, Screenshot from > 2018-01-11 01-02-51.png > > > Colleagues have had issues with output of listsnapshots/compactionstats > because of things with really long names. Mostly cosmetic but I see no reason > we shouldn't backport CASSANDRA-7950 to 3.0. It's practically a bugfix. I've > attached a patch and a bunch of images to show the relevant commands working > as intended after applying the patch. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14162) Backport 7950 (Output of nodetool compactionstats and compactionhistory does not work well with long keyspace and column family names)
[ https://issues.apache.org/jira/browse/CASSANDRA-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379251#comment-17379251 ] Brandon Williams commented on CASSANDRA-14162: -- It seems to me the only reason not to port the sorting would be to preserve old behavior, but we're already not doing that in this patch. We're better off having the output match in all versions rather than having this one still be the odd ball. > Backport 7950 (Output of nodetool compactionstats and compactionhistory does > not work well with long keyspace and column family names) > -- > > Key: CASSANDRA-14162 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14162 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Tools >Reporter: Kurt Greaves >Assignee: Stefan Miklosovic >Priority: Low > Fix For: 3.0.25 > > Attachments: 14162-3.0.patch, Screenshot from 2018-01-11 > 01-02-02.png, Screenshot from 2018-01-11 01-02-46.png, Screenshot from > 2018-01-11 01-02-51.png > > > Colleagues have had issues with output of listsnapshots/compactionstats > because of things with really long names. Mostly cosmetic but I see no reason > we shouldn't backport CASSANDRA-7950 to 3.0. It's practically a bugfix. I've > attached a patch and a bunch of images to show the relevant commands working > as intended after applying the patch. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14930) decommission may cause timeout because messaging backlog is cleared
[
https://issues.apache.org/jira/browse/CASSANDRA-14930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-14930:
-
Status: Needs Reviewer (was: Review In Progress)
> decommission may cause timeout because messaging backlog is cleared
>
>
> Key: CASSANDRA-14930
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14930
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Coordination, Legacy/Core
>Reporter: Zhao Yang
>Assignee: Zhao Yang
>Priority: Normal
> Fix For: 3.0.x, 3.11.x
>
>
> On a 3-node cluster with RF=2, decommissioning a node may cause quorum write
> timeout because messaging backlog to decommissioned node is cleared via
> {{Gossiper#removeEndpoint() -> OutboundTcpConnection#closeSocket()}}.
> (Timeout is less likely to happen with RF=3, because we can afford one less
> response)
> {code:java}
> What happened:
> 1. [WriteStage] before the leaving node is removed from tokenmetadata, the
> write endpoints are generated ( leaving endpoint is included )
> 2. [GossipStage] the leaving node is removed from tokenmetadata, no more
> future write handler will include leaving endpoints
> 3. [WriteStage] write handlers sends messages to messaging-service backlog
> 4. [GossipStage] messaging-service backlog is cleared, messages are not sent
> and connection closed
> 5. [WriteStage] write time out
> {code}
> |patch|
> |[3.0|https://github.com/jasonstack/cassandra/commits/decommission_timeout_3.0]|
> |[3.11|https://github.com/jasonstack/cassandra/commits/decommission_timeout_3.11]|
> We can avoid it by delaying to destroy messaging connection so that messages
> are sent and responded. This patch also avoids reopening already closed
> connection on {{MessagingService#convict()}}.
> New messaging framework rewrite in {{Trunk}} avoids the issues by not
> clearing messaging backlog.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] branch trunk updated (42b4fd0 -> 5fa48c2)
This is an automated email from the ASF dual-hosted git repository.
ifesdjeen pushed a change to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git.
from 42b4fd0 Removed dangling reference to the harry-runner module.
new 1c7fbc6 Numerious minor improvements while preparing for fuzz-testing
4.0 in earnest:
new 5fa48c2 Improvements: * Timestamp tie resolution * Test validating
behavior during upgrades (mixed version clusters) * Improve recent partition
validator * Add number of queries per partition * Make it easier run jobs
from a local machine * Make string postfixes more random by avoiding reusing
nibbles * Improve weight distributions * Allow clustering keys with less
entropy than 8 bytes Notable bugfixes: * Fix a problem with generation of
non-eq bounds following reverse [...]
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
harry-core/pom.xml | 2 +-
harry-core/src/harry/core/Configuration.java | 491 +++-
.../sut/NoOpSut.java => core/MetricReporter.java} | 39 +-
harry-core/src/harry/core/Run.java | 64 +-
.../src/harry/corruptor/AddExtraRowCorruptor.java | 4 +-
.../src/harry/corruptor/ChangeValueCorruptor.java | 6 +-
.../src/harry/corruptor/HideValueCorruptor.java| 31 +-
.../harry/corruptor/QueryResponseCorruptor.java| 26 +-
harry-core/src/harry/corruptor/RowCorruptor.java | 8 +-
.../src/harry/corruptor/ShowValueCorruptor.java| 2 +-
harry-core/src/harry/data/ResultSetRow.java| 33 +-
harry-core/src/harry/ddl/ColumnSpec.java | 61 +-
harry-core/src/harry/ddl/SchemaGenerators.java | 177 --
harry-core/src/harry/ddl/SchemaSpec.java | 94 ++-
harry-core/src/harry/generators/Bijections.java| 14 +-
.../src/harry/generators/DataGenerators.java | 41 +-
harry-core/src/harry/generators/PCGFastPure.java | 2 +-
harry-core/src/harry/generators/RngUtils.java | 46 ++
.../src/harry/generators/StringBijection.java | 26 +-
harry-core/src/harry/generators/Surjections.java | 8 +-
.../src/harry/model/DescriptorSelectorBuilder.java | 22 +-
harry-core/src/harry/model/ExhaustiveChecker.java | 647 -
harry-core/src/harry/model/Model.java | 40 +-
.../{DoNothingModel.java => NoOpChecker.java} | 17 +-
harry-core/src/harry/model/OpSelectors.java| 294 +++---
harry-core/src/harry/model/QuiescentChecker.java | 174 --
harry-core/src/harry/model/SelectHelper.java | 35 +-
.../harry/model/StatelessVisibleRowsChecker.java | 124
harry-core/src/harry/model/VisibleRowsChecker.java | 248
harry-core/src/harry/model/sut/PrintlnSut.java | 9 +-
.../src/harry/model/sut/SystemUnderTest.java | 51 +-
.../src/harry/operations/CompiledStatement.java| 29 +-
harry-core/src/harry/operations/DeleteHelper.java | 80 ++-
harry-core/src/harry/operations/Relation.java | 20 +-
harry-core/src/harry/operations/WriteHelper.java | 16 +
harry-core/src/harry/reconciler/Reconciler.java| 377 +---
.../src/harry/runner/AbstractPartitionVisitor.java | 17 +-
.../src/harry/runner/AllPartitionsValidator.java | 137 +
.../harry/runner/CorruptingPartitionVisitor.java | 93 +++
.../src/harry/runner/DataTracker.java | 33 +-
.../DefaultDataTracker.java} | 35 +-
.../runner/DefaultPartitionVisitorFactory.java | 198 ---
harry-core/src/harry/runner/DefaultRowVisitor.java | 68 ---
harry-core/src/harry/runner/HarryRunner.java | 96 ++-
.../src/harry/runner/LoggingPartitionVisitor.java | 79 +++
.../src/harry/runner/MutatingPartitionVisitor.java | 144 +
.../src/harry/runner/MutatingRowVisitor.java | 101
.../runner/{RowVisitor.java => Operation.java} | 29 +-
.../runner/ParallelRecentPartitionValidator.java | 170 ++
harry-core/src/harry/runner/ParallelValidator.java | 112
harry-core/src/harry/runner/PartitionVisitor.java | 11 +-
harry-core/src/harry/runner/Query.java | 8 +-
.../{QuerySelector.java => QueryGenerator.java}| 133 +++--
.../src/harry/runner/RecentPartitionValidator.java | 136 +
harry-core/src/harry/runner/Runner.java| 199 ---
harry-core/src/harry/runner/Sampler.java | 110
.../src/harry/runner/SinglePartitionValidator.java | 62 ++
harry-core/src/harry/runner/Validator.java | 119
harry-core/src/harry/util/BitSet.java | 56 +-
harry-core/src/harry/util/Ranges.java | 25 +-
.../test/harry/generators/RandomGeneratorTest.java | 59 +-
.../test/harry/generators/SurjectionsTest.java | 4 +
[jira] [Assigned] (CASSANDRA-13085) Cassandra fails to start because WindowsFailedSnapshotTracker can not write to CASSANDRA_HOME
[
https://issues.apache.org/jira/browse/CASSANDRA-13085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie reassigned CASSANDRA-13085:
-
Assignee: (was: Josh McKenzie)
> Cassandra fails to start because WindowsFailedSnapshotTracker can not write
> to CASSANDRA_HOME
> -
>
> Key: CASSANDRA-13085
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13085
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths, Packaging
> Environment: might be windows only considering the classname
>Reporter: Pieter-Jan Pintens
>Priority: Normal
> Labels: windows
>
> We are currently trying to package Cassandra with our application.
> In windows our server does not want to start because it want to write to
> CASSANDRA_HOME\.toDelete, since we install to 'C:\program files\...' this is
> not possible when started under a non privileged user. We were hoping that
> setting pointers for the data and log dir to a writable location (somewhere
> under user home) would be enough to start cassandra but this component wants
> to write to a path that we cannot modify.
> For us there are a couple of solutions:
> 1) the location can be specified using a system property like data and log
> dirs
> 2) this file is written to the data location
> Our current work arround would be to patch this class file but that is hard
> to maintain.
> {noformat}
> Exception (java.lang.RuntimeException) encountered during startup: Failed to
> cre
> ate failed snapshot tracking file [.toDelete]. Aborting
> java.lang.RuntimeException: Failed to create failed snapshot tracking file
> [.toDelete]. Aborting
> at
> org.apache.cassandra.db.WindowsFailedSnapshotTracker.deleteOldSnapshots(WindowsFailedSnapshotTracker.java:98)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:186)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:601)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:730)
> at com.id.cassandra.wrapper.Main.main(Unknown Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-11575) Add out-of-process testing for CDC
[ https://issues.apache.org/jira/browse/CASSANDRA-11575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh McKenzie reassigned CASSANDRA-11575: - Assignee: (was: Josh McKenzie) > Add out-of-process testing for CDC > -- > > Key: CASSANDRA-11575 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11575 > Project: Cassandra > Issue Type: Sub-task > Components: Legacy/Testing >Reporter: Carl Yeksigian >Priority: Normal > Fix For: 4.x > > Attachments: 11575.tgz, 11575.tgz > > > There are currently no dtests for the new cdc feature. We should have some, > at least to ensure that the cdc files have a lifecycle that makes sense, and > make sure that things like a continually cleaning daemon and a lazy daemon > have the properties we expect; for this, we don't need to actually process > the files, but make sure they fit the characteristics we expect from them. A > more complex daemon would need to be written in Java. > I already hit a problem where if the cdc is over capacity, the cdc properly > throws the WTE, but it will not reset after the overflow directory is > undersize again. It is supposed to correct the size within 250ms and allow > more writes. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-16796) Clear pending ranges for a SHUTDOWN peer
Sam Tunnicliffe created CASSANDRA-16796: --- Summary: Clear pending ranges for a SHUTDOWN peer Key: CASSANDRA-16796 URL: https://issues.apache.org/jira/browse/CASSANDRA-16796 Project: Cassandra Issue Type: Bug Components: Cluster/Membership Reporter: Sam Tunnicliffe Assignee: Sam Tunnicliffe If a node involved in a MOVE operation should fail, peers can sometimes maintain pending ranges even when it has left the ring and/or been replaced (in practice until the peer is next bounced). This in turn can lead to bogus unavailable responses to clients if a replica for the any of the pending ranges should go down. If the moving node crashes hard, a subsequent replacement will correctly fail as long as cassandra.consistent.rangemovement is set to true because the new node will learn the MOVING status from the remaining peers. A graceful shutdown, however, causes that status to be replaced with SHUTDOWN, but doesn't update TokenMetadata, so pending ranges remain for the down node, even after it has been removed from the ring. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-12734) Materialized View schema file for snapshots created as tables
[ https://issues.apache.org/jira/browse/CASSANDRA-12734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-12734: Fix Version/s: 4.0.x 3.11.x > Materialized View schema file for snapshots created as tables > - > > Key: CASSANDRA-12734 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12734 > Project: Cassandra > Issue Type: Bug > Components: Feature/Materialized Views, Legacy/Tools >Reporter: Hau Phan >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x > > > The materialized view schema file that gets created and stored with the > sstables is created as a table instead of a materialized view. > Can the materialized view be created and added to the corresponding table's > schema file? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-12734) Materialized View schema file for snapshots created as tables
[ https://issues.apache.org/jira/browse/CASSANDRA-12734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova reassigned CASSANDRA-12734: --- Assignee: Ekaterina Dimitrova (was: Zhao Yang) > Materialized View schema file for snapshots created as tables > - > > Key: CASSANDRA-12734 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12734 > Project: Cassandra > Issue Type: Bug > Components: Feature/Materialized Views, Legacy/Tools >Reporter: Hau Phan >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 3.0.x > > > The materialized view schema file that gets created and stored with the > sstables is created as a table instead of a materialized view. > Can the materialized view be created and added to the corresponding table's > schema file? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16725) Implement nodetool getauditlog command
[ https://issues.apache.org/jira/browse/CASSANDRA-16725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379209#comment-17379209 ] Ekaterina Dimitrova commented on CASSANDRA-16725: - [~stefan.miklosovic] there are a few failures you might want to check before we move on. Thanks > Implement nodetool getauditlog command > -- > > Key: CASSANDRA-16725 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16725 > Project: Cassandra > Issue Type: New Feature > Components: Tool/auditlogging >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > There is getfullquerylog already, there is not any reason why getauditlog > should not be there too. A user can not retrieve runtime configuration of > Audit log, it might be only enabled and disabled via jmx but its state can > not be queried in runtime. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16795) cqlsh shows old version native protocol but other nodes of cluster shows correct
[
https://issues.apache.org/jira/browse/CASSANDRA-16795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16795:
-
Resolution: Invalid
Status: Resolved (was: Triage Needed)
Hello,
This jira is for tracking bugs within the project. For support, the user ML or
slack will provide for a better experience:
https://cassandra.apache.org/community/
> cqlsh shows old version native protocol but other nodes of cluster shows
> correct
>
>
> Key: CASSANDRA-16795
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16795
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Srinivas P
>Priority: Normal
>
> Team,
> we got a weird issue, we are getting below error
> com.datastax.driver.core.exceptions.CodecNotFoundException: Codec not found
> for requested operation: ['org.apache.cassandra.db.marshal.ShortType' <->
> java.lang.Short]
> com.datastax.driver.core.Connection - DEBUG: Got unsupported protocol version
> error from /:9042 for version V4 server supports version V3
> cassandra]$ cqlsh -u cassandra
> Password:
> \Connected to social-graph-cassandra-cluster at :9042.
> [cqlsh 5.0.1 | Cassandra 3.11.5 | CQL spec 3.4.4 | Native protocol
> {color:#FF}v3{color}]
> Use HELP for help.
> cassandra@cqlsh> select native_protocol_version from system.local;
> native_protocol_version
> -
> {color:#FF}4{color}(1 rows)
> cassandra@cqlsh>
> but other clusters shows correct version of Native protocols.
> we are not using any cqlshrc config files as well. any help in identifying
> above issue would be appreciated.
> Regards,
> Srinivas
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-16795) cqlsh shows old version native protocol but other nodes of cluster shows correct
Srinivas P created CASSANDRA-16795:
--
Summary: cqlsh shows old version native protocol but other nodes
of cluster shows correct
Key: CASSANDRA-16795
URL: https://issues.apache.org/jira/browse/CASSANDRA-16795
Project: Cassandra
Issue Type: Bug
Components: CQL/Interpreter
Reporter: Srinivas P
Team,
we got a weird issue, we are getting below error
com.datastax.driver.core.exceptions.CodecNotFoundException: Codec not found for
requested operation: ['org.apache.cassandra.db.marshal.ShortType' <->
java.lang.Short]
com.datastax.driver.core.Connection - DEBUG: Got unsupported protocol version
error from /:9042 for version V4 server supports version V3
cassandra]$ cqlsh -u cassandra
Password:
\Connected to social-graph-cassandra-cluster at :9042.
[cqlsh 5.0.1 | Cassandra 3.11.5 | CQL spec 3.4.4 | Native protocol
{color:#FF}v3{color}]
Use HELP for help.
cassandra@cqlsh> select native_protocol_version from system.local;
native_protocol_version
-
{color:#FF}4{color}(1 rows)
cassandra@cqlsh>
but other clusters shows correct version of Native protocols.
we are not using any cqlshrc config files as well. any help in identifying
above issue would be appreciated.
Regards,
Srinivas
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16649) Add Versions.Major.v4X to Java DTests (after cassandra-4.0 branch was created)
[ https://issues.apache.org/jira/browse/CASSANDRA-16649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379170#comment-17379170 ] Alex Petrov commented on CASSANDRA-16649: - +1 > Add Versions.Major.v4X to Java DTests (after cassandra-4.0 branch was created) > -- > > Key: CASSANDRA-16649 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16649 > Project: Cassandra > Issue Type: Sub-task > Components: Test/dtest/java >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 2.2.x, 3.0.x, 3.11.x, 4.0.x, 4.x > > > - > https://github.com/apache/cassandra-in-jvm-dtest-api/compare/trunk...thelastpickle:mck/16649 > - > https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/16649/trunk > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16649) Add Versions.Major.v4X to Java DTests (after cassandra-4.0 branch was created)
[ https://issues.apache.org/jira/browse/CASSANDRA-16649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16649: --- Status: Review In Progress (was: Patch Available) > Add Versions.Major.v4X to Java DTests (after cassandra-4.0 branch was created) > -- > > Key: CASSANDRA-16649 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16649 > Project: Cassandra > Issue Type: Sub-task > Components: Test/dtest/java >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 2.2.x, 3.0.x, 3.11.x, 4.0.x, 4.x > > > - > https://github.com/apache/cassandra-in-jvm-dtest-api/compare/trunk...thelastpickle:mck/16649 > - > https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/16649/trunk > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16649) Add Versions.Major.v4X to Java DTests (after cassandra-4.0 branch was created)
[ https://issues.apache.org/jira/browse/CASSANDRA-16649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379150#comment-17379150 ] Michael Semb Wever commented on CASSANDRA-16649: dtest-api 0.0.8 [released|https://lists.apache.org/thread.html/r161c863fdcdffc63ea66852242f47b8a93a20e50e5bf8c7293a7406f%40%3Cdev.cassandra.apache.org%3E]. > Add Versions.Major.v4X to Java DTests (after cassandra-4.0 branch was created) > -- > > Key: CASSANDRA-16649 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16649 > Project: Cassandra > Issue Type: Sub-task > Components: Test/dtest/java >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 2.2.x, 3.0.x, 3.11.x, 4.0.x, 4.x > > > - > https://github.com/apache/cassandra-in-jvm-dtest-api/compare/trunk...thelastpickle:mck/16649 > - > https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/16649/trunk > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.0 updated (652eb6c -> 330cde6)
This is an automated email from the ASF dual-hosted git repository. blerer pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 652eb6c Merge branch 'cassandra-4.0.0' into cassandra-4.0 add b428552 Fix CassandraVersion::compareTo add 330cde6 Merge branch cassandra-4.0.0 into cassandra-4.0 No new revisions were added by this update. Summary of changes: CHANGES.txt| 7 +- .../apache/cassandra/utils/CassandraVersion.java | 28 ++- .../cassandra/utils/CassandraVersionTest.java | 187 - 3 files changed, 178 insertions(+), 44 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (7cc6331 -> 58515c2)
This is an automated email from the ASF dual-hosted git repository. blerer pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 7cc6331 Merge branch 'cassandra-4.0' into trunk add b428552 Fix CassandraVersion::compareTo add 330cde6 Merge branch cassandra-4.0.0 into cassandra-4.0 new 58515c2 Merge branch cassandra-4.0 into trunk The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt| 7 +- .../apache/cassandra/utils/CassandraVersion.java | 28 ++- .../cassandra/utils/CassandraVersionTest.java | 187 - 3 files changed, 178 insertions(+), 44 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch cassandra-4.0 into trunk
This is an automated email from the ASF dual-hosted git repository. blerer pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 58515c2de6d54a6c1994dfa4c78d7452b6b5cd8c Merge: 7cc6331 330cde6 Author: Benjamin Lerer AuthorDate: Mon Jul 12 13:09:24 2021 +0200 Merge branch cassandra-4.0 into trunk CHANGES.txt| 7 +- .../apache/cassandra/utils/CassandraVersion.java | 28 ++- .../cassandra/utils/CassandraVersionTest.java | 187 - 3 files changed, 178 insertions(+), 44 deletions(-) diff --cc CHANGES.txt index 7108475,a16985a..2a8074a --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,13 -1,4 +1,12 @@@ -4.0.1 +4.1 + * Remove check on gossip status from DynamicEndpointSnitch::updateScores (CASSANDRA-11671) + * Fix AbstractReadQuery::toCQLString not returning valid CQL (CASSANDRA-16510) + * Log when compacting many tombstones (CASSANDRA-16780) + * Display bytes per level in tablestats for LCS tables (CASSANDRA-16799) + * Add isolated flush timer to CommitLogMetrics and ensure writes correspond to single WaitingOnCommit data points (CASSANDRA-16701) + * Add a system property to set hostId if not yet initialized (CASSANDRA-14582) + * GossiperTest.testHasVersion3Nodes didn't take into account trunk version changes, fixed to rely on latest version (CASSANDRA-16651) +Merged from 4.0: - * BinLog does not close chronicle queue leaving this to GC to cleanup (CASSANDRA-16774) * Add repaired/unrepaired bytes back to nodetool (CASSANDRA-15282) * Upgrade lz4-java to 1.8.0 to add RH6 support back (CASSANDRA-16753) * Improve DiagnosticEventService.publish(event) logging message of events (CASSANDRA-16749) @@@ -21,8 -11,15 +20,14 @@@ Merged from 3.11 Merged from 3.0: * Clean transaction log leftovers at the beginning of sstablelevelreset and sstableofflinerelevel (CASSANDRA-12519) + 4.0.0 + * Fix CassandraVersion::compareTo (CASSANDRA-16794) + * BinLog does not close chronicle queue leaving this to GC to cleanup (CASSANDRA-16774) + Merged from 3.11: + Merged from 3.0: + 4.0-rc2 * Avoid memoizing the wrong min cluster version during upgrades (CASSANDRA-16759) - * Obfuscate passwords in statements in QueryEvents (CASSANDRA-16669) * Fix queries on empty partitions with static data (CASSANDRA-16686) * Keep python driver in artifacts (CASSANDRA-16700) * Improve AuditLogging documentation and logback.xml(CASSANDRA-16682) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.0.0 updated (a46146f -> b428552)
This is an automated email from the ASF dual-hosted git repository. blerer pushed a change to branch cassandra-4.0.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git. from a46146f Prepare debian changelog for 4.0.0 add b428552 Fix CassandraVersion::compareTo No new revisions were added by this update. Summary of changes: CHANGES.txt| 1 + .../apache/cassandra/utils/CassandraVersion.java | 28 ++- .../cassandra/utils/CassandraVersionTest.java | 191 - 3 files changed, 173 insertions(+), 47 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16794) CassandraVersion compareTo does not order SNAPSHOT versions properly
[
https://issues.apache.org/jira/browse/CASSANDRA-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-16794:
---
Fix Version/s: (was: 4.0-rc3)
4.0
Since Version: 4.0-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/b42855282d260bcd16412a1ed9da0227ee0c065e
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed into cassandra-4.0.0 at b42855282d260bcd16412a1ed9da0227ee0c065e and
merged into cassandra-4.0 and trunk.
> CassandraVersion compareTo does not order SNAPSHOT versions properly
>
>
> Key: CASSANDRA-16794
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16794
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>Priority: Normal
> Fix For: 4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{CassandraVersion::compareTo}} does not order {{SNAPSHOT}} versions properly
> in several scenario.
> It return wrong results for the 2 following usecases:
> 1. {{new CassandraVersion("4.0-rc2").compareTo(("4.0.0-SNAPSHOT")}}
> 2. {{new CassandraVersion("4.0-rc2").compareTo(("4.0-rc2-SNAPSHOT")}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16794) CassandraVersion compareTo does not order SNAPSHOT versions properly
[
https://issues.apache.org/jira/browse/CASSANDRA-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-16794:
---
Status: Ready to Commit (was: Review In Progress)
> CassandraVersion compareTo does not order SNAPSHOT versions properly
>
>
> Key: CASSANDRA-16794
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16794
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>Priority: Normal
> Fix For: 4.0-rc3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{CassandraVersion::compareTo}} does not order {{SNAPSHOT}} versions properly
> in several scenario.
> It return wrong results for the 2 following usecases:
> 1. {{new CassandraVersion("4.0-rc2").compareTo(("4.0.0-SNAPSHOT")}}
> 2. {{new CassandraVersion("4.0-rc2").compareTo(("4.0-rc2-SNAPSHOT")}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16666) Make SSLContext creation pluggable/extensible
[
https://issues.apache.org/jira/browse/CASSANDRA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379112#comment-17379112
]
Michael Semb Wever commented on CASSANDRA-1:
Moving ticket back to {{OPEN}} status, as this work is still a PoC for a CEP
that is currently pre-approval.
> Make SSLContext creation pluggable/extensible
> -
>
> Key: CASSANDRA-1
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1
> Project: Cassandra
> Issue Type: Improvement
> Components: Messaging/Internode
>Reporter: Maulin Vasavada
>Assignee: Maulin Vasavada
>Priority: Normal
> Fix For: 4.x
>
>
> Currently Cassandra creates the SSLContext via SSLFactory.java. SSLFactory is
> a final class with static methods and not overridable. The SSLFactory loads
> the keys and certs from the file based artifacts for the same. While this
> works for many, in the industry where security is stricter and contextual,
> this approach falls short. Many big organizations need flexibility to load
> the SSL artifacts from a custom resource (like custom Key Management
> Solution, HashiCorp Vault, Amazon KMS etc). While JSSE SecurityProvider
> architecture allows us flexibility to build our custom mechanisms to validate
> and process security artifacts, many times all we need is to build upon
> Java's existing extensibility that Trust/Key Manager interfaces provide to
> load keystores from various resources in the absence of any customized
> requirements on the Keys/Certificate formats.
> My proposal here is to make the SSLContext creation pluggable/extensible and
> have the current SSLFactory.java implement an extensible interface.
> I contributed a similar change that is live now in Apache Kafka (2.6.0) -
> https://issues.apache.org/jira/browse/KAFKA-8890
> I can spare some time writing the pluggable interface and run by the required
> reviewers.
>
> Created [CEP-9: Make SSLContext creation
> pluggable|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-9%3A+Make+SSLContext+creation+pluggable]
>
>
> cc: [~dcapwell] [~djoshi]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16794) CassandraVersion compareTo does not order SNAPSHOT versions properly
[
https://issues.apache.org/jira/browse/CASSANDRA-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17377979#comment-17377979
]
Benjamin Lerer edited comment on CASSANDRA-16794 at 7/12/21, 10:29 AM:
---
|| Branch || CI ||
| [4.0.0|https://github.com/apache/cassandra/pull/1107] |
[j8|https://app.circleci.com/pipelines/github/blerer/cassandra/182/workflows/4a681f71-4a95-4456-84c0-b6f4940ca34c],
[j11|https://app.circleci.com/pipelines/github/blerer/cassandra/182/workflows/0b9d07ba-7e7e-4487-8c91-d699026a22e0]|
was (Author: blerer):
|| Branch || CI ||
| [4.0.0|https://github.com/apache/cassandra/pull/1107] |
[j8|https://app.circleci.com/pipelines/github/blerer/cassandra/181/workflows/417d25ae-4dcf-41e3-ae81-8b61bba9a604],
[j11|https://app.circleci.com/pipelines/github/blerer/cassandra/181/workflows/b9f4d30d-2517-4767-a5c2-df3270967c01]|
> CassandraVersion compareTo does not order SNAPSHOT versions properly
>
>
> Key: CASSANDRA-16794
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16794
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>Priority: Normal
> Fix For: 4.0-rc3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{CassandraVersion::compareTo}} does not order {{SNAPSHOT}} versions properly
> in several scenario.
> It return wrong results for the 2 following usecases:
> 1. {{new CassandraVersion("4.0-rc2").compareTo(("4.0.0-SNAPSHOT")}}
> 2. {{new CassandraVersion("4.0-rc2").compareTo(("4.0-rc2-SNAPSHOT")}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16666) Make SSLContext creation pluggable/extensible
[ https://issues.apache.org/jira/browse/CASSANDRA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-1: --- Status: Open (was: Patch Available) > Make SSLContext creation pluggable/extensible > - > > Key: CASSANDRA-1 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1 > Project: Cassandra > Issue Type: Improvement > Components: Messaging/Internode >Reporter: Maulin Vasavada >Assignee: Maulin Vasavada >Priority: Normal > Fix For: 4.x > > > Currently Cassandra creates the SSLContext via SSLFactory.java. SSLFactory is > a final class with static methods and not overridable. The SSLFactory loads > the keys and certs from the file based artifacts for the same. While this > works for many, in the industry where security is stricter and contextual, > this approach falls short. Many big organizations need flexibility to load > the SSL artifacts from a custom resource (like custom Key Management > Solution, HashiCorp Vault, Amazon KMS etc). While JSSE SecurityProvider > architecture allows us flexibility to build our custom mechanisms to validate > and process security artifacts, many times all we need is to build upon > Java's existing extensibility that Trust/Key Manager interfaces provide to > load keystores from various resources in the absence of any customized > requirements on the Keys/Certificate formats. > My proposal here is to make the SSLContext creation pluggable/extensible and > have the current SSLFactory.java implement an extensible interface. > I contributed a similar change that is live now in Apache Kafka (2.6.0) - > https://issues.apache.org/jira/browse/KAFKA-8890 > I can spare some time writing the pluggable interface and run by the required > reviewers. > > Created [CEP-9: Make SSLContext creation > pluggable|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-9%3A+Make+SSLContext+creation+pluggable] > > > cc: [~dcapwell] [~djoshi] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16794) CassandraVersion compareTo does not order SNAPSHOT versions properly
[
https://issues.apache.org/jira/browse/CASSANDRA-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379108#comment-17379108
]
Benjamin Lerer commented on CASSANDRA-16794:
Sorry, I hit another issue with the {{lowerFamilyBound}} initial patch. I
pushed a modified version of the patch that addressed that issue and updated
the CI runs.
> CassandraVersion compareTo does not order SNAPSHOT versions properly
>
>
> Key: CASSANDRA-16794
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16794
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>Priority: Normal
> Fix For: 4.0-rc3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{CassandraVersion::compareTo}} does not order {{SNAPSHOT}} versions properly
> in several scenario.
> It return wrong results for the 2 following usecases:
> 1. {{new CassandraVersion("4.0-rc2").compareTo(("4.0.0-SNAPSHOT")}}
> 2. {{new CassandraVersion("4.0-rc2").compareTo(("4.0-rc2-SNAPSHOT")}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16666) Make SSLContext creation pluggable/extensible
[ https://issues.apache.org/jira/browse/CASSANDRA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-1: Reviewers: Berenguer Blasi > Make SSLContext creation pluggable/extensible > - > > Key: CASSANDRA-1 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1 > Project: Cassandra > Issue Type: Improvement > Components: Messaging/Internode >Reporter: Maulin Vasavada >Assignee: Maulin Vasavada >Priority: Normal > Fix For: 4.x > > > Currently Cassandra creates the SSLContext via SSLFactory.java. SSLFactory is > a final class with static methods and not overridable. The SSLFactory loads > the keys and certs from the file based artifacts for the same. While this > works for many, in the industry where security is stricter and contextual, > this approach falls short. Many big organizations need flexibility to load > the SSL artifacts from a custom resource (like custom Key Management > Solution, HashiCorp Vault, Amazon KMS etc). While JSSE SecurityProvider > architecture allows us flexibility to build our custom mechanisms to validate > and process security artifacts, many times all we need is to build upon > Java's existing extensibility that Trust/Key Manager interfaces provide to > load keystores from various resources in the absence of any customized > requirements on the Keys/Certificate formats. > My proposal here is to make the SSLContext creation pluggable/extensible and > have the current SSLFactory.java implement an extensible interface. > I contributed a similar change that is live now in Apache Kafka (2.6.0) - > https://issues.apache.org/jira/browse/KAFKA-8890 > I can spare some time writing the pluggable interface and run by the required > reviewers. > > Created [CEP-9: Make SSLContext creation > pluggable|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-9%3A+Make+SSLContext+creation+pluggable] > > > cc: [~dcapwell] [~djoshi] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16666) Make SSLContext creation pluggable/extensible
[ https://issues.apache.org/jira/browse/CASSANDRA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379098#comment-17379098 ] Berenguer Blasi commented on CASSANDRA-1: - Done a first pass. The main issue is formatting which is a small one. But I want to take another look. > Make SSLContext creation pluggable/extensible > - > > Key: CASSANDRA-1 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1 > Project: Cassandra > Issue Type: Improvement > Components: Messaging/Internode >Reporter: Maulin Vasavada >Assignee: Maulin Vasavada >Priority: Normal > Fix For: 4.x > > > Currently Cassandra creates the SSLContext via SSLFactory.java. SSLFactory is > a final class with static methods and not overridable. The SSLFactory loads > the keys and certs from the file based artifacts for the same. While this > works for many, in the industry where security is stricter and contextual, > this approach falls short. Many big organizations need flexibility to load > the SSL artifacts from a custom resource (like custom Key Management > Solution, HashiCorp Vault, Amazon KMS etc). While JSSE SecurityProvider > architecture allows us flexibility to build our custom mechanisms to validate > and process security artifacts, many times all we need is to build upon > Java's existing extensibility that Trust/Key Manager interfaces provide to > load keystores from various resources in the absence of any customized > requirements on the Keys/Certificate formats. > My proposal here is to make the SSLContext creation pluggable/extensible and > have the current SSLFactory.java implement an extensible interface. > I contributed a similar change that is live now in Apache Kafka (2.6.0) - > https://issues.apache.org/jira/browse/KAFKA-8890 > I can spare some time writing the pluggable interface and run by the required > reviewers. > > Created [CEP-9: Make SSLContext creation > pluggable|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-9%3A+Make+SSLContext+creation+pluggable] > > > cc: [~dcapwell] [~djoshi] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
