[jira] [Updated] (CASSANDRA-15241) Virtual table to expose current running queries
[
https://issues.apache.org/jira/browse/CASSANDRA-15241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-15241:
Reviewers: Benedict Elliott Smith (was: Benedict Elliott Smith, Caleb
Rackliffe)
> Virtual table to expose current running queries
> ---
>
> Key: CASSANDRA-15241
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15241
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Virtual Tables
>Reporter: Chris Lohfink
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.x
>
>
> Expose current running queries and their duration.
> {code}cqlsh> select * from system_views.queries;
> thread_id| duration_micros | task
> --+-+-
> Native-Transport-Requests-17 |6325 | QUERY
> select * from system_views.queries; [pageSize = 100]
> Native-Transport-Requests-4 | 14681 | EXECUTE
> f4115f91190d4acf09e452637f1f2444 with 0 values at consistency LOCAL_ONE
> Native-Transport-Requests-6 | 14678 | EXECUTE
> f4115f91190d4acf09e452637f1f2444 with 0 values at consistency LOCAL_ONE
> ReadStage-10 | 16535 |
>SELECT * FROM basic.wide1 LIMIT 5000
> ReadStage-13 | 16535 |
>SELECT * FROM basic.wide1 LIMIT 5000
> ReadStage-14 | 16535 |
>SELECT * FROM basic.wide1 LIMIT 5000
> ReadStage-19 | 11861 |
>SELECT * FROM basic.wide1 LIMIT 5000
> ReadStage-20 | 11861 |
>SELECT * FROM basic.wide1 LIMIT 5000
> ReadStage-22 |7279 |
>SELECT * FROM basic.wide1 LIMIT 5000
> ReadStage-23 |4716 |
>SELECT * FROM basic.wide1 LIMIT 5000
> ReadStage-5 | 16535 |
>SELECT * FROM basic.wide1 LIMIT 5000
> ReadStage-7 | 16535 |
>SELECT * FROM basic.wide1 LIMIT 5000
> ReadStage-8 | 16535 |
>SELECT * FROM basic.wide1 LIMIT 5000{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17370) Add flag enabling operators to restrict use of ALLOW FILTERING in queries
[ https://issues.apache.org/jira/browse/CASSANDRA-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Savni Nagarkar updated CASSANDRA-17370: --- Reviewers: Andres de la Peña, David Capwell > Add flag enabling operators to restrict use of ALLOW FILTERING in queries > - > > Key: CASSANDRA-17370 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17370 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Semantics, Feature/Guardrails >Reporter: Savni Nagarkar >Assignee: Savni Nagarkar >Priority: Normal > Fix For: 4.x > > > This ticket adds the ability for operators to disallow use of ALLOW FILTERING > predicates in CQL SELECT statements. As queries that ALLOW FILTERING can > place additional load on the database, the flag enables operators to provide > tighter bounds on performance guarantees. The patch includes a new yaml > property, as well as a hot property enabling the value to be modified via JMX > at runtime. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17370) Add flag enabling operators to restrict use of ALLOW FILTERING in queries
[ https://issues.apache.org/jira/browse/CASSANDRA-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-17370: -- Component/s: Feature/Guardrails > Add flag enabling operators to restrict use of ALLOW FILTERING in queries > - > > Key: CASSANDRA-17370 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17370 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Semantics, Feature/Guardrails >Reporter: Savni Nagarkar >Assignee: Savni Nagarkar >Priority: Normal > Fix For: 4.x > > > This ticket adds the ability for operators to disallow use of ALLOW FILTERING > predicates in CQL SELECT statements. As queries that ALLOW FILTERING can > place additional load on the database, the flag enables operators to provide > tighter bounds on performance guarantees. The patch includes a new yaml > property, as well as a hot property enabling the value to be modified via JMX > at runtime. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17370) Add flag enabling operators to restrict use of ALLOW FILTERING in queries
[ https://issues.apache.org/jira/browse/CASSANDRA-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-17370: -- Component/s: CQL/Semantics Feature/Guardrails (was: CQL/Syntax) > Add flag enabling operators to restrict use of ALLOW FILTERING in queries > - > > Key: CASSANDRA-17370 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17370 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Semantics, Feature/Guardrails >Reporter: Savni Nagarkar >Assignee: Savni Nagarkar >Priority: Normal > Fix For: 4.x > > > This ticket adds the ability for operators to disallow use of ALLOW FILTERING > predicates in CQL SELECT statements. As queries that ALLOW FILTERING can > place additional load on the database, the flag enables operators to provide > tighter bounds on performance guarantees. The patch includes a new yaml > property, as well as a hot property enabling the value to be modified via JMX > at runtime. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17370) Add flag enabling operators to restrict use of ALLOW FILTERING in queries
[ https://issues.apache.org/jira/browse/CASSANDRA-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Savni Nagarkar updated CASSANDRA-17370: --- Component/s: (was: Feature/Guardrails) > Add flag enabling operators to restrict use of ALLOW FILTERING in queries > - > > Key: CASSANDRA-17370 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17370 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Semantics >Reporter: Savni Nagarkar >Assignee: Savni Nagarkar >Priority: Normal > Fix For: 4.x > > > This ticket adds the ability for operators to disallow use of ALLOW FILTERING > predicates in CQL SELECT statements. As queries that ALLOW FILTERING can > place additional load on the database, the flag enables operators to provide > tighter bounds on performance guarantees. The patch includes a new yaml > property, as well as a hot property enabling the value to be modified via JMX > at runtime. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17370) Add flag enabling operators to restrict use of ALLOW FILTERING in queries
[ https://issues.apache.org/jira/browse/CASSANDRA-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Savni Nagarkar updated CASSANDRA-17370: --- Change Category: Operability Complexity: Low Hanging Fruit Component/s: CQL/Syntax Fix Version/s: 4.x Status: Open (was: Triage Needed) > Add flag enabling operators to restrict use of ALLOW FILTERING in queries > - > > Key: CASSANDRA-17370 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17370 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Syntax >Reporter: Savni Nagarkar >Assignee: Savni Nagarkar >Priority: Normal > Fix For: 4.x > > > This ticket adds the ability for operators to disallow use of ALLOW FILTERING > predicates in CQL SELECT statements. As queries that ALLOW FILTERING can > place additional load on the database, the flag enables operators to provide > tighter bounds on performance guarantees. The patch includes a new yaml > property, as well as a hot property enabling the value to be modified via JMX > at runtime. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17370) Add flag enabling operators to restrict use of ALLOW FILTERING in queries
Savni Nagarkar created CASSANDRA-17370: -- Summary: Add flag enabling operators to restrict use of ALLOW FILTERING in queries Key: CASSANDRA-17370 URL: https://issues.apache.org/jira/browse/CASSANDRA-17370 Project: Cassandra Issue Type: Improvement Reporter: Savni Nagarkar Assignee: Savni Nagarkar This ticket adds the ability for operators to disallow use of ALLOW FILTERING predicates in CQL SELECT statements. As queries that ALLOW FILTERING can place additional load on the database, the flag enables operators to provide tighter bounds on performance guarantees. The patch includes a new yaml property, as well as a hot property enabling the value to be modified via JMX at runtime. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17166) Enhance SnakeYAML properties to be reusable outside of YAML parsing, support camel case conversion to snake case, and add support to ignore properties
[ https://issues.apache.org/jira/browse/CASSANDRA-17166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489867#comment-17489867 ] David Capwell commented on CASSANDRA-17166: --- I worked on a diff test like I did for jmx, and found missing properties... trying to make sure each are safe, else will file a ticket. > Enhance SnakeYAML properties to be reusable outside of YAML parsing, support > camel case conversion to snake case, and add support to ignore properties > -- > > Key: CASSANDRA-17166 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17166 > Project: Cassandra > Issue Type: Improvement > Components: Local/Config >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.x > > Time Spent: 1h 20m > Remaining Estimate: 0h > > SnakeYaml is rather limited in the “object mapping” layer, which forces our > internal code to match specific patterns (all fields public and camel case); > we can remove this restriction by leveraging Jackson for property lookup, and > leaving the YAML handling to SnakeYAML -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17369) Set the config in In-JVM upgrade tests to the old format on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17369: Test and Documentation Plan: [Patch|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:17369-trunk?expand=1] | [CI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1374/workflows/e1492144-a7ef-4f87-8fcb-7c805eeb634a/jobs/8857/steps] Current tests Status: Patch Available (was: In Progress) > Set the config in In-JVM upgrade tests to the old format on trunk > - > > Key: CASSANDRA-17369 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17369 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > In-JVM upgrade tests do no support per-version config. > Revert the config in In-JVM upgrade tests to the old format on trunk. > CC [~dcapwell] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17369) Set the config in In-JVM upgrade tests to the old format on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489837#comment-17489837 ] Ekaterina Dimitrova commented on CASSANDRA-17369: - [Patch|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:17369-trunk?expand=1] | [CI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1374/workflows/e1492144-a7ef-4f87-8fcb-7c805eeb634a/jobs/8857/steps] [~dcapwell], do you mind to review, please? > Set the config in In-JVM upgrade tests to the old format on trunk > - > > Key: CASSANDRA-17369 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17369 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > In-JVM upgrade tests do no support per-version config. > Revert the config in In-JVM upgrade tests to the old format on trunk. > CC [~dcapwell] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17369) Set the config in In-JVM upgrade tests to the old format on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17369: Fix Version/s: 4.x > Set the config in In-JVM upgrade tests to the old format on trunk > - > > Key: CASSANDRA-17369 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17369 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > In-JVM upgrade tests do no support per-version config. > Revert the config in In-JVM upgrade tests to the old format on trunk. > CC [~dcapwell] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17369) Set the config in In-JVM upgrade tests to the old format on trunk
Ekaterina Dimitrova created CASSANDRA-17369: --- Summary: Set the config in In-JVM upgrade tests to the old format on trunk Key: CASSANDRA-17369 URL: https://issues.apache.org/jira/browse/CASSANDRA-17369 Project: Cassandra Issue Type: Bug Reporter: Ekaterina Dimitrova In-JVM upgrade tests do no support per-version config. Revert the config in In-JVM upgrade tests to the old format on trunk. CC [~dcapwell] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17369) Set the config in In-JVM upgrade tests to the old format on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-17369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17369: Bug Category: Parent values: Correctness(12982)Level 1 values: Test Failure(12990) Complexity: Low Hanging Fruit Component/s: CI Discovered By: User Report Severity: Low Assignee: Ekaterina Dimitrova Status: Open (was: Triage Needed) > Set the config in In-JVM upgrade tests to the old format on trunk > - > > Key: CASSANDRA-17369 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17369 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > In-JVM upgrade tests do no support per-version config. > Revert the config in In-JVM upgrade tests to the old format on trunk. > CC [~dcapwell] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17368) Investigate OWASP failure report
[ https://issues.apache.org/jira/browse/CASSANDRA-17368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17368: - Status: Open (was: Patch Available) > Investigate OWASP failure report > > > Key: CASSANDRA-17368 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17368 > Project: Cassandra > Issue Type: Bug > Components: Build >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x > > > 4.0: netty-all-4.1.58.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 > 3.11: netty-all-4.0.44.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 > 3.0: netty-all-4.0.44.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17368) Investigate OWASP failure report
[ https://issues.apache.org/jira/browse/CASSANDRA-17368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17368: - Fix Version/s: 3.0.x 3.11.x 4.0.x 4.x > Investigate OWASP failure report > > > Key: CASSANDRA-17368 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17368 > Project: Cassandra > Issue Type: Bug > Components: Build >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x > > > 4.0: netty-all-4.1.58.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 > 3.11: netty-all-4.0.44.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 > 3.0: netty-all-4.0.44.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17368) Investigate OWASP failure report
[ https://issues.apache.org/jira/browse/CASSANDRA-17368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17368: - Test and Documentation Plan: run CI Status: Patch Available (was: Open) > Investigate OWASP failure report > > > Key: CASSANDRA-17368 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17368 > Project: Cassandra > Issue Type: Bug > Components: Build >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x > > > 4.0: netty-all-4.1.58.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 > 3.11: netty-all-4.0.44.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 > 3.0: netty-all-4.0.44.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17368) Investigate OWASP failure report
[ https://issues.apache.org/jira/browse/CASSANDRA-17368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489736#comment-17489736 ] Brandon Williams commented on CASSANDRA-17368: -- I think since these are harmless we can add suppressions for 3.0, 3.11, and 4.0. For trunk, we can upgrade netty-all to 4.1.73.Final. ||Branch||CI|| |[3.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17368-3.0]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/351/workflows/1d7c9315-6dd2-4963-9adf-f61379ecd179]| |[3.11|https://github.com/driftx/cassandra/tree/CASSANDRA-17368-3.11]|[J8|https://app.circleci.com/pipelines/github/driftx/cassandra/352/workflows/21aa6b59-09cc-4042-8a94-0b0a561408a9]| |[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17368-4.0]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/353/workflows/634c0cf4-9d13-48f3-88df-b75e3df51d50]| |[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-17368-trunk]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/350/workflows/a7d3828f-3d35-4c01-b673-bed9319ad21b], [j11|https://app.circleci.com/pipelines/github/driftx/cassandra/350/workflows/6c707186-df54-4200-9a69-783bbc4f21bd]| > Investigate OWASP failure report > > > Key: CASSANDRA-17368 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17368 > Project: Cassandra > Issue Type: Bug > Components: Build >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > > 4.0: netty-all-4.1.58.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 > 3.11: netty-all-4.0.44.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 > 3.0: netty-all-4.0.44.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17186) Guardrail for number of partition keys on IN queries
[
https://issues.apache.org/jira/browse/CASSANDRA-17186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krishna Vadali updated CASSANDRA-17186:
---
Test and Documentation Plan: Unit tests.
Status: Patch Available (was: In Progress)
[Patch|https://github.com/apache/cassandra/pull/1442] available
> Guardrail for number of partition keys on IN queries
>
>
> Key: CASSANDRA-17186
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17186
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Assignee: Krishna Vadali
>Priority: Normal
> Labels: AdventCalendar2021, lhf
> Fix For: 4.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add a guardrail for limiting the number of partitions restricted with an
> {{IN}} clause in a {{SELECT}} query, for example:
> {code:java}
> # Guardrail to warn or abort when querying with an IN restriction selecting
> # more partition keys than threshold.
> # The two thresholds default to -1 to disable.
> partition_keys_in_select:
> warn_threshold: -1
> abort_threshold: -1
> {code}
> +Additional information for newcomers:+
> * Add the configuration for the new guardrail on the number of partitions on
> IN queries in the guardrails section of cassandra.yaml.
> * Add a getPartitionKeysInSelect method in GuardrailsConfig returning a
> Threshold.Config object
> * Implement that method in GuardrailsOptions, which is the default
> yaml-based implementation of GuardrailsConfig
> * Add a Threshold guardrail named partitionKeysInSelect in Guardrails, using
> the previously created config
> * Define JMX-friendly getters and setters for the previously created config
> in GuardrailsMBean
> * Implement the JMX-friendly getters and setters in Guardrails
> * Now that we have the guardrail ready, it’s time to use it. We should
> search for a place to invoke the Guardrails.partitionKeysInSelect#guard
> method with the number of keys specified in select query. The
> SelectStatement#getSliceCommands methods look like good candidates for this.
> * Finally, add some tests for the new guardrail. Given that the new
> guardrail is a Threshold, our new test should probably extend ThresholdTester.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17353) Flatten guardrails configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489734#comment-17489734
]
Andres de la Peña commented on CASSANDRA-17353:
---
Committed to {{trunk}} as
[8e1c8f986358aee51dd565a5a2917cb5554ed0c7|https://github.com/apache/cassandra/commit/8e1c8f986358aee51dd565a5a2917cb5554ed0c7].
Thanks for the quick review.
> Flatten guardrails configuration
>
>
> Key: CASSANDRA-17353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
> instead of the current nested format. This ticket comes from the discussion
> around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
> CASSANDRA-17212, and doesn't include any of the other nested properties on
> {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17353) Flatten guardrails configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17353:
--
Fix Version/s: 4.1
(was: 4.x)
Source Control Link:
https://github.com/apache/cassandra/commit/8e1c8f986358aee51dd565a5a2917cb5554ed0c7
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Flatten guardrails configuration
>
>
> Key: CASSANDRA-17353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
> instead of the current nested format. This ticket comes from the discussion
> around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
> CASSANDRA-17212, and doesn't include any of the other nested properties on
> {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17353) Flatten guardrails configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17353:
--
Status: Ready to Commit (was: Review In Progress)
> Flatten guardrails configuration
>
>
> Key: CASSANDRA-17353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
> instead of the current nested format. This ticket comes from the discussion
> around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
> CASSANDRA-17212, and doesn't include any of the other nested properties on
> {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: Flatten guardrails config
This is an automated email from the ASF dual-hosted git repository. adelapena pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/trunk by this push: new 8e1c8f9 Flatten guardrails config 8e1c8f9 is described below commit 8e1c8f986358aee51dd565a5a2917cb5554ed0c7 Author: Andrés de la Peña AuthorDate: Wed Feb 9 18:31:37 2022 + Flatten guardrails config patch by Andrés de la Peña; reviewed by David Capwell for CASSANDRA-17353 --- CHANGES.txt| 1 + conf/cassandra.yaml| 57 ++- src/java/org/apache/cassandra/config/Config.java | 23 +- .../cassandra/config/DatabaseDescriptor.java | 7 +- .../apache/cassandra/config/GuardrailsOptions.java | 408 +++-- .../cassandra/db/guardrails/DisableFlag.java | 2 +- .../apache/cassandra/db/guardrails/Guardrail.java | 2 +- .../apache/cassandra/db/guardrails/Guardrails.java | 102 +++--- .../cassandra/db/guardrails/GuardrailsConfig.java | 98 ++--- .../cassandra/db/guardrails/GuardrailsMBean.java | 40 +- .../apache/cassandra/db/guardrails/Threshold.java | 30 +- .../org/apache/cassandra/db/guardrails/Values.java | 4 +- .../guardrails/GuardrailColumnsPerTableTest.java | 64 ++-- .../db/guardrails/GuardrailKeyspacesTest.java | 29 +- .../db/guardrails/GuardrailPageSizeTest.java | 33 +- ...GuardrailReadBeforeWriteListOperationsTest.java | 2 +- .../GuardrailSecondaryIndexesPerTable.java | 32 +- .../guardrails/GuardrailTablePropertiesTest.java | 26 +- .../db/guardrails/GuardrailTablesTest.java | 27 +- .../cassandra/db/guardrails/GuardrailTester.java | 14 +- .../db/guardrails/GuardrailUserTimestampsTest.java | 16 +- .../db/guardrails/GuardrailViewsPerTableTest.java | 24 +- .../guardrails/GuardrailsConfigProviderTest.java | 26 +- .../cassandra/db/guardrails/GuardrailsTest.java| 46 +-- .../cassandra/db/guardrails/ThresholdTester.java | 73 ++-- 25 files changed, 608 insertions(+), 578 deletions(-) diff --git a/CHANGES.txt b/CHANGES.txt index 9b897d4..d3808db 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 4.1 + * Flatten guardrails config (CASSANDRA-17353) * Instance failed to start up due to NPE in StartupClusterConnectivityChecker (CASSANDRA-17347) * add the shorter version of version flag (-v) in cqlsh (CASSANDRA-17236) * Make vtables accessible via internode messaging (CASSANDRA-17295) diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml index 71fb562..5e8bc55 100644 --- a/conf/cassandra.yaml +++ b/conf/cassandra.yaml @@ -1510,7 +1510,7 @@ report_unconfirmed_repaired_data_mismatches: false # Having many tables and/or keyspaces negatively affects performance of many operations in the # cluster. When the number of tables/keyspaces in the cluster exceeds the following thresholds # a client warning will be sent back to the user when creating a table or keyspace. -# As of cassandra 4.1, these properties are deprecated in favor of guardrails.keyspaces and guardrails.tables +# As of cassandra 4.1, these properties are deprecated in favor of keyspaces_warn_threshold and tables_warn_threshold # table_count_warn_threshold: 150 # keyspace_count_warn_threshold: 40 @@ -1577,46 +1577,37 @@ drop_compact_storage_enabled: false # warn_threshold_kb: 0 # abort_threshold_kb: 0 -# Guardrails settings. -# guardrails: # Whether guardrails are enabled or not. Guardrails are disabled by default. -# enabled: false -# Guardrail to warn or abort when creating more user keyspaces than threshold. +# guardrails_enabled: true +# Guardrail to warn or fail when creating more user keyspaces than threshold. # The two thresholds default to -1 to disable. -# keyspaces: -# warn_threshold: -1 -# abort_threshold: -1 -# Guardrail to warn or abort when creating more user tables than threshold. +# keyspaces_warn_threshold: -1 +# keyspaces_fail_threshold: -1 +# Guardrail to warn or fail when creating more user tables than threshold. # The two thresholds default to -1 to disable. -# tables: -# warn_threshold: -1 -# abort_threshold: -1 -# Guardrail to warn or abort when creating/altering a table with more columns per table than threshold. +# tables_warn_threshold: -1 +# tables_fail_threshold: -1 +# Guardrail to warn or fail when creating/altering a table with more columns per table than threshold. # The two thresholds default to -1 to disable. -# columns_per_table: -# warn_threshold: -1 -# abort_threshold: -1 -# Guardrail to warn or abort when creating more secondary indexes per table than threshold. +# columns_per_table_warn_threshold: -1 +# columns_per_table_fail_threshold: -1 +# Guardrail to warn or fail when creating more secondary indexes per table than threshold. # The two thresholds default t
[jira] [Commented] (CASSANDRA-17186) Guardrail for number of partition keys on IN queries
[
https://issues.apache.org/jira/browse/CASSANDRA-17186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489733#comment-17489733
]
Krishna Vadali commented on CASSANDRA-17186:
[Patch|https://github.com/apache/cassandra/pull/1442] available
> Guardrail for number of partition keys on IN queries
>
>
> Key: CASSANDRA-17186
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17186
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Assignee: Krishna Vadali
>Priority: Normal
> Labels: AdventCalendar2021, lhf
> Fix For: 4.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add a guardrail for limiting the number of partitions restricted with an
> {{IN}} clause in a {{SELECT}} query, for example:
> {code:java}
> # Guardrail to warn or abort when querying with an IN restriction selecting
> # more partition keys than threshold.
> # The two thresholds default to -1 to disable.
> partition_keys_in_select:
> warn_threshold: -1
> abort_threshold: -1
> {code}
> +Additional information for newcomers:+
> * Add the configuration for the new guardrail on the number of partitions on
> IN queries in the guardrails section of cassandra.yaml.
> * Add a getPartitionKeysInSelect method in GuardrailsConfig returning a
> Threshold.Config object
> * Implement that method in GuardrailsOptions, which is the default
> yaml-based implementation of GuardrailsConfig
> * Add a Threshold guardrail named partitionKeysInSelect in Guardrails, using
> the previously created config
> * Define JMX-friendly getters and setters for the previously created config
> in GuardrailsMBean
> * Implement the JMX-friendly getters and setters in Guardrails
> * Now that we have the guardrail ready, it’s time to use it. We should
> search for a place to invoke the Guardrails.partitionKeysInSelect#guard
> method with the number of keys specified in select query. The
> SelectStatement#getSliceCommands methods look like good candidates for this.
> * Finally, add some tests for the new guardrail. Given that the new
> guardrail is a Threshold, our new test should probably extend ThresholdTester.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17347) Instance failed to start up due to NPE in StartupClusterConnectivityChecker
[
https://issues.apache.org/jira/browse/CASSANDRA-17347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANDRA-17347:
--
Since Version: 4.x
Source Control Link:
https://github.com/apache/cassandra/commit/543608ba39d5803b963d14821abe193ff0796b4f
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed into trunk as
[543608ba|https://github.com/apache/cassandra/commit/543608ba39d5803b963d14821abe193ff0796b4f]
> Instance failed to start up due to NPE in StartupClusterConnectivityChecker
> ---
>
> Key: CASSANDRA-17347
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17347
> Project: Cassandra
> Issue Type: Bug
> Components: Observability/Logging
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Instance is crashing during startup due to a NPE in
> StartupClusterConnectivityChecker with stack trace:
> {noformat}
> java.lang.NullPointerException: element cannot be mapped to a null key
> at java.util.Objects.requireNonNull(Objects.java:228)
> at
> java.util.stream.Collectors.lambda$groupingBy$45(Collectors.java:907)
> at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
> at
> java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at
> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:566)
> at
> org.apache.cassandra.net.StartupClusterConnectivityChecker.execute(StartupClusterConnectivityChecker.java:173)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (f6169d3 -> 543608b)
This is an automated email from the ASF dual-hosted git repository. ycai pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git. from f6169d3 add the shorter version of version flag (-v) in cqlsh add 543608b Instance failed to start up due to NPE in StartupClusterConnectivityChecker No new revisions were added by this update. Summary of changes: CHANGES.txt | 1 + .../apache/cassandra/net/StartupClusterConnectivityChecker.java | 8 +++- 2 files changed, 8 insertions(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17347) Instance failed to start up due to NPE in StartupClusterConnectivityChecker
[
https://issues.apache.org/jira/browse/CASSANDRA-17347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488398#comment-17488398
]
Yifan Cai edited comment on CASSANDRA-17347 at 2/9/22, 6:18 PM:
Starting commit
CI Results:
||Branch||Source||Circle CI||
|trunk|[branch|https://github.com/yifan-c/cassandra/tree/commit_remote_branch/CASSANDRA-17347-trunk-C63D5419-98C0-41CD-977E-D59055700079]|[build|https://app.circleci.com/pipelines/github/yifan-c/cassandra?branch=commit_remote_branch%2FCASSANDRA-17347-trunk-C63D5419-98C0-41CD-977E-D59055700079]|
--edit--
I had 2 CI runs of the patch. Both produce bunch of test failures. However,
they do not seem to be caused by this patch, since it only changes an internal
bit inside the connectivity checker.
So I also started a CI with just the trunk code. It showed even more failures.
See
[here|https://app.circleci.com/pipelines/github/yifan-c/cassandra?branch=test&filter=all].
It indicates the test failures are not related with the simple change in the
patch.
was (Author: yifanc):
Starting commit
CI Results (pending):
||Branch||Source||Circle CI||
|trunk|[branch|https://github.com/yifan-c/cassandra/tree/commit_remote_branch/CASSANDRA-17347-trunk-C63D5419-98C0-41CD-977E-D59055700079]|[build|https://app.circleci.com/pipelines/github/yifan-c/cassandra?branch=commit_remote_branch%2FCASSANDRA-17347-trunk-C63D5419-98C0-41CD-977E-D59055700079]|
> Instance failed to start up due to NPE in StartupClusterConnectivityChecker
> ---
>
> Key: CASSANDRA-17347
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17347
> Project: Cassandra
> Issue Type: Bug
> Components: Observability/Logging
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Instance is crashing during startup due to a NPE in
> StartupClusterConnectivityChecker with stack trace:
> {noformat}
> java.lang.NullPointerException: element cannot be mapped to a null key
> at java.util.Objects.requireNonNull(Objects.java:228)
> at
> java.util.stream.Collectors.lambda$groupingBy$45(Collectors.java:907)
> at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
> at
> java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at
> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:566)
> at
> org.apache.cassandra.net.StartupClusterConnectivityChecker.execute(StartupClusterConnectivityChecker.java:173)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17236) Add support for short form of version to CQLSH
[
https://issues.apache.org/jira/browse/CASSANDRA-17236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-17236:
--
Status: Ready to Commit (was: Review In Progress)
> Add support for short form of version to CQLSH
> --
>
> Key: CASSANDRA-17236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17236
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Semantics
>Reporter: Madhavan
>Assignee: Yash Ladha
>Priority: Low
> Labels: lhf
> Fix For: 4.x
>
>
> Today we do only support the `–version` long option/form for cqlsh and this
> enhancement Jira is to request that we also offer a shorter version `-v` to
> cqlsh. This will have consistency benefits with other tools and even match
> with what we have at `bin/cassandra -v` option for instance.
> Today, `cqlsh` does support `--v` to get the version which is different than
> the single dashed short form that is available at many other tools. Thanks to
> Ekaterina for finding this. It looks like this is stemming from Python's
> parse mechanism which is detailed here,
> [https://docs.python.org/2.7/library/optparse.html#printing-a-version-string].
>
> [https://github.com/apache/cassandra/blob/trunk/bin/cqlsh.py#L194-L196]
> {quote}parser = optparse.OptionParser(description=description, epilog=epilog,
> usage="Usage: %prog [options] [host [port]]",
> version='cqlsh ' + version)
> {quote}
>
> {{$ bin/cqlsh --v}}
> {{cqlsh 6.0.0}}
> This looks like a weird implementation at Python. Both (\-\-help) and
> (\-\-version) options are stemming from here,
> [https://github.com/python/cpython/blob/2.7/Lib/optparse.py#L1248-L1256] and
> they did decide to ignore the short form option for version and it somehow
> automatically takes the (--v) option to spit the version info.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (6d7b0a1 -> f6169d3)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 6d7b0a1 Fix classpath file creation for eclipse add f6169d3 add the shorter version of version flag (-v) in cqlsh No new revisions were added by this update. Summary of changes: CHANGES.txt | 1 + bin/cqlsh.py | 1 + 2 files changed, 2 insertions(+) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17236) Add support for short form of version to CQLSH
[
https://issues.apache.org/jira/browse/CASSANDRA-17236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-17236:
--
Fix Version/s: 4.1
(was: 4.x)
Source Control Link:
https://github.com/apache/cassandra/commit/f6169d399f79168cbc3580d95082b0e2a99db048
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Add support for short form of version to CQLSH
> --
>
> Key: CASSANDRA-17236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17236
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Semantics
>Reporter: Madhavan
>Assignee: Yash Ladha
>Priority: Low
> Labels: lhf
> Fix For: 4.1
>
>
> Today we do only support the `–version` long option/form for cqlsh and this
> enhancement Jira is to request that we also offer a shorter version `-v` to
> cqlsh. This will have consistency benefits with other tools and even match
> with what we have at `bin/cassandra -v` option for instance.
> Today, `cqlsh` does support `--v` to get the version which is different than
> the single dashed short form that is available at many other tools. Thanks to
> Ekaterina for finding this. It looks like this is stemming from Python's
> parse mechanism which is detailed here,
> [https://docs.python.org/2.7/library/optparse.html#printing-a-version-string].
>
> [https://github.com/apache/cassandra/blob/trunk/bin/cqlsh.py#L194-L196]
> {quote}parser = optparse.OptionParser(description=description, epilog=epilog,
> usage="Usage: %prog [options] [host [port]]",
> version='cqlsh ' + version)
> {quote}
>
> {{$ bin/cqlsh --v}}
> {{cqlsh 6.0.0}}
> This looks like a weird implementation at Python. Both (\-\-help) and
> (\-\-version) options are stemming from here,
> [https://github.com/python/cpython/blob/2.7/Lib/optparse.py#L1248-L1256] and
> they did decide to ignore the short form option for version and it somehow
> automatically takes the (--v) option to spit the version info.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-16052) CEP-7 Storage Attached Index for Apache Cassandra
[ https://issues.apache.org/jira/browse/CASSANDRA-16052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Rackliffe reassigned CASSANDRA-16052: --- Assignee: Caleb Rackliffe > CEP-7 Storage Attached Index for Apache Cassandra > - > > Key: CASSANDRA-16052 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16052 > Project: Cassandra > Issue Type: Epic > Components: Feature/2i Index >Reporter: Zhao Yang >Assignee: Caleb Rackliffe >Priority: Normal > > [CEP|https://docs.google.com/document/d/1V830eAMmQAspjJdjviVZIaSolVGvZ1hVsqOLWyV0DS4/edit#heading=h.67ap6rr1mxr] > - A new index implementation, called Storage > Attached Index(SAI), based on the advancement made by SASI. > * disk usage by sharing of common data between multiple column indexes on > the same table and better compression of on-disk structures. > * numeric range query performance with modified KDTree and collection type > support. > * compaction performance and stability for larger data set. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17295) Make vtables accessible via internode messaging
[ https://issues.apache.org/jira/browse/CASSANDRA-17295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489692#comment-17489692 ] Ekaterina Dimitrova commented on CASSANDRA-17295: - Just to bring some clarity, CircleCI does not pull the newly tagged version of CCM. There is workaround until I fix it. But first there were lagging issues in Jenkins so I am working on that to get proper CI pre-release of the pre-trunk branches. As Stefan pointed the thread, there is a ticket for the circle issue. In the meantime you can add the following in your config and push your branch in circle, that is the easiest to see things work - - DTEST_REPO: https://github.com/ekaterinadimitrova2/cassandra-dtest.git - DTEST_BRANCH: CASSANDRA-15234 Apologize for the inconvenience, this tagging issue is new and there was no way to know of it in advance. Also, Jenkins picks the right ccm tag…. > Make vtables accessible via internode messaging > --- > > Key: CASSANDRA-17295 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17295 > Project: Cassandra > Issue Type: Improvement > Components: Feature/Virtual Tables >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.1 > > Time Spent: 50m > Remaining Estimate: 0h > > As an extension of CASSANDRA-15399 and needed to solve CASSANDRA-15566, we > need the ability to perform queries against vtables using internode > messaging; currently this is limited to CQL which isn’t exposed in internode -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15254) Allow UPDATE on settings virtual table to change running configurations
[
https://issues.apache.org/jira/browse/CASSANDRA-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489689#comment-17489689
]
David Capwell edited comment on CASSANDRA-15254 at 2/9/22, 5:15 PM:
bq. so it might not be before a couple of weeks
No worries, wanted to have you look as we talked about this before, will have
others review, but wanted to share the SettingsTable class
{code}
final class SettingsTable extends AbstractVirtualTable
{
private static final String NAME = "name";
private static final String VALUE = "value";
protected static final Map PROPERTIES =
ImmutableMap.copyOf(getProperties());
private final Config config;
SettingsTable(String keyspace)
{
this(keyspace, DatabaseDescriptor.getRawConfig());
}
SettingsTable(String keyspace, Config config)
{
super(TableMetadata.builder(keyspace, "settings")
.comment("current settings")
.kind(TableMetadata.Kind.VIRTUAL)
.partitioner(new LocalPartitioner(UTF8Type.instance))
.addPartitionKeyColumn(NAME, UTF8Type.instance)
.addRegularColumn(VALUE, UTF8Type.instance)
.build());
this.config = config;
}
@Override
public DataSet data(DecoratedKey partitionKey)
{
SimpleDataSet result = new SimpleDataSet(metadata());
String name = UTF8Type.instance.compose(partitionKey.getKey());
if (PROPERTIES.containsKey(name))
result.row(name).column(VALUE, getValue(PROPERTIES.get(name)));
return result;
}
@Override
public DataSet data()
{
SimpleDataSet result = new SimpleDataSet(metadata());
for (Map.Entry e : PROPERTIES.entrySet())
result.row(e.getKey()).column(VALUE, getValue(e.getValue()));
return result;
}
private String getValue(Property prop)
{
Object value = prop.get(config);
return value == null ? null : value.toString();
}
private static Map getProperties()
{
//TODO possible to move away from "_" to "."? yaml supports "." so
this can cause an inconsistency
// also, with "_" it isn't clear that a value is in fact nested, so
could cause confussion...
Map properties =
Properties.defaultLoader().flatten(Config.class, "_");
Map replacements =
Replacements.getNameReplacements(Config.class)
.get(Config.class);
if (replacements != null)
{
for (Replacement r : replacements.values())
{
Property latest = properties.get(r.newName);
assert latest != null: String.format("Unable to find
replacement new name: " + r.newName);
Property conflict = properties.put(r.oldName,
r.toProperty(latest));
// some configs kept the same name, but changed the type, if
this is detected then rely on the replaced property
assert conflict == null || r.oldName.equals(r.newName):
String.format("Multiple properties exist for " + r.oldName);
}
}
return properties;
}
}
{code}
This is not backwards compatible as there were a few special cased configs that
used a different name than the yaml (documented in the settings table test).
This also works with every nested property and exposes all.
Property is get/set for each config, so now have a consistent way for YAML and
SettingTable to interact the same way; the only complication for this ticket is
that we work with Strings and Property works with the actual type, so need to
add a conversion before calling set.
was (Author: dcapwell):
No worries, wanted to have you look as we talked about this before. In the
patch the settings table is now
{code}
/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.cassandra.db.virtual;
import java.util.Map;
import com.google.common.collect.ImmutableMap;
import org.apache.cassandra.config.Config;
import or
[jira] [Commented] (CASSANDRA-15254) Allow UPDATE on settings virtual table to change running configurations
[
https://issues.apache.org/jira/browse/CASSANDRA-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489689#comment-17489689
]
David Capwell commented on CASSANDRA-15254:
---
No worries, wanted to have you look as we talked about this before. In the
patch the settings table is now
{code}
/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.cassandra.db.virtual;
import java.util.Map;
import com.google.common.collect.ImmutableMap;
import org.apache.cassandra.config.Config;
import org.apache.cassandra.config.DatabaseDescriptor;
import org.apache.cassandra.config.Properties;
import org.apache.cassandra.config.Replacement;
import org.apache.cassandra.config.Replacements;
import org.apache.cassandra.db.DecoratedKey;
import org.apache.cassandra.db.marshal.UTF8Type;
import org.apache.cassandra.dht.LocalPartitioner;
import org.apache.cassandra.schema.TableMetadata;
import org.yaml.snakeyaml.introspector.Property;
final class SettingsTable extends AbstractVirtualTable
{
private static final String NAME = "name";
private static final String VALUE = "value";
protected static final Map PROPERTIES =
ImmutableMap.copyOf(getProperties());
private final Config config;
SettingsTable(String keyspace)
{
this(keyspace, DatabaseDescriptor.getRawConfig());
}
SettingsTable(String keyspace, Config config)
{
super(TableMetadata.builder(keyspace, "settings")
.comment("current settings")
.kind(TableMetadata.Kind.VIRTUAL)
.partitioner(new LocalPartitioner(UTF8Type.instance))
.addPartitionKeyColumn(NAME, UTF8Type.instance)
.addRegularColumn(VALUE, UTF8Type.instance)
.build());
this.config = config;
}
@Override
public DataSet data(DecoratedKey partitionKey)
{
SimpleDataSet result = new SimpleDataSet(metadata());
String name = UTF8Type.instance.compose(partitionKey.getKey());
if (PROPERTIES.containsKey(name))
result.row(name).column(VALUE, getValue(PROPERTIES.get(name)));
return result;
}
@Override
public DataSet data()
{
SimpleDataSet result = new SimpleDataSet(metadata());
for (Map.Entry e : PROPERTIES.entrySet())
result.row(e.getKey()).column(VALUE, getValue(e.getValue()));
return result;
}
private String getValue(Property prop)
{
Object value = prop.get(config);
return value == null ? null : value.toString();
}
private static Map getProperties()
{
//TODO possible to move away from "_" to "."? yaml supports "." so
this can cause an inconsistency
// also, with "_" it isn't clear that a value is in fact nested, so
could cause confussion...
Map properties =
Properties.defaultLoader().flatten(Config.class, "_");
Map replacements =
Replacements.getNameReplacements(Config.class)
.get(Config.class);
if (replacements != null)
{
for (Replacement r : replacements.values())
{
Property latest = properties.get(r.newName);
assert latest != null: String.format("Unable to find
replacement new name: " + r.newName);
Property conflict = properties.put(r.oldName,
r.toProperty(latest));
// some configs kept the same name, but changed the type, if
this is detected then rely on the replaced property
assert conflict == null || r.oldName.equals(r.newName):
String.format("Multiple properties exist for " + r.oldName);
}
}
return properties;
}
}
{code}
This is not backwards compatible as there were a few special cased configs that
used a different name than the yaml (documented in the settings table test).
This also works with every nested property and exposes all.
Property is get/set for each config, so now have a consistent way for YAML and
SettingTable to interact the same
[jira] [Commented] (CASSANDRA-17295) Make vtables accessible via internode messaging
[ https://issues.apache.org/jira/browse/CASSANDRA-17295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489687#comment-17489687 ] David Capwell commented on CASSANDRA-17295: --- I am in chats with [~edimitrova] about this issue, she is looking into it atm. The CCM change attempts to migrate configs, so without the ccm change we should be using the old configs which are required to stay working... she is trying to figure out what's going on. > Make vtables accessible via internode messaging > --- > > Key: CASSANDRA-17295 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17295 > Project: Cassandra > Issue Type: Improvement > Components: Feature/Virtual Tables >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.1 > > Time Spent: 50m > Remaining Estimate: 0h > > As an extension of CASSANDRA-15399 and needed to solve CASSANDRA-15566, we > need the ability to perform queries against vtables using internode > messaging; currently this is limited to CQL which isn’t exposed in internode -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17362) Update SUPPORTED_UPGRADE_PATHS to include 3.0 and 3.x to 4.1 paths and remove obsolete tests
[ https://issues.apache.org/jira/browse/CASSANDRA-17362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Rackliffe reassigned CASSANDRA-17362: --- Assignee: Caleb Rackliffe > Update SUPPORTED_UPGRADE_PATHS to include 3.0 and 3.x to 4.1 paths and remove > obsolete tests > > > Key: CASSANDRA-17362 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17362 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java >Reporter: Caleb Rackliffe >Assignee: Caleb Rackliffe >Priority: Normal > Fix For: 4.x > > > There are two things we might want to clean up around the upgrade test > versioning: > 1.) Remove or modify tests on trunk for upgrade paths that start before a > supported version (ex. 2.2) or end before the current version > 2.) Add 3.0 -> 4.1 and 3.x -> 4.1 to the list of supported upgrade paths -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (30eca23 -> 56da4b9)
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git.
omit 30eca23 generate docs for 03f46031
add 82f848e Updated publish date for "Tightening Security Pt 2" blog to
Feb 7
add ee56da1 February 2022 blog post for "Apache Cassandra Changelog #12"
new 56da4b9 generate docs for ee56da10
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (30eca23)
\
N -- N -- N refs/heads/asf-staging (56da4b9)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../blog/cassandra-documentation-changelog-12.png | Bin 0 -> 1732984 bytes
content/_/blog.html| 26 -
...ache-Cassandra-Changelog-12-February-2022.html} | 117 ++---
...ening-Security-for-Apache-Cassandra-Part-2.html | 2 +-
content/search-index.js| 2 +-
.../blog/cassandra-documentation-changelog-12.png | Bin 0 -> 1732984 bytes
site-content/source/modules/ROOT/pages/blog.adoc | 26 -
...pache-Cassandra-Changelog-12-February-2022.adoc | 93
...ening-Security-for-Apache-Cassandra-Part-2.adoc | 2 +-
site-ui/build/ui-bundle.zip| Bin 4740084 -> 4740084
bytes
10 files changed, 201 insertions(+), 67 deletions(-)
create mode 100644
content/_/_images/blog/cassandra-documentation-changelog-12.png
copy content/_/blog/{Apache-Cassandra-Changelog-1-October-2020.html =>
Apache-Cassandra-Changelog-12-February-2022.html} (61%)
create mode 100644
site-content/source/modules/ROOT/images/blog/cassandra-documentation-changelog-12.png
create mode 100644
site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-12-February-2022.adoc
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17356) WEBSITE - February 2022 changelog #12
[ https://issues.apache.org/jira/browse/CASSANDRA-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-17356: --- Fix Version/s: NA (was: 4.0.x) Source Control Link: https://github.com/apache/cassandra-website/commit/ee56da1056fcc76bd4dc23a8ac1204dc4e815677 Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed into trunk at ee56da1056fcc76bd4dc23a8ac1204dc4e815677 > WEBSITE - February 2022 changelog #12 > - > > Key: CASSANDRA-17356 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17356 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: c17356-01-blog-index.png, c17356-02-blog-post.png > > > This ticket is to capture the work associated with publishing the January > 2022 changelog blog #12 > If this blog cannot be published by the *February 10, 2022 publish date*, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17360) WEBSITE - Change publish date for "Tightening Security Pt 2" blog post
[ https://issues.apache.org/jira/browse/CASSANDRA-17360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-17360: --- Fix Version/s: NA (was: 4.0.x) Source Control Link: https://github.com/apache/cassandra-website/commit/82f848eca138e0f383ea4fb24ac7c20f63c56223 Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed into trunk at 82f848eca138e0f383ea4fb24ac7c20f63c56223 > WEBSITE - Change publish date for "Tightening Security Pt 2" blog post > -- > > Key: CASSANDRA-17360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17360 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Diogenese Topper >Priority: Normal > Fix For: NA > > > Blog post didn't get published in time. CASSANDRA-17343 was only published > yesterday so the blog post publish date needs to be changed. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] 02/02: February 2022 blog post for "Apache Cassandra Changelog #12"
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-website.git commit ee56da1056fcc76bd4dc23a8ac1204dc4e815677 Author: Diogenese Topper AuthorDate: Mon Feb 7 15:39:46 2022 -0800 February 2022 blog post for "Apache Cassandra Changelog #12" Add blog post titled "Apache Cassandra Changelog 12" Add image for blog Modify blog index patch by Diogenese Topper; review by Erick Ramirez for CASSANDRA-17356 Co-authored-by: Erick Ramirez --- .../blog/cassandra-documentation-changelog-12.png | Bin 0 -> 1732984 bytes site-content/source/modules/ROOT/pages/blog.adoc | 24 ++ ...pache-Cassandra-Changelog-12-February-2022.adoc | 93 + 3 files changed, 117 insertions(+) diff --git a/site-content/source/modules/ROOT/images/blog/cassandra-documentation-changelog-12.png b/site-content/source/modules/ROOT/images/blog/cassandra-documentation-changelog-12.png new file mode 100644 index 000..86ad4b1 Binary files /dev/null and b/site-content/source/modules/ROOT/images/blog/cassandra-documentation-changelog-12.png differ diff --git a/site-content/source/modules/ROOT/pages/blog.adoc b/site-content/source/modules/ROOT/pages/blog.adoc index 31bd3fa..d039eff 100644 --- a/site-content/source/modules/ROOT/pages/blog.adoc +++ b/site-content/source/modules/ROOT/pages/blog.adoc @@ -14,6 +14,30 @@ NOTES FOR CONTENT CREATORS [openblock,card-header] -- [discrete] +=== Apache Cassandra Changelog #12 +[discrete] + February 10, 2022 +-- +[openblock,card-content] +-- +A new Build Lead role is announced. Ideas are requested for Google Summer of Code, and the Future of UDF is defined. Cassandra’s CI process is formalized and a Trie Memtable Implementation is discussed. + +[openblock,card-btn card-btn--blog] + +[.btn.btn--alt] +xref:blog/Apache-Cassandra-Changelog-12-February-2022.adoc[Read More] + + +-- + +//end card + +//start card +[openblock,card shadow relative test] + +[openblock,card-header] +-- +[discrete] === Tightening Security for Apache Cassandra: Part 2 [discrete] February 7, 2022 diff --git a/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-12-February-2022.adoc b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-12-February-2022.adoc new file mode 100644 index 000..7208589 --- /dev/null +++ b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-12-February-2022.adoc @@ -0,0 +1,93 @@ += Apache Cassandra Changelog #12 +:page-layout: single-post +:page-role: blog-post +:page-post-date: February 10, 2022 +:page-post-author: The Apache Cassandra Community +:description: The Apache Cassandra Community +:keywords: + +image::blog/changelog_header.jpg[Apache Cassandra Changelog] +Our monthly roundup of key activities and knowledge to keep the community informed. + += Release Notes + +=== Release + +Available since 7th September, the latest release of Apache Cassandra is https://www.apache.org/dyn/closer.lua/cassandra/4.0.1/[4.0.1^], (https://downloads.apache.org/cassandra/4.0.1/apache-cassandra-4.0.1-bin.tar.gz.asc[pgp^], https://downloads.apache.org/cassandra/4.0.1/apache-cassandra-4.0.1-bin.tar.gz.sha256[sha256^], and https://archive.apache.org/dist/cassandra/4.0.1/apache-cassandra-4.0.1-bin.tar.gz.sha512[sha512^]). This was a rapid release to fix a https://issues.apache.org/ji [...] + +Note: As the docs are not yet updated, the bintray location for Debian users is replaced with the https://apache.jfrog.io/artifactory/cassandra/[ASF's JFrog Artifactory location^]. + +See the xref:download.adoc[download section] for the latest stable and older supported versions of source and binary distributions. + +To stay up-to-date, we recommend joining the Cassandra xref:community.adoc#discussions[mailing list]. + +== Community Notes + +_Updates on Cassandra Enhancement Proposals (CEPs), how to contribute, and other community activities._ + +_Are you new to the project? We have a handy xref:development/index.adoc[‘Contributing to Cassandra’] page on how to get involved and get started. Additionally, we have established two quick labels you should take a look at if you are new to the project. One is for https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496&quickFilter=2252[“Failing Tests”^] and the other corresponds to our https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&quickFilter=2162[“Low [...] + +Read PMC member Josh McKenzie’s https://lists.apache.org/thread/pclo1tpqsfkc4skxhftrydos89o1t72q[latest bi-weekly update^] for ongoing discussions and the latest on ticket progress. + +=== Added + +A massive thank you goes to *Lorina Poland* for converting all the Cassandra documentation from reStructuredText to AsciiDoc for the new website and another heartfelt thank you to
[cassandra-website] branch trunk updated (03f4603 -> ee56da1)
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-website.git. from 03f4603 February 2022 blog "Tightening Security for Apache Cassandra Part: 2" new 82f848e Updated publish date for "Tightening Security Pt 2" blog to Feb 7 new ee56da1 February 2022 blog post for "Apache Cassandra Changelog #12" 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: .../blog/cassandra-documentation-changelog-12.png | Bin 0 -> 1732984 bytes site-content/source/modules/ROOT/pages/blog.adoc | 26 +- ...pache-Cassandra-Changelog-12-February-2022.adoc | 93 + ...ening-Security-for-Apache-Cassandra-Part-2.adoc | 2 +- 4 files changed, 119 insertions(+), 2 deletions(-) create mode 100644 site-content/source/modules/ROOT/images/blog/cassandra-documentation-changelog-12.png create mode 100644 site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-12-February-2022.adoc - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] 01/02: Updated publish date for "Tightening Security Pt 2" blog to Feb 7
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-website.git commit 82f848eca138e0f383ea4fb24ac7c20f63c56223 Author: Diogenese Topper AuthorDate: Mon Feb 7 13:10:04 2022 -0800 Updated publish date for "Tightening Security Pt 2" blog to Feb 7 patch by Diogenese Topper; review by Erick Ramirez for CASSANDRA-17360 --- site-content/source/modules/ROOT/pages/blog.adoc| 2 +- .../pages/blog/Tightening-Security-for-Apache-Cassandra-Part-2.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/site-content/source/modules/ROOT/pages/blog.adoc b/site-content/source/modules/ROOT/pages/blog.adoc index 87f608c..31bd3fa 100644 --- a/site-content/source/modules/ROOT/pages/blog.adoc +++ b/site-content/source/modules/ROOT/pages/blog.adoc @@ -16,7 +16,7 @@ NOTES FOR CONTENT CREATORS [discrete] === Tightening Security for Apache Cassandra: Part 2 [discrete] - February 4, 2022 + February 7, 2022 -- [openblock,card-content] -- diff --git a/site-content/source/modules/ROOT/pages/blog/Tightening-Security-for-Apache-Cassandra-Part-2.adoc b/site-content/source/modules/ROOT/pages/blog/Tightening-Security-for-Apache-Cassandra-Part-2.adoc index 8752c64..719c2a6 100644 --- a/site-content/source/modules/ROOT/pages/blog/Tightening-Security-for-Apache-Cassandra-Part-2.adoc +++ b/site-content/source/modules/ROOT/pages/blog/Tightening-Security-for-Apache-Cassandra-Part-2.adoc @@ -1,7 +1,7 @@ = Tightening security for Apache Cassandra: Part 2 :page-layout: single-post :page-role: blog-post -:page-post-date: February, 4 2022 +:page-post-date: February, 7 2022 :page-post-author: Maulin Vasavada :description: The Apache Cassandra Community - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17364) dependency on commons-io is to 2.6 which has a CVE
[ https://issues.apache.org/jira/browse/CASSANDRA-17364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams reassigned CASSANDRA-17364: Assignee: Brandon Williams > dependency on commons-io is to 2.6 which has a CVE > -- > > Key: CASSANDRA-17364 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17364 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: PJ Fanning >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.x > > > Can this be upgraded, ideally to v2.11.0? > [https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1] > [https://github.com/apache/cassandra/blob/trunk/build.xml#L510] > > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17353) Flatten guardrails configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489643#comment-17489643
]
Andres de la Peña commented on CASSANDRA-17353:
---
Here is a much better looking CI run after following Ekaterina's advice and
using her fixed ccm branch:
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/1440]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1290/workflows/ccf7a456-2614-4b84-a3df-0549df6969b0]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1290/workflows/cef70256-7d28-4e89-8011-f5ecfd0c79e4]
> Flatten guardrails configuration
>
>
> Key: CASSANDRA-17353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
> instead of the current nested format. This ticket comes from the discussion
> around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
> CASSANDRA-17212, and doesn't include any of the other nested properties on
> {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17048) Replace sequential sstable generation identifier with UUID v1
[ https://issues.apache.org/jira/browse/CASSANDRA-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489603#comment-17489603 ] Jacek Lewandowski commented on CASSANDRA-17048: --- Thanks [~adelapena], and sorry for not responding - most of the last week I was on vacation. I've accepted your suggestions, squashed and rebased, though after rebasing I have quite bad looking test results: https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/177/workflows/7b6e1a32-fe40-4526-899f-4162a664e736 > Replace sequential sstable generation identifier with UUID v1 > - > > Key: CASSANDRA-17048 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17048 > Project: Cassandra > Issue Type: Improvement > Components: Local/SSTable >Reporter: Jacek Lewandowski >Assignee: Jacek Lewandowski >Priority: Normal > Fix For: 4.1 > > Time Spent: 8h 10m > Remaining Estimate: 0h > > Replace the current sequential sstable generation identifier with ULID based. > ULID is better because we do not need to scan the existing files to pick the > starting number as well as we can generate globally unique identifiers. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17294) Fix generate-eclipse-files
[
https://issues.apache.org/jira/browse/CASSANDRA-17294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-17294:
---
Fix Version/s: 4.1
Source Control Link:
https://github.com/apache/cassandra/commit/6d7b0a10796cfedd11c4a7a1de81bc48bf8ea3cc
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed into trunk at 6d7b0a10796cfedd11c4a7a1de81bc48bf8ea3cc
> Fix generate-eclipse-files
> --
>
> Key: CASSANDRA-17294
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17294
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Yash Ladha
>Assignee: Yash Ladha
>Priority: Normal
> Fix For: 4.1
>
>
> I was doing the local setup of cassandra and using the
> [https://github.com/eclipse/eclipse.jdt.ls] for development. When i visited
> the `CassandraDaemon.java` greeted with an error that the file is not in
> classpath, which was very weird. Upon investigation found out that the
> `classpath` was not closed and due to which that error is occuring.
> This issue is to solve the generation of correct .{_}classpath{_} file and
> inclusion of correct libs.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17294) Fix generate-eclipse-files
[
https://issues.apache.org/jira/browse/CASSANDRA-17294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489585#comment-17489585
]
Benjamin Lerer commented on CASSANDRA-17294:
[~yashLadha] thanks for the patch. It looks good to me.
> Fix generate-eclipse-files
> --
>
> Key: CASSANDRA-17294
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17294
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Yash Ladha
>Assignee: Yash Ladha
>Priority: Normal
>
> I was doing the local setup of cassandra and using the
> [https://github.com/eclipse/eclipse.jdt.ls] for development. When i visited
> the `CassandraDaemon.java` greeted with an error that the file is not in
> classpath, which was very weird. Upon investigation found out that the
> `classpath` was not closed and due to which that error is occuring.
> This issue is to solve the generation of correct .{_}classpath{_} file and
> inclusion of correct libs.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17294) Fix generate-eclipse-files
[
https://issues.apache.org/jira/browse/CASSANDRA-17294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-17294:
---
Status: Ready to Commit (was: Review In Progress)
> Fix generate-eclipse-files
> --
>
> Key: CASSANDRA-17294
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17294
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Yash Ladha
>Assignee: Yash Ladha
>Priority: Normal
>
> I was doing the local setup of cassandra and using the
> [https://github.com/eclipse/eclipse.jdt.ls] for development. When i visited
> the `CassandraDaemon.java` greeted with an error that the file is not in
> classpath, which was very weird. Upon investigation found out that the
> `classpath` was not closed and due to which that error is occuring.
> This issue is to solve the generation of correct .{_}classpath{_} file and
> inclusion of correct libs.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17294) Fix generate-eclipse-files
[
https://issues.apache.org/jira/browse/CASSANDRA-17294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-17294:
---
Reviewers: Benjamin Lerer, Berenguer Blasi (was: Berenguer Blasi)
Status: Review In Progress (was: Needs Committer)
> Fix generate-eclipse-files
> --
>
> Key: CASSANDRA-17294
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17294
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Yash Ladha
>Assignee: Yash Ladha
>Priority: Normal
>
> I was doing the local setup of cassandra and using the
> [https://github.com/eclipse/eclipse.jdt.ls] for development. When i visited
> the `CassandraDaemon.java` greeted with an error that the file is not in
> classpath, which was very weird. Upon investigation found out that the
> `classpath` was not closed and due to which that error is occuring.
> This issue is to solve the generation of correct .{_}classpath{_} file and
> inclusion of correct libs.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17364) dependency on commons-io is to 2.6 which has a CVE
[ https://issues.apache.org/jira/browse/CASSANDRA-17364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17364: - Change Category: Operability Complexity: Low Hanging Fruit Component/s: Build Fix Version/s: 4.x Status: Open (was: Triage Needed) > dependency on commons-io is to 2.6 which has a CVE > -- > > Key: CASSANDRA-17364 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17364 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: PJ Fanning >Priority: Normal > Fix For: 4.x > > > Can this be upgraded, ideally to v2.11.0? > [https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1] > [https://github.com/apache/cassandra/blob/trunk/build.xml#L510] > > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17364) dependency on commons-io is to 2.6 which has a CVE
[ https://issues.apache.org/jira/browse/CASSANDRA-17364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489574#comment-17489574 ] Brandon Williams commented on CASSANDRA-17364: -- bq. https://github.com/apache/cassandra/blob/trunk/build.xml#L510 shows a dependency on v2.6 The scope is 'test' though and we don't ship this, which is likely why OWASP isn't interested since it's not a problem. bq. commons-io 2.x tends to be good with backward compatibility - so if code works with v2.6, it will almost certainly work with v2.11.0 (latest version). Since it's just a test dependency and thus fairly low risk, I can see the value in doing this to keep it out of other scanners' alerts. I don't want to introduce more variables to CI right this minute however, but I'll keep this ticket open for later when it's in a better state for this change. > dependency on commons-io is to 2.6 which has a CVE > -- > > Key: CASSANDRA-17364 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17364 > Project: Cassandra > Issue Type: Improvement >Reporter: PJ Fanning >Priority: Normal > > Can this be upgraded, ideally to v2.11.0? > [https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1] > [https://github.com/apache/cassandra/blob/trunk/build.xml#L510] > > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: Fix classpath file creation for eclipse
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 The following commit(s) were added to refs/heads/trunk by this push: new 6d7b0a1 Fix classpath file creation for eclipse 6d7b0a1 is described below commit 6d7b0a10796cfedd11c4a7a1de81bc48bf8ea3cc Author: Yash Ladha AuthorDate: Wed Jan 26 09:30:42 2022 +0530 Fix classpath file creation for eclipse Patch by Yash Ladha; reviewed by Benjamin Lerer and Berenguer Blasi for CASSANDRA-17294 When building the eclipse file for development, `.classpath` file was not correctly generated as it was not getting closed. Also there were missing third-party libs that were essential for development. This commit fixes the generation of classpath for `generate-eclipse-files` command. --- build.xml | 37 ++--- 1 file changed, 22 insertions(+), 15 deletions(-) diff --git a/build.xml b/build.xml index 67a758c..07c4057 100644 --- a/build.xml +++ b/build.xml @@ -2111,7 +2111,24 @@ ]]> - - - - - - - - - - - - - - + - + - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17325) Remove obsolete enum34 package from requirements
[ https://issues.apache.org/jira/browse/CASSANDRA-17325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17325: - Fix Version/s: 4.1 (was: 4.x) Source Control Link: https://github.com/apache/cassandra/commit/32bdf14ec916404f5fdd4b918b7d80a7bb92aa38 Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed, thanks! > Remove obsolete enum34 package from requirements > > > Key: CASSANDRA-17325 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17325 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.1 > > > The enum34 package was used for backwards compatibility with python prior to > the introduction of the Enum class in python 3.4. This can now be safely > removed as a dependency in requirements.txt as CQLSH supports Python 3.6+. > No code changes are needed. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: Remove obsolete enum34 package
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/trunk by this push: new 32bdf14 Remove obsolete enum34 package 32bdf14 is described below commit 32bdf14ec916404f5fdd4b918b7d80a7bb92aa38 Author: Brad Schoening <5796692+bschoen...@users.noreply.github.com> AuthorDate: Fri Jan 28 20:48:45 2022 -0500 Remove obsolete enum34 package Patch by Brad Schoening; reviewed by brandonwilliams and paulo for CASSANDRA-17325 --- pylib/requirements.txt | 1 - 1 file changed, 1 deletion(-) diff --git a/pylib/requirements.txt b/pylib/requirements.txt index 8dd527e..b6ca329 100644 --- a/pylib/requirements.txt +++ b/pylib/requirements.txt @@ -9,7 +9,6 @@ six>=1.12.0 coverage decorator docopt -enum34 flaky mock nose - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17364) dependency on commons-io is to 2.6 which has a CVE
[ https://issues.apache.org/jira/browse/CASSANDRA-17364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489567#comment-17489567 ] PJ Fanning commented on CASSANDRA-17364: [https://github.com/apache/cassandra/blob/trunk/build.xml#L510] shows a dependency on v2.6 [https://mvnrepository.com/artifact/commons-io/commons-io/2.6] shows the CVE - [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29425] In [https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1] - commons-io is a 'managed' dependency - maybe OWASP report ignores these dependencies. commons-io 2.x tends to be good with backward compatibility - so if code works with v2.6, it will almost certainly work with v2.11.0 (latest version). Would it be possible to upgrade based on this info? > dependency on commons-io is to 2.6 which has a CVE > -- > > Key: CASSANDRA-17364 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17364 > Project: Cassandra > Issue Type: Improvement >Reporter: PJ Fanning >Priority: Normal > > Can this be upgraded, ideally to v2.11.0? > [https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1] > [https://github.com/apache/cassandra/blob/trunk/build.xml#L510] > > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17325) Remove obsolete enum34 package from requirements
[ https://issues.apache.org/jira/browse/CASSANDRA-17325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17325: - Status: Review In Progress (was: Needs Committer) > Remove obsolete enum34 package from requirements > > > Key: CASSANDRA-17325 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17325 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > The enum34 package was used for backwards compatibility with python prior to > the introduction of the Enum class in python 3.4. This can now be safely > removed as a dependency in requirements.txt as CQLSH supports Python 3.6+. > No code changes are needed. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17325) Remove obsolete enum34 package from requirements
[ https://issues.apache.org/jira/browse/CASSANDRA-17325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17325: - Status: Ready to Commit (was: Review In Progress) > Remove obsolete enum34 package from requirements > > > Key: CASSANDRA-17325 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17325 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > The enum34 package was used for backwards compatibility with python prior to > the introduction of the Enum class in python 3.4. This can now be safely > removed as a dependency in requirements.txt as CQLSH supports Python 3.6+. > No code changes are needed. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17325) Remove obsolete enum34 package from requirements
[ https://issues.apache.org/jira/browse/CASSANDRA-17325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17325: - Reviewers: Brandon Williams, Paulo Motta (was: Brandon Williams) > Remove obsolete enum34 package from requirements > > > Key: CASSANDRA-17325 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17325 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > The enum34 package was used for backwards compatibility with python prior to > the introduction of the Enum class in python 3.4. This can now be safely > removed as a dependency in requirements.txt as CQLSH supports Python 3.6+. > No code changes are needed. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17325) Remove obsolete enum34 package from requirements
[ https://issues.apache.org/jira/browse/CASSANDRA-17325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489564#comment-17489564 ] Paulo Motta commented on CASSANDRA-17325: - +1 > Remove obsolete enum34 package from requirements > > > Key: CASSANDRA-17325 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17325 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > The enum34 package was used for backwards compatibility with python prior to > the introduction of the Enum class in python 3.4. This can now be safely > removed as a dependency in requirements.txt as CQLSH supports Python 3.6+. > No code changes are needed. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17325) Remove obsolete enum34 package from requirements
[ https://issues.apache.org/jira/browse/CASSANDRA-17325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489562#comment-17489562 ] Brandon Williams commented on CASSANDRA-17325: -- LGTM. [Circle|https://app.circleci.com/pipelines/github/driftx/cassandra/349/workflows/f0bf1796-e1be-4f0c-abbf-799e38610f8a] also looks good, +1. > Remove obsolete enum34 package from requirements > > > Key: CASSANDRA-17325 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17325 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > The enum34 package was used for backwards compatibility with python prior to > the introduction of the Enum class in python 3.4. This can now be safely > removed as a dependency in requirements.txt as CQLSH supports Python 3.6+. > No code changes are needed. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17325) Remove obsolete enum34 package from requirements
[ https://issues.apache.org/jira/browse/CASSANDRA-17325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17325: - Status: Needs Committer (was: Patch Available) > Remove obsolete enum34 package from requirements > > > Key: CASSANDRA-17325 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17325 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > The enum34 package was used for backwards compatibility with python prior to > the introduction of the Enum class in python 3.4. This can now be safely > removed as a dependency in requirements.txt as CQLSH supports Python 3.6+. > No code changes are needed. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17364) dependency on commons-io is to 2.6 which has a CVE
[ https://issues.apache.org/jira/browse/CASSANDRA-17364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489561#comment-17489561 ] Brandon Williams commented on CASSANDRA-17364: -- Can you provide more details? This doesn't show in an OWASP report. > dependency on commons-io is to 2.6 which has a CVE > -- > > Key: CASSANDRA-17364 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17364 > Project: Cassandra > Issue Type: Improvement >Reporter: PJ Fanning >Priority: Normal > > Can this be upgraded, ideally to v2.11.0? > [https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1] > [https://github.com/apache/cassandra/blob/trunk/build.xml#L510] > > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17368) Investigate OWASP failure report
[ https://issues.apache.org/jira/browse/CASSANDRA-17368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489559#comment-17489559 ] Brandon Williams commented on CASSANDRA-17368: -- CVE-2021-43797 is netty http stuff we don't use yet again. CVE-2021-37136 is malicious input can DOS bzip2 decompression, which does not apply. CVE-2021-37137 is roughly the same but for Snappy, which can't be exploited without having already lost the game to network or local machine access. > Investigate OWASP failure report > > > Key: CASSANDRA-17368 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17368 > Project: Cassandra > Issue Type: Bug > Components: Build >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > > 4.0: netty-all-4.1.58.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 > 3.11: netty-all-4.0.44.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 > 3.0: netty-all-4.0.44.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17326) Security Bug
[
https://issues.apache.org/jira/browse/CASSANDRA-17326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489557#comment-17489557
]
Brandon Williams commented on CASSANDRA-17326:
--
Thanks for pointing these out! We'll handle these in CASSANDRA-17368.
> Security Bug
>
>
> Key: CASSANDRA-17326
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17326
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Ori Prog
>Priority: Normal
>
> The Cassandra 3.11.11 uses _netty-all-4.0.44.Final.jar_
> This library has the following CVEs. {*}Part of these CVEs are critical{*}!
> Please upgrade to 4.1.71.Final
> CVE-2019-20445
> CVE-2019-20444
> CVE-2019-16869
> CVE-2020-7238
> CVE-2021-37136
> CVE-2021-37137
> CVE-2021-21409
> CVE-2021-43797
> CVE-2021-21295
> CVE-2021-21290
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17368) Investigate OWASP failure report
[ https://issues.apache.org/jira/browse/CASSANDRA-17368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17368: - Bug Category: Parent values: Security(12985) Complexity: Normal Component/s: Build Discovered By: User Report Severity: Normal Status: Open (was: Triage Needed) > Investigate OWASP failure report > > > Key: CASSANDRA-17368 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17368 > Project: Cassandra > Issue Type: Bug > Components: Build >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > > 4.0: netty-all-4.1.58.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 > 3.11: netty-all-4.0.44.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 > 3.0: netty-all-4.0.44.Final.jar: CVE-2021-43797, CVE-2021-37136, > CVE-2021-37137 -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17368) Investigate OWASP failure report
Brandon Williams created CASSANDRA-17368: Summary: Investigate OWASP failure report Key: CASSANDRA-17368 URL: https://issues.apache.org/jira/browse/CASSANDRA-17368 Project: Cassandra Issue Type: Bug Reporter: Brandon Williams Assignee: Brandon Williams 4.0: netty-all-4.1.58.Final.jar: CVE-2021-43797, CVE-2021-37136, CVE-2021-37137 3.11: netty-all-4.0.44.Final.jar: CVE-2021-43797, CVE-2021-37136, CVE-2021-37137 3.0: netty-all-4.0.44.Final.jar: CVE-2021-43797, CVE-2021-37136, CVE-2021-37137 -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17326) Security Bug
[
https://issues.apache.org/jira/browse/CASSANDRA-17326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489536#comment-17489536
]
Michael F commented on CASSANDRA-17326:
---
[~brandon.williams] ,
What about these CVEs:
CVE-2020-7238
CVE-2021-37136
CVE-2021-37137
CVE-2021-43797
Will you suppress them also?
> Security Bug
>
>
> Key: CASSANDRA-17326
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17326
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Ori Prog
>Priority: Normal
>
> The Cassandra 3.11.11 uses _netty-all-4.0.44.Final.jar_
> This library has the following CVEs. {*}Part of these CVEs are critical{*}!
> Please upgrade to 4.1.71.Final
> CVE-2019-20445
> CVE-2019-20444
> CVE-2019-16869
> CVE-2020-7238
> CVE-2021-37136
> CVE-2021-37137
> CVE-2021-21409
> CVE-2021-43797
> CVE-2021-21295
> CVE-2021-21290
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17344) Documentation update of virtual table system_views.clients
[ https://issues.apache.org/jira/browse/CASSANDRA-17344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-17344: --- Test and Documentation Plan: This is a documentation change. Status: Patch Available (was: Open) > Documentation update of virtual table system_views.clients > -- > > Key: CASSANDRA-17344 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17344 > Project: Cassandra > Issue Type: Improvement > Components: Documentation >Reporter: Tibor Repasi >Assignee: Tibor Repasi >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > With CASSANDRA-16378 there are changes introduced to virtual table > system_views.clients. This is updating the documentation page. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17344) Documentation update of virtual table system_views.clients
[ https://issues.apache.org/jira/browse/CASSANDRA-17344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-17344: --- Change Category: Operability Complexity: Normal Status: Open (was: Triage Needed) > Documentation update of virtual table system_views.clients > -- > > Key: CASSANDRA-17344 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17344 > Project: Cassandra > Issue Type: Improvement > Components: Documentation >Reporter: Tibor Repasi >Assignee: Tibor Repasi >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > With CASSANDRA-16378 there are changes introduced to virtual table > system_views.clients. This is updating the documentation page. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17367) sstableloader ignores streaming encryption settings
[
https://issues.apache.org/jira/browse/CASSANDRA-17367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17367:
-
Reviewers: Brandon Williams
> sstableloader ignores streaming encryption settings
> ---
>
> Key: CASSANDRA-17367
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17367
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Dmitry Potepalov
>Assignee: Dmitry Potepalov
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
> Attachments: 17367-4.0.txt, 17367-trunk.txt
>
>
> Reproducible in Cassandra 4.x. If one configures encryption for streaming in
> config yaml fed to sstableloader like this
> {{server_encryption_options:}}
> {{ internode_encryption: all}}
> {{ keystore: sstableloader.keystore.p12}}
> {{ keystore_password: changeit}}
> {{ truststore: sstableloader.truststore.jks}}
> {{ truststore_password: changeit}}
> then sstableloader should perform an SSL handshake on the streaming
> connections and encrypt the payload. But this does not happen. Judging by the
> TCPdump of the outgoing traffic on the internode port, sstableloader sends
> plaintext traffic. This is the TCP payload of the first packet that
> sstableloader sends after establishing TCP connection:
> {{ca 55 2d fa 0c 0c 0c 08 06 0a f0 01 f9 1b 58 a8 32 f2 d0}}
> The first 4 bytes look like Cassandra protocol magic, not like a client hello.
> I've discovered the issue while trying to migrate some data to a Cassandra 4
> listening on the legacy ssl storage port (therefore, accepting only encrypted
> connections on that port). Streaming phase of the migration failed with a
> "connection closed" error, which hints that the connection was closed
> server-side.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17367) sstableloader ignores streaming encryption settings
[
https://issues.apache.org/jira/browse/CASSANDRA-17367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17367:
-
Test and Documentation Plan: run CI
Status: Patch Available (was: Open)
> sstableloader ignores streaming encryption settings
> ---
>
> Key: CASSANDRA-17367
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17367
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Dmitry Potepalov
>Assignee: Dmitry Potepalov
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
> Attachments: 17367-4.0.txt, 17367-trunk.txt
>
>
> Reproducible in Cassandra 4.x. If one configures encryption for streaming in
> config yaml fed to sstableloader like this
> {{server_encryption_options:}}
> {{ internode_encryption: all}}
> {{ keystore: sstableloader.keystore.p12}}
> {{ keystore_password: changeit}}
> {{ truststore: sstableloader.truststore.jks}}
> {{ truststore_password: changeit}}
> then sstableloader should perform an SSL handshake on the streaming
> connections and encrypt the payload. But this does not happen. Judging by the
> TCPdump of the outgoing traffic on the internode port, sstableloader sends
> plaintext traffic. This is the TCP payload of the first packet that
> sstableloader sends after establishing TCP connection:
> {{ca 55 2d fa 0c 0c 0c 08 06 0a f0 01 f9 1b 58 a8 32 f2 d0}}
> The first 4 bytes look like Cassandra protocol magic, not like a client hello.
> I've discovered the issue while trying to migrate some data to a Cassandra 4
> listening on the legacy ssl storage port (therefore, accepting only encrypted
> connections on that port). Streaming phase of the migration failed with a
> "connection closed" error, which hints that the connection was closed
> server-side.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17367) sstableloader ignores streaming encryption settings
[
https://issues.apache.org/jira/browse/CASSANDRA-17367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams reassigned CASSANDRA-17367:
Assignee: Brandon Williams
> sstableloader ignores streaming encryption settings
> ---
>
> Key: CASSANDRA-17367
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17367
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Dmitry Potepalov
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
> Attachments: 17367-4.0.txt, 17367-trunk.txt
>
>
> Reproducible in Cassandra 4.x. If one configures encryption for streaming in
> config yaml fed to sstableloader like this
> {{server_encryption_options:}}
> {{ internode_encryption: all}}
> {{ keystore: sstableloader.keystore.p12}}
> {{ keystore_password: changeit}}
> {{ truststore: sstableloader.truststore.jks}}
> {{ truststore_password: changeit}}
> then sstableloader should perform an SSL handshake on the streaming
> connections and encrypt the payload. But this does not happen. Judging by the
> TCPdump of the outgoing traffic on the internode port, sstableloader sends
> plaintext traffic. This is the TCP payload of the first packet that
> sstableloader sends after establishing TCP connection:
> {{ca 55 2d fa 0c 0c 0c 08 06 0a f0 01 f9 1b 58 a8 32 f2 d0}}
> The first 4 bytes look like Cassandra protocol magic, not like a client hello.
> I've discovered the issue while trying to migrate some data to a Cassandra 4
> listening on the legacy ssl storage port (therefore, accepting only encrypted
> connections on that port). Streaming phase of the migration failed with a
> "connection closed" error, which hints that the connection was closed
> server-side.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17367) sstableloader ignores streaming encryption settings
[
https://issues.apache.org/jira/browse/CASSANDRA-17367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams reassigned CASSANDRA-17367:
Assignee: Dmitry Potepalov (was: Brandon Williams)
> sstableloader ignores streaming encryption settings
> ---
>
> Key: CASSANDRA-17367
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17367
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Dmitry Potepalov
>Assignee: Dmitry Potepalov
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
> Attachments: 17367-4.0.txt, 17367-trunk.txt
>
>
> Reproducible in Cassandra 4.x. If one configures encryption for streaming in
> config yaml fed to sstableloader like this
> {{server_encryption_options:}}
> {{ internode_encryption: all}}
> {{ keystore: sstableloader.keystore.p12}}
> {{ keystore_password: changeit}}
> {{ truststore: sstableloader.truststore.jks}}
> {{ truststore_password: changeit}}
> then sstableloader should perform an SSL handshake on the streaming
> connections and encrypt the payload. But this does not happen. Judging by the
> TCPdump of the outgoing traffic on the internode port, sstableloader sends
> plaintext traffic. This is the TCP payload of the first packet that
> sstableloader sends after establishing TCP connection:
> {{ca 55 2d fa 0c 0c 0c 08 06 0a f0 01 f9 1b 58 a8 32 f2 d0}}
> The first 4 bytes look like Cassandra protocol magic, not like a client hello.
> I've discovered the issue while trying to migrate some data to a Cassandra 4
> listening on the legacy ssl storage port (therefore, accepting only encrypted
> connections on that port). Streaming phase of the migration failed with a
> "connection closed" error, which hints that the connection was closed
> server-side.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17361) STCS documentation on website mentions LCS in title
[ https://issues.apache.org/jira/browse/CASSANDRA-17361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez reassigned CASSANDRA-17361: - Assignee: Erick Ramirez > STCS documentation on website mentions LCS in title > --- > > Key: CASSANDRA-17361 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17361 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Matt Fleming >Assignee: Erick Ramirez >Priority: Normal > > The STCS page here, > [https://cassandra.apache.org/doc/latest/cassandra/operating/compaction/stcs.html,] > says "Leveled Compaction Strategy" in the title where it should say > "Size-tiered Compaction Strategy. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17367) sstableloader ignores streaming encryption settings
[
https://issues.apache.org/jira/browse/CASSANDRA-17367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17367:
-
Fix Version/s: 4.0.x
> sstableloader ignores streaming encryption settings
> ---
>
> Key: CASSANDRA-17367
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17367
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Dmitry Potepalov
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
> Attachments: 17367-4.0.txt, 17367-trunk.txt
>
>
> Reproducible in Cassandra 4.x. If one configures encryption for streaming in
> config yaml fed to sstableloader like this
> {{server_encryption_options:}}
> {{ internode_encryption: all}}
> {{ keystore: sstableloader.keystore.p12}}
> {{ keystore_password: changeit}}
> {{ truststore: sstableloader.truststore.jks}}
> {{ truststore_password: changeit}}
> then sstableloader should perform an SSL handshake on the streaming
> connections and encrypt the payload. But this does not happen. Judging by the
> TCPdump of the outgoing traffic on the internode port, sstableloader sends
> plaintext traffic. This is the TCP payload of the first packet that
> sstableloader sends after establishing TCP connection:
> {{ca 55 2d fa 0c 0c 0c 08 06 0a f0 01 f9 1b 58 a8 32 f2 d0}}
> The first 4 bytes look like Cassandra protocol magic, not like a client hello.
> I've discovered the issue while trying to migrate some data to a Cassandra 4
> listening on the legacy ssl storage port (therefore, accepting only encrypted
> connections on that port). Streaming phase of the migration failed with a
> "connection closed" error, which hints that the connection was closed
> server-side.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17367) sstableloader ignores streaming encryption settings
[
https://issues.apache.org/jira/browse/CASSANDRA-17367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17367:
-
Bug Category: Parent values: Correctness(12982)Level 1 values: Recoverable
Corruption / Loss(12986)
Complexity: Normal
Component/s: Tool/bulk load
Discovered By: User Report
Fix Version/s: 4.x
Severity: Normal
Status: Open (was: Triage Needed)
> sstableloader ignores streaming encryption settings
> ---
>
> Key: CASSANDRA-17367
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17367
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Dmitry Potepalov
>Priority: Normal
> Fix For: 4.x
>
> Attachments: 17367-4.0.txt, 17367-trunk.txt
>
>
> Reproducible in Cassandra 4.x. If one configures encryption for streaming in
> config yaml fed to sstableloader like this
> {{server_encryption_options:}}
> {{ internode_encryption: all}}
> {{ keystore: sstableloader.keystore.p12}}
> {{ keystore_password: changeit}}
> {{ truststore: sstableloader.truststore.jks}}
> {{ truststore_password: changeit}}
> then sstableloader should perform an SSL handshake on the streaming
> connections and encrypt the payload. But this does not happen. Judging by the
> TCPdump of the outgoing traffic on the internode port, sstableloader sends
> plaintext traffic. This is the TCP payload of the first packet that
> sstableloader sends after establishing TCP connection:
> {{ca 55 2d fa 0c 0c 0c 08 06 0a f0 01 f9 1b 58 a8 32 f2 d0}}
> The first 4 bytes look like Cassandra protocol magic, not like a client hello.
> I've discovered the issue while trying to migrate some data to a Cassandra 4
> listening on the legacy ssl storage port (therefore, accepting only encrypted
> connections on that port). Streaming phase of the migration failed with a
> "connection closed" error, which hints that the connection was closed
> server-side.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17236) Add support for short form of version to CQLSH
[
https://issues.apache.org/jira/browse/CASSANDRA-17236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489503#comment-17489503
]
Brandon Williams edited comment on CASSANDRA-17236 at 2/9/22, 12:16 PM:
Indeed, the only failure is known (CASSANDRA-17144) so +1 from me.
was (Author: brandon.williams):
Indeed, the only failure is known (CASSANDRA-1744) so +1 from me.
> Add support for short form of version to CQLSH
> --
>
> Key: CASSANDRA-17236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17236
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Semantics
>Reporter: Madhavan
>Assignee: Yash Ladha
>Priority: Low
> Labels: lhf
> Fix For: 4.x
>
>
> Today we do only support the `–version` long option/form for cqlsh and this
> enhancement Jira is to request that we also offer a shorter version `-v` to
> cqlsh. This will have consistency benefits with other tools and even match
> with what we have at `bin/cassandra -v` option for instance.
> Today, `cqlsh` does support `--v` to get the version which is different than
> the single dashed short form that is available at many other tools. Thanks to
> Ekaterina for finding this. It looks like this is stemming from Python's
> parse mechanism which is detailed here,
> [https://docs.python.org/2.7/library/optparse.html#printing-a-version-string].
>
> [https://github.com/apache/cassandra/blob/trunk/bin/cqlsh.py#L194-L196]
> {quote}parser = optparse.OptionParser(description=description, epilog=epilog,
> usage="Usage: %prog [options] [host [port]]",
> version='cqlsh ' + version)
> {quote}
>
> {{$ bin/cqlsh --v}}
> {{cqlsh 6.0.0}}
> This looks like a weird implementation at Python. Both (\-\-help) and
> (\-\-version) options are stemming from here,
> [https://github.com/python/cpython/blob/2.7/Lib/optparse.py#L1248-L1256] and
> they did decide to ignore the short form option for version and it somehow
> automatically takes the (--v) option to spit the version info.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17236) Add support for short form of version to CQLSH
[
https://issues.apache.org/jira/browse/CASSANDRA-17236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489503#comment-17489503
]
Brandon Williams commented on CASSANDRA-17236:
--
Indeed, the only failure is known (CASSANDRA-1744) so +1 from me.
> Add support for short form of version to CQLSH
> --
>
> Key: CASSANDRA-17236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17236
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Semantics
>Reporter: Madhavan
>Assignee: Yash Ladha
>Priority: Low
> Labels: lhf
> Fix For: 4.x
>
>
> Today we do only support the `–version` long option/form for cqlsh and this
> enhancement Jira is to request that we also offer a shorter version `-v` to
> cqlsh. This will have consistency benefits with other tools and even match
> with what we have at `bin/cassandra -v` option for instance.
> Today, `cqlsh` does support `--v` to get the version which is different than
> the single dashed short form that is available at many other tools. Thanks to
> Ekaterina for finding this. It looks like this is stemming from Python's
> parse mechanism which is detailed here,
> [https://docs.python.org/2.7/library/optparse.html#printing-a-version-string].
>
> [https://github.com/apache/cassandra/blob/trunk/bin/cqlsh.py#L194-L196]
> {quote}parser = optparse.OptionParser(description=description, epilog=epilog,
> usage="Usage: %prog [options] [host [port]]",
> version='cqlsh ' + version)
> {quote}
>
> {{$ bin/cqlsh --v}}
> {{cqlsh 6.0.0}}
> This looks like a weird implementation at Python. Both (\-\-help) and
> (\-\-version) options are stemming from here,
> [https://github.com/python/cpython/blob/2.7/Lib/optparse.py#L1248-L1256] and
> they did decide to ignore the short form option for version and it somehow
> automatically takes the (--v) option to spit the version info.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17353) Flatten guardrails configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489489#comment-17489489
]
Andres de la Peña commented on CASSANDRA-17353:
---
The recent changes in trunk make it difficult to get a clean CI run, since
Circle has problems due to CCM retagging. These runs alternatively hit those
issues in j8 or j11:
||CI||
|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1287/workflows/61ef391d-431c-4a3d-901e-780be96ab204]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1287/workflows/ed5f725d-5988-4ff9-89c3-ac9b45ee1d98]|
|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1288/workflows/b373737c-529e-4a88-891f-36cf565ccb31]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1288/workflows/0ae4e55a-1b4e-4483-9918-d7ee49ee9d99]|
|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1289/workflows/a4298bbf-c43e-459a-953f-96515a2a0a11]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1289/workflows/90a7c3b4-5de5-4edf-895c-5425a40326e3]|
We also have [this
run|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1360/workflows/016168ce-cba1-47b2-986a-cb188959dd51]
kindly started by [~e.dimitrova], with [an additional
run|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1365/workflows/8e8e9477-ad80-4171-81c3-58a4d1b7775d/jobs/8785/parallel-runs/56?filterBy=ALL]
for upgrade tests.
I'd say that none of the failures are caused by the proposed changes, and we
are ready to commit.
> Flatten guardrails configuration
>
>
> Key: CASSANDRA-17353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
> instead of the current nested format. This ticket comes from the discussion
> around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
> CASSANDRA-17212, and doesn't include any of the other nested properties on
> {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17236) Add support for short form of version to CQLSH
[
https://issues.apache.org/jira/browse/CASSANDRA-17236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489468#comment-17489468
]
Stefan Miklosovic commented on CASSANDRA-17236:
---
[~brandon.williams] this one is way better
https://app.circleci.com/pipelines/github/instaclustr/cassandra/712/workflows/b83dde79-3399-4ff8-963c-e162b2ad28de
> Add support for short form of version to CQLSH
> --
>
> Key: CASSANDRA-17236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17236
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Semantics
>Reporter: Madhavan
>Assignee: Yash Ladha
>Priority: Low
> Labels: lhf
> Fix For: 4.x
>
>
> Today we do only support the `–version` long option/form for cqlsh and this
> enhancement Jira is to request that we also offer a shorter version `-v` to
> cqlsh. This will have consistency benefits with other tools and even match
> with what we have at `bin/cassandra -v` option for instance.
> Today, `cqlsh` does support `--v` to get the version which is different than
> the single dashed short form that is available at many other tools. Thanks to
> Ekaterina for finding this. It looks like this is stemming from Python's
> parse mechanism which is detailed here,
> [https://docs.python.org/2.7/library/optparse.html#printing-a-version-string].
>
> [https://github.com/apache/cassandra/blob/trunk/bin/cqlsh.py#L194-L196]
> {quote}parser = optparse.OptionParser(description=description, epilog=epilog,
> usage="Usage: %prog [options] [host [port]]",
> version='cqlsh ' + version)
> {quote}
>
> {{$ bin/cqlsh --v}}
> {{cqlsh 6.0.0}}
> This looks like a weird implementation at Python. Both (\-\-help) and
> (\-\-version) options are stemming from here,
> [https://github.com/python/cpython/blob/2.7/Lib/optparse.py#L1248-L1256] and
> they did decide to ignore the short form option for version and it somehow
> automatically takes the (--v) option to spit the version info.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17367) sstableloader ignores streaming encryption settings
[
https://issues.apache.org/jira/browse/CASSANDRA-17367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489462#comment-17489462
]
Dmitry Potepalov edited comment on CASSANDRA-17367 at 2/9/22, 10:59 AM:
Patches attached to the ticket. With this change, sstableloader performs the
handshake and my migration succeeded.
Just in case - sstableloader command I used to reproduce the issue on 4.0.0:
{{sstableloader -f cassandra.yaml -d : -ssp -u user -pw password }}
and the exception in sstableloader output:
{noformat}
15:38:00.725 [main] DEBUG
org.apache.cassandra.streaming.async.NettyStreamingMessageSender - [Stream
#16fda750-88f5-11ec-b4ef-0bc683c3f5ea] Closing stream connection channels on
/35.205.83.18:7000
15:38:00.728 [main] ERROR org.apache.cassandra.streaming.StreamSession -
[Stream #16fda750-88f5-11ec-b4ef-0bc683c3f5ea] Streaming error occurred on
session with peer 35.205.83.18:7000
java.io.IOException: failed to connect to /35.205.83.18:7000 for streaming data
at
org.apache.cassandra.streaming.DefaultConnectionFactory.createConnection(DefaultConnectionFactory.java:55)
at
org.apache.cassandra.tools.BulkLoadConnectionFactory.createConnection(BulkLoadConnectionFactory.java:52)
at
org.apache.cassandra.streaming.async.NettyStreamingMessageSender.createChannel(NettyStreamingMessageSender.java:199)
at
org.apache.cassandra.streaming.async.NettyStreamingMessageSender.setupControlMessageChannel(NettyStreamingMessageSender.java:180)
at
org.apache.cassandra.streaming.async.NettyStreamingMessageSender.sendMessage(NettyStreamingMessageSender.java:245)
at
org.apache.cassandra.streaming.async.NettyStreamingMessageSender.initialize(NettyStreamingMessageSender.java:149)
at
org.apache.cassandra.streaming.StreamSession.start(StreamSession.java:362)
at
org.apache.cassandra.streaming.StreamCoordinator.startSession(StreamCoordinator.java:262)
at
org.apache.cassandra.streaming.StreamCoordinator.access$700(StreamCoordinator.java:36)
at
org.apache.cassandra.streaming.StreamCoordinator$HostStreamingData.connectAllStreamSessions(StreamCoordinator.java:308)
at
org.apache.cassandra.streaming.StreamCoordinator.connectAllStreamSessions(StreamCoordinator.java:107)
at
org.apache.cassandra.streaming.StreamCoordinator.connect(StreamCoordinator.java:101)
at
org.apache.cassandra.streaming.StreamResultFuture.createInitiator(StreamResultFuture.java:98)
at
org.apache.cassandra.streaming.StreamPlan.execute(StreamPlan.java:179)
at
org.apache.cassandra.io.sstable.SSTableLoader.stream(SSTableLoader.java:215)
at org.apache.cassandra.tools.BulkLoader.load(BulkLoader.java:83)
at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:51)
Caused by: java.nio.channels.ClosedChannelException: null
at
org.apache.cassandra.net.OutboundConnectionInitiator$Handler.channelInactive(OutboundConnectionInitiator.java:248)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:241)
at
io.netty.channel.DefaultChannelPipeline$HeadContext.channelInactive(DefaultChannelPipeline.java:1405)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)
at
io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:901)
at
io.netty.channel.AbstractChannel$AbstractUnsafe$8.run(AbstractChannel.java:819)
at
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:829)
{noformat}
was (Author: JIRAUSER284878):
Patches attached to the ticket. With this change, sstableloader performs the
handshake and my migration succeeded.
Just in case - sstableloader command I used to reproduce the issue on 4.0.0:
{{sstableloader -f cassandra.yaml -d : -ssp -u user -pw password }}
and the exception in ss
[jira] [Commented] (CASSANDRA-17367) sstableloader ignores streaming encryption settings
[
https://issues.apache.org/jira/browse/CASSANDRA-17367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489462#comment-17489462
]
Dmitry Potepalov commented on CASSANDRA-17367:
--
Patches attached to the ticket. With this change, sstableloader performs the
handshake and my migration succeeded.
Just in case - sstableloader command I used to reproduce the issue on 4.0.0:
{{sstableloader -f cassandra.yaml -d : -ssp -u user -pw password }}
and the exception in sstableloader output:
{noformat}
15:38:00.725 [main] DEBUG
org.apache.cassandra.streaming.async.NettyStreamingMessageSender - [Stream
#16fda750-88f5-11ec-b4ef-0bc683c3f5ea] Closing stream connection channels on
/35.205.83.18:7000 15:38:00.728 [main] ERROR
org.apache.cassandra.streaming.StreamSession - [Stream
#16fda750-88f5-11ec-b4ef-0bc683c3f5ea] Streaming error occurred on session with
peer 35.205.83.18:7000 java.io.IOException: failed to connect to
/35.205.83.18:7000 for streaming data at
org.apache.cassandra.streaming.DefaultConnectionFactory.createConnection(DefaultConnectionFactory.java:55)
at
org.apache.cassandra.tools.BulkLoadConnectionFactory.createConnection(BulkLoadConnectionFactory.java:52)
at
org.apache.cassandra.streaming.async.NettyStreamingMessageSender.createChannel(NettyStreamingMessageSender.java:199)
at
org.apache.cassandra.streaming.async.NettyStreamingMessageSender.setupControlMessageChannel(NettyStreamingMessageSender.java:180)
at
org.apache.cassandra.streaming.async.NettyStreamingMessageSender.sendMessage(NettyStreamingMessageSender.java:245)
at
org.apache.cassandra.streaming.async.NettyStreamingMessageSender.initialize(NettyStreamingMessageSender.java:149)
at org.apache.cassandra.streaming.StreamSession.start(StreamSession.java:362)
at
org.apache.cassandra.streaming.StreamCoordinator.startSession(StreamCoordinator.java:262)
at
org.apache.cassandra.streaming.StreamCoordinator.access$700(StreamCoordinator.java:36)
at
org.apache.cassandra.streaming.StreamCoordinator$HostStreamingData.connectAllStreamSessions(StreamCoordinator.java:308)
at
org.apache.cassandra.streaming.StreamCoordinator.connectAllStreamSessions(StreamCoordinator.java:107)
at
org.apache.cassandra.streaming.StreamCoordinator.connect(StreamCoordinator.java:101)
at
org.apache.cassandra.streaming.StreamResultFuture.createInitiator(StreamResultFuture.java:98)
at org.apache.cassandra.streaming.StreamPlan.execute(StreamPlan.java:179) at
org.apache.cassandra.io.sstable.SSTableLoader.stream(SSTableLoader.java:215) at
org.apache.cassandra.tools.BulkLoader.load(BulkLoader.java:83) at
org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:51) Caused by:
java.nio.channels.ClosedChannelException: null at
org.apache.cassandra.net.OutboundConnectionInitiator$Handler.channelInactive(OutboundConnectionInitiator.java:248)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:241)
at
io.netty.channel.DefaultChannelPipeline$HeadContext.channelInactive(DefaultChannelPipeline.java:1405)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)
at
io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:901)
at
io.netty.channel.AbstractChannel$AbstractUnsafe$8.run(AbstractChannel.java:819)
at
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384) at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:829) {noformat}
> sstableloader ignores streaming encryption settings
> ---
>
> Key: CASSANDRA-17367
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17367
> Project: Cassandra
> Issue Type: Bug
>Reporter: Dmitry Potepalov
>Priority: Normal
> Attachments: 17367-4.0.txt, 17367-trunk.txt
>
>
> Reproducible in Cassandra 4.x. If one configures encryption for streaming in
> config yaml fed to sstableloader like this
> {{server_encryption_options:}}
> {{ internode_encryption: all
[jira] [Updated] (CASSANDRA-17367) sstableloader ignores streaming encryption settings
[
https://issues.apache.org/jira/browse/CASSANDRA-17367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Potepalov updated CASSANDRA-17367:
-
Attachment: 17367-4.0.txt
17367-trunk.txt
> sstableloader ignores streaming encryption settings
> ---
>
> Key: CASSANDRA-17367
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17367
> Project: Cassandra
> Issue Type: Bug
>Reporter: Dmitry Potepalov
>Priority: Normal
> Attachments: 17367-4.0.txt, 17367-trunk.txt
>
>
> Reproducible in Cassandra 4.x. If one configures encryption for streaming in
> config yaml fed to sstableloader like this
> {{server_encryption_options:}}
> {{ internode_encryption: all}}
> {{ keystore: sstableloader.keystore.p12}}
> {{ keystore_password: changeit}}
> {{ truststore: sstableloader.truststore.jks}}
> {{ truststore_password: changeit}}
> then sstableloader should perform an SSL handshake on the streaming
> connections and encrypt the payload. But this does not happen. Judging by the
> TCPdump of the outgoing traffic on the internode port, sstableloader sends
> plaintext traffic. This is the TCP payload of the first packet that
> sstableloader sends after establishing TCP connection:
> {{ca 55 2d fa 0c 0c 0c 08 06 0a f0 01 f9 1b 58 a8 32 f2 d0}}
> The first 4 bytes look like Cassandra protocol magic, not like a client hello.
> I've discovered the issue while trying to migrate some data to a Cassandra 4
> listening on the legacy ssl storage port (therefore, accepting only encrypted
> connections on that port). Streaming phase of the migration failed with a
> "connection closed" error, which hints that the connection was closed
> server-side.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17367) sstableloader ignores streaming encryption settings
[
https://issues.apache.org/jira/browse/CASSANDRA-17367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489438#comment-17489438
]
Dmitry Potepalov commented on CASSANDRA-17367:
--
I've fixed it in a local fork, preparing patches for upload, seems some
parameters got lost in BulkLoadConnectionFactory.
> sstableloader ignores streaming encryption settings
> ---
>
> Key: CASSANDRA-17367
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17367
> Project: Cassandra
> Issue Type: Bug
>Reporter: Dmitry Potepalov
>Priority: Normal
>
> Reproducible in Cassandra 4.x. If one configures encryption for streaming in
> config yaml fed to sstableloader like this
> {{server_encryption_options:}}
> {{ internode_encryption: all}}
> {{ keystore: sstableloader.keystore.p12}}
> {{ keystore_password: changeit}}
> {{ truststore: sstableloader.truststore.jks}}
> {{ truststore_password: changeit}}
> then sstableloader should perform an SSL handshake on the streaming
> connections and encrypt the payload. But this does not happen. Judging by the
> TCPdump of the outgoing traffic on the internode port, sstableloader sends
> plaintext traffic. This is the TCP payload of the first packet that
> sstableloader sends after establishing TCP connection:
> {{ca 55 2d fa 0c 0c 0c 08 06 0a f0 01 f9 1b 58 a8 32 f2 d0}}
> The first 4 bytes look like Cassandra protocol magic, not like a client hello.
> I've discovered the issue while trying to migrate some data to a Cassandra 4
> listening on the legacy ssl storage port (therefore, accepting only encrypted
> connections on that port). Streaming phase of the migration failed with a
> "connection closed" error, which hints that the connection was closed
> server-side.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17367) sstableloader ignores streaming encryption settings
Dmitry Potepalov created CASSANDRA-17367:
Summary: sstableloader ignores streaming encryption settings
Key: CASSANDRA-17367
URL: https://issues.apache.org/jira/browse/CASSANDRA-17367
Project: Cassandra
Issue Type: Bug
Reporter: Dmitry Potepalov
Reproducible in Cassandra 4.x. If one configures encryption for streaming in
config yaml fed to sstableloader like this
{{server_encryption_options:}}
{{ internode_encryption: all}}
{{ keystore: sstableloader.keystore.p12}}
{{ keystore_password: changeit}}
{{ truststore: sstableloader.truststore.jks}}
{{ truststore_password: changeit}}
then sstableloader should perform an SSL handshake on the streaming connections
and encrypt the payload. But this does not happen. Judging by the TCPdump of
the outgoing traffic on the internode port, sstableloader sends plaintext
traffic. This is the TCP payload of the first packet that sstableloader sends
after establishing TCP connection:
{{ca 55 2d fa 0c 0c 0c 08 06 0a f0 01 f9 1b 58 a8 32 f2 d0}}
The first 4 bytes look like Cassandra protocol magic, not like a client hello.
I've discovered the issue while trying to migrate some data to a Cassandra 4
listening on the legacy ssl storage port (therefore, accepting only encrypted
connections on that port). Streaming phase of the migration failed with a
"connection closed" error, which hints that the connection was closed
server-side.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17366) Fix flaky test - upgrade_tests.gossip_test.TestGossip
[
https://issues.apache.org/jira/browse/CASSANDRA-17366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksei Zotov updated CASSANDRA-17366:
--
Workflow: Copy of Cassandra Bug Workflow (was: Copy of Cassandra Default
Workflow)
Issue Type: Bug (was: Task)
> Fix flaky test - upgrade_tests.gossip_test.TestGossip
> -
>
> Key: CASSANDRA-17366
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17366
> Project: Cassandra
> Issue Type: Bug
>Reporter: Aleksei Zotov
>Priority: Normal
>
> We can see many failures for 4.x branch:
> test_2dc_parallel_startup_one_seed
> ([916|https://ci-cassandra.apache.org/job/Cassandra-trunk/916/testReport/dtest-offheap.gossip_test/TestGossip],
>
> [920|https://ci-cassandra.apache.org/job/Cassandra-trunk/920/testReport/dtest.gossip_test/TestGossip,])
> test_2dc_parallel_startup
> ([929|https://ci-cassandra.apache.org/job/Cassandra-trunk/929/testReport/dtest-novnode.gossip_test/TestGossip],
>
> [931|https://ci-cassandra.apache.org/job/Cassandra-trunk/931/testReport/dtest.gossip_test/TestGossip],
>
> [936|https://ci-cassandra.apache.org/job/Cassandra-trunk/936/testReport/dtest-novnode.gossip_test/TestGossip])
> test_2dc_parallel_startup_one_seed
> ([916|https://ci-cassandra.apache.org/job/Cassandra-trunk/916/testReport/dtest-offheap.gossip_test/TestGossip],
>
> [920|https://ci-cassandra.apache.org/job/Cassandra-trunk/920/testReport/dtest.gossip_test/TestGossip/])
> The error is always the same:
> {code:java}
> Unexpected error found in node logs (see stdout for full details). Errors:
> [ERROR [main] 2022-01-26 10:53:12,866 CassandraDaemon.java:900 - Exception
> encountered during startup
> java.lang.RuntimeException: Didn't receive schemas for all known versions
> within the timeout. Use -Dcassandra.skip_schema_check=true to skip this check.
> at
> org.apache.cassandra.service.StorageService.waitForSchema(StorageService.java:1037)
> at
> org.apache.cassandra.dht.BootStrapper.allocateTokens(BootStrapper.java:232)
> at
> org.apache.cassandra.dht.BootStrapper.getBootstrapTokens(BootStrapper.java:180)
> at
> org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1089)
> at
> org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1043)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:821)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:751)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:417)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:754)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:878),
> ERROR [main] 2022-01-26 10:53:12,866 CassandraDaemon.java:900 - Exception
> encountered during startup
> java.lang.RuntimeException: Didn't receive schemas for all known versions
> within the timeout. Use -Dcassandra.skip_schema_check=true to skip this check.
> at
> org.apache.cassandra.service.StorageService.waitForSchema(StorageService.java:1037)
> at
> org.apache.cassandra.dht.BootStrapper.allocateTokens(BootStrapper.java:232)
> at
> org.apache.cassandra.dht.BootStrapper.getBootstrapTokens(BootStrapper.java:180)
> at
> org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1089)
> at
> org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1043)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:821)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:751)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:417)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:754)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:878)]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17366) Fix flaky test - upgrade_tests.gossip_test.TestGossip
Aleksei Zotov created CASSANDRA-17366:
-
Summary: Fix flaky test - upgrade_tests.gossip_test.TestGossip
Key: CASSANDRA-17366
URL: https://issues.apache.org/jira/browse/CASSANDRA-17366
Project: Cassandra
Issue Type: Task
Reporter: Aleksei Zotov
We can see many failures for 4.x branch:
test_2dc_parallel_startup_one_seed
([916|https://ci-cassandra.apache.org/job/Cassandra-trunk/916/testReport/dtest-offheap.gossip_test/TestGossip],
[920|https://ci-cassandra.apache.org/job/Cassandra-trunk/920/testReport/dtest.gossip_test/TestGossip,])
test_2dc_parallel_startup
([929|https://ci-cassandra.apache.org/job/Cassandra-trunk/929/testReport/dtest-novnode.gossip_test/TestGossip],
[931|https://ci-cassandra.apache.org/job/Cassandra-trunk/931/testReport/dtest.gossip_test/TestGossip],
[936|https://ci-cassandra.apache.org/job/Cassandra-trunk/936/testReport/dtest-novnode.gossip_test/TestGossip])
test_2dc_parallel_startup_one_seed
([916|https://ci-cassandra.apache.org/job/Cassandra-trunk/916/testReport/dtest-offheap.gossip_test/TestGossip],
[920|https://ci-cassandra.apache.org/job/Cassandra-trunk/920/testReport/dtest.gossip_test/TestGossip/])
The error is always the same:
{code:java}
Unexpected error found in node logs (see stdout for full details). Errors:
[ERROR [main] 2022-01-26 10:53:12,866 CassandraDaemon.java:900 - Exception
encountered during startup
java.lang.RuntimeException: Didn't receive schemas for all known versions
within the timeout. Use -Dcassandra.skip_schema_check=true to skip this check.
at
org.apache.cassandra.service.StorageService.waitForSchema(StorageService.java:1037)
at
org.apache.cassandra.dht.BootStrapper.allocateTokens(BootStrapper.java:232)
at
org.apache.cassandra.dht.BootStrapper.getBootstrapTokens(BootStrapper.java:180)
at
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1089)
at
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1043)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:821)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:751)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:417)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:754)
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:878),
ERROR [main] 2022-01-26 10:53:12,866 CassandraDaemon.java:900 - Exception
encountered during startup
java.lang.RuntimeException: Didn't receive schemas for all known versions
within the timeout. Use -Dcassandra.skip_schema_check=true to skip this check.
at
org.apache.cassandra.service.StorageService.waitForSchema(StorageService.java:1037)
at
org.apache.cassandra.dht.BootStrapper.allocateTokens(BootStrapper.java:232)
at
org.apache.cassandra.dht.BootStrapper.getBootstrapTokens(BootStrapper.java:180)
at
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1089)
at
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1043)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:821)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:751)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:417)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:754)
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:878)]
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15254) Allow UPDATE on settings virtual table to change running configurations
[ https://issues.apache.org/jira/browse/CASSANDRA-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489396#comment-17489396 ] Benjamin Lerer commented on CASSANDRA-15254: [~dcapwell] I can but I am a bit overloaded currently so it might not be before a couple of weeks :-( > Allow UPDATE on settings virtual table to change running configurations > --- > > Key: CASSANDRA-15254 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15254 > Project: Cassandra > Issue Type: New Feature > Components: Feature/Virtual Tables >Reporter: Chris Lohfink >Assignee: Benjamin Lerer >Priority: Normal > > Allow using UPDATE on the system_views.settings virtual table to update > configs at runtime for the equivalent of the dispersed JMX > attributes/operations. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16677) Fix flaky ConnectionTest
[ https://issues.apache.org/jira/browse/CASSANDRA-16677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489386#comment-17489386 ] Aleksei Zotov commented on CASSANDRA-16677: --- Also I can see that [https://ci-cassandra.apache.org/job/Cassandra-trunk/936/testReport/org.apache.cassandra.net/ConnectionTest/testTimeout/] failed once for trunk. However, the error message is pretty much the same, so linking to this ticket as well. > Fix flaky ConnectionTest > > > Key: CASSANDRA-16677 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16677 > Project: Cassandra > Issue Type: Bug > Components: Messaging/Internode >Reporter: Brandon Williams >Priority: Normal > Fix For: 4.0.x > > Attachments: TEST-org.apache.cassandra.net.ConnectionTest.log.xz > > > https://ci-cassandra.apache.org/job/Cassandra-devbranch/785/testReport/junit/org.apache.cassandra.net/ConnectionTest/testMessageDeliveryOnReconnect_compression/ > https://app.circleci.com/pipelines/github/adelapena/cassandra/460/workflows/cf7dcec6-612c-45d1-8471-623bde481dca/jobs/4069 > https://app.circleci.com/pipelines/github/adelapena/cassandra/460/workflows/b750cd38-0263-4b5e-9bb8-a8be98214378/jobs/4065 -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16677) Fix flaky ConnectionTest
[ https://issues.apache.org/jira/browse/CASSANDRA-16677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489383#comment-17489383 ] Aleksei Zotov commented on CASSANDRA-16677: --- I can see it failed again for [935|https://ci-cassandra.apache.org/job/Cassandra-trunk/935/testReport/org.apache.cassandra.net/ConnectionTest] and [937|https://ci-cassandra.apache.org/job/Cassandra-trunk/937/testReport/org.apache.cassandra.net/ConnectionTest/] builds. I linked this ticket to the failure Butler. Attaching the full log for 937 build (in case someone may want to check that in the future): [^TEST-org.apache.cassandra.net.ConnectionTest.log.xz] > Fix flaky ConnectionTest > > > Key: CASSANDRA-16677 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16677 > Project: Cassandra > Issue Type: Bug > Components: Messaging/Internode >Reporter: Brandon Williams >Priority: Normal > Fix For: 4.0.x > > Attachments: TEST-org.apache.cassandra.net.ConnectionTest.log.xz > > > https://ci-cassandra.apache.org/job/Cassandra-devbranch/785/testReport/junit/org.apache.cassandra.net/ConnectionTest/testMessageDeliveryOnReconnect_compression/ > https://app.circleci.com/pipelines/github/adelapena/cassandra/460/workflows/cf7dcec6-612c-45d1-8471-623bde481dca/jobs/4069 > https://app.circleci.com/pipelines/github/adelapena/cassandra/460/workflows/b750cd38-0263-4b5e-9bb8-a8be98214378/jobs/4065 -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16677) Fix flaky ConnectionTest
[ https://issues.apache.org/jira/browse/CASSANDRA-16677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksei Zotov updated CASSANDRA-16677: -- Attachment: TEST-org.apache.cassandra.net.ConnectionTest.log.xz > Fix flaky ConnectionTest > > > Key: CASSANDRA-16677 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16677 > Project: Cassandra > Issue Type: Bug > Components: Messaging/Internode >Reporter: Brandon Williams >Priority: Normal > Fix For: 4.0.x > > Attachments: TEST-org.apache.cassandra.net.ConnectionTest.log.xz > > > https://ci-cassandra.apache.org/job/Cassandra-devbranch/785/testReport/junit/org.apache.cassandra.net/ConnectionTest/testMessageDeliveryOnReconnect_compression/ > https://app.circleci.com/pipelines/github/adelapena/cassandra/460/workflows/cf7dcec6-612c-45d1-8471-623bde481dca/jobs/4069 > https://app.circleci.com/pipelines/github/adelapena/cassandra/460/workflows/b750cd38-0263-4b5e-9bb8-a8be98214378/jobs/4065 -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17295) Make vtables accessible via internode messaging
[ https://issues.apache.org/jira/browse/CASSANDRA-17295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489381#comment-17489381 ] Stefan Miklosovic commented on CASSANDRA-17295: --- [~dcapwell] FYI read this if you missed it, it is supposed to fix these failures but I still do have various success with it. (1) https://lists.apache.org/thread/x6vojt50z5gcq9n3xfjvgb5cptnh36mz > Make vtables accessible via internode messaging > --- > > Key: CASSANDRA-17295 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17295 > Project: Cassandra > Issue Type: Improvement > Components: Feature/Virtual Tables >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.1 > > Time Spent: 50m > Remaining Estimate: 0h > > As an extension of CASSANDRA-15399 and needed to solve CASSANDRA-15566, we > need the ability to perform queries against vtables using internode > messaging; currently this is limited to CQL which isn’t exposed in internode -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17244) Fix org.apache.cassandra.distributed.test.trackwarnings.TombstoneCountWarningTest.failThresholdSinglePartition
[ https://issues.apache.org/jira/browse/CASSANDRA-17244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489375#comment-17489375 ] Aleksei Zotov commented on CASSANDRA-17244: --- I linked the failed tests in Butler with this ticket. Here is the detailed log from 935 build: https://ci-cassandra.apache.org/job/Cassandra-trunk-jvm-dtest/1072/jdk=jdk_11_latest,label=cassandra,split=1/consoleFull > Fix > org.apache.cassandra.distributed.test.trackwarnings.TombstoneCountWarningTest.failThresholdSinglePartition > -- > > Key: CASSANDRA-17244 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17244 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > org.apache.cassandra.distributed.test.trackwarnings.TombstoneCountWarningTest.failThresholdSinglePartition > failed > [here|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1354/testReport/junit/org.apache.cassandra.distributed.test.trackwarnings/TombstoneCountWarningTest/failThresholdSinglePartition/] > I didn't find any other occurrences but seems to me legit failure. > CC [~dcapwell] as I think you were working on those and probably you will > make better assessment than me. :) -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16950) Documentation for: CEP-9 Make SSLContext creation pluggable
[ https://issues.apache.org/jira/browse/CASSANDRA-16950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489357#comment-17489357 ] Stefan Miklosovic commented on CASSANDRA-16950: --- I did the review & put some comments on PR. > Documentation for: CEP-9 Make SSLContext creation pluggable > --- > > Key: CASSANDRA-16950 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16950 > Project: Cassandra > Issue Type: Improvement > Components: Documentation >Reporter: Maulin Vasavada >Assignee: Maulin Vasavada >Priority: Low > Fix For: 4.1 > > Time Spent: 10m > Remaining Estimate: 0h > > This ticket is to specifically cover the documentation for the pluggable > SSLContext creation code changes done as part of CASSANDRA-1. As a > general agreement on that ticket, it is decided that we should separate the > documentation work from the implementation due to the parallel on-going > documentation revamp (see CASSANDRA-16763). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16950) Documentation for: CEP-9 Make SSLContext creation pluggable
[ https://issues.apache.org/jira/browse/CASSANDRA-16950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489344#comment-17489344 ] Stefan Miklosovic commented on CASSANDRA-16950: --- Ah I see it, I am taking it back, it is there like a link, that is enough. > Documentation for: CEP-9 Make SSLContext creation pluggable > --- > > Key: CASSANDRA-16950 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16950 > Project: Cassandra > Issue Type: Improvement > Components: Documentation >Reporter: Maulin Vasavada >Assignee: Maulin Vasavada >Priority: Low > Fix For: 4.1 > > > This ticket is to specifically cover the documentation for the pluggable > SSLContext creation code changes done as part of CASSANDRA-1. As a > general agreement on that ticket, it is decided that we should separate the > documentation work from the implementation due to the parallel on-going > documentation revamp (see CASSANDRA-16763). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16950) Documentation for: CEP-9 Make SSLContext creation pluggable
[ https://issues.apache.org/jira/browse/CASSANDRA-16950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489341#comment-17489341 ] Stefan Miklosovic edited comment on CASSANDRA-16950 at 2/9/22, 8:13 AM: Hi [~maulin.vasavada], I would like to see the commands / examples how to actually create such PEM material which would be put into the documentation. If I know nothing about that stuff, I do not know how to produce the respective certificates / keys. was (Author: smiklosovic): Hi [~maulin.vasavada], I would like to see the commands / examples how to actually create suck PEM material which would be put into the documentation. If I know nothing about that stuff, I do not know how to produce the respective certificates / keys. > Documentation for: CEP-9 Make SSLContext creation pluggable > --- > > Key: CASSANDRA-16950 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16950 > Project: Cassandra > Issue Type: Improvement > Components: Documentation >Reporter: Maulin Vasavada >Assignee: Maulin Vasavada >Priority: Low > Fix For: 4.1 > > > This ticket is to specifically cover the documentation for the pluggable > SSLContext creation code changes done as part of CASSANDRA-1. As a > general agreement on that ticket, it is decided that we should separate the > documentation work from the implementation due to the parallel on-going > documentation revamp (see CASSANDRA-16763). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16950) Documentation for: CEP-9 Make SSLContext creation pluggable
[ https://issues.apache.org/jira/browse/CASSANDRA-16950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489341#comment-17489341 ] Stefan Miklosovic commented on CASSANDRA-16950: --- Hi [~maulin.vasavada], I would like to see the commands / examples how to actually create suck PEM material which would be put into the documentation. If I know nothing about that stuff, I do not know how to produce the respective certificates / keys. > Documentation for: CEP-9 Make SSLContext creation pluggable > --- > > Key: CASSANDRA-16950 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16950 > Project: Cassandra > Issue Type: Improvement > Components: Documentation >Reporter: Maulin Vasavada >Assignee: Maulin Vasavada >Priority: Low > Fix For: 4.1 > > > This ticket is to specifically cover the documentation for the pluggable > SSLContext creation code changes done as part of CASSANDRA-1. As a > general agreement on that ticket, it is decided that we should separate the > documentation work from the implementation due to the parallel on-going > documentation revamp (see CASSANDRA-16763). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16950) Documentation for: CEP-9 Make SSLContext creation pluggable
[ https://issues.apache.org/jira/browse/CASSANDRA-16950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-16950: -- Test and Documentation Plan: this ticket provides documentation Status: Patch Available (was: In Progress) https://github.com/apache/cassandra/pull/1441/files > Documentation for: CEP-9 Make SSLContext creation pluggable > --- > > Key: CASSANDRA-16950 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16950 > Project: Cassandra > Issue Type: Improvement > Components: Documentation >Reporter: Maulin Vasavada >Assignee: Maulin Vasavada >Priority: Low > Fix For: 4.1 > > > This ticket is to specifically cover the documentation for the pluggable > SSLContext creation code changes done as part of CASSANDRA-1. As a > general agreement on that ticket, it is decided that we should separate the > documentation work from the implementation due to the parallel on-going > documentation revamp (see CASSANDRA-16763). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16950) Documentation for: CEP-9 Make SSLContext creation pluggable
[ https://issues.apache.org/jira/browse/CASSANDRA-16950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-16950: -- Change Category: Operability Complexity: Low Hanging Fruit Component/s: Documentation (was: Messaging/Internode) Fix Version/s: 4.1 Reviewers: Stefan Miklosovic Priority: Low (was: Normal) Status: Open (was: Triage Needed) > Documentation for: CEP-9 Make SSLContext creation pluggable > --- > > Key: CASSANDRA-16950 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16950 > Project: Cassandra > Issue Type: Improvement > Components: Documentation >Reporter: Maulin Vasavada >Assignee: Maulin Vasavada >Priority: Low > Fix For: 4.1 > > > This ticket is to specifically cover the documentation for the pluggable > SSLContext creation code changes done as part of CASSANDRA-1. As a > general agreement on that ticket, it is decided that we should separate the > documentation work from the implementation due to the parallel on-going > documentation revamp (see CASSANDRA-16763). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
