[jira] [Updated] (CASSANDRA-18600) [Analytics] Add NOTICE.txt in Cassandra Analytics
[
https://issues.apache.org/jira/browse/CASSANDRA-18600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-18600:
Fix Version/s: 5.0
(was: 5.x)
Source Control Link:
https://github.com/apache/cassandra-analytics/commit/cbae09ca71b9eb9a581b77c23844da21474b095a
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Sorry was being silly trying to commit to GH instead of gitbox... Not sure
about the fixVer though...
> [Analytics] Add NOTICE.txt in Cassandra Analytics
> --
>
> Key: CASSANDRA-18600
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18600
> Project: Cassandra
> Issue Type: Task
> Components: Analytics Library
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Fix For: 5.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Cassandra Analytics project is missing the {{NOTICE.txt}} file required
> for compliance with the ASF guidance
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-analytics] branch trunk updated: CASSANDRA-18600 Add NOTICE.txt file
This is an automated email from the ASF dual-hosted git repository. bereng pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra-analytics.git The following commit(s) were added to refs/heads/trunk by this push: new cbae09c CASSANDRA-18600 Add NOTICE.txt file cbae09c is described below commit cbae09ca71b9eb9a581b77c23844da21474b095a Author: Francisco Guerrero AuthorDate: Wed Jun 14 11:52:55 2023 -0700 CASSANDRA-18600 Add NOTICE.txt file The NOTICE.txt file is currently missing in the repository. This commit adds the file to comply with ASF's guidance. patch by Francisco Guerrero; reviewed by Dinesh Joshi, Michael Semb Wever, Berenguer Blasi for CASSANDRA-18600 --- NOTICE.txt | 6 ++ 1 file changed, 6 insertions(+) diff --git a/NOTICE.txt b/NOTICE.txt new file mode 100644 index 000..3dd5d8b --- /dev/null +++ b/NOTICE.txt @@ -0,0 +1,6 @@ +Apache Cassandra Analytics +Copyright 2023- The Apache Software Foundation + +This product includes software developed by The Apache Software +Foundation (http://www.apache.org/). + - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18582) BulkLoader withCipherSuites option is ignored
[
https://issues.apache.org/jira/browse/CASSANDRA-18582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dan jatnieks updated CASSANDRA-18582:
-
Test and Documentation Plan:
Run pre-commit tests via CircleCI - free tier, and lack of resources may be
responsible to many errors?
https://app.circleci.com/pipelines/github/djatnieks/cassandra?branch=CASSANDRA-18582-4.0
https://app.circleci.com/pipelines/github/djatnieks/cassandra?branch=CASSANDRA-18582-4.1
https://app.circleci.com/pipelines/github/djatnieks/cassandra?branch=CASSANDRA-18582-trunk
Status: Patch Available (was: In Progress)
> BulkLoader withCipherSuites option is ignored
> -
>
> Key: CASSANDRA-18582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18582
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: dan jatnieks
>Assignee: dan jatnieks
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
>
> The {{withCipherSuites}} option of {{BulkLoader}} is being ignored. It seems
> that since CASSANDRA-16362 the {{BulkLoader.buildSSLOptions}} method no
> longer applies the cipher suite options provided by
> {{clientEncryptionOptions}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18617) Disable the deprecated keyspace/table thresholds and convert them to Guardrails
[
https://issues.apache.org/jira/browse/CASSANDRA-18617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737404#comment-17737404
]
dan jatnieks commented on CASSANDRA-18617:
--
Part of this change is to add converters that will take the old threshold
value, including the number of system keyspaces/tables, and convert that to a
guardrail value that excludes system keyspaces/tables.
To determine the number of system keyspaces, there is an existing
{{SchemaConstants.getSystemKeyspaces}} method that seems reasonable to use.
However, I'm finding it harder to find an existing way to get the number of
system tables.
Some test code uses {{metadata}} method in system keyspace classes to get
metadata including the tables, e.g. {{{}SystemKeyspace.metadata{}}}. However,
aside from maybe doing more work than is needed, this doesn't work when called
from converter code because just accessing {{SystemKeyspace}} triggers static
initialization, and at some point that leads to needing some value from
{{{}DatabaseDescriptor{}}}. But the initialization of {{DatabaseDescriptor}} is
what triggered the loading of the config in the first place (so it ends up with
an NPE trying to access an uninitialized field).
So I think something is needed similar to {{getSystemKeyspaces}} also located
in {{SchemaConstants}} where static initialization problems are less likely. A
downside to this approach is that it depends on being updated whenever a new
system table is added, but I supposed it's no worse than the existing situation
with {{{}getSystemKeyspaces{}}}.
> Disable the deprecated keyspace/table thresholds and convert them to
> Guardrails
> ---
>
> Key: CASSANDRA-18617
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18617
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Guardrails
>Reporter: dan jatnieks
>Assignee: dan jatnieks
>Priority: Normal
> Fix For: 5.x
>
>
> The non-guardrail thresholds 'keyspace_count_warn_threshold' and
> 'table_count_warn_threshold' configuration settings were first added with
> CASSANDRA-16309 in 4.0-beta4 and have subsequently been deprecated since
> 4.1-alpha in CASSANDRA-17195 when they were replaced/migrated to guardrails
> as part of CEP-3 (Guardrails).
> These thresholds should now be removed from cassandra.yaml, while still
> allowed in existing yaml files.
> The old thresholds will be disabled by removing their default values from
> Config.java, and any existing values for these thresholds will be converted
> to the new guardrails using the '@Replaces' tag on the corresponding
> guardrail values.
> Since the old thresholds considered the number of system keyspace/tables in
> their values, the '@Replaces' conversion will subtract the current number of
> system tables from the old value and log a descriptive message.
> See dev list discussion:
> https://lists.apache.org/thread/0zjg08hrd6xv7lhvo96frz456b2rvr8b
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18629) BLOG - Clarify wording on 3.x EOL post
[ https://issues.apache.org/jira/browse/CASSANDRA-18629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18629: -- Status: Review In Progress (was: Patch Available) I've staged the PR locally and confirmed that it's ready to commit. > BLOG - Clarify wording on 3.x EOL post > -- > > Key: CASSANDRA-18629 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18629 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Patrick McFadin >Assignee: Patrick McFadin >Priority: Normal > Fix For: NA > > Attachments: c18629-01-blog-index.png, c18629-02-blog-post.png > > > CASSANDRA-18531 generated some confusion so attempting to clean up the > wording. > https://cassandra.apache.org/_/blog/Apache-Cassandra-3.0.x-and-3.11.x-End-of-Life-Announcement.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18629) BLOG - Clarify wording on 3.x EOL post
[ https://issues.apache.org/jira/browse/CASSANDRA-18629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18629: -- Status: Ready to Commit (was: Review In Progress) > BLOG - Clarify wording on 3.x EOL post > -- > > Key: CASSANDRA-18629 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18629 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Patrick McFadin >Assignee: Patrick McFadin >Priority: Normal > Fix For: NA > > Attachments: c18629-01-blog-index.png, c18629-02-blog-post.png > > > CASSANDRA-18531 generated some confusion so attempting to clean up the > wording. > https://cassandra.apache.org/_/blog/Apache-Cassandra-3.0.x-and-3.11.x-End-of-Life-Announcement.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18629) BLOG - Clarify wording on 3.x EOL post
[ https://issues.apache.org/jira/browse/CASSANDRA-18629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18629: -- Test and Documentation Plan: Stage locally and verify updates render as expected Status: Patch Available (was: Open) Patch - https://github.com/apache/cassandra-website/pull/227 > BLOG - Clarify wording on 3.x EOL post > -- > > Key: CASSANDRA-18629 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18629 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Patrick McFadin >Assignee: Patrick McFadin >Priority: Normal > Fix For: NA > > Attachments: c18629-01-blog-index.png, c18629-02-blog-post.png > > > CASSANDRA-18531 generated some confusion so attempting to clean up the > wording. > https://cassandra.apache.org/_/blog/Apache-Cassandra-3.0.x-and-3.11.x-End-of-Life-Announcement.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18629) BLOG - Clarify wording on 3.x EOL post
[ https://issues.apache.org/jira/browse/CASSANDRA-18629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick McFadin updated CASSANDRA-18629: Attachment: c18629-01-blog-index.png > BLOG - Clarify wording on 3.x EOL post > -- > > Key: CASSANDRA-18629 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18629 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Patrick McFadin >Assignee: Patrick McFadin >Priority: Normal > Fix For: NA > > Attachments: c18629-01-blog-index.png, c18629-02-blog-post.png > > > CASSANDRA-18531 generated some confusion so attempting to clean up the > wording. > https://cassandra.apache.org/_/blog/Apache-Cassandra-3.0.x-and-3.11.x-End-of-Life-Announcement.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18629) BLOG - Clarify wording on 3.x EOL post
[ https://issues.apache.org/jira/browse/CASSANDRA-18629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737400#comment-17737400 ] Patrick McFadin commented on CASSANDRA-18629: - Changes added !c18629-01-blog-index.png!!c18629-02-blog-post.png! > BLOG - Clarify wording on 3.x EOL post > -- > > Key: CASSANDRA-18629 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18629 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Patrick McFadin >Assignee: Patrick McFadin >Priority: Normal > Fix For: NA > > Attachments: c18629-01-blog-index.png, c18629-02-blog-post.png > > > CASSANDRA-18531 generated some confusion so attempting to clean up the > wording. > https://cassandra.apache.org/_/blog/Apache-Cassandra-3.0.x-and-3.11.x-End-of-Life-Announcement.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18629) BLOG - Clarify wording on 3.x EOL post
[ https://issues.apache.org/jira/browse/CASSANDRA-18629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick McFadin updated CASSANDRA-18629: Attachment: c18629-02-blog-post.png > BLOG - Clarify wording on 3.x EOL post > -- > > Key: CASSANDRA-18629 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18629 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Patrick McFadin >Assignee: Patrick McFadin >Priority: Normal > Fix For: NA > > Attachments: c18629-01-blog-index.png, c18629-02-blog-post.png > > > CASSANDRA-18531 generated some confusion so attempting to clean up the > wording. > https://cassandra.apache.org/_/blog/Apache-Cassandra-3.0.x-and-3.11.x-End-of-Life-Announcement.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18629) BLOG - Clarify wording on 3.x EOL post
[ https://issues.apache.org/jira/browse/CASSANDRA-18629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18629: -- Change Category: Semantic Complexity: Normal Component/s: Documentation/Blog Fix Version/s: NA Reviewers: Erick Ramirez Assignee: Patrick McFadin Status: Open (was: Triage Needed) > BLOG - Clarify wording on 3.x EOL post > -- > > Key: CASSANDRA-18629 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18629 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Patrick McFadin >Assignee: Patrick McFadin >Priority: Normal > Fix For: NA > > > CASSANDRA-18531 generated some confusion so attempting to clean up the > wording. > https://cassandra.apache.org/_/blog/Apache-Cassandra-3.0.x-and-3.11.x-End-of-Life-Announcement.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18629) BLOG - Clarify wording on 3.x EOL post
[ https://issues.apache.org/jira/browse/CASSANDRA-18629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18629: -- Summary: BLOG - Clarify wording on 3.x EOL post (was: Clarify wording on EOL blog post) > BLOG - Clarify wording on 3.x EOL post > -- > > Key: CASSANDRA-18629 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18629 > Project: Cassandra > Issue Type: Task >Reporter: Patrick McFadin >Priority: Normal > > CASSANDRA-18531 generated some confusion so attempting to clean up the > wording. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18629) BLOG - Clarify wording on 3.x EOL post
[ https://issues.apache.org/jira/browse/CASSANDRA-18629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-18629: -- Description: CASSANDRA-18531 generated some confusion so attempting to clean up the wording. https://cassandra.apache.org/_/blog/Apache-Cassandra-3.0.x-and-3.11.x-End-of-Life-Announcement.html was:CASSANDRA-18531 generated some confusion so attempting to clean up the wording. > BLOG - Clarify wording on 3.x EOL post > -- > > Key: CASSANDRA-18629 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18629 > Project: Cassandra > Issue Type: Task >Reporter: Patrick McFadin >Priority: Normal > > CASSANDRA-18531 generated some confusion so attempting to clean up the > wording. > https://cassandra.apache.org/_/blog/Apache-Cassandra-3.0.x-and-3.11.x-End-of-Life-Announcement.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18615) CREATE INDEX Modifications for Initial Release of SAI
[
https://issues.apache.org/jira/browse/CASSANDRA-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737398#comment-17737398
]
Caleb Rackliffe commented on CASSANDRA-18615:
-
[~jbellis] What about going the descriptive route, like "hidden_table" :D
> CREATE INDEX Modifications for Initial Release of SAI
> -
>
> Key: CASSANDRA-18615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18615
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax, Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: NA
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> After a lengthy discussion on the dev list, the community seems to have
> arrived at the following list of TODOs before we release SAI in 5.0:
> 1.) CREATE INDEX should be expanded to support {{USING … WITH OPTIONS…}}
> Essentially, we should be able to do something like {{CREATE INDEX ON tbl(v)
> USING ’sai’ WITH OPTIONS = ...}} and {{CREATE INDEX ON tbl(v) USING
> ‘cassandra’}} as a more specific/complete way to emulate the current behavior
> of {{CREATE INDEX}}.
> 2.) Allow operators to configure, in the YAML, a.) whether an index
> implementation must be specified w/ USING and {{CREATE INDEX}} and b.) what
> the default implementation will be, if {{USING}} isn’t required.
> 3.) The defaults we ship w/ will avoid breaking existing {{CREATE INDEX}}
> usage. (i.e. A default is allowed, and that default will remain ‘cassandra’,
> or the legacy 2i)
> With all this in place, users should be able create SAI indexes w/ the
> simplest possible syntax, no defaults will change, and operators will have
> the ability to change defaults to favor SAI whenever they like.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18574) [Analytics] Fix example documentation
[
https://issues.apache.org/jira/browse/CASSANDRA-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737394#comment-17737394
]
Dinesh Joshi commented on CASSANDRA-18574:
--
+1, thanks for the patch!
> [Analytics] Fix example documentation
> --
>
> Key: CASSANDRA-18574
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18574
> Project: Cassandra
> Issue Type: Improvement
> Components: Analytics Library
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Low
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The documentation for the example job for Cassandra Analytics
> [link|https://github.com/apache/cassandra-analytics/blob/trunk/cassandra-analytics-core-example/README.md]
> configures Sidecar to use the local CCM cluster. This documentation is
> however broken since some feedback during the review of the Sidecar PR
> changed one of the yaml options from {{uploads_staging_dir}} to
> {{staging_dir}}.
> We need to update the documentation to reflect that change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-59) Expose JMX host and port from JMXClient
[ https://issues.apache.org/jira/browse/CASSANDRASC-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737393#comment-17737393 ] Dinesh Joshi commented on CASSANDRASC-59: - +1, thanks for the patch! > Expose JMX host and port from JMXClient > --- > > Key: CASSANDRASC-59 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-59 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > Many integrations require the JMX host and port configured for a given JMX > client. It is desired that this information is available in the > ICassandraDelegate. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-58) Support retries in Sidecar Client when MD5 checksum is mismatched
[ https://issues.apache.org/jira/browse/CASSANDRASC-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737392#comment-17737392 ] Dinesh Joshi commented on CASSANDRASC-58: - +1, thanks for the patch! > Support retries in Sidecar Client when MD5 checksum is mismatched > - > > Key: CASSANDRASC-58 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-58 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > In rare occasions an SSTable upload will get corrupted during upload. Bit > flips are expected to occur occasionally while transmitting the SSTables from > the client to the server. The current behavior of the Sidecar Client in those > situations is to fail fast without any retries. > We want to support Sidecar Client retries when checksum mismatch occurs > during SSTable upload. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-53) [Sidecar Client] Allow unknown fields in the response
[
https://issues.apache.org/jira/browse/CASSANDRASC-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737391#comment-17737391
]
Dinesh Joshi commented on CASSANDRASC-53:
-
+1, thanks for the patch!
> [Sidecar Client] Allow unknown fields in the response
> -
>
> Key: CASSANDRASC-53
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-53
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: pull-request-available
>
> While testing CASSANDRASC-52 on the server side, the Sidecar client based off
> of {{trunk}} failed to deserialize the JSON payload with error
> {code:java}
> Caused by:
> o.a.c.sidecar.client.shaded.com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException:
> Unrecognized field "sidecar" (class
> org.apache.cassandra.sidecar.common.NodeSettings), not marked as ignorable (2
> known properties: "releaseVersion", "partitioner"])
> at [Source:
> (byte[])"{"releaseVersion":"4.0.9-SNAPSHOT","partitioner":"org.apache.cassandra.dht.Murmur3Partitioner","sidecar":{"version":"1.0-SNAPSHOT"}}";
> line: 1, column: 107] (through reference chain:
> org.apache.cassandra.sidecar.common.NodeSettings["sidecar"])
> at
> o.a.c.sidecar.client.shaded.com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException.from(UnrecognizedPropertyException.java:61)
> at
> o.a.c.sidecar.client.shaded.com.fasterxml.jackson.databind.DeserializationContext.handleUnknownProperty(DeserializationContext.java:1132)
> {code}
> As we are evolving the code, we expect the API on the server side to evolve.
> The deployed clients need to tolerate these new fields in the response JSON
> payload to continue working correctly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-56) Create staging directory if it doesn't exists
[ https://issues.apache.org/jira/browse/CASSANDRASC-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737390#comment-17737390 ] Dinesh Joshi commented on CASSANDRASC-56: - +1, thanks for the patch! > Create staging directory if it doesn't exists > - > > Key: CASSANDRASC-56 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-56 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > During SSTable upload, the upload will fail if the configured staging > directory does not exist. When this occurs we must manually have to create > the directory, which increases the configuration toil. To improve the > experience, it is desired that Sidecar creates the staging directory if it > doesn't exist. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (60ba1690 -> 7f53765c)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 60ba1690 generate docs for 8efdf127 new 7f53765c generate docs for 8efdf127 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 (60ba1690) \ N -- N -- N refs/heads/asf-staging (7f53765c) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4796900 -> 4796900 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18629) Clarify wording on EOL blog post
Patrick McFadin created CASSANDRA-18629: --- Summary: Clarify wording on EOL blog post Key: CASSANDRA-18629 URL: https://issues.apache.org/jira/browse/CASSANDRA-18629 Project: Cassandra Issue Type: Task Reporter: Patrick McFadin CASSANDRA-18531 generated some confusion so attempting to clean up the wording. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18615) CREATE INDEX Modifications for Initial Release of SAI
[
https://issues.apache.org/jira/browse/CASSANDRA-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737381#comment-17737381
]
Jonathan Ellis commented on CASSANDRA-18615:
I don't think the name `cassandra` is very descriptive to end users. How about
`hash_legacy`, `equalityonly_legacy`, something like that ?
> CREATE INDEX Modifications for Initial Release of SAI
> -
>
> Key: CASSANDRA-18615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18615
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax, Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: NA
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> After a lengthy discussion on the dev list, the community seems to have
> arrived at the following list of TODOs before we release SAI in 5.0:
> 1.) CREATE INDEX should be expanded to support {{USING … WITH OPTIONS…}}
> Essentially, we should be able to do something like {{CREATE INDEX ON tbl(v)
> USING ’sai’ WITH OPTIONS = ...}} and {{CREATE INDEX ON tbl(v) USING
> ‘cassandra’}} as a more specific/complete way to emulate the current behavior
> of {{CREATE INDEX}}.
> 2.) Allow operators to configure, in the YAML, a.) whether an index
> implementation must be specified w/ USING and {{CREATE INDEX}} and b.) what
> the default implementation will be, if {{USING}} isn’t required.
> 3.) The defaults we ship w/ will avoid breaking existing {{CREATE INDEX}}
> usage. (i.e. A default is allowed, and that default will remain ‘cassandra’,
> or the legacy 2i)
> With all this in place, users should be able create SAI indexes w/ the
> simplest possible syntax, no defaults will change, and operators will have
> the ability to change defaults to favor SAI whenever they like.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-60) Sidecar API to expose cluster topology information
[ https://issues.apache.org/jira/browse/CASSANDRASC-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Ashok updated CASSANDRASC-60: --- Change Category: Semantic Complexity: Normal Status: Open (was: Triage Needed) > Sidecar API to expose cluster topology information > -- > > Key: CASSANDRASC-60 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-60 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > > This API will expose token ranges and the corresponding read and write > replicas. The write replica-set token ranges will include natural and pending > ranges, so clients can have a complete view of the cluster as nodes are > joining or leaving. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRASC-60) Sidecar API to expose cluster topology information
Arjun Ashok created CASSANDRASC-60: -- Summary: Sidecar API to expose cluster topology information Key: CASSANDRASC-60 URL: https://issues.apache.org/jira/browse/CASSANDRASC-60 Project: Sidecar for Apache Cassandra Issue Type: Improvement Components: Rest API Reporter: Arjun Ashok Assignee: Arjun Ashok This API will expose token ranges and the corresponding read and write replicas. The write replica-set token ranges will include natural and pending ranges, so clients can have a complete view of the cluster as nodes are joining or leaving. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18628) Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
[
https://issues.apache.org/jira/browse/CASSANDRA-18628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18628:
-
Resolution: Not A Problem
Status: Resolved (was: Awaiting Feedback)
> Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
> ---
>
> Key: CASSANDRA-18628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18628
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Ke Han
>Priority: Normal
>
> When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
> columns could not be accessed because of the syntax problem. I had a column
> named "Is" in the 2.x. However, after the upgrade process, when I try to
> perform the same select command, it throws an exception since "Is" will be
> interpreted separately.
> I observed this after my cluster was fully upgraded. I cannot downgrade it
> back to 2.2.19. I cannot rename this column directly either.
> h2. Steps to reproduce
> Execute the following commands in Cassandra-2.2.19 (single node)
> {code:java}
> CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
> 'replication_factor' : 2 };
> CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c2 INT,c3 TEXT,rJr INT,c4 TEXT,c5
> TEXT,ds INT, Is INT,
> PRIMARY KEY (c2, c5, c3, rJr, Is, c1, ds, c4 ));
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> c2 | ds | is | c4
> +++
> (0 rows){code}
> Then perform an upgrade to Cassandra-3.0.29/Cassandra-3.11.15
> {code:java}
> // Do the same select
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> SyntaxException: line 1:15 no viable alternative at input 'Is' (SELECT c2,
> ds, [Is]...){code}
> The column still exists in the table, but I cannot access it.
> I am wondering whether I can directly rename it in the new version or get
> some prompts telling me to rename is before the upgrade process. "Is" is also
> not marked as a reserved word in the [CQL Keywords
> doc|https://docs.datastax.com/en/cql-oss/3.3/cql/cql_reference/keywords_r.html]).
> Any help is appreciated!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18628) Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
[
https://issues.apache.org/jira/browse/CASSANDRA-18628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737358#comment-17737358
]
Ke Han commented on CASSANDRA-18628:
It works, thanks a lot!
It seems it's case-sensitive with quotes.
> Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
> ---
>
> Key: CASSANDRA-18628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18628
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Ke Han
>Priority: Normal
>
> When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
> columns could not be accessed because of the syntax problem. I had a column
> named "Is" in the 2.x. However, after the upgrade process, when I try to
> perform the same select command, it throws an exception since "Is" will be
> interpreted separately.
> I observed this after my cluster was fully upgraded. I cannot downgrade it
> back to 2.2.19. I cannot rename this column directly either.
> h2. Steps to reproduce
> Execute the following commands in Cassandra-2.2.19 (single node)
> {code:java}
> CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
> 'replication_factor' : 2 };
> CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c2 INT,c3 TEXT,rJr INT,c4 TEXT,c5
> TEXT,ds INT, Is INT,
> PRIMARY KEY (c2, c5, c3, rJr, Is, c1, ds, c4 ));
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> c2 | ds | is | c4
> +++
> (0 rows){code}
> Then perform an upgrade to Cassandra-3.0.29/Cassandra-3.11.15
> {code:java}
> // Do the same select
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> SyntaxException: line 1:15 no viable alternative at input 'Is' (SELECT c2,
> ds, [Is]...){code}
> The column still exists in the table, but I cannot access it.
> I am wondering whether I can directly rename it in the new version or get
> some prompts telling me to rename is before the upgrade process. "Is" is also
> not marked as a reserved word in the [CQL Keywords
> doc|https://docs.datastax.com/en/cql-oss/3.3/cql/cql_reference/keywords_r.html]).
> Any help is appreciated!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18628) Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
[
https://issues.apache.org/jira/browse/CASSANDRA-18628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737357#comment-17737357
]
Brandon Williams commented on CASSANDRA-18628:
--
Since it's lowercase in your definition it needs to be lowercase in your quoted
query:
{noformat}
cqlsh> SELECT c2, ds, "is", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
c2 | ds | is | c4
+++
(0 rows)
{noformat}
> Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
> ---
>
> Key: CASSANDRA-18628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18628
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Ke Han
>Priority: Normal
>
> When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
> columns could not be accessed because of the syntax problem. I had a column
> named "Is" in the 2.x. However, after the upgrade process, when I try to
> perform the same select command, it throws an exception since "Is" will be
> interpreted separately.
> I observed this after my cluster was fully upgraded. I cannot downgrade it
> back to 2.2.19. I cannot rename this column directly either.
> h2. Steps to reproduce
> Execute the following commands in Cassandra-2.2.19 (single node)
> {code:java}
> CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
> 'replication_factor' : 2 };
> CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c2 INT,c3 TEXT,rJr INT,c4 TEXT,c5
> TEXT,ds INT, Is INT,
> PRIMARY KEY (c2, c5, c3, rJr, Is, c1, ds, c4 ));
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> c2 | ds | is | c4
> +++
> (0 rows){code}
> Then perform an upgrade to Cassandra-3.0.29/Cassandra-3.11.15
> {code:java}
> // Do the same select
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> SyntaxException: line 1:15 no viable alternative at input 'Is' (SELECT c2,
> ds, [Is]...){code}
> The column still exists in the table, but I cannot access it.
> I am wondering whether I can directly rename it in the new version or get
> some prompts telling me to rename is before the upgrade process. "Is" is also
> not marked as a reserved word in the [CQL Keywords
> doc|https://docs.datastax.com/en/cql-oss/3.3/cql/cql_reference/keywords_r.html]).
> Any help is appreciated!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18628) Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
[
https://issues.apache.org/jira/browse/CASSANDRA-18628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737356#comment-17737356
]
Ke Han edited comment on CASSANDRA-18628 at 6/26/23 9:50 PM:
-
[~brandon.williams] Thanks for the reply! But it doesn't work actually. Here
are the exceptions I got when running 3.11.15.
{code:java}
cqlsh> DESC ks.tb ;
CREATE TABLE ks.tb (
c2 int,
c5 text,
c3 text,
rjr int,
"is" int,
c1 int,
ds int,
c4 text,
PRIMARY KEY (c2, c5, c3, rjr, "is", c1, ds, c4)
) WITH CLUSTERING ORDER BY (c5 ASC, c3 ASC, rjr ASC, "is" ASC, c1 ASC, ds ASC,
c4 ASC)
AND bloom_filter_fp_chance = 0.01
AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND comment = ''
AND compaction = {'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}
AND compression = {'chunk_length_in_kb': '64', 'class':
'org.apache.cassandra.io.compress.LZ4Compressor'}
AND crc_check_chance = 1.0
AND dclocal_read_repair_chance = 0.1
AND default_time_to_live = 0
AND gc_grace_seconds = 864000
AND max_index_interval = 2048
AND memtable_flush_period_in_ms = 0
AND min_index_interval = 128
AND read_repair_chance = 0.0
AND speculative_retry = '99PERCENTILE';
cqlsh> SELECT c2, ds, "Is", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Undefined
column name "Is""
cqlsh> SELECT c2, ds, \"Is\", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
Invalid syntax at line 1, char 16
SELECT c2, ds, \"Is\", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
^
cqlsh> SELECT c2, ds, 'Is', c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot
infer type for term 'Is' in selection clause (try using a cast to force a
type)" {code}
May I ask whether you could run it without exception?
was (Author: JIRAUSER289562):
[~brandon.williams] Thanks for the reply! But it doesn't work actually. Here
are the exceptions I got when running 3.11.15.
{code:java}
cqlsh> DESC ks.tb ;
CREATE TABLE ks.tb (
c2 int,
c5 text,
c3 text,
rjr int,
"is" int,
c1 int,
ds int,
c4 text,
PRIMARY KEY (c2, c5, c3, rjr, "is", c1, ds, c4)
) WITH CLUSTERING ORDER BY (c5 ASC, c3 ASC, rjr ASC, "is" ASC, c1 ASC, ds ASC,
c4 ASC)
AND bloom_filter_fp_chance = 0.01
AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND comment = ''
AND compaction = {'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}
AND compression = {'chunk_length_in_kb': '64', 'class':
'org.apache.cassandra.io.compress.LZ4Compressor'}
AND crc_check_chance = 1.0
AND dclocal_read_repair_chance = 0.1
AND default_time_to_live = 0
AND gc_grace_seconds = 864000
AND max_index_interval = 2048
AND memtable_flush_period_in_ms = 0
AND min_index_interval = 128
AND read_repair_chance = 0.0
AND speculative_retry = '99PERCENTILE';
cqlsh> SELECT c2, ds, "Is", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Undefined
column name "Is""
cqlsh> SELECT c2, ds, \"Is\", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
Invalid syntax at line 1, char 16
SELECT c2, ds, \"Is\", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
^
cqlsh> SELECT c2, ds, 'Is', c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot
infer type for term 'Is' in selection clause (try using a cast to force a
type)" {code}
May I ask whether you get the correct results after the upgrade?
> Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
> ---
>
> Key: CASSANDRA-18628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18628
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Ke Han
>Priority: Normal
>
> When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
> columns could not be accessed because of the syntax problem. I had a column
>
[jira] [Comment Edited] (CASSANDRA-18628) Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
[
https://issues.apache.org/jira/browse/CASSANDRA-18628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737356#comment-17737356
]
Ke Han edited comment on CASSANDRA-18628 at 6/26/23 9:49 PM:
-
[~brandon.williams] Thanks for the reply! But it doesn't work actually. Here
are the exceptions I got when running 3.11.15.
{code:java}
cqlsh> DESC ks.tb ;
CREATE TABLE ks.tb (
c2 int,
c5 text,
c3 text,
rjr int,
"is" int,
c1 int,
ds int,
c4 text,
PRIMARY KEY (c2, c5, c3, rjr, "is", c1, ds, c4)
) WITH CLUSTERING ORDER BY (c5 ASC, c3 ASC, rjr ASC, "is" ASC, c1 ASC, ds ASC,
c4 ASC)
AND bloom_filter_fp_chance = 0.01
AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND comment = ''
AND compaction = {'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}
AND compression = {'chunk_length_in_kb': '64', 'class':
'org.apache.cassandra.io.compress.LZ4Compressor'}
AND crc_check_chance = 1.0
AND dclocal_read_repair_chance = 0.1
AND default_time_to_live = 0
AND gc_grace_seconds = 864000
AND max_index_interval = 2048
AND memtable_flush_period_in_ms = 0
AND min_index_interval = 128
AND read_repair_chance = 0.0
AND speculative_retry = '99PERCENTILE';
cqlsh> SELECT c2, ds, "Is", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Undefined
column name "Is""
cqlsh> SELECT c2, ds, \"Is\", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
Invalid syntax at line 1, char 16
SELECT c2, ds, \"Is\", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
^
cqlsh> SELECT c2, ds, 'Is', c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot
infer type for term 'Is' in selection clause (try using a cast to force a
type)" {code}
May I ask whether you get the correct results after the upgrade?
was (Author: JIRAUSER289562):
[~brandon.williams] Thanks for the reply! But it doesn't work actually. Here
are the exceptions I got when running 3.11.15.
{code:java}
cqlsh> DESC ks.tb ;
CREATE TABLE ks.tb (
c2 int,
c5 text,
c3 text,
rjr int,
"is" int,
c1 int,
ds int,
c4 text,
PRIMARY KEY (c2, c5, c3, rjr, "is", c1, ds, c4)
) WITH CLUSTERING ORDER BY (c5 ASC, c3 ASC, rjr ASC, "is" ASC, c1 ASC, ds ASC,
c4 ASC)
AND bloom_filter_fp_chance = 0.01
AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND comment = ''
AND compaction = {'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}
AND compression = {'chunk_length_in_kb': '64', 'class':
'org.apache.cassandra.io.compress.LZ4Compressor'}
AND crc_check_chance = 1.0
AND dclocal_read_repair_chance = 0.1
AND default_time_to_live = 0
AND gc_grace_seconds = 864000
AND max_index_interval = 2048
AND memtable_flush_period_in_ms = 0
AND min_index_interval = 128
AND read_repair_chance = 0.0
AND speculative_retry = '99PERCENTILE';
cqlsh> SELECT c2, ds, "Is", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Undefined
column name "Is""
cqlsh> SELECT c2, ds, \"Is\", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
Invalid syntax at line 1, char 16
SELECT c2, ds, \"Is\", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
^
cqlsh> SELECT c2, ds, 'Is', c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot
infer type for term 'Is' in selection clause (try using a cast to force a
type)" {code}
> Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
> ---
>
> Key: CASSANDRA-18628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18628
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Ke Han
>Priority: Normal
>
> When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
> columns could not be accessed because of the syntax problem. I had a column
> named "Is" in the 2.x. However, after the upgrade process,
[jira] [Comment Edited] (CASSANDRA-18628) Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
[
https://issues.apache.org/jira/browse/CASSANDRA-18628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737356#comment-17737356
]
Ke Han edited comment on CASSANDRA-18628 at 6/26/23 9:47 PM:
-
[~brandon.williams] Thanks for the reply! But it doesn't work actually. Here
are the exceptions I got when running 3.11.15.
{code:java}
cqlsh> DESC ks.tb ;
CREATE TABLE ks.tb (
c2 int,
c5 text,
c3 text,
rjr int,
"is" int,
c1 int,
ds int,
c4 text,
PRIMARY KEY (c2, c5, c3, rjr, "is", c1, ds, c4)
) WITH CLUSTERING ORDER BY (c5 ASC, c3 ASC, rjr ASC, "is" ASC, c1 ASC, ds ASC,
c4 ASC)
AND bloom_filter_fp_chance = 0.01
AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND comment = ''
AND compaction = {'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}
AND compression = {'chunk_length_in_kb': '64', 'class':
'org.apache.cassandra.io.compress.LZ4Compressor'}
AND crc_check_chance = 1.0
AND dclocal_read_repair_chance = 0.1
AND default_time_to_live = 0
AND gc_grace_seconds = 864000
AND max_index_interval = 2048
AND memtable_flush_period_in_ms = 0
AND min_index_interval = 128
AND read_repair_chance = 0.0
AND speculative_retry = '99PERCENTILE';
cqlsh> SELECT c2, ds, "Is", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Undefined
column name "Is""
cqlsh> SELECT c2, ds, \"Is\", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
Invalid syntax at line 1, char 16
SELECT c2, ds, \"Is\", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
^
cqlsh> SELECT c2, ds, 'Is', c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot
infer type for term 'Is' in selection clause (try using a cast to force a
type)" {code}
was (Author: JIRAUSER289562):
[~brandon.williams] Thanks for the reply! But it don't work actually. Here are
the exceptions I got when running 3.11.15.
{code:java}
cqlsh> DESC ks.tb ;
CREATE TABLE ks.tb (
c2 int,
c5 text,
c3 text,
rjr int,
"is" int,
c1 int,
ds int,
c4 text,
PRIMARY KEY (c2, c5, c3, rjr, "is", c1, ds, c4)
) WITH CLUSTERING ORDER BY (c5 ASC, c3 ASC, rjr ASC, "is" ASC, c1 ASC, ds ASC,
c4 ASC)
AND bloom_filter_fp_chance = 0.01
AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND comment = ''
AND compaction = {'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}
AND compression = {'chunk_length_in_kb': '64', 'class':
'org.apache.cassandra.io.compress.LZ4Compressor'}
AND crc_check_chance = 1.0
AND dclocal_read_repair_chance = 0.1
AND default_time_to_live = 0
AND gc_grace_seconds = 864000
AND max_index_interval = 2048
AND memtable_flush_period_in_ms = 0
AND min_index_interval = 128
AND read_repair_chance = 0.0
AND speculative_retry = '99PERCENTILE';
cqlsh> SELECT c2, ds, "Is", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Undefined
column name "Is""
cqlsh> SELECT c2, ds, \"Is\", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
Invalid syntax at line 1, char 16
SELECT c2, ds, \"Is\", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
^
cqlsh> SELECT c2, ds, 'Is', c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot
infer type for term 'Is' in selection clause (try using a cast to force a
type)" {code}
> Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
> ---
>
> Key: CASSANDRA-18628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18628
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Ke Han
>Priority: Normal
>
> When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
> columns could not be accessed because of the syntax problem. I had a column
> named "Is" in the 2.x. However, after the upgrade process, when I try to
> perform the same select command, it throws an exception
[jira] [Commented] (CASSANDRA-18628) Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
[
https://issues.apache.org/jira/browse/CASSANDRA-18628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737356#comment-17737356
]
Ke Han commented on CASSANDRA-18628:
[~brandon.williams] Thanks for the reply! But it don't work actually. Here are
the exceptions I got when running 3.11.15.
{code:java}
cqlsh> DESC ks.tb ;
CREATE TABLE ks.tb (
c2 int,
c5 text,
c3 text,
rjr int,
"is" int,
c1 int,
ds int,
c4 text,
PRIMARY KEY (c2, c5, c3, rjr, "is", c1, ds, c4)
) WITH CLUSTERING ORDER BY (c5 ASC, c3 ASC, rjr ASC, "is" ASC, c1 ASC, ds ASC,
c4 ASC)
AND bloom_filter_fp_chance = 0.01
AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND comment = ''
AND compaction = {'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}
AND compression = {'chunk_length_in_kb': '64', 'class':
'org.apache.cassandra.io.compress.LZ4Compressor'}
AND crc_check_chance = 1.0
AND dclocal_read_repair_chance = 0.1
AND default_time_to_live = 0
AND gc_grace_seconds = 864000
AND max_index_interval = 2048
AND memtable_flush_period_in_ms = 0
AND min_index_interval = 128
AND read_repair_chance = 0.0
AND speculative_retry = '99PERCENTILE';
cqlsh> SELECT c2, ds, "Is", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Undefined
column name "Is""
cqlsh> SELECT c2, ds, \"Is\", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
Invalid syntax at line 1, char 16
SELECT c2, ds, \"Is\", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
^
cqlsh> SELECT c2, ds, 'Is', c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Cannot
infer type for term 'Is' in selection clause (try using a cast to force a
type)" {code}
> Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
> ---
>
> Key: CASSANDRA-18628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18628
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Ke Han
>Priority: Normal
>
> When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
> columns could not be accessed because of the syntax problem. I had a column
> named "Is" in the 2.x. However, after the upgrade process, when I try to
> perform the same select command, it throws an exception since "Is" will be
> interpreted separately.
> I observed this after my cluster was fully upgraded. I cannot downgrade it
> back to 2.2.19. I cannot rename this column directly either.
> h2. Steps to reproduce
> Execute the following commands in Cassandra-2.2.19 (single node)
> {code:java}
> CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
> 'replication_factor' : 2 };
> CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c2 INT,c3 TEXT,rJr INT,c4 TEXT,c5
> TEXT,ds INT, Is INT,
> PRIMARY KEY (c2, c5, c3, rJr, Is, c1, ds, c4 ));
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> c2 | ds | is | c4
> +++
> (0 rows){code}
> Then perform an upgrade to Cassandra-3.0.29/Cassandra-3.11.15
> {code:java}
> // Do the same select
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> SyntaxException: line 1:15 no viable alternative at input 'Is' (SELECT c2,
> ds, [Is]...){code}
> The column still exists in the table, but I cannot access it.
> I am wondering whether I can directly rename it in the new version or get
> some prompts telling me to rename is before the upgrade process. "Is" is also
> not marked as a reserved word in the [CQL Keywords
> doc|https://docs.datastax.com/en/cql-oss/3.3/cql/cql_reference/keywords_r.html]).
> Any help is appreciated!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18628) Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
[
https://issues.apache.org/jira/browse/CASSANDRA-18628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737353#comment-17737353
]
Brandon Williams edited comment on CASSANDRA-18628 at 6/26/23 9:43 PM:
---
I think you just need to quote the column name in cqlsh:
{noformat}
cqlsh> SELECT c2, ds, "Is", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
c2 | ds | Is | c4
+++
(0 rows)
{noformat}
was (Author: brandon.williams):
I think you just need to quote the column name:
{noformat}
cqlsh> SELECT c2, ds, "Is", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
c2 | ds | Is | c4
+++
(0 rows)
{noformat}
> Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
> ---
>
> Key: CASSANDRA-18628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18628
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Ke Han
>Priority: Normal
>
> When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
> columns could not be accessed because of the syntax problem. I had a column
> named "Is" in the 2.x. However, after the upgrade process, when I try to
> perform the same select command, it throws an exception since "Is" will be
> interpreted separately.
> I observed this after my cluster was fully upgraded. I cannot downgrade it
> back to 2.2.19. I cannot rename this column directly either.
> h2. Steps to reproduce
> Execute the following commands in Cassandra-2.2.19 (single node)
> {code:java}
> CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
> 'replication_factor' : 2 };
> CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c2 INT,c3 TEXT,rJr INT,c4 TEXT,c5
> TEXT,ds INT, Is INT,
> PRIMARY KEY (c2, c5, c3, rJr, Is, c1, ds, c4 ));
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> c2 | ds | is | c4
> +++
> (0 rows){code}
> Then perform an upgrade to Cassandra-3.0.29/Cassandra-3.11.15
> {code:java}
> // Do the same select
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> SyntaxException: line 1:15 no viable alternative at input 'Is' (SELECT c2,
> ds, [Is]...){code}
> The column still exists in the table, but I cannot access it.
> I am wondering whether I can directly rename it in the new version or get
> some prompts telling me to rename is before the upgrade process. "Is" is also
> not marked as a reserved word in the [CQL Keywords
> doc|https://docs.datastax.com/en/cql-oss/3.3/cql/cql_reference/keywords_r.html]).
> Any help is appreciated!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18628) Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
[
https://issues.apache.org/jira/browse/CASSANDRA-18628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18628:
-
Status: Awaiting Feedback (was: Triage Needed)
> Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
> ---
>
> Key: CASSANDRA-18628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18628
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Ke Han
>Priority: Normal
>
> When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
> columns could not be accessed because of the syntax problem. I had a column
> named "Is" in the 2.x. However, after the upgrade process, when I try to
> perform the same select command, it throws an exception since "Is" will be
> interpreted separately.
> I observed this after my cluster was fully upgraded. I cannot downgrade it
> back to 2.2.19. I cannot rename this column directly either.
> h2. Steps to reproduce
> Execute the following commands in Cassandra-2.2.19 (single node)
> {code:java}
> CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
> 'replication_factor' : 2 };
> CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c2 INT,c3 TEXT,rJr INT,c4 TEXT,c5
> TEXT,ds INT, Is INT,
> PRIMARY KEY (c2, c5, c3, rJr, Is, c1, ds, c4 ));
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> c2 | ds | is | c4
> +++
> (0 rows){code}
> Then perform an upgrade to Cassandra-3.0.29/Cassandra-3.11.15
> {code:java}
> // Do the same select
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> SyntaxException: line 1:15 no viable alternative at input 'Is' (SELECT c2,
> ds, [Is]...){code}
> The column still exists in the table, but I cannot access it.
> I am wondering whether I can directly rename it in the new version or get
> some prompts telling me to rename is before the upgrade process. "Is" is also
> not marked as a reserved word in the [CQL Keywords
> doc|https://docs.datastax.com/en/cql-oss/3.3/cql/cql_reference/keywords_r.html]).
> Any help is appreciated!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18628) Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
[
https://issues.apache.org/jira/browse/CASSANDRA-18628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737353#comment-17737353
]
Brandon Williams commented on CASSANDRA-18628:
--
I think you just need to quote the column name:
{noformat}
cqlsh> SELECT c2, ds, "Is", c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 =
'teststring1' AND c3 = 'teststring2' AND rJr = -1012111692;
c2 | ds | Is | c4
+++
(0 rows)
{noformat}
> Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
> ---
>
> Key: CASSANDRA-18628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18628
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Ke Han
>Priority: Normal
>
> When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
> columns could not be accessed because of the syntax problem. I had a column
> named "Is" in the 2.x. However, after the upgrade process, when I try to
> perform the same select command, it throws an exception since "Is" will be
> interpreted separately.
> I observed this after my cluster was fully upgraded. I cannot downgrade it
> back to 2.2.19. I cannot rename this column directly either.
> h2. Steps to reproduce
> Execute the following commands in Cassandra-2.2.19 (single node)
> {code:java}
> CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
> 'replication_factor' : 2 };
> CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c2 INT,c3 TEXT,rJr INT,c4 TEXT,c5
> TEXT,ds INT, Is INT,
> PRIMARY KEY (c2, c5, c3, rJr, Is, c1, ds, c4 ));
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> c2 | ds | is | c4
> +++
> (0 rows){code}
> Then perform an upgrade to Cassandra-3.0.29/Cassandra-3.11.15
> {code:java}
> // Do the same select
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> SyntaxException: line 1:15 no viable alternative at input 'Is' (SELECT c2,
> ds, [Is]...){code}
> The column still exists in the table, but I cannot access it.
> I am wondering whether I can directly rename it in the new version or get
> some prompts telling me to rename is before the upgrade process. "Is" is also
> not marked as a reserved word in the [CQL Keywords
> doc|https://docs.datastax.com/en/cql-oss/3.3/cql/cql_reference/keywords_r.html]).
> Any help is appreciated!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18615) CREATE INDEX Modifications for Initial Release of SAI
[
https://issues.apache.org/jira/browse/CASSANDRA-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737352#comment-17737352
]
Caleb Rackliffe commented on CASSANDRA-18615:
-
btw, the 3 unit test failures are known/pre-existing, and will be fixed either
in CASSANDRA-18490 or CASSANDRA-18067.
> CREATE INDEX Modifications for Initial Release of SAI
> -
>
> Key: CASSANDRA-18615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18615
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax, Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: NA
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> After a lengthy discussion on the dev list, the community seems to have
> arrived at the following list of TODOs before we release SAI in 5.0:
> 1.) CREATE INDEX should be expanded to support {{USING … WITH OPTIONS…}}
> Essentially, we should be able to do something like {{CREATE INDEX ON tbl(v)
> USING ’sai’ WITH OPTIONS = ...}} and {{CREATE INDEX ON tbl(v) USING
> ‘cassandra’}} as a more specific/complete way to emulate the current behavior
> of {{CREATE INDEX}}.
> 2.) Allow operators to configure, in the YAML, a.) whether an index
> implementation must be specified w/ USING and {{CREATE INDEX}} and b.) what
> the default implementation will be, if {{USING}} isn’t required.
> 3.) The defaults we ship w/ will avoid breaking existing {{CREATE INDEX}}
> usage. (i.e. A default is allowed, and that default will remain ‘cassandra’,
> or the legacy 2i)
> With all this in place, users should be able create SAI indexes w/ the
> simplest possible syntax, no defaults will change, and operators will have
> the ability to change defaults to favor SAI whenever they like.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18628) Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
[
https://issues.apache.org/jira/browse/CASSANDRA-18628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ke Han updated CASSANDRA-18628:
---
Description:
When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
columns could not be accessed because of the syntax problem. I had a column
named "Is" in the 2.x. However, after the upgrade process, when I try to
perform the same select command, it throws an exception since "Is" will be
interpreted separately.
I observed this after my cluster was fully upgraded. I cannot downgrade it back
to 2.2.19. I cannot rename this column directly either.
h2. Steps to reproduce
Execute the following commands in Cassandra-2.2.19 (single node)
{code:java}
CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
'replication_factor' : 2 };
CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c2 INT,c3 TEXT,rJr INT,c4 TEXT,c5
TEXT,ds INT, Is INT,
PRIMARY KEY (c2, c5, c3, rJr, Is, c1, ds, c4 ));
SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
AND c3 = 'teststring2' AND rJr = -1012111692;
c2 | ds | is | c4
+++
(0 rows){code}
Then perform an upgrade to Cassandra-3.0.29/Cassandra-3.11.15
{code:java}
// Do the same select
SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
AND c3 = 'teststring2' AND rJr = -1012111692;
SyntaxException: line 1:15 no viable alternative at input 'Is' (SELECT c2, ds,
[Is]...){code}
The column still exists in the table, but I cannot access it.
I am wondering whether I can directly rename it in the new version or get some
prompts telling me to rename is before the upgrade process. "Is" is also not
marked as a reserved word in the [CQL Keywords
doc|https://docs.datastax.com/en/cql-oss/3.3/cql/cql_reference/keywords_r.html]).
was:
When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
columns could not be accessed because of the syntax problem. I had a column
named "Is" in the 2.x. However, after the upgrade process, when I try to
perform the same select command, it throws an exception since "Is" will be
interpreted separately.
I observed this after my cluster was fully upgraded. I cannot downgrade it back
to 2.2.19. I cannot rename this column directly either.
h2. Steps to reproduce
Execute the following commands in Cassandra-2.2.19 (single node)
{code:java}
CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
'replication_factor' : 2 };
CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c2 INT,c3 TEXT,rJr INT,c4 TEXT,c5
TEXT,ds INT, Is INT,
PRIMARY KEY (c2, c5, c3, rJr, Is, c1, ds, c4 ));
SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
AND c3 = 'teststring2' AND rJr = -1012111692;
c2 | ds | is | c4
+++
(0 rows){code}
Then perform an upgrade to Cassandra-3.0.29/Cassandra-3.11.15
{code:java}
// Do the same select
SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
AND c3 = 'teststring2' AND rJr = -1012111692;
SyntaxException: line 1:15 no viable alternative at input 'Is' (SELECT c2, ds,
[Is]...){code}
This column still exists in the table, but I cannot access it.
I am wondering whether I can directly rename it in the new version or get some
prompts telling me to rename is before the upgrade process. "Is" is also not
marked as a reserved word in the [CQL Keywords
doc|https://docs.datastax.com/en/cql-oss/3.3/cql/cql_reference/keywords_r.html]).
> Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
> ---
>
> Key: CASSANDRA-18628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18628
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Ke Han
>Priority: Normal
>
> When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
> columns could not be accessed because of the syntax problem. I had a column
> named "Is" in the 2.x. However, after the upgrade process, when I try to
> perform the same select command, it throws an exception since "Is" will be
> interpreted separately.
> I observed this after my cluster was fully upgraded. I cannot downgrade it
> back to 2.2.19. I cannot rename this column directly either.
> h2. Steps to reproduce
> Execute the following commands in Cassandra-2.2.19 (single node)
> {code:java}
> CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
> 'replication_factor' : 2 };
> CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c2 INT,c3 TEXT,rJr INT,c4 TEXT,c5
> TEXT,ds INT, Is INT,
> PRIMARY KEY (c2, c5, c3, rJr, Is, c1, ds, c4 ));
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> c2 | ds | is | c4
>
[jira] [Created] (CASSANDRA-18628) Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
Ke Han created CASSANDRA-18628:
--
Summary: Handle special column name when upgrading from 2.2.19 to
3.0.29/3.11.15
Key: CASSANDRA-18628
URL: https://issues.apache.org/jira/browse/CASSANDRA-18628
Project: Cassandra
Issue Type: Bug
Components: CQL/Interpreter
Reporter: Ke Han
When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
columns could not be accessed because of the syntax problem. I had a column
named "Is" in the 2.x. However, after the upgrade process, when I try to
perform the same select command, it throws an exception since "Is" will be
interpreted separately.
I observed this after my cluster was fully upgraded. I cannot downgrade it back
to 2.2.19. I cannot rename this column directly either.
h2. Steps to reproduce
Execute the following commands in Cassandra-2.2.19 (single node)
{code:java}
CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
'replication_factor' : 2 };
CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c2 INT,c3 TEXT,rJr INT,c4 TEXT,c5
TEXT,ds INT, Is INT,
PRIMARY KEY (c2, c5, c3, rJr, Is, c1, ds, c4 ));
SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
AND c3 = 'teststring2' AND rJr = -1012111692;
c2 | ds | is | c4
+++
(0 rows){code}
Then perform an upgrade to Cassandra-3.0.29/Cassandra-3.11.15
{code:java}
// Do the same select
SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
AND c3 = 'teststring2' AND rJr = -1012111692;
SyntaxException: line 1:15 no viable alternative at input 'Is' (SELECT c2, ds,
[Is]...){code}
This column still exists in the table, but I cannot access it.
I am wondering whether I can directly rename it in the new version or get some
prompts telling me to rename is before the upgrade process. "Is" is also not
marked as a reserved word in the [CQL Keywords
doc|https://docs.datastax.com/en/cql-oss/3.3/cql/cql_reference/keywords_r.html]).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18628) Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
[
https://issues.apache.org/jira/browse/CASSANDRA-18628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ke Han updated CASSANDRA-18628:
---
Description:
When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
columns could not be accessed because of the syntax problem. I had a column
named "Is" in the 2.x. However, after the upgrade process, when I try to
perform the same select command, it throws an exception since "Is" will be
interpreted separately.
I observed this after my cluster was fully upgraded. I cannot downgrade it back
to 2.2.19. I cannot rename this column directly either.
h2. Steps to reproduce
Execute the following commands in Cassandra-2.2.19 (single node)
{code:java}
CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
'replication_factor' : 2 };
CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c2 INT,c3 TEXT,rJr INT,c4 TEXT,c5
TEXT,ds INT, Is INT,
PRIMARY KEY (c2, c5, c3, rJr, Is, c1, ds, c4 ));
SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
AND c3 = 'teststring2' AND rJr = -1012111692;
c2 | ds | is | c4
+++
(0 rows){code}
Then perform an upgrade to Cassandra-3.0.29/Cassandra-3.11.15
{code:java}
// Do the same select
SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
AND c3 = 'teststring2' AND rJr = -1012111692;
SyntaxException: line 1:15 no viable alternative at input 'Is' (SELECT c2, ds,
[Is]...){code}
The column still exists in the table, but I cannot access it.
I am wondering whether I can directly rename it in the new version or get some
prompts telling me to rename is before the upgrade process. "Is" is also not
marked as a reserved word in the [CQL Keywords
doc|https://docs.datastax.com/en/cql-oss/3.3/cql/cql_reference/keywords_r.html]).
Any help is appreciated!
was:
When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
columns could not be accessed because of the syntax problem. I had a column
named "Is" in the 2.x. However, after the upgrade process, when I try to
perform the same select command, it throws an exception since "Is" will be
interpreted separately.
I observed this after my cluster was fully upgraded. I cannot downgrade it back
to 2.2.19. I cannot rename this column directly either.
h2. Steps to reproduce
Execute the following commands in Cassandra-2.2.19 (single node)
{code:java}
CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
'replication_factor' : 2 };
CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c2 INT,c3 TEXT,rJr INT,c4 TEXT,c5
TEXT,ds INT, Is INT,
PRIMARY KEY (c2, c5, c3, rJr, Is, c1, ds, c4 ));
SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
AND c3 = 'teststring2' AND rJr = -1012111692;
c2 | ds | is | c4
+++
(0 rows){code}
Then perform an upgrade to Cassandra-3.0.29/Cassandra-3.11.15
{code:java}
// Do the same select
SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
AND c3 = 'teststring2' AND rJr = -1012111692;
SyntaxException: line 1:15 no viable alternative at input 'Is' (SELECT c2, ds,
[Is]...){code}
The column still exists in the table, but I cannot access it.
I am wondering whether I can directly rename it in the new version or get some
prompts telling me to rename is before the upgrade process. "Is" is also not
marked as a reserved word in the [CQL Keywords
doc|https://docs.datastax.com/en/cql-oss/3.3/cql/cql_reference/keywords_r.html]).
> Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15
> ---
>
> Key: CASSANDRA-18628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18628
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Ke Han
>Priority: Normal
>
> When I was migrating from 2.2.19 to 3.0.29/3.11.15, I noticed some of my
> columns could not be accessed because of the syntax problem. I had a column
> named "Is" in the 2.x. However, after the upgrade process, when I try to
> perform the same select command, it throws an exception since "Is" will be
> interpreted separately.
> I observed this after my cluster was fully upgraded. I cannot downgrade it
> back to 2.2.19. I cannot rename this column directly either.
> h2. Steps to reproduce
> Execute the following commands in Cassandra-2.2.19 (single node)
> {code:java}
> CREATE KEYSPACE ks WITH REPLICATION = { 'class' : 'SimpleStrategy',
> 'replication_factor' : 2 };
> CREATE TABLE IF NOT EXISTS ks.tb (c1 INT,c2 INT,c3 TEXT,rJr INT,c4 TEXT,c5
> TEXT,ds INT, Is INT,
> PRIMARY KEY (c2, c5, c3, rJr, Is, c1, ds, c4 ));
> SELECT c2, ds, Is, c4 FROM ks.tb WHERE c2 = 1566089765 AND c5 = 'teststring1'
> AND c3 = 'teststring2' AND rJr = -1012111692;
> c2 | ds | is | c4
>
[jira] [Comment Edited] (CASSANDRA-18627) Tidy up vestigial code left over after CASSANDRA-17931
[
https://issues.apache.org/jira/browse/CASSANDRA-18627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737322#comment-17737322
]
Josh McKenzie edited comment on CASSANDRA-18627 at 6/26/23 9:24 PM:
-Hm. To anyone wandering past and curious, I'm not convinced this actually
_fixes_ anything since the only call sites in the {{PendingRepairManager}}
actually don't pass in any additional sstables or bytes (just 0), so the
compaction strategies don't have any estimated extra sstables or bytes to
calculate anything from. I'll need to dig a bit into where those values make
their way into this scope to then be passed on to compaction to determine where
and why they're vestigial in this way.-
Restructured ticket to clean this code up since it's clearly confusing. :)
was (Author: jmckenzie):
Hm. To anyone wandering past and curious, I'm not convinced this actually
_fixes_ anything since the only call sites in the {{PendingRepairManager}}
actually don't pass in any additional sstables or bytes (just 0), so the
compaction strategies don't have any estimated extra sstables or bytes to
calculate anything from. I'll need to dig a bit into where those values make
their way into this scope to then be passed on to compaction to determine where
and why they're vestigial in this way.
> Tidy up vestigial code left over after CASSANDRA-17931
> --
>
> Key: CASSANDRA-18627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18627
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Local/Compaction
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 5.x
>
>
> In CASSANDRA-17931, some code was left over (\{{additionalBytes}},
> {{{}additionalSSTables{}}}) inside the {{PendingRepairManager}} which, while
> not explicitly hurting anything, provides for some confusion around when we
> do or don't take additional values into account when adjusting for pending
> operations when deciding what to do with upcoming repairs etc.
>
> We should tidy that up and consider making the role of those methods / their
> structure more clear between the \{{PendingRepairManager]} hierarchy and the
> {{AbstractCompactionStrategy}} hierarchy to prevent further confusion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] (CASSANDRA-18627) Tidy up vestigial code left over after CASSANDRA-17931
[ https://issues.apache.org/jira/browse/CASSANDRA-18627 ]
Josh McKenzie deleted comment on CASSANDRA-18627:
---
was (Author: jmckenzie):
||Item|Link||
|PR|[link|https://github.com/apache/cassandra/pull/2450]|
|JDK8
CI|[link|https://app.circleci.com/pipelines/github/jmckenzie-dev/cassandra/337/workflows/4a26c29b-dca6-4b14-bc7c-8b7c9977a977]|
|JDK11
CI|[link|https://app.circleci.com/pipelines/github/jmckenzie-dev/cassandra/337/workflows/2eb8052f-4f63-4099-a96c-e19fafe6634b]|
> Tidy up vestigial code left over after CASSANDRA-17931
> --
>
> Key: CASSANDRA-18627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18627
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Local/Compaction
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 5.x
>
>
> In CASSANDRA-17931, some code was left over (\{{additionalBytes}},
> {{{}additionalSSTables{}}}) inside the {{PendingRepairManager}} which, while
> not explicitly hurting anything, provides for some confusion around when we
> do or don't take additional values into account when adjusting for pending
> operations when deciding what to do with upcoming repairs etc.
>
> We should tidy that up and consider making the role of those methods / their
> structure more clear between the \{{PendingRepairManager]} hierarchy and the
> {{AbstractCompactionStrategy}} hierarchy to prevent further confusion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18627) Tidy up vestigial code left over after CASSANDRA-17931
[
https://issues.apache.org/jira/browse/CASSANDRA-18627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-18627:
--
Description:
In CASSANDRA-17931, some code was left over (\{{additionalBytes}},
{{{}additionalSSTables{}}}) inside the {{PendingRepairManager}} which, while
not explicitly hurting anything, provides for some confusion around when we do
or don't take additional values into account when adjusting for pending
operations when deciding what to do with upcoming repairs etc.
We should tidy that up and consider making the role of those methods / their
structure more clear between the \{{PendingRepairManager]} hierarchy and the
{{AbstractCompactionStrategy}} hierarchy to prevent further confusion.
was:
In CASSANDRA-17931, we failed to correctly take into account the
additionalSSTables and additionalBytes passed in in one of our calls to
{code}PendingRepairManager.getEstimatedRemainingTasks{code}
> Tidy up vestigial code left over after CASSANDRA-17931
> --
>
> Key: CASSANDRA-18627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18627
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Local/Compaction
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 5.x
>
>
> In CASSANDRA-17931, some code was left over (\{{additionalBytes}},
> {{{}additionalSSTables{}}}) inside the {{PendingRepairManager}} which, while
> not explicitly hurting anything, provides for some confusion around when we
> do or don't take additional values into account when adjusting for pending
> operations when deciding what to do with upcoming repairs etc.
>
> We should tidy that up and consider making the role of those methods / their
> structure more clear between the \{{PendingRepairManager]} hierarchy and the
> {{AbstractCompactionStrategy}} hierarchy to prevent further confusion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15241) Virtual table to expose current running queries
[
https://issues.apache.org/jira/browse/CASSANDRA-15241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737350#comment-17737350
]
Caleb Rackliffe commented on CASSANDRA-15241:
-
Just started a CircleCI run with more hardware
[here|https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-15241-4.1-ci]...
> 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: 5.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> 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.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18627) Tidy up vestigial code left over after CASSANDRA-17931
[
https://issues.apache.org/jira/browse/CASSANDRA-18627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-18627:
--
Summary: Tidy up vestigial code left over after CASSANDRA-17931 (was: Fix
calculation of pending compactions in pending repair manager)
> Tidy up vestigial code left over after CASSANDRA-17931
> --
>
> Key: CASSANDRA-18627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18627
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Local/Compaction
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 5.x
>
>
> In CASSANDRA-17931, we failed to correctly take into account the
> additionalSSTables and additionalBytes passed in in one of our calls to
> {code}PendingRepairManager.getEstimatedRemainingTasks{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (aebe6ae5 -> 60ba1690)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard aebe6ae5 generate docs for 8efdf127 new 60ba1690 generate docs for 8efdf127 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 (aebe6ae5) \ N -- N -- N refs/heads/asf-staging (60ba1690) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4796900 -> 4796900 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18627) Fix calculation of pending compactions in pending repair manager
[
https://issues.apache.org/jira/browse/CASSANDRA-18627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737322#comment-17737322
]
Josh McKenzie commented on CASSANDRA-18627:
---
Hm. To anyone wandering past and curious, I'm not convinced this actually
_fixes_ anything since the only call sites in the {{PendingRepairManager}}
actually don't pass in any additional sstables or bytes (just 0), so the
compaction strategies don't have any estimated extra sstables or bytes to
calculate anything from. I'll need to dig a bit into where those values make
their way into this scope to then be passed on to compaction to determine where
and why they're vestigial in this way.
> Fix calculation of pending compactions in pending repair manager
>
>
> Key: CASSANDRA-18627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18627
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Local/Compaction
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 5.x
>
>
> In CASSANDRA-17931, we failed to correctly take into account the
> additionalSSTables and additionalBytes passed in in one of our calls to
> {code}PendingRepairManager.getEstimatedRemainingTasks{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18627) Fix calculation of pending compactions in pending repair manager
[
https://issues.apache.org/jira/browse/CASSANDRA-18627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-18627:
--
Status: Open (was: Patch Available)
> Fix calculation of pending compactions in pending repair manager
>
>
> Key: CASSANDRA-18627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18627
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Local/Compaction
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 5.x
>
>
> In CASSANDRA-17931, we failed to correctly take into account the
> additionalSSTables and additionalBytes passed in in one of our calls to
> {code}PendingRepairManager.getEstimatedRemainingTasks{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18627) Fix calculation of pending compactions in pending repair manager
[
https://issues.apache.org/jira/browse/CASSANDRA-18627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737310#comment-17737310
]
Josh McKenzie commented on CASSANDRA-18627:
---
||Item|Link||
|PR|[link|https://github.com/apache/cassandra/pull/2450]|
|JDK8
CI|[link|https://app.circleci.com/pipelines/github/jmckenzie-dev/cassandra/337/workflows/4a26c29b-dca6-4b14-bc7c-8b7c9977a977]|
|JDK11
CI|[link|https://app.circleci.com/pipelines/github/jmckenzie-dev/cassandra/337/workflows/2eb8052f-4f63-4099-a96c-e19fafe6634b]|
> Fix calculation of pending compactions in pending repair manager
>
>
> Key: CASSANDRA-18627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18627
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Local/Compaction
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
>
> In CASSANDRA-17931, we failed to correctly take into account the
> additionalSSTables and additionalBytes passed in in one of our calls to
> {code}PendingRepairManager.getEstimatedRemainingTasks{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18627) Fix calculation of pending compactions in pending repair manager
[
https://issues.apache.org/jira/browse/CASSANDRA-18627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-18627:
--
Bug Category: Parent values: Degradation(12984)
Complexity: Low Hanging Fruit
Discovered By: User Report
Fix Version/s: 5.x
Severity: Normal
Status: Open (was: Triage Needed)
> Fix calculation of pending compactions in pending repair manager
>
>
> Key: CASSANDRA-18627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18627
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Local/Compaction
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 5.x
>
>
> In CASSANDRA-17931, we failed to correctly take into account the
> additionalSSTables and additionalBytes passed in in one of our calls to
> {code}PendingRepairManager.getEstimatedRemainingTasks{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18627) Fix calculation of pending compactions in pending repair manager
[
https://issues.apache.org/jira/browse/CASSANDRA-18627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-18627:
--
Test and Documentation Plan: No new testing; confirm existing tests pass.
Status: Patch Available (was: Open)
> Fix calculation of pending compactions in pending repair manager
>
>
> Key: CASSANDRA-18627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18627
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Local/Compaction
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 5.x
>
>
> In CASSANDRA-17931, we failed to correctly take into account the
> additionalSSTables and additionalBytes passed in in one of our calls to
> {code}PendingRepairManager.getEstimatedRemainingTasks{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (9776b5ea -> aebe6ae5)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 9776b5ea generate docs for 8efdf127 new aebe6ae5 generate docs for 8efdf127 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 (9776b5ea) \ N -- N -- N refs/heads/asf-staging (aebe6ae5) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: site-ui/build/ui-bundle.zip | Bin 4796900 -> 4796900 bytes 1 file changed, 0 insertions(+), 0 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18627) Fix calculation of pending compactions in pending repair manager
Josh McKenzie created CASSANDRA-18627:
-
Summary: Fix calculation of pending compactions in pending repair
manager
Key: CASSANDRA-18627
URL: https://issues.apache.org/jira/browse/CASSANDRA-18627
Project: Cassandra
Issue Type: Bug
Components: Consistency/Repair, Local/Compaction
Reporter: Josh McKenzie
Assignee: Josh McKenzie
In CASSANDRA-17931, we failed to correctly take into account the
additionalSSTables and additionalBytes passed in in one of our calls to
{code}PendingRepairManager.getEstimatedRemainingTasks{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-59) Expose JMX host and port from JMXClient
[ https://issues.apache.org/jira/browse/CASSANDRASC-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737306#comment-17737306 ] Yifan Cai commented on CASSANDRASC-59: -- +1 on the patch > Expose JMX host and port from JMXClient > --- > > Key: CASSANDRASC-59 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-59 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > Many integrations require the JMX host and port configured for a given JMX > client. It is desired that this information is available in the > ICassandraDelegate. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18615) CREATE INDEX Modifications for Initial Release of SAI
[
https://issues.apache.org/jira/browse/CASSANDRA-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737270#comment-17737270
]
Caleb Rackliffe edited comment on CASSANDRA-18615 at 6/26/23 4:59 PM:
--
SASI is already experimental, and the release SAI should allow us to deprecate
it, then eventually remove it (although I would say after 5.0). Existing SASI
tests that use {{CREATE CUSTOM INDEX}} haven't been touched of course, but we
do not need to support or document it around the changes in this patch.
(See {{sasi_indexes_enabled: false}} in {{cassandra.yaml}}. For an already
experimental feature disabled by default, there shouldn't be an issue going
directly to removing SASI in the next major release after 5.0...)
was (Author: maedhroz):
SASI is already experimental, and the release SAI should allow us to deprecate
it, then eventually remove it (although I would say after 5.0). Existing SASI
tests that use {{CREATE CUSTOM INDEX}} haven't been touched of course, but we
do not need to support or document it around the changes in this patch.
> CREATE INDEX Modifications for Initial Release of SAI
> -
>
> Key: CASSANDRA-18615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18615
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax, Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: NA
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> After a lengthy discussion on the dev list, the community seems to have
> arrived at the following list of TODOs before we release SAI in 5.0:
> 1.) CREATE INDEX should be expanded to support {{USING … WITH OPTIONS…}}
> Essentially, we should be able to do something like {{CREATE INDEX ON tbl(v)
> USING ’sai’ WITH OPTIONS = ...}} and {{CREATE INDEX ON tbl(v) USING
> ‘cassandra’}} as a more specific/complete way to emulate the current behavior
> of {{CREATE INDEX}}.
> 2.) Allow operators to configure, in the YAML, a.) whether an index
> implementation must be specified w/ USING and {{CREATE INDEX}} and b.) what
> the default implementation will be, if {{USING}} isn’t required.
> 3.) The defaults we ship w/ will avoid breaking existing {{CREATE INDEX}}
> usage. (i.e. A default is allowed, and that default will remain ‘cassandra’,
> or the legacy 2i)
> With all this in place, users should be able create SAI indexes w/ the
> simplest possible syntax, no defaults will change, and operators will have
> the ability to change defaults to favor SAI whenever they like.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18615) CREATE INDEX Modifications for Initial Release of SAI
[
https://issues.apache.org/jira/browse/CASSANDRA-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737270#comment-17737270
]
Caleb Rackliffe edited comment on CASSANDRA-18615 at 6/26/23 4:56 PM:
--
SASI is already experimental, and the release SAI should allow us to deprecate
it, then eventually remove it (although I would say after 5.0). Existing SASI
tests that use {{CREATE CUSTOM INDEX}} haven't been touched of course, but we
do not need to support or document it around the changes in this patch.
was (Author: maedhroz):
SASI is already experimental, and the release SAI should allow us to deprecate
it, then eventually remove it. Existing SASI tests that use {{CREATE CUSTOM
INDEX}} haven't been touched of course, but we do not need to support or
document it around the changes in this patch.
> CREATE INDEX Modifications for Initial Release of SAI
> -
>
> Key: CASSANDRA-18615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18615
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax, Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: NA
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> After a lengthy discussion on the dev list, the community seems to have
> arrived at the following list of TODOs before we release SAI in 5.0:
> 1.) CREATE INDEX should be expanded to support {{USING … WITH OPTIONS…}}
> Essentially, we should be able to do something like {{CREATE INDEX ON tbl(v)
> USING ’sai’ WITH OPTIONS = ...}} and {{CREATE INDEX ON tbl(v) USING
> ‘cassandra’}} as a more specific/complete way to emulate the current behavior
> of {{CREATE INDEX}}.
> 2.) Allow operators to configure, in the YAML, a.) whether an index
> implementation must be specified w/ USING and {{CREATE INDEX}} and b.) what
> the default implementation will be, if {{USING}} isn’t required.
> 3.) The defaults we ship w/ will avoid breaking existing {{CREATE INDEX}}
> usage. (i.e. A default is allowed, and that default will remain ‘cassandra’,
> or the legacy 2i)
> With all this in place, users should be able create SAI indexes w/ the
> simplest possible syntax, no defaults will change, and operators will have
> the ability to change defaults to favor SAI whenever they like.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18615) CREATE INDEX Modifications for Initial Release of SAI
[
https://issues.apache.org/jira/browse/CASSANDRA-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737270#comment-17737270
]
Caleb Rackliffe commented on CASSANDRA-18615:
-
SASI is already experimental, and the release SAI should allow us to deprecate
it, then eventually remove it. Existing SASI tests that use {{CREATE CUSTOM
INDEX}} haven't been touched of course, but we do not need to support or
document it around the changes in this patch.
> CREATE INDEX Modifications for Initial Release of SAI
> -
>
> Key: CASSANDRA-18615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18615
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax, Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: NA
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> After a lengthy discussion on the dev list, the community seems to have
> arrived at the following list of TODOs before we release SAI in 5.0:
> 1.) CREATE INDEX should be expanded to support {{USING … WITH OPTIONS…}}
> Essentially, we should be able to do something like {{CREATE INDEX ON tbl(v)
> USING ’sai’ WITH OPTIONS = ...}} and {{CREATE INDEX ON tbl(v) USING
> ‘cassandra’}} as a more specific/complete way to emulate the current behavior
> of {{CREATE INDEX}}.
> 2.) Allow operators to configure, in the YAML, a.) whether an index
> implementation must be specified w/ USING and {{CREATE INDEX}} and b.) what
> the default implementation will be, if {{USING}} isn’t required.
> 3.) The defaults we ship w/ will avoid breaking existing {{CREATE INDEX}}
> usage. (i.e. A default is allowed, and that default will remain ‘cassandra’,
> or the legacy 2i)
> With all this in place, users should be able create SAI indexes w/ the
> simplest possible syntax, no defaults will change, and operators will have
> the ability to change defaults to favor SAI whenever they like.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18600) [Analytics] Add NOTICE.txt in Cassandra Analytics
[
https://issues.apache.org/jira/browse/CASSANDRA-18600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737262#comment-17737262
]
Dinesh Joshi commented on CASSANDRA-18600:
--
[~bereng] what's the error that you're getting? There aren't any special
permissions for this repo. Can you ping me on ASF slack and we can look at it
together?
> [Analytics] Add NOTICE.txt in Cassandra Analytics
> --
>
> Key: CASSANDRA-18600
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18600
> Project: Cassandra
> Issue Type: Task
> Components: Analytics Library
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Cassandra Analytics project is missing the {{NOTICE.txt}} file required
> for compliance with the ASF guidance
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18591) assertion failure when reading after writes and column drop are executed in parallel
[
https://issues.apache.org/jira/browse/CASSANDRA-18591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737239#comment-17737239
]
Jakub Zytka commented on CASSANDRA-18591:
-
Reproduction test is on branch:
[https://github.com/jakubzytka/cassandra/pull/new/CASSANDRA-15589-repro]
Reproduction:
{{ant test-jvm-dtest-some
-Dtest.name=org.apache.cassandra.distributed.test.DropColumnAndReadsTest
-Dno-checkstyle=1}}
Example failure:
{code:java}
[junit-timeout] Testcase:
testReadsAfterSimpleColumnDrop[0](org.apache.cassandra.distributed.test.DropColumnAndReadsTest)-.jdk11:
Caused an ERROR
[junit-timeout] Cassandra failure during read query at consistency LOCAL_ONE (1
responses were required but only 0 replica responded, 1 failed)
[junit-timeout] com.datastax.driver.core.exceptions.ReadFailureException:
Cassandra failure during read query at consistency LOCAL_ONE (1 responses were
required but only 0 replica responded, 1 failed)
[junit-timeout] at
com.datastax.driver.core.exceptions.ReadFailureException.copy(ReadFailureException.java:180)
[junit-timeout] at
com.datastax.driver.core.exceptions.ReadFailureException.copy(ReadFailureException.java:30)
[junit-timeout] at
com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:35)
[junit-timeout] at
com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:293)
[junit-timeout] at
com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:58)
[junit-timeout] at
org.apache.cassandra.distributed.test.DropColumnAndReadsTest.testReadsAfterSimpleColumnDrop(DropColumnAndReadsTest.java:251)
[junit-timeout] at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit-timeout] at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[junit-timeout] at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[junit-timeout] Suppressed:
org.apache.cassandra.distributed.shared.ShutdownException: Uncaught exceptions
were thrown during test
[junit-timeout] at
org.apache.cassandra.distributed.impl.AbstractCluster.checkAndResetUncaughtExceptions(AbstractCluster.java:1078)
[junit-timeout] at
org.apache.cassandra.distributed.impl.AbstractCluster.close(AbstractCluster.java:1064)
[junit-timeout] at
org.apache.cassandra.distributed.test.DropColumnAndReadsTest.testReadsAfterSimpleColumnDrop(DropColumnAndReadsTest.java:167)
[junit-timeout] Suppressed: java.lang.AssertionError: droppedcolumn
[junit-timeout] at
org.apache.cassandra.db.rows.UnfilteredSerializer.lambda$serializeRowBody$0(UnfilteredSerializer.java:245)
[junit-timeout] at
org.apache.cassandra.utils.btree.BTree.applyValue(BTree.java:1762)
[junit-timeout] at
org.apache.cassandra.utils.btree.BTree.applyLeaf(BTree.java:1770)
[junit-timeout] at
org.apache.cassandra.utils.btree.BTree.apply(BTree.java:1785)
[junit-timeout] at
org.apache.cassandra.utils.btree.BTree.apply(BTree.java:1811)
[junit-timeout] at
org.apache.cassandra.db.rows.BTreeRow.apply(BTreeRow.java:199)
[junit-timeout] at
org.apache.cassandra.db.rows.UnfilteredSerializer.serializeRowBody(UnfilteredSerializer.java:238)
[junit-timeout] at
org.apache.cassandra.db.rows.UnfilteredSerializer.serialize(UnfilteredSerializer.java:206)
[junit-timeout] at
org.apache.cassandra.db.rows.UnfilteredSerializer.serialize(UnfilteredSerializer.java:138)
[junit-timeout] at
org.apache.cassandra.db.rows.UnfilteredSerializer.serialize(UnfilteredSerializer.java:126)
[junit-timeout] at
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:152)
[junit-timeout] at
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:101)
[junit-timeout] at
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:86)
[junit-timeout] at
org.apache.cassandra.db.partitions.UnfilteredPartitionIterators$Serializer.serialize(UnfilteredPartitionIterators.java:308)
[junit-timeout] at
org.apache.cassandra.db.ReadResponse$LocalDataResponse.build(ReadResponse.java:201)
[junit-timeout] at
org.apache.cassandra.db.ReadResponse$LocalDataResponse.(ReadResponse.java:186)
[junit-timeout] at
org.apache.cassandra.db.ReadResponse.createDataResponse(ReadResponse.java:48)
[junit-timeout] at
org.apache.cassandra.db.ReadCommand.createResponse(ReadCommand.java:341)
[junit-timeout] at
org.apache.cassandra.service.StorageProxy$LocalReadRunnable.runMayThrow(StorageProxy.java:2186)
[cassandra-website] branch asf-staging updated (19989b0c -> 9776b5ea)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 19989b0c generate docs for 8efdf127 new 9776b5ea generate docs for 8efdf127 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 (19989b0c) \ N -- N -- N refs/heads/asf-staging (9776b5ea) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4796900 -> 4796900 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18589) NPE during reads after complex column drop
[
https://issues.apache.org/jira/browse/CASSANDRA-18589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737236#comment-17737236
]
Jakub Zytka commented on CASSANDRA-18589:
-
Reproduction test is on branch:
[https://github.com/jakubzytka/cassandra/pull/new/CASSANDRA-15589-repro]
Reproduction:
{{ant test-jvm-dtest-some
-Dtest.name=org.apache.cassandra.distributed.test.DropColumnAndReadsTest
-Dno-checkstyle=1}}
Example failure:
{code:java}
[junit-timeout] Testcase:
testReadsAfterComplexColumnDrop[0](org.apache.cassandra.distributed.test.DropColumnAndReadsTest)-.jdk11:
Caused an ERROR
[junit-timeout] Cassandra failure during read query at consistency LOCAL_ONE (1
responses were required but only 0 replica responded, 1 failed)
[junit-timeout] com.datastax.driver.core.exceptions.ReadFailureException:
Cassandra failure during read query at consistency LOCAL_ONE (1 responses were
required but only 0 replica responded, 1 failed)
[junit-timeout] at
com.datastax.driver.core.exceptions.ReadFailureException.copy(ReadFailureException.java:180)
[junit-timeout] at
com.datastax.driver.core.exceptions.ReadFailureException.copy(ReadFailureException.java:30)
[junit-timeout] at
com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:35)
[junit-timeout] at
com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:293)
[junit-timeout] at
com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:58)
[junit-timeout] at
org.apache.cassandra.distributed.test.DropColumnAndReadsTest.testReadsAfterComplexColumnDrop(DropColumnAndReadsTest.java:159)
[junit-timeout] at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit-timeout] at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[junit-timeout] at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[junit-timeout] Suppressed:
org.apache.cassandra.distributed.shared.ShutdownException: Uncaught exceptions
were thrown during test
[junit-timeout] at
org.apache.cassandra.distributed.impl.AbstractCluster.checkAndResetUncaughtExceptions(AbstractCluster.java:1078)
[junit-timeout] at
org.apache.cassandra.distributed.impl.AbstractCluster.close(AbstractCluster.java:1064)
[junit-timeout] at
org.apache.cassandra.distributed.test.DropColumnAndReadsTest.testReadsAfterComplexColumnDrop(DropColumnAndReadsTest.java:75)
[junit-timeout] Suppressed: java.lang.RuntimeException:
java.lang.NullPointerException
[junit-timeout] at
org.apache.cassandra.service.StorageProxy$DroppableRunnable.run(StorageProxy.java:2585)
[junit-timeout] at
org.apache.cassandra.concurrent.ExecutionFailure$2.run(ExecutionFailure.java:163)
[junit-timeout] at
org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:143)
[junit-timeout] at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
[junit-timeout] at java.base/java.lang.Thread.run(Thread.java:829)
[junit-timeout] Caused by: java.lang.NullPointerException
[junit-timeout] at
org.apache.cassandra.db.rows.Row$Merger$ColumnDataReducer.getReduced(Row.java:854)
[junit-timeout] at
org.apache.cassandra.db.rows.Row$Merger$ColumnDataReducer.getReduced(Row.java:793)
[junit-timeout] at
org.apache.cassandra.utils.MergeIterator$ManyToOne.consume(MergeIterator.java:219)
[junit-timeout] at
org.apache.cassandra.utils.MergeIterator$ManyToOne.computeNext(MergeIterator.java:158)
[junit-timeout] at
org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
[junit-timeout] at
org.apache.cassandra.db.rows.Row$Merger.merge(Row.java:770)
[junit-timeout] at
org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator$MergeReducer.getReduced(UnfilteredRowIterators.java:588)
[junit-timeout] at
org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator$MergeReducer.getReduced(UnfilteredRowIterators.java:552)
[junit-timeout] at
org.apache.cassandra.utils.MergeIterator$ManyToOne.consume(MergeIterator.java:219)
[junit-timeout] at
org.apache.cassandra.utils.MergeIterator$ManyToOne.computeNext(MergeIterator.java:158)
[junit-timeout] at
org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
[junit-timeout] at
org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:534)
[junit-timeout] at
org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:402)
[jira] [Commented] (CASSANDRA-15241) Virtual table to expose current running queries
[
https://issues.apache.org/jira/browse/CASSANDRA-15241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737232#comment-17737232
]
Maxim Muzafarov commented on CASSANDRA-15241:
-
[~maedhroz] ,
Here are the changes (no merge conflicts occurred):
[https://github.com/apache/cassandra/pull/2438/files]
I have run and checked the CI results here:
[https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/2518/]
The butler results here to be sure that we are not introducing new flaky tests:
[https://butler.cassandra.apache.org/?#/ci/upstream/compare/Cassandra-4.1/cassandra-15241-4.1]
I have run the CircleCI, but I'm not able to run everything related to
pre-commit as my account plan is limited:
[https://app.circleci.com/pipelines/github/Mmuzaf/cassandra/238/workflows/5bd1dcb4-a080-464c-a44c-3b202b3c1f59/jobs/15303]
--
Can you help to run everything on CircleCI and review the PR?
I've preserved the commit author and message.
> 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: 5.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> 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.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18626) compaction_tombstone_warning_threshold and compaction_large_partition_warning_threshold cause deprecation warnings
[
https://issues.apache.org/jira/browse/CASSANDRA-18626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18626:
-
Bug Category: Parent values: Correctness(12982)
Complexity: Normal
Component/s: Feature/Guardrails
Discovered By: User Report
Fix Version/s: 5.x
Severity: Normal
Status: Open (was: Triage Needed)
> compaction_tombstone_warning_threshold and
> compaction_large_partition_warning_threshold cause deprecation warnings
> --
>
> Key: CASSANDRA-18626
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18626
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Guardrails
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 5.x
>
>
> If you start trunk without any changes you will see at startup:
> {noformat}
> WARN [main] 2023-06-26 15:59:36,613 YamlConfigurationLoader.java:426 -
> [compaction_tombstone_warning_threshold,
> compaction_large_partition_warning_threshold] parameters have been
> deprecated. They have new names and/or value format; For more information,
> please refer to NEWS.txt
> {noformat}
> We should give these the same treatment as CASSANDRA-18617, removing them
> from the default yaml to stop the warnings, but still accepting them with
> converters and @Replaces tags.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18626) compaction_tombstone_warning_threshold and compaction_large_partition_warning_threshold cause deprecation warnings
Brandon Williams created CASSANDRA-18626:
Summary: compaction_tombstone_warning_threshold and
compaction_large_partition_warning_threshold cause deprecation warnings
Key: CASSANDRA-18626
URL: https://issues.apache.org/jira/browse/CASSANDRA-18626
Project: Cassandra
Issue Type: Bug
Reporter: Brandon Williams
If you start trunk without any changes you will see at startup:
{noformat}
WARN [main] 2023-06-26 15:59:36,613 YamlConfigurationLoader.java:426 -
[compaction_tombstone_warning_threshold,
compaction_large_partition_warning_threshold] parameters have been deprecated.
They have new names and/or value format; For more information, please refer to
NEWS.txt
{noformat}
We should give these the same treatment as CASSANDRA-18617, removing them from
the default yaml to stop the warnings, but still accepting them with converters
and @Replaces tags.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18570) Fix org.apache.cassandra.transport.DriverBurnTest.measureLargeV4WithCompression-.jdk17
[
https://issues.apache.org/jira/browse/CASSANDRA-18570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737188#comment-17737188
]
Brandon Williams commented on CASSANDRA-18570:
--
We did some archaeology here and discovered that this test has been flaky since
j17 was added, so it is likely just pushing jenkins over the top sometimes.
> Fix
> org.apache.cassandra.transport.DriverBurnTest.measureLargeV4WithCompression-.jdk17
>
> ---
>
> Key: CASSANDRA-18570
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18570
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ningzi Zhan
>Priority: Normal
> Fix For: 5.x
>
>
> h1.
> {code:java}
> Regression
> org.apache.cassandra.transport.DriverBurnTest.measureLargeV4WithCompression-.jdk17
> (from org.apache.cassandra.transport.DriverBurnTest-.jdk17)
> Failing for the past 1 build (Since #1590 ) Took 30 sec. Failed 5 times
> in the last 30 runs. Flakiness: 24%, Stability: 83% Stacktrace
> junit.framework.AssertionFailedError at
> org.apache.cassandra.transport.DriverBurnTest.perfTest(DriverBurnTest.java:425)
> at
> org.apache.cassandra.transport.DriverBurnTest.measureLargeV4WithCompression(DriverBurnTest.java:316)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> {code}
> The test is flaky since recently, failing every other time in Jenkins (burn
> tests are not running in CircleCI) First seen with run #1572 this commit -
> CASSANDRA-18025
> CC [~stefan.miklosovic] and [~brandon.williams]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18494) Upgrade lucene-core library to the latest stable version
[ https://issues.apache.org/jira/browse/CASSANDRA-18494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña updated CASSANDRA-18494: -- Change Category: Semantic Complexity: Normal Status: Open (was: Triage Needed) > Upgrade lucene-core library to the latest stable version > > > Key: CASSANDRA-18494 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18494 > Project: Cassandra > Issue Type: Task > Components: Feature/2i Index >Reporter: Mike Adamson >Assignee: Andres de la Peña >Priority: Normal > > The lucene-core library is currently at 7.5. This should be updated to > whatever the latest stable version of lucene is. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18494) Upgrade lucene-core library to the latest stable version
[ https://issues.apache.org/jira/browse/CASSANDRA-18494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña reassigned CASSANDRA-18494: - Assignee: Andres de la Peña > Upgrade lucene-core library to the latest stable version > > > Key: CASSANDRA-18494 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18494 > Project: Cassandra > Issue Type: Task > Components: Feature/2i Index >Reporter: Mike Adamson >Assignee: Andres de la Peña >Priority: Normal > > The lucene-core library is currently at 7.5. This should be updated to > whatever the latest stable version of lucene is. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18438) Refactor the code for public cloud platform snitch to be configurable
[ https://issues.apache.org/jira/browse/CASSANDRA-18438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737185#comment-17737185 ] Jacek Lewandowski commented on CASSANDRA-18438: --- [~xgerman42] wait for CASSANDRA-16555 to be merged (should be soon), then we can refactor all cloud snitches in this ticket in the same way as 16555 implements new EC2 snitch. > Refactor the code for public cloud platform snitch to be configurable > - > > Key: CASSANDRA-18438 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18438 > Project: Cassandra > Issue Type: Improvement > Components: Local/Other >Reporter: Maxwell Guo >Assignee: Maxwell Guo >Priority: Normal > Fix For: 5.x > > > Nowadays we have got about four public cloud platform snitchs ： EC2 snitch > for aws, google cloud snitch for google cloud, alibaba cloud snitch for > alibaba cloud and multi region snitch for ec2. And the common place for the > first three is that we just need to query the zone center to get the ec2 / > ecs id , so I think we can refactor the code , and if some new public cloud > platform want to add one more snitch for himself, there is no need to pull a > pr for him and configure some options in yaml is enough . > Besides it would be even better that we may reuse the multic region snitch > for ec2 for other public cloud platform. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18624) Make Corretto Crypto Provider the Default
[ https://issues.apache.org/jira/browse/CASSANDRA-18624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737178#comment-17737178 ] Jordan West commented on CASSANDRA-18624: - Added a graph that show the performance benefit of turning on ACCP in a recent benchmark we performed. The peak p99s were regularly above 200ms. After they are consistently around 100-130ms. > Make Corretto Crypto Provider the Default > - > > Key: CASSANDRA-18624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18624 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Jordan West >Assignee: Jordan West >Priority: Normal > Attachments: image.png > > > [Amazon Corretto Crypto Provider| > https://github.com/corretto/amazon-corretto-crypto-provider] is an > alternative provider of TLS and cryptographic functions that has significant > performance benefits for Cassandra. It is Apache 2.0 licensed and has been > deployed in several existing large fleets. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18624) Make Corretto Crypto Provider the Default
[ https://issues.apache.org/jira/browse/CASSANDRA-18624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan West updated CASSANDRA-18624: Attachment: image.png > Make Corretto Crypto Provider the Default > - > > Key: CASSANDRA-18624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18624 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Jordan West >Assignee: Jordan West >Priority: Normal > Attachments: image.png > > > [Amazon Corretto Crypto Provider| > https://github.com/corretto/amazon-corretto-crypto-provider] is an > alternative provider of TLS and cryptographic functions that has significant > performance benefits for Cassandra. It is Apache 2.0 licensed and has been > deployed in several existing large fleets. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18438) Refactor the code for public cloud platform snitch to be configurable
[ https://issues.apache.org/jira/browse/CASSANDRA-18438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737176#comment-17737176 ] German Eichberger commented on CASSANDRA-18438: --- Agree with [~smiklosovic] that we should code this in Java rather than come up with some endpoint/regex/etc. in yaml. That said I am watching this with interest so I can write an Azure snitch. > Refactor the code for public cloud platform snitch to be configurable > - > > Key: CASSANDRA-18438 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18438 > Project: Cassandra > Issue Type: Improvement > Components: Local/Other >Reporter: Maxwell Guo >Assignee: Maxwell Guo >Priority: Normal > Fix For: 5.x > > > Nowadays we have got about four public cloud platform snitchs ： EC2 snitch > for aws, google cloud snitch for google cloud, alibaba cloud snitch for > alibaba cloud and multi region snitch for ec2. And the common place for the > first three is that we just need to query the zone center to get the ec2 / > ecs id , so I think we can refactor the code , and if some new public cloud > platform want to add one more snitch for himself, there is no need to pull a > pr for him and configure some options in yaml is enough . > Besides it would be even better that we may reuse the multic region snitch > for ec2 for other public cloud platform. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18613) Add support for vectors on UDFs
[
https://issues.apache.org/jira/browse/CASSANDRA-18613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737138#comment-17737138
]
Maxwell Guo commented on CASSANDRA-18613:
-
LGTM
> Add support for vectors on UDFs
> ---
>
> Key: CASSANDRA-18613
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18613
> Project: Cassandra
> Issue Type: New Feature
> Components: Cluster/Schema
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> CASSANDRA-18504 will add a new vector type, but [it won't be supported on
> UDFs|https://github.com/apache/cassandra/blob/5027e688da006e5d5bf9bfdf4719caddbf85986a/test/unit/org/apache/cassandra/cql3/validation/operations/CQLVectorTest.java#L248-L271].
> The goal of this ticket is to add that support.
> This will require adding a new {{o.a.c.cql3.functions.types.TypeCodec}} for
> vectors. Those codecs are mostly duplicates of the codecs on the Java driver.
> They are used for UDFs instead of the regular {{AbstractType}} to prevent
> pulling too many internal dependencies. The driver's vector codec has
> recently been added by
> [JAVA-3060|https://datastax-oss.atlassian.net/browse/JAVA-3060].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18613) Add support for vectors on UDFs
[
https://issues.apache.org/jira/browse/CASSANDRA-18613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxwell Guo updated CASSANDRA-18613:
Status: Needs Committer (was: Review In Progress)
> Add support for vectors on UDFs
> ---
>
> Key: CASSANDRA-18613
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18613
> Project: Cassandra
> Issue Type: New Feature
> Components: Cluster/Schema
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> CASSANDRA-18504 will add a new vector type, but [it won't be supported on
> UDFs|https://github.com/apache/cassandra/blob/5027e688da006e5d5bf9bfdf4719caddbf85986a/test/unit/org/apache/cassandra/cql3/validation/operations/CQLVectorTest.java#L248-L271].
> The goal of this ticket is to add that support.
> This will require adding a new {{o.a.c.cql3.functions.types.TypeCodec}} for
> vectors. Those codecs are mostly duplicates of the codecs on the Java driver.
> They are used for UDFs instead of the regular {{AbstractType}} to prevent
> pulling too many internal dependencies. The driver's vector codec has
> recently been added by
> [JAVA-3060|https://datastax-oss.atlassian.net/browse/JAVA-3060].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18613) Add support for vectors on UDFs
[
https://issues.apache.org/jira/browse/CASSANDRA-18613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737138#comment-17737138
]
Maxwell Guo edited comment on CASSANDRA-18613 at 6/26/23 1:12 PM:
--
LGTM and CI are all green
was (Author: maxwellguo):
LGTM
> Add support for vectors on UDFs
> ---
>
> Key: CASSANDRA-18613
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18613
> Project: Cassandra
> Issue Type: New Feature
> Components: Cluster/Schema
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> CASSANDRA-18504 will add a new vector type, but [it won't be supported on
> UDFs|https://github.com/apache/cassandra/blob/5027e688da006e5d5bf9bfdf4719caddbf85986a/test/unit/org/apache/cassandra/cql3/validation/operations/CQLVectorTest.java#L248-L271].
> The goal of this ticket is to add that support.
> This will require adding a new {{o.a.c.cql3.functions.types.TypeCodec}} for
> vectors. Those codecs are mostly duplicates of the codecs on the Java driver.
> They are used for UDFs instead of the regular {{AbstractType}} to prevent
> pulling too many internal dependencies. The driver's vector codec has
> recently been added by
> [JAVA-3060|https://datastax-oss.atlassian.net/browse/JAVA-3060].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14204) Remove unrepaired SSTables from garbage collection when only_purge_repaired_tombstones is true to avoid AssertionError in nodetool garbagecollect
[
https://issues.apache.org/jira/browse/CASSANDRA-14204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737133#comment-17737133
]
Stefan Miklosovic commented on CASSANDRA-14204:
---
[~jjirsa] would you mind to take a look please? This should be quite
straightforward.
> Remove unrepaired SSTables from garbage collection when
> only_purge_repaired_tombstones is true to avoid AssertionError in nodetool
> garbagecollect
> -
>
> Key: CASSANDRA-14204
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14204
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
>Reporter: Vincent White
>Assignee: Stefan Miklosovic
>Priority: Low
> Fix For: 3.11.x, 4.0.x, 4.1.x, 5.x
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When manually running a garbage collection compaction across a table with
> unrepaired sstables and only_purge_repaired_tombstones set to true an
> assertion error is thrown. This is because the unrepaired sstables aren't
> being removed from the transaction as they are filtered out in
> filterSSTables().
> ||3.11||trunk||
> |[branch|https://github.com/vincewhite/cassandra/commit/e13c822736edd3df3403c02e8ef90816f158cde2]|[branch|https://github.com/vincewhite/cassandra/commit/cc8828576404e72504d9b334be85f84c90e77aa7]|
> The stacktrace:
> {noformat}
> -- StackTrace --
> java.lang.AssertionError
> at
> org.apache.cassandra.db.compaction.CompactionManager.parallelAllSSTableOperation(CompactionManager.java:339)
> at
> org.apache.cassandra.db.compaction.CompactionManager.performGarbageCollection(CompactionManager.java:476)
> at
> org.apache.cassandra.db.ColumnFamilyStore.garbageCollect(ColumnFamilyStore.java:1579)
> at
> org.apache.cassandra.service.StorageService.garbageCollect(StorageService.java:3069)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)
> at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
> at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
> at
> com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> at
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> at
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
> at
> javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
> at
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
> at
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
> at
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> at
>
[jira] [Updated] (CASSANDRA-12183) compaction_history system table does not capture all historical compaction sessions
[
https://issues.apache.org/jira/browse/CASSANDRA-12183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-12183:
--
Fix Version/s: 3.0.30
3.11.16
4.0.11
4.1.3
5.0
(was: 5.x)
Since Version: 3.0.0
Source Control Link:
https://github.com/apache/cassandra/commit/a00d1de4414bb5ab57a27cb463af0e33af6e36c8
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> compaction_history system table does not capture all historical compaction
> sessions
> ---
>
> Key: CASSANDRA-12183
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12183
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability, Local/Compaction
>Reporter: Wei Deng
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 3.0.30, 3.11.16, 4.0.11, 4.1.3, 5.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> It appears that some compaction sessions are not recorded in
> system.compaction_history table after the compaction session successfully
> finishes.
> The following is an example (test by simply running +cassandra-stress write
> n=1+):
> {noformat}
> automaton@wdengdse50google-98425b985-3:~$ nodetool compactionstats
> pending tasks: 46
> id compaction typekeyspace
> tablecompletedtotalunit progress
>fa8a4f30-4884-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1 4233184044 4774209875 bytes 88.67%
>91e30d21-4887-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1836983029889773060 bytes 94.07%
> Active compaction remaining time : 0h00m35s
> automaton@wdengdse50google-98425b985-3:~$ nodetool compactionstats
> pending tasks: 47
> id compaction typekeyspace
> tablecompletedtotalunit progress
>fa8a4f30-4884-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1 4353251539 4774209875 bytes 91.18%
>28359094-4888-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1 49732274 4071652280 bytes 1.22%
> Active compaction remaining time : 0h04m24s
> {noformat}
> At this point you know the previous compaction session
> 91e30d21-4887-11e6-b916-1dbd340a212f finished and confirmation can be found
> from debug.log
> {noformat}
> automaton@wdengdse50google-98425b985-3:~$ grep
> 91e30d21-4887-11e6-b916-1dbd340a212f /var/log/cassandra/debug.log
> DEBUG [CompactionExecutor:4] 2016-07-12 23:22:58,674 CompactionTask.java:146
> - Compacting (91e30d21-4887-11e6-b916-1dbd340a212f)
> [/var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-290-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-279-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-281-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-280-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-284-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-283-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-287-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-292-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-286-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-289-big-Data.db:level=0,
> ]
> DEBUG [CompactionExecutor:4] 2016-07-12 23:26:56,054 CompactionTask.java:217
> - Compacted (91e30d21-4887-11e6-b916-1dbd340a212f) 10 sstables to
> [/var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-293-big,]
> to level=0. 889,773,060 bytes to 890,473,350 (~100% of original) in
> 237,365ms = 3.577703MB/s. 0 total partitions merged to 3,871,921. Partition
> merge counts were {1:3871921, }
> {noformat}
> However, if you query system.compaction_history table or run "nodetool
> compactionhistory | grep 91e30d21-4887-11e6-b916-1dbd340a212f" you will get
> nothing:
> {noformat}
> automaton@wdengdse50google-98425b985-3:~$ cqlsh -u cassandra
> Password:
> Connected to dse50 at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 3.0.7.1158 | DSE 5.0.0 | CQL spec 3.4.0 | Native
> protocol v4]
> Use HELP for
[cassandra] branch cassandra-4.0 updated (776b33753b -> 04fd3747cf)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 776b33753b Upgrade snappy to 1.1.10.1 add a00d1de441 Pass taskId from CompactionTask to system.compaction_history add 55dc5b43f1 Merge branch 'cassandra-3.0' into cassandra-3.11 add 04fd3747cf Merge branch 'cassandra-3.11' into cassandra-4.0 No new revisions were added by this update. Summary of changes: CHANGES.txt | 1 + src/java/org/apache/cassandra/db/SystemKeyspace.java | 5 +++-- .../org/apache/cassandra/db/compaction/CompactionTask.java| 11 +++ 3 files changed, 11 insertions(+), 6 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.1 updated (41e62e6147 -> 0dd69ab854)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 41e62e6147 Merge branch 'cassandra-4.0' into cassandra-4.1 add a00d1de441 Pass taskId from CompactionTask to system.compaction_history add 55dc5b43f1 Merge branch 'cassandra-3.0' into cassandra-3.11 add 04fd3747cf Merge branch 'cassandra-3.11' into cassandra-4.0 add 0dd69ab854 Merge branch 'cassandra-4.0' into cassandra-4.1 No new revisions were added by this update. Summary of changes: CHANGES.txt| 1 + .../org/apache/cassandra/db/SystemKeyspace.java| 6 ++-- .../cassandra/db/compaction/CompactionTask.java| 6 ++-- .../db/compaction/CompactionTaskTest.java | 37 ++ 4 files changed, 44 insertions(+), 6 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-3.0 updated (d99bccd649 -> a00d1de441)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-3.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from d99bccd649 Suppress CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 add a00d1de441 Pass taskId from CompactionTask to system.compaction_history No new revisions were added by this update. Summary of changes: CHANGES.txt | 1 + src/java/org/apache/cassandra/db/SystemKeyspace.java | 5 +++-- .../org/apache/cassandra/db/compaction/CompactionTask.java | 12 +++- 3 files changed, 11 insertions(+), 7 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-3.11 updated (b15a7da208 -> 55dc5b43f1)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git from b15a7da208 Merge branch 'cassandra-3.0' into cassandra-3.11 add a00d1de441 Pass taskId from CompactionTask to system.compaction_history add 55dc5b43f1 Merge branch 'cassandra-3.0' into cassandra-3.11 No new revisions were added by this update. Summary of changes: CHANGES.txt | 1 + src/java/org/apache/cassandra/db/SystemKeyspace.java | 5 +++-- .../org/apache/cassandra/db/compaction/CompactionTask.java| 11 +++ 3 files changed, 11 insertions(+), 6 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (81026b95c4 -> eda0bcbefa)
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 81026b95c4 Merge branch 'cassandra-4.1' into trunk add a00d1de441 Pass taskId from CompactionTask to system.compaction_history add 55dc5b43f1 Merge branch 'cassandra-3.0' into cassandra-3.11 add 04fd3747cf Merge branch 'cassandra-3.11' into cassandra-4.0 add 0dd69ab854 Merge branch 'cassandra-4.0' into cassandra-4.1 new eda0bcbefa Merge branch 'cassandra-4.1' into trunk The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt| 1 + .../org/apache/cassandra/db/SystemKeyspace.java| 6 ++-- .../cassandra/db/compaction/CompactionTask.java| 6 ++-- .../db/compaction/CompactionTaskTest.java | 37 ++ 4 files changed, 44 insertions(+), 6 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.1' into trunk
This is an automated email from the ASF dual-hosted git repository.
smiklosovic pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit eda0bcbefaf38e4069ac6db3a00937d778090083
Merge: 81026b95c4 0dd69ab854
Author: Stefan Miklosovic
AuthorDate: Mon Jun 26 14:15:45 2023 +0200
Merge branch 'cassandra-4.1' into trunk
CHANGES.txt| 1 +
.../org/apache/cassandra/db/SystemKeyspace.java| 6 ++--
.../cassandra/db/compaction/CompactionTask.java| 6 ++--
.../db/compaction/CompactionTaskTest.java | 37 ++
4 files changed, 44 insertions(+), 6 deletions(-)
diff --cc src/java/org/apache/cassandra/db/SystemKeyspace.java
index 3c8690d657,a5baecefd4..5d81a151ab
--- a/src/java/org/apache/cassandra/db/SystemKeyspace.java
+++ b/src/java/org/apache/cassandra/db/SystemKeyspace.java
@@@ -614,9 -620,9 +614,9 @@@ public final class SystemKeyspac
// don't write anything when the history table itself is compacted,
since that would in turn cause new compactions
if (ksname.equals("system") && cfname.equals(COMPACTION_HISTORY))
return;
-String req = "INSERT INTO system.%s (id, keyspace_name,
columnfamily_name, compacted_at, bytes_in, bytes_out, rows_merged) VALUES (?,
?, ?, ?, ?, ?, ?)";
+String req = "INSERT INTO system.%s (id, keyspace_name,
columnfamily_name, compacted_at, bytes_in, bytes_out, rows_merged,
compaction_properties) VALUES (?, ?, ?, ?, ?, ?, ?, ?)";
executeInternal(format(req, COMPACTION_HISTORY),
- nextTimeUUID(),
+ taskId,
ksname,
cfname,
ByteBufferUtil.bytes(compactedAt),
diff --cc src/java/org/apache/cassandra/db/compaction/CompactionTask.java
index ed240c10ad,82139ced51..1f28ee07f2
--- a/src/java/org/apache/cassandra/db/compaction/CompactionTask.java
+++ b/src/java/org/apache/cassandra/db/compaction/CompactionTask.java
@@@ -252,8 -248,7 +252,8 @@@ public class CompactionTask extends Abs
for (int i = 0; i < mergedRowCounts.length; i++)
totalSourceRows += mergedRowCounts[i] * (i + 1);
- String mergeSummary =
updateCompactionHistory(cfs.keyspace.getName(), cfs.getTableName(),
mergedRowCounts, startsize, endsize,
-String mergeSummary = updateCompactionHistory(taskId,
cfs.keyspace.getName(), cfs.getTableName(), mergedRowCounts, startsize,
endsize);
++String mergeSummary = updateCompactionHistory(taskId,
cfs.keyspace.getName(), cfs.getTableName(), mergedRowCounts, startsize, endsize,
+
ImmutableMap.of(COMPACTION_TYPE_PROPERTY, compactionType.type));
logger.info(String.format("Compacted (%s) %d sstables to [%s] to
level=%d. %s to %s (~%d%% of original) in %,dms. Read Throughput = %s, Write
Throughput = %s, Row Throughput = ~%,d/s. %,d total partitions merged to %,d.
Partition merge counts were {%s}. Time spent writing keys = %,dms",
taskId,
@@@ -292,7 -287,7 +292,7 @@@
return new DefaultCompactionWriter(cfs, directories, transaction,
nonExpiredSSTables, keepOriginals, getLevel());
}
- public static String updateCompactionHistory(String keyspaceName, String
columnFamilyName, long[] mergedRowCounts, long startSize, long endSize,
Map compactionProperties)
-public static String updateCompactionHistory(TimeUUID taskId, String
keyspaceName, String columnFamilyName, long[] mergedRowCounts, long startSize,
long endSize)
++public static String updateCompactionHistory(TimeUUID taskId, String
keyspaceName, String columnFamilyName, long[] mergedRowCounts, long startSize,
long endSize, Map compactionProperties)
{
StringBuilder mergeSummary = new StringBuilder(mergedRowCounts.length
* 10);
Map mergedRows = new HashMap<>();
@@@ -306,7 -301,7 +306,7 @@@
mergeSummary.append(String.format("%d:%d, ", rows, count));
mergedRows.put(rows, count);
}
- SystemKeyspace.updateCompactionHistory(keyspaceName,
columnFamilyName, currentTimeMillis(), startSize, endSize, mergedRows,
compactionProperties);
-SystemKeyspace.updateCompactionHistory(taskId, keyspaceName,
columnFamilyName, currentTimeMillis(), startSize, endSize, mergedRows);
++SystemKeyspace.updateCompactionHistory(taskId, keyspaceName,
columnFamilyName, currentTimeMillis(), startSize, endSize, mergedRows,
compactionProperties);
return mergeSummary.toString();
}
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18608) snappy-java vulnerability: CVE-2023-34455, CVE-2023-34454, CVE-2023-34453
[
https://issues.apache.org/jira/browse/CASSANDRA-18608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18608:
-
Fix Version/s: 3.0.30
3.11.16
4.0.11
4.1.3
5.0
(was: 3.0.x)
(was: 3.11.x)
(was: 5.x)
(was: 4.0.x)
(was: 4.1.x)
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra/commit/d99bccd6493ceb7aed4e05b05f81913ea876d855
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed suppressions to 3.11 and 3.0, upgraded snappy to 1.1.10.1 in higher
branches. Thanks!
> snappy-java vulnerability: CVE-2023-34455, CVE-2023-34454, CVE-2023-34453
> -
>
> Key: CASSANDRA-18608
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18608
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Compression
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.30, 3.11.16, 4.0.11, 4.1.3, 5.0
>
>
> Failing owasp:
> [https://nvd.nist.gov/vuln/detail/CVE-2023-34455]
> {quote}Due to use of an unchecked chunk length, an unrecoverable fatal error
> can occur in versions prior to 1.1.10.1.
> {quote}
> [https://nvd.nist.gov/vuln/detail/CVE-2023-34454]
> {quote}Due to unchecked multiplications, an integer overflow may occur in
> versions prior to 1.1.10.1, causing an unrecoverable fatal error.
> {quote}
> [https://nvd.nist.gov/vuln/detail/CVE-2023-34453]
> {quote}Due to unchecked multiplications, an integer overflow may occur in
> versions prior to 1.1.10.1, causing a fatal error.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.0 updated (bc3700da05 -> 776b33753b)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from bc3700da05 Merge branch 'cassandra-3.11' into cassandra-4.0 new d99bccd649 Suppress CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 new b15a7da208 Merge branch 'cassandra-3.0' into cassandra-3.11 new 72b1949157 Merge branch 'cassandra-3.11' into cassandra-4.0 new 776b33753b Upgrade snappy to 1.1.10.1 The 4 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt | 1 + build.xml | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-3.0' into cassandra-3.11
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit b15a7da20863efb85ffa892b1d19891563cc44dd Merge: 254991750c d99bccd649 Author: Brandon Williams AuthorDate: Mon Jun 26 06:04:45 2023 -0500 Merge branch 'cassandra-3.0' into cassandra-3.11 .build/dependency-check-suppressions.xml | 7 +++ CHANGES.txt | 1 + 2 files changed, 8 insertions(+) diff --cc CHANGES.txt index f36257a8e1,43b4cc40fb..dc0d7e99af --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,9 -1,5 +1,10 @@@ -3.0.30 +3.11.16 + * Wait for live endpoints in gossip waiting to settle (CASSANDRA-18543) + * Fix error message handling when trying to use CLUSTERING ORDER with non-clustering column (CASSANDRA-17818 + * Add keyspace and table name to exception message during ColumnSubselection deserialization (CASSANDRA-18346) + * Remove unnecessary String.format invocation in QueryProcessor when getting a prepared statement from cache (CASSANDRA-17202) +Merged from 3.0: + * Suppress CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 (CASSANDRA-18608) * Backport CASSANDRA-10508: Remove hard-coded SSL cipher suites (CASSANDRA-18575) * Suppress CVE-2023-2976 (CASSANDRA-18562) * Remove dh_python use in Debian packaging (CASSANDRA-18558) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.1 updated (f7b952387a -> 41e62e6147)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from f7b952387a Move checkstyle files into .build new d99bccd649 Suppress CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 new b15a7da208 Merge branch 'cassandra-3.0' into cassandra-3.11 new 72b1949157 Merge branch 'cassandra-3.11' into cassandra-4.0 new 776b33753b Upgrade snappy to 1.1.10.1 new 41e62e6147 Merge branch 'cassandra-4.0' into cassandra-4.1 The 5 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt | 1 + build.xml | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (9026f96234 -> 81026b95c4)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 9026f96234 Merge branch 'cassandra-4.1' into trunk new d99bccd649 Suppress CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 new b15a7da208 Merge branch 'cassandra-3.0' into cassandra-3.11 new 72b1949157 Merge branch 'cassandra-3.11' into cassandra-4.0 new 776b33753b Upgrade snappy to 1.1.10.1 new 41e62e6147 Merge branch 'cassandra-4.0' into cassandra-4.1 new 81026b95c4 Merge branch 'cassandra-4.1' into trunk The 6 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .build/parent-pom-template.xml | 2 +- CHANGES.txt| 1 + 2 files changed, 2 insertions(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.0' into cassandra-4.1
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 41e62e6147da74d2b523106c3aef48c7c4e6d837 Merge: f7b952387a 776b33753b Author: Brandon Williams AuthorDate: Mon Jun 26 06:07:53 2023 -0500 Merge branch 'cassandra-4.0' into cassandra-4.1 CHANGES.txt | 1 + build.xml | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --cc CHANGES.txt index 80bb3eafd0,43a33eb9e7..6d36de8c05 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,5 -1,5 +1,6 @@@ -4.0.11 +4.1.3 +Merged from 4.0: + * Upgrade snappy to 1.1.10.1 (CASSANDRA-18608) * Fix assertion error when describing mv as table (CASSANDRA-18596) * Track the amount of read data per row (CASSANDRA-18513) * Fix Down nodes counter in nodetool describecluster (CASSANDRA-18512) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.1' into trunk
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 81026b95c4bdeeffd9b2eb4469ed4e1bcec84536 Merge: 9026f96234 41e62e6147 Author: Brandon Williams AuthorDate: Mon Jun 26 06:09:54 2023 -0500 Merge branch 'cassandra-4.1' into trunk .build/parent-pom-template.xml | 2 +- CHANGES.txt| 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --cc .build/parent-pom-template.xml index e4b63bf3a8,00..9203d4ad89 mode 100644,00..100644 --- a/.build/parent-pom-template.xml +++ b/.build/parent-pom-template.xml @@@ -1,1052 -1,0 +1,1052 @@@ + + +http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; xmlns="http://maven.apache.org/POM/4.0.0; +xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;> + 4.0.0 + +apache +org.apache +22 + + org.apache.cassandra + cassandra-parent + @version@ + pom + Apache Cassandra + The Apache Cassandra Project develops a highly scalable second-generation distributed database, bringing together Dynamo's fully distributed design and Bigtable's ColumnFamily-based data model. + https://cassandra.apache.org + 2009 + + + The Apache Software License, Version 2.0 + https://www.apache.org/licenses/LICENSE-2.0.txt + + + +1.12.13 +4.0.20 +0.5.1 + + +@asm.version@ +@jamm.version@ + @allocation-instrumenter.version@ +@ecj.version@ +@jacoco.version@ +@jflex.version@ + + + + adelapena + Andres de la Peña + + + alakshman + Avinash Lakshman + + + aleksey + Aleksey Yeschenko + + + amorton + Aaron Morton + + + aweisberg + Ariel Weisberg + + + bdeggleston + Blake Eggleston + + + benedict + Benedict Elliott Smith + + + benjamin + Benjamin Lerer + + + blambov + Branimir Lambov + + + brandonwilliams + Brandon Williams + + + carl + Carl Yeksigian + + + dbrosius + David Brosiusd + + + dikang + Dikang Gu + + + eevans + Eric Evans + + + edimitrova + Ekaterina Dimitrova + + + gdusbabek + Gary Dusbabek + + + goffinet + Chris Goffinet + + + ifesdjeen + Alex Petrov + + + jaakko + Laine Jaakko Olavi + + + jake + T Jake Luciani + + + jasonbrown + Jason Brown + + + jbellis + Jonathan Ellis + + + jfarrell + Jake Farrell + + + jjirsa + Jeff Jirsa + + + jkni + Joel Knighton + + + jmckenzie + Josh McKenzie + + + johan + Johan Oskarsson + + + junrao + Jun Rao + + + jzhuang + Jay Zhuang + + + kohlisankalp + Sankalp Kohli + + + marcuse + Marcus Eriksson + + + mck + Michael Semb Wever + + + mishail + Mikhail Stepura + + + mshuler + Michael Shuler + + + paulo + Paulo Motta + + + pmalik + Prashant Malik + + + rstupp + Robert Stupp + + + scode + Peter Schuller + + + beobal + Sam Tunnicliffe + + + slebresne + Sylvain Lebresne + + + stefania + Stefania Alborghetti + + + tylerhobbs + Tyler Hobbs + + + vijay + Vijay Parthasarathy + + + xedin + Pavel Yaskevich + + + yukim + Yuki Morishita + + + zznate + Nate McCall + + + + scm:https://gitbox.apache.org/repos/asf/cassandra.git + scm:https://gitbox.apache.org/repos/asf/cassandra.git +https://gitbox.apache.org/repos/asf?p=cassandra.git;a=tree + + + + + +org.xerial.snappy +snappy-java - 1.1.8.4 ++1.1.10.1 + + +org.lz4 +lz4-java +1.8.0 + + +com.ning +compress-lzf +0.8.4 +provided + + +com.github.luben +zstd-jni +1.5.5-1 + + +com.google.guava +guava +27.0-jre + + +jsr305 +com.google.code.findbugs + + +animal-sniffer-annotations +org.codehaus.mojo + + +listenablefuture +
[cassandra] branch cassandra-3.11 updated (254991750c -> b15a7da208)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 254991750c Add missing changes new d99bccd649 Suppress CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 new b15a7da208 Merge branch 'cassandra-3.0' into cassandra-3.11 The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .build/dependency-check-suppressions.xml | 7 +++ CHANGES.txt | 1 + 2 files changed, 8 insertions(+) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/02: Merge branch 'cassandra-3.11' into cassandra-4.0
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 72b1949157ce15d0daaade27172633c08d6f5acc Merge: bc3700da05 b15a7da208 Author: Brandon Williams AuthorDate: Mon Jun 26 06:05:24 2023 -0500 Merge branch 'cassandra-3.11' into cassandra-4.0 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 02/02: Upgrade snappy to 1.1.10.1
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 776b33753b4779efc33a80acf3feb7da767c1bbf Author: Brandon Williams AuthorDate: Fri Jun 23 09:43:09 2023 -0500 Upgrade snappy to 1.1.10.1 Patch by brandonwilliams; reviewed by bereng for CASSANDRA-18608 --- CHANGES.txt | 1 + build.xml | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/CHANGES.txt b/CHANGES.txt index 1d76328e15..43a33eb9e7 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 4.0.11 + * Upgrade snappy to 1.1.10.1 (CASSANDRA-18608) * Fix assertion error when describing mv as table (CASSANDRA-18596) * Track the amount of read data per row (CASSANDRA-18513) * Fix Down nodes counter in nodetool describecluster (CASSANDRA-18512) diff --git a/build.xml b/build.xml index f50cb9bf4d..e6f0a4ce5e 100644 --- a/build.xml +++ b/build.xml @@ -511,7 +511,7 @@ https://www.apache.org/licenses/LICENSE-2.0.txt"/> - + - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-3.0 updated: Suppress CVE-2023-34455, CVE-2023-34454, CVE-2023-34453
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-3.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/cassandra-3.0 by this push: new d99bccd649 Suppress CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 d99bccd649 is described below commit d99bccd6493ceb7aed4e05b05f81913ea876d855 Author: Brandon Williams AuthorDate: Thu Jun 22 11:55:09 2023 -0500 Suppress CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 Patch by brandonwilliams; reviewed by bereng for CASSANDRA-18608 --- .build/dependency-check-suppressions.xml | 7 +++ CHANGES.txt | 1 + 2 files changed, 8 insertions(+) diff --git a/.build/dependency-check-suppressions.xml b/.build/dependency-check-suppressions.xml index 02dbb8dd92..08bf3f7236 100644 --- a/.build/dependency-check-suppressions.xml +++ b/.build/dependency-check-suppressions.xml @@ -20,6 +20,13 @@ https://jeremylong.github.io/DependencyCheck/general/suppression.html --> https://jeremylong.github.io/DependencyCheck/dependency-suppression.1.3.xsd;> + + +^pkg:maven/org\.xerial\.snappy/snappy\-java@.*$ +CVE-2023-34453 +CVE-2023-34454 +CVE-2023-34455 + ^pkg:maven/org\.yaml/snakeyaml@.*$ diff --git a/CHANGES.txt b/CHANGES.txt index 6e0853c3a4..43b4cc40fb 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 3.0.30 + * Suppress CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 (CASSANDRA-18608) * Backport CASSANDRA-10508: Remove hard-coded SSL cipher suites (CASSANDRA-18575) * Suppress CVE-2023-2976 (CASSANDRA-18562) * Remove dh_python use in Debian packaging (CASSANDRA-18558) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-12183) compaction_history system table does not capture all historical compaction sessions
[
https://issues.apache.org/jira/browse/CASSANDRA-12183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-12183:
-
Status: Ready to Commit (was: Review In Progress)
> compaction_history system table does not capture all historical compaction
> sessions
> ---
>
> Key: CASSANDRA-12183
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12183
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability, Local/Compaction
>Reporter: Wei Deng
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> It appears that some compaction sessions are not recorded in
> system.compaction_history table after the compaction session successfully
> finishes.
> The following is an example (test by simply running +cassandra-stress write
> n=1+):
> {noformat}
> automaton@wdengdse50google-98425b985-3:~$ nodetool compactionstats
> pending tasks: 46
> id compaction typekeyspace
> tablecompletedtotalunit progress
>fa8a4f30-4884-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1 4233184044 4774209875 bytes 88.67%
>91e30d21-4887-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1836983029889773060 bytes 94.07%
> Active compaction remaining time : 0h00m35s
> automaton@wdengdse50google-98425b985-3:~$ nodetool compactionstats
> pending tasks: 47
> id compaction typekeyspace
> tablecompletedtotalunit progress
>fa8a4f30-4884-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1 4353251539 4774209875 bytes 91.18%
>28359094-4888-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1 49732274 4071652280 bytes 1.22%
> Active compaction remaining time : 0h04m24s
> {noformat}
> At this point you know the previous compaction session
> 91e30d21-4887-11e6-b916-1dbd340a212f finished and confirmation can be found
> from debug.log
> {noformat}
> automaton@wdengdse50google-98425b985-3:~$ grep
> 91e30d21-4887-11e6-b916-1dbd340a212f /var/log/cassandra/debug.log
> DEBUG [CompactionExecutor:4] 2016-07-12 23:22:58,674 CompactionTask.java:146
> - Compacting (91e30d21-4887-11e6-b916-1dbd340a212f)
> [/var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-290-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-279-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-281-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-280-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-284-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-283-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-287-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-292-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-286-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-289-big-Data.db:level=0,
> ]
> DEBUG [CompactionExecutor:4] 2016-07-12 23:26:56,054 CompactionTask.java:217
> - Compacted (91e30d21-4887-11e6-b916-1dbd340a212f) 10 sstables to
> [/var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-293-big,]
> to level=0. 889,773,060 bytes to 890,473,350 (~100% of original) in
> 237,365ms = 3.577703MB/s. 0 total partitions merged to 3,871,921. Partition
> merge counts were {1:3871921, }
> {noformat}
> However, if you query system.compaction_history table or run "nodetool
> compactionhistory | grep 91e30d21-4887-11e6-b916-1dbd340a212f" you will get
> nothing:
> {noformat}
> automaton@wdengdse50google-98425b985-3:~$ cqlsh -u cassandra
> Password:
> Connected to dse50 at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 3.0.7.1158 | DSE 5.0.0 | CQL spec 3.4.0 | Native
> protocol v4]
> Use HELP for help.
> cassandra@cqlsh> select * from system.compaction_history where
> id=91e30d21-4887-11e6-b916-1dbd340a212f;
> id | bytes_in | bytes_out | columnfamily_name | compacted_at | keyspace_name
> | rows_merged
> +--+---+---+--+---+-
> (0 rows)
> automaton@wdengdse50google-98425b985-3:~$ nodetool flush system
>
[jira] [Updated] (CASSANDRA-12183) compaction_history system table does not capture all historical compaction sessions
[
https://issues.apache.org/jira/browse/CASSANDRA-12183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-12183:
-
Reviewers: Brandon Williams
> compaction_history system table does not capture all historical compaction
> sessions
> ---
>
> Key: CASSANDRA-12183
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12183
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability, Local/Compaction
>Reporter: Wei Deng
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> It appears that some compaction sessions are not recorded in
> system.compaction_history table after the compaction session successfully
> finishes.
> The following is an example (test by simply running +cassandra-stress write
> n=1+):
> {noformat}
> automaton@wdengdse50google-98425b985-3:~$ nodetool compactionstats
> pending tasks: 46
> id compaction typekeyspace
> tablecompletedtotalunit progress
>fa8a4f30-4884-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1 4233184044 4774209875 bytes 88.67%
>91e30d21-4887-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1836983029889773060 bytes 94.07%
> Active compaction remaining time : 0h00m35s
> automaton@wdengdse50google-98425b985-3:~$ nodetool compactionstats
> pending tasks: 47
> id compaction typekeyspace
> tablecompletedtotalunit progress
>fa8a4f30-4884-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1 4353251539 4774209875 bytes 91.18%
>28359094-4888-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1 49732274 4071652280 bytes 1.22%
> Active compaction remaining time : 0h04m24s
> {noformat}
> At this point you know the previous compaction session
> 91e30d21-4887-11e6-b916-1dbd340a212f finished and confirmation can be found
> from debug.log
> {noformat}
> automaton@wdengdse50google-98425b985-3:~$ grep
> 91e30d21-4887-11e6-b916-1dbd340a212f /var/log/cassandra/debug.log
> DEBUG [CompactionExecutor:4] 2016-07-12 23:22:58,674 CompactionTask.java:146
> - Compacting (91e30d21-4887-11e6-b916-1dbd340a212f)
> [/var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-290-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-279-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-281-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-280-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-284-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-283-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-287-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-292-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-286-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-289-big-Data.db:level=0,
> ]
> DEBUG [CompactionExecutor:4] 2016-07-12 23:26:56,054 CompactionTask.java:217
> - Compacted (91e30d21-4887-11e6-b916-1dbd340a212f) 10 sstables to
> [/var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-293-big,]
> to level=0. 889,773,060 bytes to 890,473,350 (~100% of original) in
> 237,365ms = 3.577703MB/s. 0 total partitions merged to 3,871,921. Partition
> merge counts were {1:3871921, }
> {noformat}
> However, if you query system.compaction_history table or run "nodetool
> compactionhistory | grep 91e30d21-4887-11e6-b916-1dbd340a212f" you will get
> nothing:
> {noformat}
> automaton@wdengdse50google-98425b985-3:~$ cqlsh -u cassandra
> Password:
> Connected to dse50 at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 3.0.7.1158 | DSE 5.0.0 | CQL spec 3.4.0 | Native
> protocol v4]
> Use HELP for help.
> cassandra@cqlsh> select * from system.compaction_history where
> id=91e30d21-4887-11e6-b916-1dbd340a212f;
> id | bytes_in | bytes_out | columnfamily_name | compacted_at | keyspace_name
> | rows_merged
> +--+---+---+--+---+-
> (0 rows)
> automaton@wdengdse50google-98425b985-3:~$ nodetool flush system
> automaton@wdengdse50google-98425b985-3:~$
[jira] [Updated] (CASSANDRA-12183) compaction_history system table does not capture all historical compaction sessions
[
https://issues.apache.org/jira/browse/CASSANDRA-12183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-12183:
-
Status: Review In Progress (was: Needs Committer)
> compaction_history system table does not capture all historical compaction
> sessions
> ---
>
> Key: CASSANDRA-12183
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12183
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability, Local/Compaction
>Reporter: Wei Deng
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> It appears that some compaction sessions are not recorded in
> system.compaction_history table after the compaction session successfully
> finishes.
> The following is an example (test by simply running +cassandra-stress write
> n=1+):
> {noformat}
> automaton@wdengdse50google-98425b985-3:~$ nodetool compactionstats
> pending tasks: 46
> id compaction typekeyspace
> tablecompletedtotalunit progress
>fa8a4f30-4884-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1 4233184044 4774209875 bytes 88.67%
>91e30d21-4887-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1836983029889773060 bytes 94.07%
> Active compaction remaining time : 0h00m35s
> automaton@wdengdse50google-98425b985-3:~$ nodetool compactionstats
> pending tasks: 47
> id compaction typekeyspace
> tablecompletedtotalunit progress
>fa8a4f30-4884-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1 4353251539 4774209875 bytes 91.18%
>28359094-4888-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1 49732274 4071652280 bytes 1.22%
> Active compaction remaining time : 0h04m24s
> {noformat}
> At this point you know the previous compaction session
> 91e30d21-4887-11e6-b916-1dbd340a212f finished and confirmation can be found
> from debug.log
> {noformat}
> automaton@wdengdse50google-98425b985-3:~$ grep
> 91e30d21-4887-11e6-b916-1dbd340a212f /var/log/cassandra/debug.log
> DEBUG [CompactionExecutor:4] 2016-07-12 23:22:58,674 CompactionTask.java:146
> - Compacting (91e30d21-4887-11e6-b916-1dbd340a212f)
> [/var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-290-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-279-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-281-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-280-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-284-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-283-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-287-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-292-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-286-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-289-big-Data.db:level=0,
> ]
> DEBUG [CompactionExecutor:4] 2016-07-12 23:26:56,054 CompactionTask.java:217
> - Compacted (91e30d21-4887-11e6-b916-1dbd340a212f) 10 sstables to
> [/var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-293-big,]
> to level=0. 889,773,060 bytes to 890,473,350 (~100% of original) in
> 237,365ms = 3.577703MB/s. 0 total partitions merged to 3,871,921. Partition
> merge counts were {1:3871921, }
> {noformat}
> However, if you query system.compaction_history table or run "nodetool
> compactionhistory | grep 91e30d21-4887-11e6-b916-1dbd340a212f" you will get
> nothing:
> {noformat}
> automaton@wdengdse50google-98425b985-3:~$ cqlsh -u cassandra
> Password:
> Connected to dse50 at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 3.0.7.1158 | DSE 5.0.0 | CQL spec 3.4.0 | Native
> protocol v4]
> Use HELP for help.
> cassandra@cqlsh> select * from system.compaction_history where
> id=91e30d21-4887-11e6-b916-1dbd340a212f;
> id | bytes_in | bytes_out | columnfamily_name | compacted_at | keyspace_name
> | rows_merged
> +--+---+---+--+---+-
> (0 rows)
> automaton@wdengdse50google-98425b985-3:~$ nodetool flush system
>
[jira] [Commented] (CASSANDRA-12183) compaction_history system table does not capture all historical compaction sessions
[
https://issues.apache.org/jira/browse/CASSANDRA-12183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737097#comment-17737097
]
Brandon Williams commented on CASSANDRA-12183:
--
+1
> compaction_history system table does not capture all historical compaction
> sessions
> ---
>
> Key: CASSANDRA-12183
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12183
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability, Local/Compaction
>Reporter: Wei Deng
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> It appears that some compaction sessions are not recorded in
> system.compaction_history table after the compaction session successfully
> finishes.
> The following is an example (test by simply running +cassandra-stress write
> n=1+):
> {noformat}
> automaton@wdengdse50google-98425b985-3:~$ nodetool compactionstats
> pending tasks: 46
> id compaction typekeyspace
> tablecompletedtotalunit progress
>fa8a4f30-4884-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1 4233184044 4774209875 bytes 88.67%
>91e30d21-4887-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1836983029889773060 bytes 94.07%
> Active compaction remaining time : 0h00m35s
> automaton@wdengdse50google-98425b985-3:~$ nodetool compactionstats
> pending tasks: 47
> id compaction typekeyspace
> tablecompletedtotalunit progress
>fa8a4f30-4884-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1 4353251539 4774209875 bytes 91.18%
>28359094-4888-11e6-b916-1dbd340a212fCompaction keyspace1
> standard1 49732274 4071652280 bytes 1.22%
> Active compaction remaining time : 0h04m24s
> {noformat}
> At this point you know the previous compaction session
> 91e30d21-4887-11e6-b916-1dbd340a212f finished and confirmation can be found
> from debug.log
> {noformat}
> automaton@wdengdse50google-98425b985-3:~$ grep
> 91e30d21-4887-11e6-b916-1dbd340a212f /var/log/cassandra/debug.log
> DEBUG [CompactionExecutor:4] 2016-07-12 23:22:58,674 CompactionTask.java:146
> - Compacting (91e30d21-4887-11e6-b916-1dbd340a212f)
> [/var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-290-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-279-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-281-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-280-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-284-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-283-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-287-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-292-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-286-big-Data.db:level=0,
>
> /var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-289-big-Data.db:level=0,
> ]
> DEBUG [CompactionExecutor:4] 2016-07-12 23:26:56,054 CompactionTask.java:217
> - Compacted (91e30d21-4887-11e6-b916-1dbd340a212f) 10 sstables to
> [/var/lib/cassandra/data/keyspace1/standard1-9c02e9c1487c11e6b9161dbd340a212f/mb-293-big,]
> to level=0. 889,773,060 bytes to 890,473,350 (~100% of original) in
> 237,365ms = 3.577703MB/s. 0 total partitions merged to 3,871,921. Partition
> merge counts were {1:3871921, }
> {noformat}
> However, if you query system.compaction_history table or run "nodetool
> compactionhistory | grep 91e30d21-4887-11e6-b916-1dbd340a212f" you will get
> nothing:
> {noformat}
> automaton@wdengdse50google-98425b985-3:~$ cqlsh -u cassandra
> Password:
> Connected to dse50 at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 3.0.7.1158 | DSE 5.0.0 | CQL spec 3.4.0 | Native
> protocol v4]
> Use HELP for help.
> cassandra@cqlsh> select * from system.compaction_history where
> id=91e30d21-4887-11e6-b916-1dbd340a212f;
> id | bytes_in | bytes_out | columnfamily_name | compacted_at | keyspace_name
> | rows_merged
> +--+---+---+--+---+-
> (0 rows)
> automaton@wdengdse50google-98425b985-3:~$ nodetool flush system
>
[jira] [Updated] (CASSANDRA-18345) Enable streaming SAI components as part of repair
[ https://issues.apache.org/jira/browse/CASSANDRA-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña updated CASSANDRA-18345: -- Reviewers: Andres de la Peña, Caleb Rackliffe, Mike Adamson (was: Caleb Rackliffe, Mike Adamson) > Enable streaming SAI components as part of repair > - > > Key: CASSANDRA-18345 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18345 > Project: Cassandra > Issue Type: Improvement > Components: Feature/2i Index >Reporter: Mike Adamson >Assignee: Piotr Kolaczkowski >Priority: Normal > Labels: SAI > Fix For: NA > > > SAI registers it's components with the SSTable descriptor expecting them to > form part of the SSTable lifecycle, including streaming. This is not the case. > The current SSTable format in Cassandra uses a fixed set of components > (Components.STREAMING_COMPONENTS) when streaming SSTables. This needs to > change to use the set of components that are registered with a specific > SSTable by calls to SSTable.registerComponents. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18600) [Analytics] Add NOTICE.txt in Cassandra Analytics
[
https://issues.apache.org/jira/browse/CASSANDRA-18600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737040#comment-17737040
]
Berenguer Blasi commented on CASSANDRA-18600:
-
Ops, tried to push but I have no rights... :shrug:
> [Analytics] Add NOTICE.txt in Cassandra Analytics
> --
>
> Key: CASSANDRA-18600
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18600
> Project: Cassandra
> Issue Type: Task
> Components: Analytics Library
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Cassandra Analytics project is missing the {{NOTICE.txt}} file required
> for compliance with the ASF guidance
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18608) snappy-java vulnerability: CVE-2023-34455, CVE-2023-34454, CVE-2023-34453
[
https://issues.apache.org/jira/browse/CASSANDRA-18608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-18608:
Status: Ready to Commit (was: Review In Progress)
> snappy-java vulnerability: CVE-2023-34455, CVE-2023-34454, CVE-2023-34453
> -
>
> Key: CASSANDRA-18608
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18608
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Compression
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> Failing owasp:
> [https://nvd.nist.gov/vuln/detail/CVE-2023-34455]
> {quote}Due to use of an unchecked chunk length, an unrecoverable fatal error
> can occur in versions prior to 1.1.10.1.
> {quote}
> [https://nvd.nist.gov/vuln/detail/CVE-2023-34454]
> {quote}Due to unchecked multiplications, an integer overflow may occur in
> versions prior to 1.1.10.1, causing an unrecoverable fatal error.
> {quote}
> [https://nvd.nist.gov/vuln/detail/CVE-2023-34453]
> {quote}Due to unchecked multiplications, an integer overflow may occur in
> versions prior to 1.1.10.1, causing a fatal error.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18603) Move checkstyle files into .build
[ https://issues.apache.org/jira/browse/CASSANDRA-18603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-18603: Fix Version/s: 4.1.3 5.0 (was: 5.x) (was: 4.1.x) Source Control Link: https://github.com/apache/cassandra/commit/f7b952387ae17a5975de2c1da12410eac41559cc Resolution: Fixed Status: Resolved (was: Ready to Commit) > Move checkstyle files into .build > - > > Key: CASSANDRA-18603 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18603 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.1.3, 5.0 > > > Checkstyle files are currently in the root folder whereas the rest of similar > purposed files live under .build. Let's move them for consistency. > CC [~mck] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18603) Move checkstyle files into .build
[ https://issues.apache.org/jira/browse/CASSANDRA-18603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-18603: Status: Review In Progress (was: Patch Available) > Move checkstyle files into .build > - > > Key: CASSANDRA-18603 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18603 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.1.x, 5.x > > > Checkstyle files are currently in the root folder whereas the rest of similar > purposed files live under .build. Let's move them for consistency. > CC [~mck] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
