[jira] [Updated] (CASSANDRA-17361) DOC - STCS page has LCS in title, broken links in compaction page
[
https://issues.apache.org/jira/browse/CASSANDRA-17361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17361:
--
Summary: DOC - STCS page has LCS in title, broken links in compaction page
(was: STCS documentation on website mentions LCS in title)
> DOC - STCS page has LCS in title, broken links in compaction page
> -
>
> Key: CASSANDRA-17361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17361
> Project: Cassandra
> Issue Type: Bug
> Components: Documentation/Website
>Reporter: Matt Fleming
>Assignee: Erick Ramirez
>Priority: Normal
>
> The STCS page here,
> [https://cassandra.apache.org/doc/latest/cassandra/operating/compaction/stcs.html],
> says "Leveled Compaction Strategy" in the title where it should say
> "Size-tiered Compaction Strategy.
> *EDIT:* This needs to be fixed in the following branches:
> * {{trunk}} -
> https://cassandra.apache.org/doc/trunk/cassandra/operating/compaction/stcs.html
> * {{4.0}} -
> https://cassandra.apache.org/doc/4.0/cassandra/operating/compaction/stcs.html
> * {{3.11}} -
> https://cassandra.apache.org/doc/3.11/cassandra/operating/compaction/stcs.html
> While looking into this ticket, I've also discovered that the links to the
> compaction strategy sub-pages are broken in the
> {{operating/compaction/index.adoc}} and will need to be fixed in the
> following branches:
> * {{trunk}} -
> https://cassandra.apache.org/doc/trunk/cassandra/operating/compaction/index.html
> * {{4.0}} -
> https://cassandra.apache.org/doc/4.0/cassandra/operating/compaction/index.html
> * {{3.11}} -
> https://cassandra.apache.org/doc/3.11/cassandra/operating/compaction/index.html
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17361) STCS documentation on website mentions LCS in title
[
https://issues.apache.org/jira/browse/CASSANDRA-17361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17361:
--
Description:
The STCS page here,
[https://cassandra.apache.org/doc/latest/cassandra/operating/compaction/stcs.html],
says "Leveled Compaction Strategy" in the title where it should say
"Size-tiered Compaction Strategy.
*EDIT:* This needs to be fixed in the following branches:
* {{trunk}} -
https://cassandra.apache.org/doc/trunk/cassandra/operating/compaction/stcs.html
* {{4.0}} -
https://cassandra.apache.org/doc/4.0/cassandra/operating/compaction/stcs.html
* {{3.11}} -
https://cassandra.apache.org/doc/3.11/cassandra/operating/compaction/stcs.html
While looking into this ticket, I've also discovered that the links to the
compaction strategy sub-pages are broken in the
{{operating/compaction/index.adoc}} and will need to be fixed in the following
branches:
* {{trunk}} -
https://cassandra.apache.org/doc/trunk/cassandra/operating/compaction/index.html
* {{4.0}} -
https://cassandra.apache.org/doc/4.0/cassandra/operating/compaction/index.html
* {{3.11}} -
https://cassandra.apache.org/doc/3.11/cassandra/operating/compaction/index.html
was:The STCS page here,
[https://cassandra.apache.org/doc/latest/cassandra/operating/compaction/stcs.html,]
says "Leveled Compaction Strategy" in the title where it should say
"Size-tiered Compaction Strategy.
> STCS documentation on website mentions LCS in title
> ---
>
> Key: CASSANDRA-17361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17361
> Project: Cassandra
> Issue Type: Bug
> Components: Documentation/Website
>Reporter: Matt Fleming
>Assignee: Erick Ramirez
>Priority: Normal
>
> The STCS page here,
> [https://cassandra.apache.org/doc/latest/cassandra/operating/compaction/stcs.html],
> says "Leveled Compaction Strategy" in the title where it should say
> "Size-tiered Compaction Strategy.
> *EDIT:* This needs to be fixed in the following branches:
> * {{trunk}} -
> https://cassandra.apache.org/doc/trunk/cassandra/operating/compaction/stcs.html
> * {{4.0}} -
> https://cassandra.apache.org/doc/4.0/cassandra/operating/compaction/stcs.html
> * {{3.11}} -
> https://cassandra.apache.org/doc/3.11/cassandra/operating/compaction/stcs.html
> While looking into this ticket, I've also discovered that the links to the
> compaction strategy sub-pages are broken in the
> {{operating/compaction/index.adoc}} and will need to be fixed in the
> following branches:
> * {{trunk}} -
> https://cassandra.apache.org/doc/trunk/cassandra/operating/compaction/index.html
> * {{4.0}} -
> https://cassandra.apache.org/doc/4.0/cassandra/operating/compaction/index.html
> * {{3.11}} -
> https://cassandra.apache.org/doc/3.11/cassandra/operating/compaction/index.html
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17416) Test Failure: org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testCDCIndexFileWriteOnSync
Marcus Eriksson created CASSANDRA-17416: --- Summary: Test Failure: org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testCDCIndexFileWriteOnSync Key: CASSANDRA-17416 URL: https://issues.apache.org/jira/browse/CASSANDRA-17416 Project: Cassandra Issue Type: Bug Components: Test/unit Reporter: Marcus Eriksson [https://ci-cassandra.apache.org/job/Cassandra-trunk/985/testReport/org.apache.cassandra.db.commitlog/CommitLogSegmentManagerCDCTest/testCDCIndexFileWriteOnSync_cdc_3/] h3. Error Message expected:<1748956> but was:<1749196> h3. Stacktrace junit.framework.AssertionFailedError: expected:<1748956> but was:<1749196> at org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testCDCIndexFileWriteOnSync(CommitLogSegmentManagerCDCTest.java:160) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) h3. Standard Output INFO [main] 2022-03-02 15:04:59,516 YamlConfigurationLoader.java:103 - Configuration location: file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml DEBUG [main] 2022-03-02 15:04:59,520 YamlConfigurationLoader.java:124 - Loading settings from file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml INFO [main] 2022-03-02 15:04:59,674 Config.java:907 - Node configuration:[allocate_tokens_for_keyspace=null; allocate_tokens_for_local_replication_factor=null; allow_extra_insecure_ ...[truncated 4125855 chars]... -02 15:06:57,491 PathUtils.java:73 - Deleting file during startup: /home/cassandra/cassandra/build/test/cassandra/data/system_schema/views-9786ac1cdd583201a7cdad556410c985/nb-11-big-Summary.db DEBUG [MemtableFlushWriter:2] 2022-03-02 15:06:57,496 ColumnFamilyStore.java:1207 - Flushed to [BigTableReader(path='/home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb-55-big-Data.db')] (1 sstables, 4.895KiB), biggest 4.895KiB, smallest 4.895KiB -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16916) Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
[
https://issues.apache.org/jira/browse/CASSANDRA-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501125#comment-17501125
]
Jogesh Anand commented on CASSANDRA-16916:
--
[~e.dimitrova] - No worries at all. I didn't know I could update the ticket
status, thought reviewers/committers change that status. Will do so next time
onwards. Sorry about that
I can re-base this weekend so if you decide to run CI it's up-to-date. Let me
know how you would like. thanks again!
> Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
> ---
>
> Key: CASSANDRA-16916
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16916
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax
>Reporter: Benjamin Lerer
>Assignee: Jogesh Anand
>Priority: Normal
> Fix For: 4.x
>
>
> It would make sense to add support for {{IF EXISTS}} and {{IF NOT EXISTS}} in
> the different {{ALTER}} statements.
> For example:
> * {{ALTER TABLE IF EXISTS myTable ...}}
> * {{ALTER TABLE myTable ADD IF NOT EXISTS ...}}
> * {{ALTER TABLE myTable DROP IF EXISTS ...}}
> * {{ALTER TYPE IF EXISTS myType ...}}
> * {{ALTER TYPE myType ADD IF NOT EXISTS ...}}
> +Additional info for newcomers:+
> In order to implement this change you will need to change the {{Parser.g}}
> ANTLR file located in the src/antlr directory and the java classes
> corresponding to the different alter statements located in the
> {{org.apache.cassandra.cql3.statements.schema}} package. You can look at the
> CreateTableStatement class to see how it was done there.
> The unit test for the CQL logic are located under
> {{org.apache.cassandra.cql3.validation}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16916) Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
[
https://issues.apache.org/jira/browse/CASSANDRA-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501125#comment-17501125
]
Jogesh Anand edited comment on CASSANDRA-16916 at 3/4/22, 3:21 AM:
---
[~e.dimitrova] - No worries at all. I didn't know I could update the ticket
status, thought reviewers/committers change that status. Will do so next time
onwards. Sorry about that
I can re-base this weekend so if you decide to run CI on Monday it's
up-to-date. Let me know how you would like. thanks again!
was (Author: djanand):
[~e.dimitrova] - No worries at all. I didn't know I could update the ticket
status, thought reviewers/committers change that status. Will do so next time
onwards. Sorry about that
I can re-base this weekend so if you decide to run CI it's up-to-date. Let me
know how you would like. thanks again!
> Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
> ---
>
> Key: CASSANDRA-16916
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16916
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax
>Reporter: Benjamin Lerer
>Assignee: Jogesh Anand
>Priority: Normal
> Fix For: 4.x
>
>
> It would make sense to add support for {{IF EXISTS}} and {{IF NOT EXISTS}} in
> the different {{ALTER}} statements.
> For example:
> * {{ALTER TABLE IF EXISTS myTable ...}}
> * {{ALTER TABLE myTable ADD IF NOT EXISTS ...}}
> * {{ALTER TABLE myTable DROP IF EXISTS ...}}
> * {{ALTER TYPE IF EXISTS myType ...}}
> * {{ALTER TYPE myType ADD IF NOT EXISTS ...}}
> +Additional info for newcomers:+
> In order to implement this change you will need to change the {{Parser.g}}
> ANTLR file located in the src/antlr directory and the java classes
> corresponding to the different alter statements located in the
> {{org.apache.cassandra.cql3.statements.schema}} package. You can look at the
> CreateTableStatement class to see how it was done there.
> The unit test for the CQL logic are located under
> {{org.apache.cassandra.cql3.validation}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16916) Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
[
https://issues.apache.org/jira/browse/CASSANDRA-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16916:
Status: Review In Progress (was: Patch Available)
> Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
> ---
>
> Key: CASSANDRA-16916
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16916
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax
>Reporter: Benjamin Lerer
>Assignee: Jogesh Anand
>Priority: Normal
> Fix For: 4.x
>
>
> It would make sense to add support for {{IF EXISTS}} and {{IF NOT EXISTS}} in
> the different {{ALTER}} statements.
> For example:
> * {{ALTER TABLE IF EXISTS myTable ...}}
> * {{ALTER TABLE myTable ADD IF NOT EXISTS ...}}
> * {{ALTER TABLE myTable DROP IF EXISTS ...}}
> * {{ALTER TYPE IF EXISTS myType ...}}
> * {{ALTER TYPE myType ADD IF NOT EXISTS ...}}
> +Additional info for newcomers:+
> In order to implement this change you will need to change the {{Parser.g}}
> ANTLR file located in the src/antlr directory and the java classes
> corresponding to the different alter statements located in the
> {{org.apache.cassandra.cql3.statements.schema}} package. You can look at the
> CreateTableStatement class to see how it was done there.
> The unit test for the CQL logic are located under
> {{org.apache.cassandra.cql3.validation}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16916) Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
[
https://issues.apache.org/jira/browse/CASSANDRA-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16916:
Status: Patch Available (was: Review In Progress)
> Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
> ---
>
> Key: CASSANDRA-16916
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16916
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax
>Reporter: Benjamin Lerer
>Assignee: Jogesh Anand
>Priority: Normal
> Fix For: 4.x
>
>
> It would make sense to add support for {{IF EXISTS}} and {{IF NOT EXISTS}} in
> the different {{ALTER}} statements.
> For example:
> * {{ALTER TABLE IF EXISTS myTable ...}}
> * {{ALTER TABLE myTable ADD IF NOT EXISTS ...}}
> * {{ALTER TABLE myTable DROP IF EXISTS ...}}
> * {{ALTER TYPE IF EXISTS myType ...}}
> * {{ALTER TYPE myType ADD IF NOT EXISTS ...}}
> +Additional info for newcomers:+
> In order to implement this change you will need to change the {{Parser.g}}
> ANTLR file located in the src/antlr directory and the java classes
> corresponding to the different alter statements located in the
> {{org.apache.cassandra.cql3.statements.schema}} package. You can look at the
> CreateTableStatement class to see how it was done there.
> The unit test for the CQL logic are located under
> {{org.apache.cassandra.cql3.validation}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16916) Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
[
https://issues.apache.org/jira/browse/CASSANDRA-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16916:
Status: Review In Progress (was: Changes Suggested)
> Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
> ---
>
> Key: CASSANDRA-16916
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16916
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax
>Reporter: Benjamin Lerer
>Assignee: Jogesh Anand
>Priority: Normal
> Fix For: 4.x
>
>
> It would make sense to add support for {{IF EXISTS}} and {{IF NOT EXISTS}} in
> the different {{ALTER}} statements.
> For example:
> * {{ALTER TABLE IF EXISTS myTable ...}}
> * {{ALTER TABLE myTable ADD IF NOT EXISTS ...}}
> * {{ALTER TABLE myTable DROP IF EXISTS ...}}
> * {{ALTER TYPE IF EXISTS myType ...}}
> * {{ALTER TYPE myType ADD IF NOT EXISTS ...}}
> +Additional info for newcomers:+
> In order to implement this change you will need to change the {{Parser.g}}
> ANTLR file located in the src/antlr directory and the java classes
> corresponding to the different alter statements located in the
> {{org.apache.cassandra.cql3.statements.schema}} package. You can look at the
> CreateTableStatement class to see how it was done there.
> The unit test for the CQL logic are located under
> {{org.apache.cassandra.cql3.validation}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16916) Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
[
https://issues.apache.org/jira/browse/CASSANDRA-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501121#comment-17501121
]
Ekaterina Dimitrova commented on CASSANDRA-16916:
-
[~djanand] , I am really sorry I missed your previous comment and the ticket
still has CHANGES SUGGESTED status.
I will review it on Monday, I am truly sorry for this misunderstanding and
delay. Definitely not intentional…
> Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
> ---
>
> Key: CASSANDRA-16916
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16916
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax
>Reporter: Benjamin Lerer
>Assignee: Jogesh Anand
>Priority: Normal
> Fix For: 4.x
>
>
> It would make sense to add support for {{IF EXISTS}} and {{IF NOT EXISTS}} in
> the different {{ALTER}} statements.
> For example:
> * {{ALTER TABLE IF EXISTS myTable ...}}
> * {{ALTER TABLE myTable ADD IF NOT EXISTS ...}}
> * {{ALTER TABLE myTable DROP IF EXISTS ...}}
> * {{ALTER TYPE IF EXISTS myType ...}}
> * {{ALTER TYPE myType ADD IF NOT EXISTS ...}}
> +Additional info for newcomers:+
> In order to implement this change you will need to change the {{Parser.g}}
> ANTLR file located in the src/antlr directory and the java classes
> corresponding to the different alter statements located in the
> {{org.apache.cassandra.cql3.statements.schema}} package. You can look at the
> CreateTableStatement class to see how it was done there.
> The unit test for the CQL logic are located under
> {{org.apache.cassandra.cql3.validation}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16916) Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
[
https://issues.apache.org/jira/browse/CASSANDRA-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501121#comment-17501121
]
Ekaterina Dimitrova edited comment on CASSANDRA-16916 at 3/4/22, 3:13 AM:
--
[~djanand] , I am really sorry, I missed your previous comment and the ticket
still has CHANGES SUGGESTED status.
I will review it on Monday, I am truly sorry for this misunderstanding and
delay. Definitely not intentional…
was (Author: e.dimitrova):
[~djanand] , I am really sorry I missed your previous comment and the ticket
still has CHANGES SUGGESTED status.
I will review it on Monday, I am truly sorry for this misunderstanding and
delay. Definitely not intentional…
> Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
> ---
>
> Key: CASSANDRA-16916
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16916
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax
>Reporter: Benjamin Lerer
>Assignee: Jogesh Anand
>Priority: Normal
> Fix For: 4.x
>
>
> It would make sense to add support for {{IF EXISTS}} and {{IF NOT EXISTS}} in
> the different {{ALTER}} statements.
> For example:
> * {{ALTER TABLE IF EXISTS myTable ...}}
> * {{ALTER TABLE myTable ADD IF NOT EXISTS ...}}
> * {{ALTER TABLE myTable DROP IF EXISTS ...}}
> * {{ALTER TYPE IF EXISTS myType ...}}
> * {{ALTER TYPE myType ADD IF NOT EXISTS ...}}
> +Additional info for newcomers:+
> In order to implement this change you will need to change the {{Parser.g}}
> ANTLR file located in the src/antlr directory and the java classes
> corresponding to the different alter statements located in the
> {{org.apache.cassandra.cql3.statements.schema}} package. You can look at the
> CreateTableStatement class to see how it was done there.
> The unit test for the CQL logic are located under
> {{org.apache.cassandra.cql3.validation}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16916) Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
[
https://issues.apache.org/jira/browse/CASSANDRA-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501112#comment-17501112
]
Jogesh Anand commented on CASSANDRA-16916:
--
[~blerer] , [~e.dimitrova] , @mentors - gentle ping!
> Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
> ---
>
> Key: CASSANDRA-16916
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16916
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax
>Reporter: Benjamin Lerer
>Assignee: Jogesh Anand
>Priority: Normal
> Fix For: 4.x
>
>
> It would make sense to add support for {{IF EXISTS}} and {{IF NOT EXISTS}} in
> the different {{ALTER}} statements.
> For example:
> * {{ALTER TABLE IF EXISTS myTable ...}}
> * {{ALTER TABLE myTable ADD IF NOT EXISTS ...}}
> * {{ALTER TABLE myTable DROP IF EXISTS ...}}
> * {{ALTER TYPE IF EXISTS myType ...}}
> * {{ALTER TYPE myType ADD IF NOT EXISTS ...}}
> +Additional info for newcomers:+
> In order to implement this change you will need to change the {{Parser.g}}
> ANTLR file located in the src/antlr directory and the java classes
> corresponding to the different alter statements located in the
> {{org.apache.cassandra.cql3.statements.schema}} package. You can look at the
> CreateTableStatement class to see how it was done there.
> The unit test for the CQL logic are located under
> {{org.apache.cassandra.cql3.validation}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16765) Update Cassandra build CI script for new website
[ https://issues.apache.org/jira/browse/CASSANDRA-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16765: --- Status: Ready to Commit (was: Review In Progress) Tested steps in groovy script. All commands look to be correct. This patch can be committed. > Update Cassandra build CI script for new website > > > Key: CASSANDRA-16765 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16765 > Project: Cassandra > Issue Type: Task > Components: Build, CI, Documentation/Website >Reporter: Anthony Grasso >Assignee: Michael Semb Wever >Priority: Normal > > Update the apache/cassandra-build repository has [.groovy job > script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy] > to use the new tooling to build the website. > The apache/cassandra-build repository has [.groovy job > script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy]. > It [builds and deploys the > website|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L1255-L1268] > to cassandra-website staging when the cassandra-website is updated. > We need to change the commands in the .groovy script to at least rebuild the > site when a change happens in the cassandra-website repository. > It would be also good to build the docs when a change happens to doc/source > directory in the cassandra repository. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17335) Fix race condition bug during local session repair
[
https://issues.apache.org/jira/browse/CASSANDRA-17335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501082#comment-17501082
]
Yifan Cai commented on CASSANDRA-17335:
---
Starting commit
CI Results (pending):
||Branch||Source||Circle CI||
|cassandra-4.0|[branch|https://github.com/yifan-c/cassandra/tree/commit_remote_branch/CASSANDRA-17335-cassandra-4.0-3EE5D631-3BA2-47A0-B74F-D79A5776514F]|[build|https://app.circleci.com/pipelines/github/yifan-c/cassandra?branch=commit_remote_branch%2FCASSANDRA-17335-cassandra-4.0-3EE5D631-3BA2-47A0-B74F-D79A5776514F]|
|trunk|[branch|https://github.com/yifan-c/cassandra/tree/commit_remote_branch/CASSANDRA-17335-trunk-3EE5D631-3BA2-47A0-B74F-D79A5776514F]|[build|https://app.circleci.com/pipelines/github/yifan-c/cassandra?branch=commit_remote_branch%2FCASSANDRA-17335-trunk-3EE5D631-3BA2-47A0-B74F-D79A5776514F]|
> Fix race condition bug during local session repair
> --
>
> Key: CASSANDRA-17335
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17335
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Bernardo Botella Corbi
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
> Attachments:
> 0001-Fix-Flaky-testNoSuchRepairSessionAnticompaction-trunk.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The in-JVM dtest {{RepairErrorsTest#testNoSuchRepairSessionAnticompaction}}
> seems to be flaky, as it's shown by [this repeated
> run|https://app.circleci.com/pipelines/github/adelapena/cassandra/1280/workflows/8a4e04cb-64cc-46a3-9e1e-c946dfafc7fa/jobs/12114]
> on trunk, which hits 18 failures in 500 iterations. The config for CircleCI
> was generated with:
> {code}
> .circleci/generate.sh -m \
> -e REPEATED_UTEST_TARGET=test-jvm-dtest-some \
> -e REPEATED_UTEST_COUNT=500 \
> -e
> REPEATED_UTEST_CLASS=org.apache.cassandra.distributed.test.RepairErrorsTest
> {code}
> This was discovered while testing CASSANDRA-16878, on [this CI
> run|https://app.circleci.com/pipelines/github/adelapena/cassandra/1268/workflows/aef1c703-c816-40f8-8e07-9055027d6403/jobs/12000].
> The error consists on a failed assertion when grepping the logs in search of
> an error message.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17144) Fix test TestHintedHandoff#test_hintedhandoff_window
[
https://issues.apache.org/jira/browse/CASSANDRA-17144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-17144:
Reviewers: Caleb Rackliffe
> Fix test TestHintedHandoff#test_hintedhandoff_window
>
>
> Key: CASSANDRA-17144
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17144
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: David Capwell
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.x
>
>
> This test fails from time to time (see butler
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/hintedhandoff_test/TestHintedHandoff/test_hintedhandoff_window)
> Example:
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/1101/workflows/7afb1c7e-8330-4ac6-963d-d7864282f2f3/jobs/7877
> {code}
> # Ensure second and third datasets are not present
> for x in range(100, 300):
> > query_c1c2(session, x, ConsistencyLevel.ONE,
> > tolerate_missing=True, must_be_missing=True)
> hintedhandoff_test.py:264:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> tools/data.py:44: in query_c1c2
> assertions.assert_length_equal(rows, 0)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> object_with_length = [Row(c1='value1', c2='value2')], expected_length = 0
> def assert_length_equal(object_with_length, expected_length):
> """
> Assert an object has a specific length.
> @param object_with_length The object whose length will be checked
> @param expected_length The expected length of the object
>
> Examples:
> assert_length_equal(res, nb_counter)
> """
> assert len(object_with_length) == expected_length, \
> "Expected {} to have length {}, but instead is of length {}"\
> > .format(object_with_length, expected_length,
> > len(object_with_length))
> E AssertionError: Expected [Row(c1='value1', c2='value2')] to have
> length 0, but instead is of length 1
> tools/assertions.py:269: AssertionError
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16765) Update Cassandra build CI script for new website
[ https://issues.apache.org/jira/browse/CASSANDRA-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16765: --- Mentor: Michael Semb Wever Status: Review In Progress (was: Patch Available) > Update Cassandra build CI script for new website > > > Key: CASSANDRA-16765 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16765 > Project: Cassandra > Issue Type: Task > Components: Build, CI, Documentation/Website >Reporter: Anthony Grasso >Assignee: Michael Semb Wever >Priority: Normal > > Update the apache/cassandra-build repository has [.groovy job > script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy] > to use the new tooling to build the website. > The apache/cassandra-build repository has [.groovy job > script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy]. > It [builds and deploys the > website|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L1255-L1268] > to cassandra-website staging when the cassandra-website is updated. > We need to change the commands in the .groovy script to at least rebuild the > site when a change happens in the cassandra-website repository. > It would be also good to build the docs when a change happens to doc/source > directory in the cassandra repository. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17335) Fix race condition bug during local session repair
[
https://issues.apache.org/jira/browse/CASSANDRA-17335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANDRA-17335:
--
Summary: Fix race condition bug during local session repair (was: Flaky
testNoSuchRepairSessionAnticompaction)
> Fix race condition bug during local session repair
> --
>
> Key: CASSANDRA-17335
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17335
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Bernardo Botella Corbi
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
> Attachments:
> 0001-Fix-Flaky-testNoSuchRepairSessionAnticompaction-trunk.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The in-JVM dtest {{RepairErrorsTest#testNoSuchRepairSessionAnticompaction}}
> seems to be flaky, as it's shown by [this repeated
> run|https://app.circleci.com/pipelines/github/adelapena/cassandra/1280/workflows/8a4e04cb-64cc-46a3-9e1e-c946dfafc7fa/jobs/12114]
> on trunk, which hits 18 failures in 500 iterations. The config for CircleCI
> was generated with:
> {code}
> .circleci/generate.sh -m \
> -e REPEATED_UTEST_TARGET=test-jvm-dtest-some \
> -e REPEATED_UTEST_COUNT=500 \
> -e
> REPEATED_UTEST_CLASS=org.apache.cassandra.distributed.test.RepairErrorsTest
> {code}
> This was discovered while testing CASSANDRA-16878, on [this CI
> run|https://app.circleci.com/pipelines/github/adelapena/cassandra/1268/workflows/aef1c703-c816-40f8-8e07-9055027d6403/jobs/12000].
> The error consists on a failed assertion when grepping the logs in search of
> an error message.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17404) Return windows_timer_interval to Config
[ https://issues.apache.org/jira/browse/CASSANDRA-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned CASSANDRA-17404: - Assignee: Stefan Miklosovic > Return windows_timer_interval to Config > > > Key: CASSANDRA-17404 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17404 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.x > > > _windows_timer_interval_ was removed from Config in CASSANDRA-16956 > Considering trunk is still considered to be released 4.1 and not 5, we need > to deprecate this parameter with a note in NEWS.txt that it is just a > placeholder, to prevent breaking upgrades. > When we bump to 5.0, we can revise this decision again. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17404) Return windows_timer_interval to Config
[ https://issues.apache.org/jira/browse/CASSANDRA-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501078#comment-17501078 ] Ekaterina Dimitrova commented on CASSANDRA-17404: - Ping [~stefan.miklosovic] > Return windows_timer_interval to Config > > > Key: CASSANDRA-17404 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17404 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > _windows_timer_interval_ was removed from Config in CASSANDRA-16956 > Considering trunk is still considered to be released 4.1 and not 5, we need > to deprecate this parameter with a note in NEWS.txt that it is just a > placeholder, to prevent breaking upgrades. > When we bump to 5.0, we can revise this decision again. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17246) DOCS - Update changed config + JVM, guide post CASSANDRA-15234
[ https://issues.apache.org/jira/browse/CASSANDRA-17246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501077#comment-17501077 ] Ekaterina Dimitrova edited comment on CASSANDRA-17246 at 3/3/22, 11:20 PM: --- I think I did the bigger part of the docs [here|https://github.com/ekaterinadimitrova2/cassandra/commit/246c3b605e9693c69588b26be8df05bcb4d7082d]. For sure I need to polish this language :) I still want to proof-read things and check for any details I might have missed but I wanted to share it already to see whether there are general concerns around structure, sections, etc. CC [~mck] and [~maedhroz] in case you have some time to skim through it and give some feedback. Thanks was (Author: e.dimitrova): I think I did the bigger part of the docs [here|https://github.com/ekaterinadimitrova2/cassandra/commit/246c3b605e9693c69588b26be8df05bcb4d7082d] I still want to proof-read things and check for any details I might have missed but I wanted to share it already to see whether there are general concerns around structure, sections, etc. CC [~mck] and [~maedhroz] in case you have some time to skim through it and give some feedback. Thanks > DOCS - Update changed config + JVM, guide post CASSANDRA-15234 > -- > > Key: CASSANDRA-17246 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17246 > Project: Cassandra > Issue Type: Task > Components: Documentation/NEWS.txt, Documentation/Website >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > When CASSANDRA-15234 gets committed we need to update everywhere in the docs > the changed parameters names and we need to document: > * new types > * guide how to add new parameters > * some information about the backward compatibility network > Possibly missing some bullets, to be considered while doing the actual work. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17246) DOCS - Update changed config + JVM, guide post CASSANDRA-15234
[ https://issues.apache.org/jira/browse/CASSANDRA-17246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501077#comment-17501077 ] Ekaterina Dimitrova commented on CASSANDRA-17246: - I think I did the bigger part of the docs [here|https://github.com/ekaterinadimitrova2/cassandra/commit/246c3b605e9693c69588b26be8df05bcb4d7082d] I still want to proof-read things and check for any details I might have missed but I wanted to share it already to see whether there are general concerns around structure, sections, etc. CC [~mck] and [~maedhroz] in case you have some time to skim through it and give some feedback. Thanks > DOCS - Update changed config + JVM, guide post CASSANDRA-15234 > -- > > Key: CASSANDRA-17246 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17246 > Project: Cassandra > Issue Type: Task > Components: Documentation/NEWS.txt, Documentation/Website >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > When CASSANDRA-15234 gets committed we need to update everywhere in the docs > the changed parameters names and we need to document: > * new types > * guide how to add new parameters > * some information about the backward compatibility network > Possibly missing some bullets, to be considered while doing the actual work. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17144) Fix test TestHintedHandoff#test_hintedhandoff_window
[
https://issues.apache.org/jira/browse/CASSANDRA-17144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic reassigned CASSANDRA-17144:
-
Assignee: Stefan Miklosovic
> Fix test TestHintedHandoff#test_hintedhandoff_window
>
>
> Key: CASSANDRA-17144
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17144
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: David Capwell
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.x
>
>
> This test fails from time to time (see butler
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/hintedhandoff_test/TestHintedHandoff/test_hintedhandoff_window)
> Example:
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/1101/workflows/7afb1c7e-8330-4ac6-963d-d7864282f2f3/jobs/7877
> {code}
> # Ensure second and third datasets are not present
> for x in range(100, 300):
> > query_c1c2(session, x, ConsistencyLevel.ONE,
> > tolerate_missing=True, must_be_missing=True)
> hintedhandoff_test.py:264:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> tools/data.py:44: in query_c1c2
> assertions.assert_length_equal(rows, 0)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> object_with_length = [Row(c1='value1', c2='value2')], expected_length = 0
> def assert_length_equal(object_with_length, expected_length):
> """
> Assert an object has a specific length.
> @param object_with_length The object whose length will be checked
> @param expected_length The expected length of the object
>
> Examples:
> assert_length_equal(res, nb_counter)
> """
> assert len(object_with_length) == expected_length, \
> "Expected {} to have length {}, but instead is of length {}"\
> > .format(object_with_length, expected_length,
> > len(object_with_length))
> E AssertionError: Expected [Row(c1='value1', c2='value2')] to have
> length 0, but instead is of length 1
> tools/assertions.py:269: AssertionError
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17413) Remove unused imports
[ https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501074#comment-17501074 ] Brandon Williams commented on CASSANDRA-17413: -- I think we should leave the rest to different tickets, there's no need to block this one. > Remove unused imports > - > > Key: CASSANDRA-17413 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17413 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python3 no longer requires the import of unicode_literals from futures. This > and a few other unused imports, should be removed. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17144) Fix test TestHintedHandoff#test_hintedhandoff_window
[
https://issues.apache.org/jira/browse/CASSANDRA-17144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501071#comment-17501071
]
Caleb Rackliffe commented on CASSANDRA-17144:
-
[~stefan.miklosovic] Any chance this is related to the CASSANDRA-14309 changes?
> Fix test TestHintedHandoff#test_hintedhandoff_window
>
>
> Key: CASSANDRA-17144
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17144
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: David Capwell
>Priority: Normal
> Fix For: 4.x
>
>
> This test fails from time to time (see butler
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/hintedhandoff_test/TestHintedHandoff/test_hintedhandoff_window)
> Example:
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/1101/workflows/7afb1c7e-8330-4ac6-963d-d7864282f2f3/jobs/7877
> {code}
> # Ensure second and third datasets are not present
> for x in range(100, 300):
> > query_c1c2(session, x, ConsistencyLevel.ONE,
> > tolerate_missing=True, must_be_missing=True)
> hintedhandoff_test.py:264:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> tools/data.py:44: in query_c1c2
> assertions.assert_length_equal(rows, 0)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> object_with_length = [Row(c1='value1', c2='value2')], expected_length = 0
> def assert_length_equal(object_with_length, expected_length):
> """
> Assert an object has a specific length.
> @param object_with_length The object whose length will be checked
> @param expected_length The expected length of the object
>
> Examples:
> assert_length_equal(res, nb_counter)
> """
> assert len(object_with_length) == expected_length, \
> "Expected {} to have length {}, but instead is of length {}"\
> > .format(object_with_length, expected_length,
> > len(object_with_length))
> E AssertionError: Expected [Row(c1='value1', c2='value2')] to have
> length 0, but instead is of length 1
> tools/assertions.py:269: AssertionError
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17413) Remove unused imports
[ https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501066#comment-17501066 ] Brad Schoening commented on CASSANDRA-17413: [~smiklosovic] sure thing, I've fixed most of the above. Resolving profile_on/off and timedelta require some more careful consideration but we're down to 4 issues with pyflake now. Note that PyCharm flags dozens more problems. > Remove unused imports > - > > Key: CASSANDRA-17413 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17413 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python3 no longer requires the import of unicode_literals from futures. This > and a few other unused imports, should be removed. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17413) Remove unused imports
[ https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501066#comment-17501066 ] Brad Schoening edited comment on CASSANDRA-17413 at 3/3/22, 10:36 PM: -- [~smiklosovic] sure thing, I've fixed most of the above. Resolving profile_on/off and timedelta require some more careful consideration but we're down to 4 issues with pyflake now. Note that PyCharm flags dozens more problems. I'd like to do this in bite sized chunks, but we also need to replace old-style six conventions with PY3 ones. was (Author: bschoeni): [~smiklosovic] sure thing, I've fixed most of the above. Resolving profile_on/off and timedelta require some more careful consideration but we're down to 4 issues with pyflake now. Note that PyCharm flags dozens more problems. > Remove unused imports > - > > Key: CASSANDRA-17413 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17413 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python3 no longer requires the import of unicode_literals from futures. This > and a few other unused imports, should be removed. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17187) Guardrail for SELECT IN terms and their cartesian product
[
https://issues.apache.org/jira/browse/CASSANDRA-17187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501022#comment-17501022
]
Ekaterina Dimitrova commented on CASSANDRA-17187:
-
Overall looks good to me, left just two nits and 2 questions for quick
confirmation of my understanding.
CI also LGTM. Thanks!
> Guardrail for SELECT IN terms and their cartesian product
> -
>
> Key: CASSANDRA-17187
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17187
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Labels: lhf
> Fix For: 4.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add a guardrail to limit the number restrictions generated by the cartesian
> product of the {{IN}} restrictions of a {{SELECT}} query, for example:
> {code}
> # Guardrail to warn or abort when IN query creates a cartesian product with a
> # size exceeding threshold, eg. "a in (1,2,...10) and b in (1,2...10)"
> results in
> # cartesian product of 100.
> # The two thresholds default to -1 to disable.
> in_select_cartesian_product:
> warn_threshold: -1
> abort_threshold: -1
> {code}
> As an example of why this guardrails is proposed, these queries bring a C*
> instance to its knees even before the query starts executing:
> {code}
> @Test
> public void testPartitionKeyTerms() throws Throwable
> {
> createTable("CREATE TABLE %s (pk1 int, pk2 int, pk3 int, pk4 int, pk5
> int, pk6 int, pk7 int, pk8 int, pk9 int, " +
>"PRIMARY KEY((pk1, pk2, pk3, pk4, pk5, pk6, pk7, pk8, pk9)))");
> execute("SELECT * FROM %s WHERE pk1 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND pk2 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND pk3 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND pk4 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND pk5 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND pk6 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND pk7 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND pk8 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND pk9 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10);");
> }
> @Test
> public void testClusteringKeyTerms() throws Throwable
> {
> createTable("CREATE TABLE %s (pk int ,ck1 int, ck2 int, ck3 int, ck4 int,
> ck5 int, ck6 int, ck7 int, ck8 int, ck9 int, " +
> "PRIMARY KEY(pk, ck1, ck2, ck3, ck4, ck5, ck6, ck7, ck8, ck9))");
> execute("SELECT * FROM %s WHERE pk = 1 " +
> "AND ck1 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND ck2 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND ck3 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND ck4 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND ck5 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND ck6 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND ck7 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND ck8 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) " +
> "AND ck9 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10);");
> }
> {code}
> +Additional information for newcomers:+
> # Add the configuration for the new guardrail on cartesian product in the
> guardrails section of cassandra.yaml.
> # Add a {{getInCartesianProduct}} method in {{GuardrailsConfig}} returning a
> {{Threshold.Config}} object
> # Implement that method in {{GuardrailsOptions}}, which is the default
> yaml-based implementation of {{GuardrailsConfig}}
> # Add a Threshold guardrail named {{inCartesianProduct}} in Guardrails, using
> the previously created config
> # Define JMX-friendly getters and setters for the previously created config
> in {{GuardrailsMBean}}
> # Implement the JMX-friendly getters and setters in Guardrails
> # Now that we have the guardrail ready, it’s time to use it. We should search
> for a place to invoke the Guardrails#inCartesianProduct guard method. The
> {{MultiCBuilder}} look like good candidates for this.
> # Finally, add some tests for the new guardrail. Given that the new guardrail
> is a Threshold, our new test should probably extend {{ThresholdTester}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17402) Unshared heap size excluding data calculation is broken
[ https://issues.apache.org/jira/browse/CASSANDRA-17402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500965#comment-17500965 ] Jacek Lewandowski commented on CASSANDRA-17402: --- Thanks [~adelapena], I've applied your comment and created trunk PR, also started CI. https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/184/workflows/9250c6e7-fb12-420b-b2c2-867f3fbe2ef3 https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/184/workflows/354e0996-9070-43f7-8e08-fa8720725c9a https://github.com/apache/cassandra/pull/1479/files > Unshared heap size excluding data calculation is broken > --- > > Key: CASSANDRA-17402 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17402 > Project: Cassandra > Issue Type: Bug > Components: Local/Memtable >Reporter: Jacek Lewandowski >Assignee: Jacek Lewandowski >Priority: Normal > Fix For: 4.1, 4.0.x > > Time Spent: 50m > Remaining Estimate: 0h > > Unshared heap size excluding data calculation is broken. > For example, it does not takes into consideration whether the buffers are > on-heap or off-heap - empty offheap buffer is 64-bytes while empty heap > buffer is 48-bytes. > It matters especially when we have offheap buffers-based memtables. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17151) Guardrail for column size
[
https://issues.apache.org/jira/browse/CASSANDRA-17151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña reassigned CASSANDRA-17151:
-
Assignee: (was: Andres de la Peña)
> Guardrail for column size
> -
>
> Key: CASSANDRA-17151
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17151
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
>
> Add a guardrail for limiting the max size of column values, for example:
> {code}
> # Failure threshold to prevent writing large column values.
> # Defaults to -1 to disable.
> column_value_size_failure_threshold_in_kb: -1
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17197) Diagnostic events for guardrails
[ https://issues.apache.org/jira/browse/CASSANDRA-17197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña updated CASSANDRA-17197: -- Change Category: Operability Complexity: Normal Status: Open (was: Triage Needed) > Diagnostic events for guardrails > > > Key: CASSANDRA-17197 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17197 > Project: Cassandra > Issue Type: New Feature > Components: Feature/Guardrails >Reporter: Andres de la Peña >Assignee: Andres de la Peña >Priority: Normal > > Add diagnostic events for guardrails, so we can monitor when each type of > guardrail is triggered. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17197) Diagnostic events for guardrails
[ https://issues.apache.org/jira/browse/CASSANDRA-17197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña reassigned CASSANDRA-17197: - Assignee: Andres de la Peña > Diagnostic events for guardrails > > > Key: CASSANDRA-17197 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17197 > Project: Cassandra > Issue Type: New Feature > Components: Feature/Guardrails >Reporter: Andres de la Peña >Assignee: Andres de la Peña >Priority: Normal > > Add diagnostic events for guardrails, so we can monitor when each type of > guardrail is triggered. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17415) dropping of a materialized view does not create a snapshot with dropped- prefix
[ https://issues.apache.org/jira/browse/CASSANDRA-17415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17415: -- Bug Category: Parent values: Correctness(12982) Complexity: Low Hanging Fruit Discovered By: Adhoc Test Severity: Low Status: Open (was: Triage Needed) > dropping of a materialized view does not create a snapshot with dropped- > prefix > --- > > Key: CASSANDRA-17415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17415 > Project: Cassandra > Issue Type: Bug > Components: Feature/Materialized Views >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.11.x > > > When auto_snapshot: true and MV is dropped, the name of the snapshot does not > start with "dropped-" prefix as a normal table would. This is an issue for > 3.11.x only. In 4.x, the code was refactored a lot and it does not happen > there. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17413) Remove unused imports
[ https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17413: -- Status: Changes Suggested (was: Ready to Commit) > Remove unused imports > - > > Key: CASSANDRA-17413 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17413 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python3 no longer requires the import of unicode_literals from futures. This > and a few other unused imports, should be removed. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17413) Remove unused imports
[
https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500917#comment-17500917
]
Stefan Miklosovic commented on CASSANDRA-17413:
---
[~bschoeni]
could you spend more time on this, please? I used "pyflakes" (installed by pip)
against the sources and this is what I got:
{code}
$ pyflakes .
./copyutil.py:53:1 'cassandra.cqltypes.BytesType' imported but unused
./copyutil.py:58:1 redefinition of unused 'profile_on' from line 44
./copyutil.py:58:1 redefinition of unused 'profile_off' from line 44
./copyutil.py:204:30 undefined name 'errno'
./tracing.py:17:1 'datetime.timedelta' imported but unused
./cqlhandling.py:118:13 local variable 'str_token' is assigned to but never used
./test/test_cqlsh_output.py:405:13 'pytz' imported but unused
./test/ansi_colors.py:153:9 local variable 'oldclr' is assigned to but never
used
./test/__init__.py:17:1 '.cassconnect.create_db' imported but unused
./test/__init__.py:17:1 '.cassconnect.remove_db' imported but unused
{code}
this is against cqlsh.py
{code}
$ pyflakes cqlsh.py
cqlsh.py:141:1 'cassandra.metadata.protect_name' imported but unused
cqlsh.py:141:1 'cassandra.metadata.protect_names' imported but unused
cqlsh.py:153:1 'cqlshlib.cqlhandling' imported but unused
cqlsh.py:157:1 'cqlshlib.formatting.formatter_for' imported but unused
cqlsh.py:161:1 'cqlshlib.util.trim_if_present' imported but unused
cqlsh.py:259:17 '...'.format(...) has unused arguments at position(s): 0, 1
{code}
Would be nice if we took more in-depth approach here!
> Remove unused imports
> -
>
> Key: CASSANDRA-17413
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17413
> Project: Cassandra
> Issue Type: Task
> Components: CQL/Interpreter
>Reporter: Brad Schoening
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.x
>
>
> Python3 no longer requires the import of unicode_literals from futures. This
> and a few other unused imports, should be removed.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17413) Remove unused imports
[ https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500878#comment-17500878 ] Stefan Miklosovic commented on CASSANDRA-17413: --- [~bschoeni] could you double check this whole import is useless there? It seems like it is not only about unicode_literals but two other imports are not used anywhere ... from __future__ import division, unicode_literals, print_function > Remove unused imports > - > > Key: CASSANDRA-17413 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17413 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python3 no longer requires the import of unicode_literals from futures. This > and a few other unused imports, should be removed. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17413) Remove unused imports
[ https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500861#comment-17500861 ] Brad Schoening edited comment on CASSANDRA-17413 at 3/3/22, 4:33 PM: - This should include bin/cqlsh.py which imports unicode_litterals also was (Author: bschoeni): I should include bin/cqlsh.py also > Remove unused imports > - > > Key: CASSANDRA-17413 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17413 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python3 no longer requires the import of unicode_literals from futures. This > and a few other unused imports, should be removed. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17413) Remove unused imports
[ https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500861#comment-17500861 ] Brad Schoening commented on CASSANDRA-17413: I should include bin/cqlsh.py also > Remove unused imports > - > > Key: CASSANDRA-17413 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17413 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python3 no longer requires the import of unicode_literals from futures. This > and a few other unused imports, should be removed. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17413) Remove unused imports
[ https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17413: - Status: Review In Progress (was: Needs Committer) > Remove unused imports > - > > Key: CASSANDRA-17413 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17413 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python3 no longer requires the import of unicode_literals from futures. This > and a few other unused imports, should be removed. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17413) Remove unused imports
[ https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17413: - Status: Ready to Commit (was: Review In Progress) > Remove unused imports > - > > Key: CASSANDRA-17413 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17413 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python3 no longer requires the import of unicode_literals from futures. This > and a few other unused imports, should be removed. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17413) Remove unused imports
[ https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500860#comment-17500860 ] Brandon Williams commented on CASSANDRA-17413: -- +1 > Remove unused imports > - > > Key: CASSANDRA-17413 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17413 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python3 no longer requires the import of unicode_literals from futures. This > and a few other unused imports, should be removed. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17413) Remove unused imports
[ https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17413: -- Status: Needs Committer (was: Review In Progress) > Remove unused imports > - > > Key: CASSANDRA-17413 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17413 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python3 no longer requires the import of unicode_literals from futures. This > and a few other unused imports, should be removed. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17413) Remove unused imports
[ https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500851#comment-17500851 ] Stefan Miklosovic commented on CASSANDRA-17413: --- [https://app.circleci.com/pipelines/github/instaclustr/cassandra/777/workflows/544b0994-210c-4523-a478-42a8c46894a1] https://github.com/instaclustr/cassandra/tree/CASSANDRA-17413 > Remove unused imports > - > > Key: CASSANDRA-17413 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17413 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python3 no longer requires the import of unicode_literals from futures. This > and a few other unused imports, should be removed. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17413) Remove unused imports
[ https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500851#comment-17500851 ] Stefan Miklosovic edited comment on CASSANDRA-17413 at 3/3/22, 4:05 PM: [https://app.circleci.com/pipelines/github/instaclustr/cassandra/777/workflows/544b0994-210c-4523-a478-42a8c46894a1] [https://github.com/instaclustr/cassandra/tree/CASSANDRA-17413] lgtm +1 was (Author: smiklosovic): [https://app.circleci.com/pipelines/github/instaclustr/cassandra/777/workflows/544b0994-210c-4523-a478-42a8c46894a1] https://github.com/instaclustr/cassandra/tree/CASSANDRA-17413 > Remove unused imports > - > > Key: CASSANDRA-17413 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17413 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python3 no longer requires the import of unicode_literals from futures. This > and a few other unused imports, should be removed. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17415) dropping of a materialized view does not create a snapshot with dropped- prefix
[ https://issues.apache.org/jira/browse/CASSANDRA-17415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17415: -- Description: When auto_snapshot: true and MV is dropped, the name of the snapshot does not start with "dropped-" prefix as a normal table would. This is an issue for 3.11.x only. In 4.x, the code was refactored a lot and it does not happen there. (was: When auto_snapshot: true and MV is dropped, the name of the snapshot does not start with "dropped-" prefix as a normal table would. This is an issue for 3.11.x only.) > dropping of a materialized view does not create a snapshot with dropped- > prefix > --- > > Key: CASSANDRA-17415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17415 > Project: Cassandra > Issue Type: Bug > Components: Feature/Materialized Views >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.11.x > > > When auto_snapshot: true and MV is dropped, the name of the snapshot does not > start with "dropped-" prefix as a normal table would. This is an issue for > 3.11.x only. In 4.x, the code was refactored a lot and it does not happen > there. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17415) dropping of a materialized view does not create a snapshot with dropped- prefix
[ https://issues.apache.org/jira/browse/CASSANDRA-17415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned CASSANDRA-17415: - Assignee: Stefan Miklosovic > dropping of a materialized view does not create a snapshot with dropped- > prefix > --- > > Key: CASSANDRA-17415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17415 > Project: Cassandra > Issue Type: Bug > Components: Feature/Materialized Views >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.11.x > > > When auto_snapshot: true and MV is dropped, the name of the snapshot does not > start with "dropped-" prefix as a normal table would. This is an issue for > 3.11.x only. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17415) dropping of a materialized view does not create a snapshot with dropped- prefix
Stefan Miklosovic created CASSANDRA-17415: - Summary: dropping of a materialized view does not create a snapshot with dropped- prefix Key: CASSANDRA-17415 URL: https://issues.apache.org/jira/browse/CASSANDRA-17415 Project: Cassandra Issue Type: Bug Components: Feature/Materialized Views Reporter: Stefan Miklosovic When auto_snapshot: true and MV is dropped, the name of the snapshot does not start with "dropped-" prefix as a normal table would. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17415) dropping of a materialized view does not create a snapshot with dropped- prefix
[ https://issues.apache.org/jira/browse/CASSANDRA-17415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17415: -- Description: When auto_snapshot: true and MV is dropped, the name of the snapshot does not start with "dropped-" prefix as a normal table would. This is an issue for 3.11.x only. (was: When auto_snapshot: true and MV is dropped, the name of the snapshot does not start with "dropped-" prefix as a normal table would.) > dropping of a materialized view does not create a snapshot with dropped- > prefix > --- > > Key: CASSANDRA-17415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17415 > Project: Cassandra > Issue Type: Bug > Components: Feature/Materialized Views >Reporter: Stefan Miklosovic >Priority: Normal > Fix For: 3.11.x > > > When auto_snapshot: true and MV is dropped, the name of the snapshot does not > start with "dropped-" prefix as a normal table would. This is an issue for > 3.11.x only. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17415) dropping of a materialized view does not create a snapshot with dropped- prefix
[ https://issues.apache.org/jira/browse/CASSANDRA-17415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17415: -- Fix Version/s: 3.11.x > dropping of a materialized view does not create a snapshot with dropped- > prefix > --- > > Key: CASSANDRA-17415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17415 > Project: Cassandra > Issue Type: Bug > Components: Feature/Materialized Views >Reporter: Stefan Miklosovic >Priority: Normal > Fix For: 3.11.x > > > When auto_snapshot: true and MV is dropped, the name of the snapshot does not > start with "dropped-" prefix as a normal table would. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15832) Typo in website documentation for file "mvs.rst"
[
https://issues.apache.org/jira/browse/CASSANDRA-15832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500824#comment-17500824
]
Stefan Miklosovic commented on CASSANDRA-15832:
---
[~polandll] do you think this might be closed?
> Typo in website documentation for file "mvs.rst"
> -
>
> Key: CASSANDRA-15832
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15832
> Project: Cassandra
> Issue Type: Bug
> Components: Documentation/Website
>Reporter: Tajinder Singh
>Assignee: Lorina Poland
>Priority: Normal
>
> It appears that there is a typo in the doc for mvs.rst file. Please refer
> this link -
> [https://cassandra.apache.org/doc/latest/cql/mvs.html#drop-materialized-view]
> _Current sentence in doc:_
> "Dropping a materialized view {color:#de350b}*users* {color}the DROP
> MATERIALIZED VIEW statement:"
> _Expected sentence in doc:_
> "Dropping a materialized view {color:#00875a}*using* {color}the DROP
> MATERIALIZED VIEW statement:"
> _Patch for proposed fix:_
> [https://github.com/tsingh2k15/cassandra/commit/1a56c295843bd74f2e856c01fa76a4676875dc7c]
>
> Please review and let me know if this patch can be accepted as a fix?
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17402) Unshared heap size excluding data calculation is broken
[ https://issues.apache.org/jira/browse/CASSANDRA-17402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500725#comment-17500725 ] Andres de la Peña commented on CASSANDRA-17402: --- [~jlewandowski] it looks good, could you please prepare a PR for trunk? There could be some divergence there due to CASSANDRA-16896. > Unshared heap size excluding data calculation is broken > --- > > Key: CASSANDRA-17402 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17402 > Project: Cassandra > Issue Type: Bug > Components: Local/Memtable >Reporter: Jacek Lewandowski >Assignee: Jacek Lewandowski >Priority: Normal > Fix For: 4.1, 4.0.x > > Time Spent: 0.5h > Remaining Estimate: 0h > > Unshared heap size excluding data calculation is broken. > For example, it does not takes into consideration whether the buffers are > on-heap or off-heap - empty offheap buffer is 64-bytes while empty heap > buffer is 48-bytes. > It matters especially when we have offheap buffers-based memtables. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17413) Remove unused imports
[ https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17413: -- Status: Review In Progress (was: Patch Available) > Remove unused imports > - > > Key: CASSANDRA-17413 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17413 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python3 no longer requires the import of unicode_literals from futures. This > and a few other unused imports, should be removed. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17413) Remove unused imports
[ https://issues.apache.org/jira/browse/CASSANDRA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17413: -- Reviewers: Brandon Williams, Stefan Miklosovic (was: Brandon Williams) > Remove unused imports > - > > Key: CASSANDRA-17413 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17413 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python3 no longer requires the import of unicode_literals from futures. This > and a few other unused imports, should be removed. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17334) Pre hashed passwords in CQL
[
https://issues.apache.org/jira/browse/CASSANDRA-17334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500700#comment-17500700
]
Bowen Song commented on CASSANDRA-17334:
Are the algorithms proprietary? If not, you should be able to implement them in
Python using other libraries, such as cryptography
([https://pypi.org/project/cryptography/]) which is licensed under the Apache
Software License.
> Pre hashed passwords in CQL
> ---
>
> Key: CASSANDRA-17334
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17334
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Authorization
>Reporter: Berenguer Blasi
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.1
>
> Attachments: cqlsh.diff
>
>
> As seen on CASSANDRA-16801 and friends we are working across the system with
> plain text passwords. These can be unintentionally revealed by intermediate
> systems. Allowing the use of hashed passwords should mitigate that. The idea
> is to add a new option {{HASHED PASSWORD}} for {{CREATE/ALTER ROLE/USER}}.
> Examples:
> {noformat}
> CREATE ROLE foo WITH login = true AND hashed password =
> '$2a$10$JSJEMFm6GeaW9XxT5JIheuEtPvat6i7uKbnTcxX3c1wshIIsGyUtG';
> ALTER ROLE foo WITH hashed password =
> '$2a$10$JSJEMFm6GeaW9XxT5JIheuEtPvat6i7uKbnTcxX3c1wshIIsGyUtG';
> {noformat}
> To generate the password hash, there will be a new tool {{hash_password}} in
> resources/cassandra/bin
> Based on original works from [~snazy]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17402) Unshared heap size excluding data calculation is broken
[ https://issues.apache.org/jira/browse/CASSANDRA-17402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña updated CASSANDRA-17402: -- Reviewers: Andres de la Peña, Branimir Lambov, Andres de la Peña (was: Andres de la Peña, Branimir Lambov) Andres de la Peña, Branimir Lambov, Andres de la Peña (was: Andres de la Peña, Branimir Lambov) Status: Review In Progress (was: Patch Available) > Unshared heap size excluding data calculation is broken > --- > > Key: CASSANDRA-17402 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17402 > Project: Cassandra > Issue Type: Bug > Components: Local/Memtable >Reporter: Jacek Lewandowski >Assignee: Jacek Lewandowski >Priority: Normal > Fix For: 4.1, 4.0.x > > Time Spent: 20m > Remaining Estimate: 0h > > Unshared heap size excluding data calculation is broken. > For example, it does not takes into consideration whether the buffers are > on-heap or off-heap - empty offheap buffer is 64-bytes while empty heap > buffer is 48-bytes. > It matters especially when we have offheap buffers-based memtables. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17406) WEBSITE - March 2022 blog "Apache Cassandra Changelog #13"
[
https://issues.apache.org/jira/browse/CASSANDRA-17406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500683#comment-17500683
]
Erick Ramirez commented on CASSANDRA-17406:
---
I've completed final verification in staging and [published to
production|https://github.com/apache/cassandra-website#merging-asf-staging-to-asf-site]:
{noformat}
$ git branch
* trunk
$ git fetch origin
$ git checkout asf-site
Branch 'asf-site' set up to track remote branch 'asf-site' from 'origin'.
Switched to a new branch 'asf-site'
$ git branch
* asf-site
trunk
$ git reset --hard origin/asf-staging
HEAD is now at 93cf40c8 generate docs for c39b688e
$ git push -f origin asf-site
Username for 'https://github.com': erickramirezau
Password for 'https://erickramire...@github.com':
Total 0 (delta 0), reused 0 (delta 0)
To https://github.com/apache/cassandra-website.git
+ bb9a39d2...93cf40c8 asf-site -> asf-site (forced update)
{noformat}
The blog post is now live at
https://cassandra.apache.org/_/blog/Apache-Cassandra-Changelog-13-March-2022.html.
> WEBSITE - March 2022 blog "Apache Cassandra Changelog #13"
> --
>
> Key: CASSANDRA-17406
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17406
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Chris Thornett
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
> Attachments: c17406-01-blog-index.png, c17406-02-blog-post.png
>
>
> This ticket is to capture the work associated with publishing the March 2022
> changelog blog #13
> If this blog cannot be published by the *March 3, 2022 publish date*, please
> contact me, suggest changes, or correct the date when possible in the pull
> request for the appropriate time that the blog will go live (on both the
> blog.adoc and the blog post's file).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-site updated (bb9a39d -> 93cf40c)
This is an automated email from the ASF dual-hosted git repository.
erickramirezau pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git.
discard bb9a39d generate docs for 2c535052
add c39b688 March 2022 blog post "Apache Cassandra Changelog # 13"
add 93cf40c generate docs for c39b688e
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 (bb9a39d)
\
N -- N -- N refs/heads/asf-site (93cf40c)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
content/_/_images/blog/SAI-channel.PNG | Bin 0 -> 413167 bytes
content/_/blog.html| 24 +
... Apache-Cassandra-Changelog-13-March-2022.html} | 119 +
content/search-index.js| 2 +-
.../modules/ROOT/images/blog/SAI-channel.PNG | Bin 0 -> 413167 bytes
site-content/source/modules/ROOT/pages/blog.adoc | 25 +
.../Apache-Cassandra-Changelog-13-March-2022.adoc | 111 +++
site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078
bytes
8 files changed, 238 insertions(+), 43 deletions(-)
create mode 100644 content/_/_images/blog/SAI-channel.PNG
copy content/_/blog/{Apache-Cassandra-Changelog-12-February-2022.html =>
Apache-Cassandra-Changelog-13-March-2022.html} (59%)
create mode 100644 site-content/source/modules/ROOT/images/blog/SAI-channel.PNG
create mode 100644
site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-13-March-2022.adoc
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17414) Block usage of Instant.now()
[ https://issues.apache.org/jira/browse/CASSANDRA-17414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500682#comment-17500682 ] Benedict Elliott Smith commented on CASSANDRA-17414: +1 > Block usage of Instant.now() > > > Key: CASSANDRA-17414 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17414 > Project: Cassandra > Issue Type: Bug > Components: Build >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 4.x > > > After CEP-10 we should avoid using Instant.now() -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15266) java internal exception on attempt to UPDATE a row using CONTAINS operator
[
https://issues.apache.org/jira/browse/CASSANDRA-15266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500681#comment-17500681
]
Andres de la Peña commented on CASSANDRA-15266:
---
The failures of {{test_sstableloader_empty_stream}} in 4.0 on the above runs
are due to missing the changes recently introduced by CASSANDRA-17367, they go
away after rebasing. Here is a final CI round after rebasing without conflicts:
||PR||CI||
|[3.0|https://github.com/apache/cassandra/pull/1458]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1330/workflows/836a5035-4a8f-4197-9e08-60358792e5ba]|
|[3.11|https://github.com/apache/cassandra/pull/1472]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1329/workflows/da76f88f-5896-4902-ad5c-274437f09c35]|
|[4.0|https://github.com/apache/cassandra/pull/1473]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1331/workflows/beb36191-3029-4a5d-9cb7-cfbe78336cbe]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1331/workflows/41ba8047-debb-4f4f-b34f-846fba4e277b]|
|[trunk|https://github.com/apache/cassandra/pull/1474]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1332/workflows/eee3f571-809c-4bee-acb9-25c4ad21424a]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1332/workflows/c0323446-6fcf-4263-9961-36698baa7f53]|
Unless there is any surprise in these runs, changes look good to me, +1.
> java internal exception on attempt to UPDATE a row using CONTAINS operator
> --
>
> Key: CASSANDRA-15266
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15266
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/CQL
>Reporter: Konstantin
>Assignee: Maciej Sokol
>Priority: Normal
> Labels: lhf
> Fix For: 3.0.x, 3.11.x, 4.0.x
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> kostja@atlas ~ % cqlsh -ucassandra -pcassandra
> Connected to My Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 3.11.4 | CQL spec 3.4.4 | Native protocol v4]
> Use HELP for help.
> cassandra@cqlsh> CREATE KEYSPACE t1 WITH replication =
> \{'class':'SimpleStrategy', 'replication_factor' : 1};
> cassandra@cqlsh> use t1;
> cassandra@cqlsh:t1> create table t (a int, b frozen>, c int,
> primary key (a, b));
> cassandra@cqlsh:t1> insert into t (a, b, c) values (1, \{1:1, 2:2}, 3);
> cassandra@cqlsh:t1> update t set c=3 where a=1 and b contains 1;
> ServerError: java.lang.UnsupportedOperationException
>
> Server log file:
> ```
> ERROR [Native-Transport-Requests-1] 2019-08-07 17:02:59,283
> QueryMessage.java:129 - Unexpected error during query
> java.lang.UnsupportedOperationException: null
> at
> org.apache.cassandra.cql3.restrictions.SingleColumnRestriction$ContainsRestriction.appendTo(SingleColumnRestriction.java:454)
> ~[a
> pache-cassandra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.cql3.restrictions.ClusteringColumnRestrictions.valuesAsClustering(ClusteringColumnRestrictions.java:109)
> ~[a
> pache-cassandra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.cql3.restrictions.StatementRestrictions.getClusteringColumns(StatementRestrictions.java:770)
> ~[apache-cassan
> dra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.createClustering(ModificationStatement.java:312)
> ~[apache-cassandra-3.
> 11.4.jar:3.11.4]
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.addUpdates(ModificationStatement.java:677)
> ~[apache-cassandra-3.11.4.j
> ar:3.11.4]
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.getMutations(ModificationStatement.java:635)
> ~[apache-cassandra-3.11.4
> .jar:3.11.4]
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithoutCondition(ModificationStatement.java:437)
> ~[apache-cassa
> ndra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:425)
> ~[apache-cassandra-3.11.4.jar:
> 3.11.4]
> at
> org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:225)
> ~[apache-cassandra-3.11.4.jar:3.11.4]
> at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:256)
> ~[apache-cassandra-3.11.4.jar:3.11.4]
> at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:241)
> ~[apache-cassandra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.transport.messages.QueryMessage.execute(QueryMessage.java:116)
> ~[apache-cassandra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:566)
> [apache-cassandra-3.11.4.jar:3.11.4]
> at
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:410)
>
[jira] [Commented] (CASSANDRA-17406) WEBSITE - March 2022 blog "Apache Cassandra Changelog #13"
[ https://issues.apache.org/jira/browse/CASSANDRA-17406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500680#comment-17500680 ] Erick Ramirez commented on CASSANDRA-17406: --- CI/Jenkins [build #159|https://ci-cassandra.apache.org/job/cassandra-website/159/] completed and the blog post is now live on staging – https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-Changelog-13-March-2022.html. > WEBSITE - March 2022 blog "Apache Cassandra Changelog #13" > -- > > Key: CASSANDRA-17406 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17406 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Chris Thornett >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: c17406-01-blog-index.png, c17406-02-blog-post.png > > > This ticket is to capture the work associated with publishing the March 2022 > changelog blog #13 > If this blog cannot be published by the *March 3, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (bb9a39d -> 93cf40c)
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git.
omit bb9a39d generate docs for 2c535052
add c39b688 March 2022 blog post "Apache Cassandra Changelog # 13"
new 93cf40c generate docs for c39b688e
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 (bb9a39d)
\
N -- N -- N refs/heads/asf-staging (93cf40c)
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/_/_images/blog/SAI-channel.PNG | Bin 0 -> 413167 bytes
content/_/blog.html| 24 +
... Apache-Cassandra-Changelog-13-March-2022.html} | 119 +
content/search-index.js| 2 +-
.../modules/ROOT/images/blog/SAI-channel.PNG | Bin 0 -> 413167 bytes
site-content/source/modules/ROOT/pages/blog.adoc | 25 +
.../Apache-Cassandra-Changelog-13-March-2022.adoc | 111 +++
site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078
bytes
8 files changed, 238 insertions(+), 43 deletions(-)
create mode 100644 content/_/_images/blog/SAI-channel.PNG
copy content/_/blog/{Apache-Cassandra-Changelog-12-February-2022.html =>
Apache-Cassandra-Changelog-13-March-2022.html} (59%)
create mode 100644 site-content/source/modules/ROOT/images/blog/SAI-channel.PNG
create mode 100644
site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-13-March-2022.adoc
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17334) Pre hashed passwords in CQL
[
https://issues.apache.org/jira/browse/CASSANDRA-17334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500661#comment-17500661
]
Berenguer Blasi edited comment on CASSANDRA-17334 at 3/3/22, 11:09 AM:
---
Well,
the PR is up. Some shadows and some lights though. I managed to pin down 2
unrelated nasty bugs which is good. I managed to make the thing work which is
good also.
The problem comes from the cqlsh command. I got onto that path and I am
attaching a diff of the hash command currently just clearing the screen so I
don't loose that bit of code. Server side hash is done with jBcrypt. It does
have a py port which is just a wrapper to C code. The problem is that jBcrypt
and pyBcrypt have difference licenses, the py one not being friendly to us
after checking with some PMC members and
([link|https://www.apache.org/legal/resolved.html]) because of the advertising
clause to start with. Hence we have no py lib and the alternative would be to
call some java code. This takes us back to square 1 where we don't have a
self-contained nice command solution.
I need to explore more the hash py lib side of things and licenses. We could
replace both server and client with a new lib that supports more languages.
That would be a bit like future proofing for future hashing needs which seems
like a good idea. The problem being upgrade scenarios where we'd have to
support both hash versions, old and new, at some point. All this is well beyond
what I wanted to do in this ticket and too much of a big-bang change for my
taste if it can be avoided.
The plain text passwords path remains untouched, this will all be opt-in, it's
an improvement to the current state, we fix some bugs and doesn't block future
development. So I would get this ticket done as a first step and open a new one
for the other work . I don't have any better ideas so far.
was (Author: bereng):
Well,
the PR is up. Some shadows and some lights though. I managed to pin down 2
unrelated nasty bugs which is good. I managed to make the thing work which is
good also.
The problem comes from the cqlsh command. I got onto that path and I am
attaching a diff of the hash command currently just clearing the screen so I
don't loose that bit of code. Server side hash is done with jBcrypt. It does
have a py port which is just a wrapper to C code. The problem is that jBcrypt
and pyBcrypt have difference licenses, the py one not being friendly to us
after checking with some PMC members and
([link|https://www.apache.org/legal/resolved.html]) because of the advertising
clause to start with. Hence we have no py lib and the alternative would be to
call some java code. This takes us back to square 1 where we don't have a
self-contained nice command solution.
I need to explore more the hash py lib side of things and licenses. We could
replace both server and client with a new lib that supports more languages.
That would be a bit like future proofing for future hashing needs which seems
like a good idea. The problem being upgrade scenarios where we'd have to
support both hash versions, old and new, at some point. All this is well beyond
what I wanted to do in this ticket and too much of a big-bang change for my
taste if it can be avoided.
The plain text passwords path remains untouched, this will all be opt-in, it's
an improvement to the current state, we fix some bugs and doesn't block future
development. So I would get this ticket done as a first step and open a new one
for the other work .
> Pre hashed passwords in CQL
> ---
>
> Key: CASSANDRA-17334
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17334
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Authorization
>Reporter: Berenguer Blasi
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.1
>
> Attachments: cqlsh.diff
>
>
> As seen on CASSANDRA-16801 and friends we are working across the system with
> plain text passwords. These can be unintentionally revealed by intermediate
> systems. Allowing the use of hashed passwords should mitigate that. The idea
> is to add a new option {{HASHED PASSWORD}} for {{CREATE/ALTER ROLE/USER}}.
> Examples:
> {noformat}
> CREATE ROLE foo WITH login = true AND hashed password =
> '$2a$10$JSJEMFm6GeaW9XxT5JIheuEtPvat6i7uKbnTcxX3c1wshIIsGyUtG';
> ALTER ROLE foo WITH hashed password =
> '$2a$10$JSJEMFm6GeaW9XxT5JIheuEtPvat6i7uKbnTcxX3c1wshIIsGyUtG';
> {noformat}
> To generate the password hash, there will be a new tool {{hash_password}} in
> resources/cassandra/bin
> Based on original works from [~snazy]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail:
[jira] [Commented] (CASSANDRA-17334) Pre hashed passwords in CQL
[
https://issues.apache.org/jira/browse/CASSANDRA-17334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500661#comment-17500661
]
Berenguer Blasi commented on CASSANDRA-17334:
-
Well,
the PR is up. Some shadows and some lights though. I managed to pin down 2
unrelated nasty bugs which is good. I managed to make the thing work which is
good also.
The problem comes from the cqlsh command. I got onto that path and I am
attaching a diff of the hash command currently just clearing the screen so I
don't loose that bit of code. Server side hash is done with jBcrypt. It does
have a py port which is just a wrapper to C code. The problem is that jBcrypt
and pyBcrypt have difference licenses, the py one not being friendly to us
after checking with some PMC members and
([link|https://www.apache.org/legal/resolved.html]) because of the advertising
clause to start with. Hence we have no py lib and the alternative would be to
call some java code. This takes us back to square 1 where we don't have a
self-contained nice command solution.
I need to explore more the hash py lib side of things and licenses. We could
replace both server and client with a new lib that supports more languages.
That would be a bit like future proofing for future hashing needs which seems
like a good idea. The problem being upgrade scenarios where we'd have to
support both hash versions, old and new, at some point. All this is well beyond
what I wanted to do in this ticket and too much of a big-bang change for my
taste if it can be avoided.
The plain text passwords path remains untouched, this will all be opt-in, it's
an improvement to the current state, we fix some bugs and doesn't block future
development. So I would get this ticket done as a first step and open a new one
for the other work .
> Pre hashed passwords in CQL
> ---
>
> Key: CASSANDRA-17334
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17334
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Authorization
>Reporter: Berenguer Blasi
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.1
>
> Attachments: cqlsh.diff
>
>
> As seen on CASSANDRA-16801 and friends we are working across the system with
> plain text passwords. These can be unintentionally revealed by intermediate
> systems. Allowing the use of hashed passwords should mitigate that. The idea
> is to add a new option {{HASHED PASSWORD}} for {{CREATE/ALTER ROLE/USER}}.
> Examples:
> {noformat}
> CREATE ROLE foo WITH login = true AND hashed password =
> '$2a$10$JSJEMFm6GeaW9XxT5JIheuEtPvat6i7uKbnTcxX3c1wshIIsGyUtG';
> ALTER ROLE foo WITH hashed password =
> '$2a$10$JSJEMFm6GeaW9XxT5JIheuEtPvat6i7uKbnTcxX3c1wshIIsGyUtG';
> {noformat}
> To generate the password hash, there will be a new tool {{hash_password}} in
> resources/cassandra/bin
> Based on original works from [~snazy]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17406) WEBSITE - March 2022 blog "Apache Cassandra Changelog #13"
[ https://issues.apache.org/jira/browse/CASSANDRA-17406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17406: -- Source Control Link: https://github.com/apache/cassandra-website/commit/c39b688e9c7c9fd27c6b7320c5da0f2f1f19b745 Resolution: Fixed Status: Resolved (was: Ready to Commit) Merged as [c39b688|https://github.com/apache/cassandra-website/commit/c39b688e9c7c9fd27c6b7320c5da0f2f1f19b745]. > WEBSITE - March 2022 blog "Apache Cassandra Changelog #13" > -- > > Key: CASSANDRA-17406 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17406 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Chris Thornett >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: c17406-01-blog-index.png, c17406-02-blog-post.png > > > This ticket is to capture the work associated with publishing the March 2022 > changelog blog #13 > If this blog cannot be published by the *March 3, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch trunk updated: March 2022 blog post "Apache Cassandra Changelog # 13"
This is an automated email from the ASF dual-hosted git repository. erickramirezau pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra-website.git The following commit(s) were added to refs/heads/trunk by this push: new c39b688 March 2022 blog post "Apache Cassandra Changelog # 13" c39b688 is described below commit c39b688e9c7c9fd27c6b7320c5da0f2f1f19b745 Author: Diogenese Topper AuthorDate: Mon Feb 28 17:45:15 2022 -0800 March 2022 blog post "Apache Cassandra Changelog # 13" patch by Chris Thornett, Diogenese Topper; reviewed by Erick Ramirez for CASSANDRA-17406 --- .../modules/ROOT/images/blog/SAI-channel.PNG | Bin 0 -> 413167 bytes site-content/source/modules/ROOT/pages/blog.adoc | 25 + .../Apache-Cassandra-Changelog-13-March-2022.adoc | 111 + 3 files changed, 136 insertions(+) diff --git a/site-content/source/modules/ROOT/images/blog/SAI-channel.PNG b/site-content/source/modules/ROOT/images/blog/SAI-channel.PNG new file mode 100644 index 000..d7f38d8 Binary files /dev/null and b/site-content/source/modules/ROOT/images/blog/SAI-channel.PNG differ diff --git a/site-content/source/modules/ROOT/pages/blog.adoc b/site-content/source/modules/ROOT/pages/blog.adoc index 9aa11e9..7c88ef5 100644 --- a/site-content/source/modules/ROOT/pages/blog.adoc +++ b/site-content/source/modules/ROOT/pages/blog.adoc @@ -14,6 +14,31 @@ NOTES FOR CONTENT CREATORS [openblock,card-header] -- [discrete] +=== Apache Cassandra Changelog #13 +[discrete] + March 3, 2022 +-- +[openblock,card-content] +-- +A new patch is released for all supported versions to address a known vulnerability, we celebrate three new committers, and see SAI and other CEP features approved. + +[openblock,card-btn card-btn--blog] + + +[.btn.btn--alt] +xref:blog/Apache-Cassandra-Changelog-13-March-2022.adoc[Read More] + + +-- + +//end card + +//start card +[openblock,card shadow relative test] + +[openblock,card-header] +-- +[discrete] === Java SE 11 LTS and Apache Cassandra [discrete] February 24, 2022 diff --git a/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-13-March-2022.adoc b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-13-March-2022.adoc new file mode 100644 index 000..54c8310 --- /dev/null +++ b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-Changelog-13-March-2022.adoc @@ -0,0 +1,111 @@ += Apache Cassandra Changelog #13 +:page-layout: single-post +:page-role: blog-post +:page-post-date: March 3, 2022 +:page-post-author: The Apache Cassandra Community +:description: The Apache Cassandra Community +:keywords: + +image::blog/changelog_header.jpg[Apache Cassandra Changelog] +Our monthly roundup of key activities and knowledge to keep the community informed. + +== Release Notes + +=== Released + +The latest release of Apache Cassandra is https://www.apache.org/dyn/closer.lua/cassandra/4.0.3/apache-cassandra-4.0.3-bin.tar.gz[4.0.3^] (https://downloads.apache.org/cassandra/4.0.3/apache-cassandra-4.0.3-bin.tar.gz.asc[pgp^], https://downloads.apache.org/cassandra/4.0.3/apache-cassandra-4.0.3-bin.tar.gz.sha256[sha256^], and https://downloads.apache.org/cassandra/4.0.3/apache-cassandra-4.0.3-bin.tar.gz.sha512[sha512^]), which has been available since 17 February 2022. We released new v [...] + +Essentially, if you're running Cassandra in the following non-default configuration, below, it's possible for an attacker to execute arbitrary code on the host: + +``` +enable_user_defined_functions: true +enable_scripted_user_defined_functions: true +enable_user_defined_functions_threads: false +``` + +The attacker also needs permission to create user-defined functions as well as this configuration arrangement. + +We suggest 3.0 users should upgrade to 3.0.26; 3.11 users should upgrade to 3.11.12; and 4.0 users should upgrade to 4.0.3. + +Thanks to Omer Kaspi of the JFrog Security vulnerability research team for the discovery. + +Please read the https://github.com/apache/cassandra/blob/cassandra-4.0/NEWS.txt[release notes^] and https://issues.apache.org/jira/browse/CASSANDRA[let us know^] if you encounter any problems. + +Note: As the docs are not yet updated, the bintray location for Debian users is replaced with the https://apache.jfrog.io/artifactory/cassandra/[ASF's JFrog Artifactory location^]. + +See the xref:download.adoc[download section] for the latest stable and older supported versions of source and binary distributions. + +To stay up-to-date, we recommend joining the Cassandra xref:community.adoc#discussions[mailing lists]. + +== Community Notes + +_Updates on Cassandra Enhancement Proposals (CEPs), how to contribute, and other community activities._ + +_Are you new to the project? We have a handy xref:development/index.adoc[‘Contributing to Cassandra’] page for how to get involved and get
[jira] [Updated] (CASSANDRA-17334) Pre hashed passwords in CQL
[
https://issues.apache.org/jira/browse/CASSANDRA-17334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-17334:
Attachment: cqlsh.diff
> Pre hashed passwords in CQL
> ---
>
> Key: CASSANDRA-17334
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17334
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Authorization
>Reporter: Berenguer Blasi
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.1
>
> Attachments: cqlsh.diff
>
>
> As seen on CASSANDRA-16801 and friends we are working across the system with
> plain text passwords. These can be unintentionally revealed by intermediate
> systems. Allowing the use of hashed passwords should mitigate that. The idea
> is to add a new option {{HASHED PASSWORD}} for {{CREATE/ALTER ROLE/USER}}.
> Examples:
> {noformat}
> CREATE ROLE foo WITH login = true AND hashed password =
> '$2a$10$JSJEMFm6GeaW9XxT5JIheuEtPvat6i7uKbnTcxX3c1wshIIsGyUtG';
> ALTER ROLE foo WITH hashed password =
> '$2a$10$JSJEMFm6GeaW9XxT5JIheuEtPvat6i7uKbnTcxX3c1wshIIsGyUtG';
> {noformat}
> To generate the password hash, there will be a new tool {{hash_password}} in
> resources/cassandra/bin
> Based on original works from [~snazy]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17414) Block usage of Instant.now()
[ https://issues.apache.org/jira/browse/CASSANDRA-17414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-17414: Test and Documentation Plan: cci run Status: Patch Available (was: Open) https://github.com/apache/cassandra/pull/1477 https://app.circleci.com/pipelines/github/krummas/cassandra/784/workflows/e0879aae-d97a-4eaf-ac32-e205133a6f7c > Block usage of Instant.now() > > > Key: CASSANDRA-17414 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17414 > Project: Cassandra > Issue Type: Bug > Components: Build >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 4.x > > > After CEP-10 we should avoid using Instant.now() -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17414) Block usage of Instant.now()
[ https://issues.apache.org/jira/browse/CASSANDRA-17414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-17414: Reviewers: Benedict Elliott Smith > Block usage of Instant.now() > > > Key: CASSANDRA-17414 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17414 > Project: Cassandra > Issue Type: Bug > Components: Build >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 4.x > > > After CEP-10 we should avoid using Instant.now() -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17414) Block usage of Instant.now()
[ https://issues.apache.org/jira/browse/CASSANDRA-17414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-17414: Bug Category: Parent values: Code(13163)Level 1 values: Bug - Unclear Impact(13164) Complexity: Low Hanging Fruit Component/s: Build Discovered By: Code Inspection Fix Version/s: 4.x Severity: Low Status: Open (was: Triage Needed) > Block usage of Instant.now() > > > Key: CASSANDRA-17414 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17414 > Project: Cassandra > Issue Type: Bug > Components: Build >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 4.x > > > After CEP-10 we should avoid using Instant.now() -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17414) Block usage of Instant.now()
Marcus Eriksson created CASSANDRA-17414: --- Summary: Block usage of Instant.now() Key: CASSANDRA-17414 URL: https://issues.apache.org/jira/browse/CASSANDRA-17414 Project: Cassandra Issue Type: Bug Reporter: Marcus Eriksson Assignee: Marcus Eriksson After CEP-10 we should avoid using Instant.now() -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
