[jira] [Updated] (CASSANDRA-17823) WEBSITE – in-tree trunk should be marked as `prerelease: true`

[Michael Semb Wever (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Semb Wever updated CASSANDRA-17823:
---
Reviewers: Michael Semb Wever, Michael Semb Wever
   Michael Semb Wever, Michael Semb Wever  (was: Michael Semb Wever)
   Status: Review In Progress  (was: Patch Available)

> WEBSITE – in-tree trunk should be marked as `prerelease: true`
> --
>
> Key: CASSANDRA-17823
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17823
> Project: Cassandra
>  Issue Type: Bug
>  Components: Documentation/Website
>Reporter: Michael Semb Wever
>Assignee: Milan Krisko
>Priority: Normal
>  Labels: lhf
> Fix For: 4.x
>
>
> this will avoid the "A newer version of this documentation is available." 
> banner displaying on the version docs for our latest released version.
> ref: https://docs.antora.org/antora/latest/component-prerelease/#true
> change is to be applied to 
> https://github.com/apache/cassandra/blob/trunk/doc/antora.yml 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17613) Avoid getting hanging repairs due to repair message timeouts

[Marcus Eriksson (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584644#comment-17584644
 ] 

Marcus Eriksson commented on CASSANDRA-17613:
-

tests look fine, I'll get this committed once 4.0.6 has been released (so we 
can set the correct 4.0 since version (4.0.7-SNAPSHOT) without breaking the 
tests)

4.0: 
https://app.circleci.com/pipelines/github/krummas/cassandra/810/workflows/d2ee32db-cbeb-4741-a674-ca0b4f9b2a81
4.1: 
https://app.circleci.com/pipelines/github/krummas/cassandra/814/workflows/5d10dc0a-0359-4e10-89ef-d4f8f9b2a187
trunk: 
https://app.circleci.com/pipelines/github/krummas/cassandra/815/workflows/4f388b44-c478-4682-a17b-52a04f99a163

> Avoid getting hanging repairs due to repair message timeouts
> 
>
> Key: CASSANDRA-17613
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17613
> Project: Cassandra
>  Issue Type: Bug
>  Components: Consistency/Repair
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 4.0.x, 4.1-beta
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> In 4.0 repair messages can get expired before reaching a replica, this causes 
> repairs to hang.
> CASSANDRA-16909 is meant to fix this, but we need a stopgap fix in 4.0.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17856) Unable to Access Convenience Package Download Sites

[Ben Dalling (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584621#comment-17584621
 ] 

Ben Dalling commented on CASSANDRA-17856:
-

[~brandon.williams],

Thank you for raising the ticket with INFRA (I don't fully know my way around 
Apache Jira).  I can confirm all is now operating as expected.  Also if such a 
scenario arises again, I'll raise the ticket directly with the INFRA project.

Thank you again,

[~dallinb] 

> Unable to Access Convenience Package Download Sites
> ---
>
> Key: CASSANDRA-17856
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17856
> Project: Cassandra
>  Issue Type: Bug
>  Components: Packaging
>Reporter: Ben Dalling
>Priority: Normal
>
> The web addresses setup in CASSANDRA-17748 don't seem to be accessible.  The 
> specific download sites are:
>  * [https://redhat.cassandra.apache.org/]
>  * [https://debian.cassandra.apache.org|https://debian.cassandra.apache.org/]
> They were definitely working on the 16th of August (when I last ran a test 
> installation) but have been failing since at least 2022-08-22T07:24Z and are 
> still failing now.
> Attempting to access the raw [https://redhat.cassandra.apache.org/] results 
> in a connection timeout, but accessing the underlying 
> [https://apache.jfrog.io/ui/native/cassandra-rpm] works OK.
> These affected web addresses are also referred to in the installation 
> documentation at:
>  * 
> [https://cassandra.apache.org/doc/latest/cassandra/getting_started/installing.html#installing-the-rpm-packages]
>  * 
> [https://cassandra.apache.org/doc/latest/cassandra/getting_started/installing.html#installing-the-debian-packages]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra-website] branch asf-staging updated (f89baafc -> 84a9dfa9)

[git-site-role]

This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git


 discard f89baafc generate docs for 8cf784cf
 new 84a9dfa9 generate docs for 8cf784cf

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   (f89baafc)
\
 N -- N -- N   refs/heads/asf-staging (84a9dfa9)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17750) Remove dependency on Maven Ant Tasks

[David Capwell (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Capwell updated CASSANDRA-17750:
--
  Fix Version/s: 4.2
 (was: 4.x)
Source Control Link: 
https://github.com/apache/cassandra/commit/1e27ffc6aded5b54b0207b114b154cffbc64dda5
 Resolution: Fixed
 Status: Resolved  (was: Ready to Commit)

> Remove dependency on Maven Ant Tasks
> 
>
> Key: CASSANDRA-17750
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17750
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Build, Dependencies, Packaging
>Reporter: Abe Ratnofsky
>Assignee: Abe Ratnofsky
>Priority: Normal
> Fix For: 4.2
>
>  Time Spent: 10h 10m
>  Remaining Estimate: 0h
>
> Apache Cassandra depends on Maven Ant Tasks (MAT) during build, for declaring 
> dependencies and generating POM files from within build.xml. MAT has long 
> been retired (no commits since maintenance in 2015), has registered CVEs in 
> dependencies (CVE-2017-1000487), and encourages migration to its successor, 
> Maven Artifact Resolver Ant Tasks (MARAT).
> As part of CASSANDRA-16391 
> , mck migrated 
> dependency resolution to MARAT, but MAT is still included in our build for 
> generating POMs since MARAT does not have an alternative to the writepom task 
> provided by MAT. I have a patch ready that removes MAT completely, with a 
> workaround for POM generation.
> I am not advocating for any kind of migration away from Ant to an alternative 
> like Gradle or Maven, just to be extra clear.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] branch trunk updated: Remove dependency on Maven Ant Tasks

[dcapwell]

This is an automated email from the ASF dual-hosted git repository.

dcapwell pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git


The following commit(s) were added to refs/heads/trunk by this push:
 new 1e27ffc6ad Remove dependency on Maven Ant Tasks
1e27ffc6ad is described below

commit 1e27ffc6aded5b54b0207b114b154cffbc64dda5
Author: Abe Ratnofsky 
AuthorDate: Wed Aug 24 13:23:09 2022 -0700

Remove dependency on Maven Ant Tasks

patch by Abe Ratnofsky; reviewed by David Capwell, Michael Semb Wever for 
CASSANDRA-17750
---
 .build/build-resolver.xml|5 +-
 .build/cassandra-build-deps-template.xml |  127 
 .build/cassandra-deps-template.xml   |  344 ++
 .build/parent-pom-template.xml   | 1029 ++
 CHANGES.txt  |1 +
 build.xml|  492 +-
 6 files changed, 1533 insertions(+), 465 deletions(-)

diff --git a/.build/build-resolver.xml b/.build/build-resolver.xml
index f17ad23396..84311ade17 100644
--- a/.build/build-resolver.xml
+++ b/.build/build-resolver.xml
@@ -175,7 +175,8 @@
 
 
 
-
+
+
 
 
 
@@ -188,7 +189,7 @@
 
 
 
-
+
 
 
 
diff --git a/.build/cassandra-build-deps-template.xml 
b/.build/cassandra-build-deps-template.xml
new file mode 100644
index 00..727da9179a
--- /dev/null
+++ b/.build/cassandra-build-deps-template.xml
@@ -0,0 +1,127 @@
+
+
+http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd"; 
xmlns="http://maven.apache.org/POM/4.0.0";
+xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
+  4.0.0
+  
+cassandra-parent
+org.apache.cassandra
+@version@
+@final.n...@-parent.pom
+  
+  org.apache.cassandra
+  cassandra-build-deps
+  @version@
+  
+
+  junit
+  junit
+
+
+  commons-io
+  commons-io
+
+
+  org.mockito
+  mockito-core
+
+
+  org.ow2.asm
+  asm
+
+
+  org.ow2.asm
+  asm-tree
+
+
+  org.ow2.asm
+  asm-commons
+
+
+  org.ow2.asm
+  asm-util
+
+
+  com.google.jimfs
+  jimfs
+
+
+  com.puppycrawl.tools
+  checkstyle
+
+
+  org.quicktheories
+  quicktheories
+
+
+  org.reflections
+  reflections
+
+
+  com.google.code.java-allocation-instrumenter
+  java-allocation-instrumenter
+
+
+  org.apache.cassandra
+  dtest-api
+
+
+  org.openjdk.jmh
+  jmh-core
+
+
+  org.openjdk.jmh
+  jmh-generator-annprocess
+
+
+  net.ju-n.compile-command-annotations
+  compile-command-annotations
+
+
+  org.apache.ant
+  ant-junit
+
+
+  org.apache.cassandra
+  harry-core
+
+
+  org.junit
+  junit-bom
+  pom
+
+
+  org.awaitility
+  awaitility
+
+
+  org.hamcrest
+  hamcrest
+
+
+  org.jacoco
+  org.jacoco.agent
+
+
+  org.jacoco
+  org.jacoco.ant
+
+
+  com.fasterxml.jackson.dataformat
+  jackson-dataformat-yaml
+
+  
+
diff --git a/.build/cassandra-deps-template.xml 
b/.build/cassandra-deps-template.xml
new file mode 100644
index 00..513fcbc5aa
--- /dev/null
+++ b/.build/cassandra-deps-template.xml
@@ -0,0 +1,344 @@
+
+
+http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd"; 
xmlns="http://maven.apache.org/POM/4.0.0";
+xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
+  4.0.0
+  
+cassandra-parent
+org.apache.cassandra
+@version@
+@final.n...@-parent.pom
+  
+  org.apache.cassandra
+  cassandra-all
+  @version@
+  Apache Cassandra
+  The Apache Cassandra Project develops a highly scalable 
second-generation distributed database, bringing together Dynamo's fully 
distributed design and Bigtable's ColumnFamily-based data model.
+  https://cassandra.apache.org
+  2009
+  
+
+  The Apache Software License, Version 2.0
+  https://www.apache.org/licenses/LICENSE-2.0.txt
+
+  
+  
+
scm:https://gitbox.apache.org/repos/asf/cassandra.git
+
scm:https://gitbox.apache.org/repos/asf/cassandra.git
+https://gitbox.apache.org/repos/asf?p=cassandra.git;a=tree
+  
+  
+
+  org.xerial.snappy
+  snappy-java
+
+
+  org.lz4
+  lz4-java
+
+
+  com.ning
+  compress-lzf
+
+
+  com.google.guava
+  guava
+
+
+  commons-cli
+  commons-cli
+
+
+  commons-codec
+  commons-codec
+
+
+  org.apache.commons
+  commons-lang3
+
+
+  org.apache.commons
+  commons-math3
+
+
+  org.antlr
+  antlr
+
+
+  org.antlr
+  ST4
+
+
+  org.antlr
+  antlr-ru

[jira] [Updated] (CASSANDRA-17860) WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra"

[Diogenese Topper (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Diogenese Topper updated CASSANDRA-17860:
-
Status: Patch Available  (was: Open)

https://github.com/apache/cassandra-website/pull/168

> WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra"
> --
>
> Key: CASSANDRA-17860
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17860
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Diogenese Topper
>Priority: Normal
>  Labels: pull-request-available
>
> This ticket is to capture the work associated with publishing the August 2022 
> blog "Learn How CommitLog Works in Apache Cassandra"
> If this blog cannot be published by the *August 25, 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.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17860) WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra"

[Diogenese Topper (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584603#comment-17584603
 ] 

Diogenese Topper commented on CASSANDRA-17860:
--

Text reviewed, translated to .adoc format - need someone for final check in 
staging and commit.

> WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra"
> --
>
> Key: CASSANDRA-17860
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17860
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Diogenese Topper
>Priority: Normal
>  Labels: pull-request-available
>
> This ticket is to capture the work associated with publishing the August 2022 
> blog "Learn How CommitLog Works in Apache Cassandra"
> If this blog cannot be published by the *August 25, 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.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17860) WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra"

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated CASSANDRA-17860:
---
Labels: pull-request-available  (was: )

> WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra"
> --
>
> Key: CASSANDRA-17860
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17860
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Diogenese Topper
>Priority: Normal
>  Labels: pull-request-available
>
> This ticket is to capture the work associated with publishing the August 2022 
> blog "Learn How CommitLog Works in Apache Cassandra"
> If this blog cannot be published by the *August 25, 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.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17860) WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra"

[Diogenese Topper (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Diogenese Topper updated CASSANDRA-17860:
-
Status: Open  (was: Triage Needed)

> WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra"
> --
>
> Key: CASSANDRA-17860
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17860
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Diogenese Topper
>Priority: Normal
>  Labels: pull-request-available
>
> This ticket is to capture the work associated with publishing the August 2022 
> blog "Learn How CommitLog Works in Apache Cassandra"
> If this blog cannot be published by the *August 25, 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.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17860) WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra"

[Diogenese Topper (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Diogenese Topper updated CASSANDRA-17860:
-
Change Category: Semantic
 Complexity: Normal
Component/s: Documentation/Blog
Impacts: None,Docs  (was: None)
Test and Documentation Plan: 
Add blog post titled "Learn How CommitLog Works in Apache Cassandra"
Modify blog index page
Add images for blog: "Allocating and active segments.png", "Compressed Segment 
layout.png", "Dirty intervals.png", "Encrypted Segment layout.png", "Memtables 
and CommitLog.png", "Mmaped Segment layout.png", and "Segment layout.png"

> WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra"
> --
>
> Key: CASSANDRA-17860
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17860
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Blog
>Reporter: Diogenese Topper
>Priority: Normal
>
> This ticket is to capture the work associated with publishing the August 2022 
> blog "Learn How CommitLog Works in Apache Cassandra"
> If this blog cannot be published by the *August 25, 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.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-17860) WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra"

[Diogenese Topper (Jira)]

Diogenese Topper created CASSANDRA-17860:


 Summary: WEBSITE - August 2022 blog "Learn How CommitLog Works in 
Apache Cassandra"
 Key: CASSANDRA-17860
 URL: https://issues.apache.org/jira/browse/CASSANDRA-17860
 Project: Cassandra
  Issue Type: Task
Reporter: Diogenese Topper


This ticket is to capture the work associated with publishing the August 2022 
blog "Learn How CommitLog Works in Apache Cassandra"

If this blog cannot be published by the *August 25, 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.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra-website] branch asf-staging updated (e1fff187 -> f89baafc)

[git-site-role]

This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git


 discard e1fff187 generate docs for 8cf784cf
 new f89baafc generate docs for 8cf784cf

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   (e1fff187)
\
 N -- N -- N   refs/heads/asf-staging (f89baafc)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-17831) Add support in CQLSH for COPY FROM / TO in compact Parquet format

[Brad Schoening (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584560#comment-17584560
 ] 

Brad Schoening edited comment on CASSANDRA-17831 at 8/25/22 2:53 AM:
-

Let's benchmark it.  I'll run some tests with moderate to large data sets.  
Based upon the 
[Radečić|https://medium.com/@radecicdario?source=post_page-72c78a414d1d]
 article, he saw 80% reduction in disk space and 33X performance boost with 
parquet.  Of course, performance with Cassandra involves the DB latency as well 
so I'm not expecting performance to be as dramatic.

I'm on vacation for the next few weeks, but will run some tests upon my return.

 


was (Author: bschoeni):
Let's benchmark it.  I'll run some tests with moderate to large data sets.  
Based upon the 
[Radečić|https://medium.com/@radecicdario?source=post_page-72c78a414d1d]
 article, he saw 80% reduction in disk space and 33X performance boost with 
parquet.  Of course, performance with Cassandra involves the DB latency as well 
so I'm not expecting performance to be as dramatic.

I'm on vacation for the next few weeks, but will run some tests upon my return.

"{_}One accurate measurement is worth a thousand expert opinions{_}" – Grace 
Hopper

 

> Add support in CQLSH for COPY FROM / TO in compact Parquet format
> -
>
> Key: CASSANDRA-17831
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17831
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Tool/cqlsh
>Reporter: Brad Schoening
>Priority: Normal
>
> CQL supports only CSV as a format for import and export. A binary big data 
> format such as Avro and/or Parquet would be more compact and highly portable 
> to other platforms.
> Parquet does not require a schema, so it appears the easier format to support.
> The existing syntax supports adding key value pair options, such as FORMAT = 
> PARQUET
> {{     COPY table_name ... FROM 'file_name'[, 'file2_name', ...] }}
>                      {{[WITH option = 'value' [AND ...]]}}
> Side by side comparisons of CSV and Parquet show a 80% plus saving in disk 
> space.
> [https://towardsdatascience.com/csv-files-for-storage-no-thanks-theres-a-better-option-72c78a414d1d]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-17831) Add support in CQLSH for COPY FROM / TO in compact Parquet format

[Brad Schoening (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584560#comment-17584560
 ] 

Brad Schoening edited comment on CASSANDRA-17831 at 8/25/22 2:50 AM:
-

Let's benchmark it.  I'll run some tests with moderate to large data sets.  
Based upon the 
[Radečić|https://medium.com/@radecicdario?source=post_page-72c78a414d1d]
 article, he saw 80% reduction in disk space and 33X performance boost with 
parquet.  Of course, performance with Cassandra involves the DB latency as well 
so I'm not expecting performance to be as dramatic.

I'm on vacation for the next few weeks, but will run some tests upon my return.

"{_}One accurate measurement is worth a thousand expert opinions{_}" – Grace 
Hopper

 


was (Author: bschoeni):
Let's benchmark it.  I'll run some test with moderate to large data sets.  
Based upon the 
[Radečić|https://medium.com/@radecicdario?source=post_page-72c78a414d1d]
 article, he saw 80% reduction in disk space and 33X performance boost with 
parquet.  Of course, performance with Cassandra involves the DB latency as well 
so I'm not expecting performance to be as dramatic.

I'm on vacation for the next few weeks, but will run some tests upon my return.

"{_}One accurate measurement is worth a thousand expert opinions{_}" – Grace 
Hopper

 

> Add support in CQLSH for COPY FROM / TO in compact Parquet format
> -
>
> Key: CASSANDRA-17831
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17831
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Tool/cqlsh
>Reporter: Brad Schoening
>Priority: Normal
>
> CQL supports only CSV as a format for import and export. A binary big data 
> format such as Avro and/or Parquet would be more compact and highly portable 
> to other platforms.
> Parquet does not require a schema, so it appears the easier format to support.
> The existing syntax supports adding key value pair options, such as FORMAT = 
> PARQUET
> {{     COPY table_name ... FROM 'file_name'[, 'file2_name', ...] }}
>                      {{[WITH option = 'value' [AND ...]]}}
> Side by side comparisons of CSV and Parquet show a 80% plus saving in disk 
> space.
> [https://towardsdatascience.com/csv-files-for-storage-no-thanks-theres-a-better-option-72c78a414d1d]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-17831) Add support in CQLSH for COPY FROM / TO in compact Parquet format

[Brad Schoening (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584560#comment-17584560
 ] 

Brad Schoening edited comment on CASSANDRA-17831 at 8/25/22 2:49 AM:
-

Let's benchmark it.  I'll run some test with moderate to large data sets.  
Based upon the 
[Radečić|https://medium.com/@radecicdario?source=post_page-72c78a414d1d]
 article, he saw 80% reduction in disk space and 33X performance boost with 
parquet.  Of course, performance with Cassandra involves the DB latency as well 
so I'm not expecting performance to be as dramatic.

I'm on vacation for the next few weeks, but will run some tests upon my return.

"{_}One accurate measurement is worth a thousand expert opinions{_}" – Grace 
Hopper

 


was (Author: bschoeni):
Let's benchmark it.  I'll run some test with moderate to large data sets.  
Based upon the 
[Radečić|https://medium.com/@radecicdario?source=post_page-72c78a414d1d]
 article, he saw 80% reduction in disk space and 33X performance boost with 
parquet.  Of course, performance with Cassandra involves the DB latency as well 
as so I'm not expecting performance to be as dramatic.

I'm on vacation for the next few weeks, but will run some tests upon my return.

"{_}One accurate measurement is worth a thousand expert opinions{_}" – Grace 
Hopper

 

> Add support in CQLSH for COPY FROM / TO in compact Parquet format
> -
>
> Key: CASSANDRA-17831
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17831
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Tool/cqlsh
>Reporter: Brad Schoening
>Priority: Normal
>
> CQL supports only CSV as a format for import and export. A binary big data 
> format such as Avro and/or Parquet would be more compact and highly portable 
> to other platforms.
> Parquet does not require a schema, so it appears the easier format to support.
> The existing syntax supports adding key value pair options, such as FORMAT = 
> PARQUET
> {{     COPY table_name ... FROM 'file_name'[, 'file2_name', ...] }}
>                      {{[WITH option = 'value' [AND ...]]}}
> Side by side comparisons of CSV and Parquet show a 80% plus saving in disk 
> space.
> [https://towardsdatascience.com/csv-files-for-storage-no-thanks-theres-a-better-option-72c78a414d1d]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-17831) Add support in CQLSH for COPY FROM / TO in compact Parquet format

[Brad Schoening (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584560#comment-17584560
 ] 

Brad Schoening edited comment on CASSANDRA-17831 at 8/25/22 2:46 AM:
-

Let's benchmark it.  I'll run some test with moderate to large data sets.  
Based upon the 
[Radečić|https://medium.com/@radecicdario?source=post_page-72c78a414d1d]
 article, he saw 80% reduction in disk space and 33X performance boost with 
parquet.  Of course, performance with Cassandra involves the DB latency as well 
as so I'm not expecting performance to be as dramatic.

I'm on vacation for the next few weeks, but will run some tests upon my return.

"{_}One accurate measurement is worth a thousand expert opinions{_}" – Grace 
Hopper

 


was (Author: bschoeni):
Let's benchmark it.  I'll run some test with moderate to large data sets.  
Based upon the 
[Radečić|https://medium.com/@radecicdario?source=post_page-72c78a414d1d]
 article, he saw 80% reduction in disk space and 33X performance boost with 
parquet.  Of course, performance with Cassandra involves the DB latency as well 
as so I'm not expecting performance to be as dramatic.

I'm on vacation for the next few weeks, but will run some tests upon my return.

 

> Add support in CQLSH for COPY FROM / TO in compact Parquet format
> -
>
> Key: CASSANDRA-17831
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17831
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Tool/cqlsh
>Reporter: Brad Schoening
>Priority: Normal
>
> CQL supports only CSV as a format for import and export. A binary big data 
> format such as Avro and/or Parquet would be more compact and highly portable 
> to other platforms.
> Parquet does not require a schema, so it appears the easier format to support.
> The existing syntax supports adding key value pair options, such as FORMAT = 
> PARQUET
> {{     COPY table_name ... FROM 'file_name'[, 'file2_name', ...] }}
>                      {{[WITH option = 'value' [AND ...]]}}
> Side by side comparisons of CSV and Parquet show a 80% plus saving in disk 
> space.
> [https://towardsdatascience.com/csv-files-for-storage-no-thanks-theres-a-better-option-72c78a414d1d]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-17831) Add support in CQLSH for COPY FROM / TO in compact Parquet format

[Brad Schoening (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584560#comment-17584560
 ] 

Brad Schoening edited comment on CASSANDRA-17831 at 8/25/22 2:44 AM:
-

Let's benchmark it.  I'll run some test with moderate to large data sets.  
Based upon the 
[Radečić|https://medium.com/@radecicdario?source=post_page-72c78a414d1d]
 article, he saw 80% reduction in disk space and 33X performance boost with 
parquet.  Of course, performance with Cassandra involves the DB latency as well 
as so I'm not expecting performance to be as dramatic.

I'm on vacation for the next few weeks, but will run some tests upon my return.

 


was (Author: bschoeni):
Let's benchmark it.  I'll run some test with moderate to large data sets.  
Based upon the 
[Radečić|https://medium.com/@radecicdario?source=post_page-72c78a414d1d]
 article, he saw 80% reduction in disk space and 33X performance boost with 
parquet.

I'm on vacation for the next few weeks, but will run some tests upon my return.

 

> Add support in CQLSH for COPY FROM / TO in compact Parquet format
> -
>
> Key: CASSANDRA-17831
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17831
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Tool/cqlsh
>Reporter: Brad Schoening
>Priority: Normal
>
> CQL supports only CSV as a format for import and export. A binary big data 
> format such as Avro and/or Parquet would be more compact and highly portable 
> to other platforms.
> Parquet does not require a schema, so it appears the easier format to support.
> The existing syntax supports adding key value pair options, such as FORMAT = 
> PARQUET
> {{     COPY table_name ... FROM 'file_name'[, 'file2_name', ...] }}
>                      {{[WITH option = 'value' [AND ...]]}}
> Side by side comparisons of CSV and Parquet show a 80% plus saving in disk 
> space.
> [https://towardsdatascience.com/csv-files-for-storage-no-thanks-theres-a-better-option-72c78a414d1d]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17831) Add support in CQLSH for COPY FROM / TO in compact Parquet format

[Brad Schoening (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584560#comment-17584560
 ] 

Brad Schoening commented on CASSANDRA-17831:


Let's benchmark it.  I'll run some test with moderate to large data sets.  
Based upon the 
[Radečić|https://medium.com/@radecicdario?source=post_page-72c78a414d1d]
 article, he saw 80% reduction in disk space and 33X performance boost with 
parquet.

I'm on vacation for the next few weeks, but will run some tests upon my return.

 

> Add support in CQLSH for COPY FROM / TO in compact Parquet format
> -
>
> Key: CASSANDRA-17831
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17831
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Tool/cqlsh
>Reporter: Brad Schoening
>Priority: Normal
>
> CQL supports only CSV as a format for import and export. A binary big data 
> format such as Avro and/or Parquet would be more compact and highly portable 
> to other platforms.
> Parquet does not require a schema, so it appears the easier format to support.
> The existing syntax supports adding key value pair options, such as FORMAT = 
> PARQUET
> {{     COPY table_name ... FROM 'file_name'[, 'file2_name', ...] }}
>                      {{[WITH option = 'value' [AND ...]]}}
> Side by side comparisons of CSV and Parquet show a 80% plus saving in disk 
> space.
> [https://towardsdatascience.com/csv-files-for-storage-no-thanks-theres-a-better-option-72c78a414d1d]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17293) Update python test framework from nose to pytest

[Brad Schoening (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584554#comment-17584554
 ] 

Brad Schoening commented on CASSANDRA-17293:


[~e.dimitrova] the switch to pytest was quite easy.  I'm open to helping, but 
will be on vacation until mid September.

> Update python test framework from nose to pytest
> 
>
> Key: CASSANDRA-17293
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17293
> Project: Cassandra
>  Issue Type: Task
>  Components: CQL/Interpreter
>Reporter: Brad Schoening
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.1, 4.1-alpha1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> I had trouble trying to install and run the python nose test from pip 
> (nosetest not found).
> According to the homepage of nose at [https://nose.readthedocs.io/en/latest/]
> h1. _Note to Users_
> _Nose has been in maintenance mode for the past several years and will likely 
> cease without a new person/team to take over maintainership. New projects 
> should consider using [Nose2|https://github.com/nose-devs/nose2], 
> [py.test|http://pytest.org/], or just plain unittest/unittest2._
>  
> Upgrading to pytest is likely the least effort. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17823) WEBSITE – in-tree trunk should be marked as `prerelease: true`

[Milan Krisko (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Milan Krisko updated CASSANDRA-17823:
-
Test and Documentation Plan: Documentation update
 Status: Patch Available  (was: In Progress)

https://github.com/apache/cassandra/pull/1814

> WEBSITE – in-tree trunk should be marked as `prerelease: true`
> --
>
> Key: CASSANDRA-17823
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17823
> Project: Cassandra
>  Issue Type: Bug
>  Components: Documentation/Website
>Reporter: Michael Semb Wever
>Assignee: Milan Krisko
>Priority: Normal
>  Labels: lhf
> Fix For: 4.x
>
>
> this will avoid the "A newer version of this documentation is available." 
> banner displaying on the version docs for our latest released version.
> ref: https://docs.antora.org/antora/latest/component-prerelease/#true
> change is to be applied to 
> https://github.com/apache/cassandra/blob/trunk/doc/antora.yml 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] (CASSANDRA-17823) WEBSITE – in-tree trunk should be marked as `prerelease: true`

[Milan Krisko (Jira)]

[ https://issues.apache.org/jira/browse/CASSANDRA-17823 ]


Milan Krisko deleted comment on CASSANDRA-17823:
--

was (Author: JIRAUSER290146):
Created PR: https://github.com/apache/cassandra/pull/1814

> WEBSITE – in-tree trunk should be marked as `prerelease: true`
> --
>
> Key: CASSANDRA-17823
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17823
> Project: Cassandra
>  Issue Type: Bug
>  Components: Documentation/Website
>Reporter: Michael Semb Wever
>Assignee: Milan Krisko
>Priority: Normal
>  Labels: lhf
> Fix For: 4.x
>
>
> this will avoid the "A newer version of this documentation is available." 
> banner displaying on the version docs for our latest released version.
> ref: https://docs.antora.org/antora/latest/component-prerelease/#true
> change is to be applied to 
> https://github.com/apache/cassandra/blob/trunk/doc/antora.yml 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-17293) Update python test framework from nose to pytest

[Ekaterina Dimitrova (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584532#comment-17584532
 ] 

Ekaterina Dimitrova edited comment on CASSANDRA-17293 at 8/25/22 1:27 AM:
--

I noticed ccm still uses nose too and I have the same issue trying to run its 
tests locally. Anyone of you interested to migrate that one to pytest too?  :) 

Those tests do not run in CI and we do not have many ccm changes but it is good 
people to be able to run them locally before new commits.

[~bschoeni] ? [~yashLadha] ?


was (Author: e.dimitrova):
I noticed ccm still uses nose too and I have the same issue trying to run its 
tests locally. Anyone of you interested to migrate that one to pytest too?  :) 

Those tests do not run in CI and we do not have many ccm changes but it is good 
people to be able to run them locally before new commits.

> Update python test framework from nose to pytest
> 
>
> Key: CASSANDRA-17293
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17293
> Project: Cassandra
>  Issue Type: Task
>  Components: CQL/Interpreter
>Reporter: Brad Schoening
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.1, 4.1-alpha1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> I had trouble trying to install and run the python nose test from pip 
> (nosetest not found).
> According to the homepage of nose at [https://nose.readthedocs.io/en/latest/]
> h1. _Note to Users_
> _Nose has been in maintenance mode for the past several years and will likely 
> cease without a new person/team to take over maintainership. New projects 
> should consider using [Nose2|https://github.com/nose-devs/nose2], 
> [py.test|http://pytest.org/], or just plain unittest/unittest2._
>  
> Upgrading to pytest is likely the least effort. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17293) Update python test framework from nose to pytest

[Ekaterina Dimitrova (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584532#comment-17584532
 ] 

Ekaterina Dimitrova commented on CASSANDRA-17293:
-

I noticed ccm still uses nose too and I have the same issue trying to run its 
tests locally. Anyone of you interested to migrate that one to pytest too?  :) 

Those tests do not run in CI and we do not have many ccm changes but it is good 
people to be able to run them locally before new commits.

> Update python test framework from nose to pytest
> 
>
> Key: CASSANDRA-17293
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17293
> Project: Cassandra
>  Issue Type: Task
>  Components: CQL/Interpreter
>Reporter: Brad Schoening
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.1, 4.1-alpha1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> I had trouble trying to install and run the python nose test from pip 
> (nosetest not found).
> According to the homepage of nose at [https://nose.readthedocs.io/en/latest/]
> h1. _Note to Users_
> _Nose has been in maintenance mode for the past several years and will likely 
> cease without a new person/team to take over maintainership. New projects 
> should consider using [Nose2|https://github.com/nose-devs/nose2], 
> [py.test|http://pytest.org/], or just plain unittest/unittest2._
>  
> Upgrading to pytest is likely the least effort. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra-website] branch asf-staging updated (fa766dc2 -> e1fff187)

[git-site-role]

This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git


 discard fa766dc2 generate docs for 8cf784cf
 new e1fff187 generate docs for 8cf784cf

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   (fa766dc2)
\
 N -- N -- N   refs/heads/asf-staging (e1fff187)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 content/search-index.js |   2 +-
 site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes
 2 files changed, 1 insertion(+), 1 deletion(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17859) WEBSITE - Add guide for Asking Good Questions

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17859:
--
Reviewers:   (was: Bowen Song)

> WEBSITE - Add guide for Asking Good Questions
> -
>
> Key: CASSANDRA-17859
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17859
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: 4.0.x
>
>
> This is for publishing the guide to *Asking Good Questions* [proposed on the 
> Dev ML|https://lists.apache.org/thread/fnlzos2v78xmgxhz37xsskpdc30dl95l].
> The draft guide is [available 
> here|https://docs.google.com/document/d/1-ZYpl9tif9OAMdAxFLxA1mTPNp0zkNW4kzXvfvRBHUc/edit?usp=sharing].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17859) WEBSITE - Add guide for Asking Good Questions

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17859:
--
Change Category: Semantic
 Complexity: Normal
  Fix Version/s: 4.0.x
  Reviewers: Bowen Song
 Status: Open  (was: Triage Needed)

> WEBSITE - Add guide for Asking Good Questions
> -
>
> Key: CASSANDRA-17859
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17859
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: 4.0.x
>
>
> This is for publishing the guide to *Asking Good Questions* [proposed on the 
> Dev ML|https://lists.apache.org/thread/fnlzos2v78xmgxhz37xsskpdc30dl95l].
> The draft guide is [available 
> here|https://docs.google.com/document/d/1-ZYpl9tif9OAMdAxFLxA1mTPNp0zkNW4kzXvfvRBHUc/edit?usp=sharing].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17859) WEBSITE - Add guide for Asking Good Questions

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17859:
--
Authors: Bowen Song, Erick Ramirez  (was: Erick Ramirez)

> WEBSITE - Add guide for Asking Good Questions
> -
>
> Key: CASSANDRA-17859
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17859
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: 4.0.x
>
>
> This is for publishing the guide to *Asking Good Questions* [proposed on the 
> Dev ML|https://lists.apache.org/thread/fnlzos2v78xmgxhz37xsskpdc30dl95l].
> The draft guide is [available 
> here|https://docs.google.com/document/d/1-ZYpl9tif9OAMdAxFLxA1mTPNp0zkNW4kzXvfvRBHUc/edit?usp=sharing].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-17859) WEBSITE - Add guide for Asking Good Questions

[Erick Ramirez (Jira)]

Erick Ramirez created CASSANDRA-17859:
-

 Summary: WEBSITE - Add guide for Asking Good Questions
 Key: CASSANDRA-17859
 URL: https://issues.apache.org/jira/browse/CASSANDRA-17859
 Project: Cassandra
  Issue Type: Task
  Components: Documentation/Website
Reporter: Erick Ramirez
Assignee: Erick Ramirez


This is for publishing the guide to *Asking Good Questions* [proposed on the 
Dev ML|https://lists.apache.org/thread/fnlzos2v78xmgxhz37xsskpdc30dl95l].

The draft guide is [available 
here|https://docs.google.com/document/d/1-ZYpl9tif9OAMdAxFLxA1mTPNp0zkNW4kzXvfvRBHUc/edit?usp=sharing].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra-website] branch asf-staging updated (82fec7cc -> fa766dc2)

[git-site-role]

This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git


 discard 82fec7cc generate docs for 8cf784cf
 new fa766dc2 generate docs for 8cf784cf

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   (82fec7cc)
\
 N -- N -- N   refs/heads/asf-staging (fa766dc2)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 content/search-index.js |   2 +-
 site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes
 2 files changed, 1 insertion(+), 1 deletion(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-16656) Assertion Error on invalid ALTER TABLE Command

[Ekaterina Dimitrova (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584486#comment-17584486
 ] 

Ekaterina Dimitrova edited comment on CASSANDRA-16656 at 8/24/22 10:10 PM:
---

 [~atris], are you interested to investigate this one maybe? If not, I might 
take it for the Grace Hopper Conference :) Please let me know 


was (Author: e.dimitrova):
 [~atris], are you interested to investigate this one maybe? 

> Assertion Error on invalid ALTER TABLE Command
> --
>
> Key: CASSANDRA-16656
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16656
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL/Syntax
>Reporter: Norbert Schultz
>Priority: Low
> Fix For: 3.11.x
>
>
> If there is an invalid ALTER TABLE statement (extra comma), then Cassandra 
> responds with an assertion error.
>  
> This happens on 3.11.10 but not on 4.0-rc1
> This statement fails:
> {code:java}
> > cqlsh
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 3.11.10 | CQL spec 3.4.4 | Native protocol v4]
> Use HELP for help.
> cqlsh> CREATE KEYSPACE foo WITH REPLICATION = { 'class' : 'SimpleStrategy', 
> 'replication_factor' : 1 };
> cqlsh> use foo;
> cqlsh:foo> create table test(id INT, PRIMARY KEY(id));
> cqlsh:foo> alter table test ADD (x INT, y INT,);
> ServerError: java.lang.AssertionError
> {code}
> The following can be found inside the Log:
> {code}
> java.lang.AssertionError: null
>   at 
> org.apache.cassandra.cql3.statements.AlterTableStatementColumn.(AlterTableStatementColumn.java:36)
>  ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.cql3.Cql_Parser.alterTableStatement(Cql_Parser.java:5820)
>  ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.cql3.Cql_Parser.cqlStatement(Cql_Parser.java:628) 
> ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at org.apache.cassandra.cql3.CqlParser.cqlStatement(CqlParser.java:604) 
> ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at org.apache.cassandra.cql3.CqlParser.query(CqlParser.java:344) 
> ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.cql3.CQLFragmentParser.parseAnyUnhandled(CQLFragmentParser.java:76)
>  ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.cql3.QueryProcessor.parseStatement(QueryProcessor.java:589)
>  ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.cql3.QueryProcessor.getStatement(QueryProcessor.java:559)
>  ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:247) 
> ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:241) 
> ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.transport.messages.QueryMessage.execute(QueryMessage.java:116)
>  ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.transport.Message$Dispatcher.processRequest(Message.java:685)
>  [apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.transport.Message$Dispatcher.lambda$channelRead0$0(Message.java:591)
>  [apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_292]
>   at 
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
>  ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:113) 
> ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_292]
> {code}
> Cassandra 4.0-rc1 responds as expected:
> {code}
> cqlsh:foo> alter table test ADD (x INT, y INT,);
> SyntaxException: line 1:35 no viable alternative at input ')' (...(x INT, y 
> INT,[)]...)
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-16656) Assertion Error on invalid ALTER TABLE Command

[Ekaterina Dimitrova (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584486#comment-17584486
 ] 

Ekaterina Dimitrova commented on CASSANDRA-16656:
-

 [~atris], are you interested to investigate this one maybe? 

> Assertion Error on invalid ALTER TABLE Command
> --
>
> Key: CASSANDRA-16656
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16656
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL/Syntax
>Reporter: Norbert Schultz
>Priority: Low
> Fix For: 3.11.x
>
>
> If there is an invalid ALTER TABLE statement (extra comma), then Cassandra 
> responds with an assertion error.
>  
> This happens on 3.11.10 but not on 4.0-rc1
> This statement fails:
> {code:java}
> > cqlsh
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 3.11.10 | CQL spec 3.4.4 | Native protocol v4]
> Use HELP for help.
> cqlsh> CREATE KEYSPACE foo WITH REPLICATION = { 'class' : 'SimpleStrategy', 
> 'replication_factor' : 1 };
> cqlsh> use foo;
> cqlsh:foo> create table test(id INT, PRIMARY KEY(id));
> cqlsh:foo> alter table test ADD (x INT, y INT,);
> ServerError: java.lang.AssertionError
> {code}
> The following can be found inside the Log:
> {code}
> java.lang.AssertionError: null
>   at 
> org.apache.cassandra.cql3.statements.AlterTableStatementColumn.(AlterTableStatementColumn.java:36)
>  ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.cql3.Cql_Parser.alterTableStatement(Cql_Parser.java:5820)
>  ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.cql3.Cql_Parser.cqlStatement(Cql_Parser.java:628) 
> ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at org.apache.cassandra.cql3.CqlParser.cqlStatement(CqlParser.java:604) 
> ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at org.apache.cassandra.cql3.CqlParser.query(CqlParser.java:344) 
> ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.cql3.CQLFragmentParser.parseAnyUnhandled(CQLFragmentParser.java:76)
>  ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.cql3.QueryProcessor.parseStatement(QueryProcessor.java:589)
>  ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.cql3.QueryProcessor.getStatement(QueryProcessor.java:559)
>  ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:247) 
> ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:241) 
> ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.transport.messages.QueryMessage.execute(QueryMessage.java:116)
>  ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.transport.Message$Dispatcher.processRequest(Message.java:685)
>  [apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> org.apache.cassandra.transport.Message$Dispatcher.lambda$channelRead0$0(Message.java:591)
>  [apache-cassandra-3.11.10.jar:3.11.10]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_292]
>   at 
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
>  ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:113) 
> ~[apache-cassandra-3.11.10.jar:3.11.10]
>   at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_292]
> {code}
> Cassandra 4.0-rc1 responds as expected:
> {code}
> cqlsh:foo> alter table test ADD (x INT, y INT,);
> SyntaxException: line 1:35 no viable alternative at input ')' (...(x INT, y 
> INT,[)]...)
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17818) Fix error message handling when trying to use CLUSTERING ORDER with non-clustering column

[Ekaterina Dimitrova (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ekaterina Dimitrova updated CASSANDRA-17818:

Labels: ghc-lhf lhf  (was: ghc-lhf)

> Fix error message handling when trying to use CLUSTERING ORDER with 
> non-clustering column
> -
>
> Key: CASSANDRA-17818
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17818
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL/Syntax
>Reporter: Ekaterina Dimitrova
>Priority: Normal
>  Labels: ghc-lhf, lhf
> Fix For: 3.11.x, 4.0.x, 4.1.x, 4.x
>
>
> Imagine ck1, ck2, v columns. For "CLUSTERING ORDER ck1 ASC, v DESC" error msg 
> will suggest that information for ck2 is missing. But if you add it it will 
> still be wrong as "v" cannot be used. So the problem here is really about 
> using non-clustering column rather than about not providing information about 
> some clustering column.
> The following is example from 3.11, but the code is the same in 4.0, 4.1, 
> trunk:
> {code:java}
> cqlsh:k_test> CREATE TABLE test2 (pk int, ck1 int, ck2 int, v int, PRIMARY 
> KEY ((pk),ck1, ck2)) WITH CLUSTERING ORDER BY (v ASC);
> InvalidRequest: Error from server: code=2200 [Invalid query] message="Missing 
> CLUSTERING ORDER for column ck1"
> cqlsh:k_test> CREATE TABLE test2 (pk int, ck1 int, ck2 int, v int, PRIMARY 
> KEY ((pk),ck1, ck2)) WITH CLUSTERING ORDER BY (ck1 ASC, v ASC);
> InvalidRequest: Error from server: code=2200 [Invalid query] message="Missing 
> CLUSTERING ORDER for column ck2"
> cqlsh:k_test> CREATE TABLE test2 (pk int, ck1 int, ck2 int, v int, PRIMARY 
> KEY ((pk),ck1, ck2)) WITH CLUSTERING ORDER BY (ck1 ASC, ck2 DESC, v ASC);
> InvalidRequest: Error from server: code=2200 [Invalid query] message="Only 
> clustering key columns can be defined in CLUSTERING ORDER directive"{code}
> We need to be sure that we return to the user the same correct error message 
> in all three cases and it should be "Only clustering key columns can be 
> defined in CLUSTERING ORDER directive"
> +Additional information for newcomers+
>  * 
> [This|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/schema/CreateTableStatement.java#L251-L252]
>  is where we handle the issue incorrectly as proved by the example. The 
> easiest way to handle this issue would be to  check the key set content of 
> {_}clusteringOrder{_}.
>  * It would be good also to add more unit tests in 
> [CreateTableValidationTest|https://github.com/apache/cassandra/blob/trunk/test/unit/org/apache/cassandra/schema/CreateTableValidationTest.java]
>  to cover different cases. 
>  * I suggest we create patch first for 3.11 and then we can propagate it up 
> to the next versions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Assigned] (CASSANDRA-10715) Allow filtering on NULL

[Ekaterina Dimitrova (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-10715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ekaterina Dimitrova reassigned CASSANDRA-10715:
---

Assignee: Ekaterina Dimitrova

> Allow filtering on NULL
> ---
>
> Key: CASSANDRA-10715
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10715
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/CQL
> Environment: C* 3.0.0 | cqlsh | C# driver 3.0.0beta2 | Windows 2012 R2
>Reporter: Kishan Karunaratne
>Assignee: Ekaterina Dimitrova
>Priority: Low
> Fix For: 4.x
>
> Attachments: 
> 0001-Allow-null-values-in-filtered-searches-reuse-Operato.patch
>
>
> This is an issue I first noticed through the C# driver, but I was able to 
> repro on cqlsh, leading me to believe this is a Cassandra bug.
> Given the following schema:
> {noformat}
> CREATE TABLE "TestKeySpace_4928dc892922"."coolMovies" (
> unique_movie_title text,
> movie_maker text,
> director text,
> list list,
> "mainGuy" text,
> "yearMade" int,
> PRIMARY KEY ((unique_movie_title, movie_maker), director)
> ) WITH CLUSTERING ORDER BY (director ASC)
> {noformat}
> Executing a SELECT with FILTERING on a non-PK column, using a NULL as the 
> argument:
> {noformat}
> SELECT "mainGuy", "movie_maker", "unique_movie_title", "list", "director", 
> "yearMade" FROM "coolMovies" WHERE "mainGuy" = null ALLOW FILTERING
> {noformat}
> returns a ReadFailure exception:
> {noformat}
> cqlsh:TestKeySpace_4c8f2cf8d5cc> SELECT "mainGuy", "movie_maker", 
> "unique_movie_title", "list", "director", "yearMade" FROM "coolMovies" WHERE 
> "mainGuy" = null ALLOW FILTERING;
> ←[0;1;31mTraceback (most recent call last):
>   File "C:\Users\Kishan\.ccm\repository\3.0.0\bin\\cqlsh.py", line 1216, in 
> perform_simple_statement
> result = future.result()
>   File 
> "C:\Users\Kishan\.ccm\repository\3.0.0\bin\..\lib\cassandra-driver-internal-only-3.0.0a3.post0-3f15725.zip\cassandra-driver-3.0.0a3.post0-3f15725\cassandra\cluster.py",
>  line 3118, in result
> raise self._final_exception
> ReadFailure: code=1300 [Replica(s) failed to execute read] message="Operation 
> failed - received 0 responses and 1 failures" info={'failures': 1, 
> 'received_responses': 0, 'required_responses': 1, 'cons
> istency': 'ONE'}
> ←[0m
> {noformat}
> Cassandra log shows:
> {noformat}
> WARN  [SharedPool-Worker-2] 2015-11-16 13:51:00,259 
> AbstractTracingAwareExecutorService.java:169 - Uncaught exception on thread 
> Thread[SharedPool-Worker-2,10,main]: {}
> java.lang.AssertionError: null
>   at 
> org.apache.cassandra.db.filter.RowFilter$SimpleExpression.isSatisfiedBy(RowFilter.java:581)
>  ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at 
> org.apache.cassandra.db.filter.RowFilter$CQLFilter$1IsSatisfiedFilter.applyToRow(RowFilter.java:243)
>  ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at 
> org.apache.cassandra.db.transform.BaseRows.applyOne(BaseRows.java:95) 
> ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at org.apache.cassandra.db.transform.BaseRows.add(BaseRows.java:86) 
> ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at 
> org.apache.cassandra.db.transform.UnfilteredRows.add(UnfilteredRows.java:21) 
> ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at 
> org.apache.cassandra.db.transform.Transformation.add(Transformation.java:136) 
> ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at 
> org.apache.cassandra.db.transform.Transformation.apply(Transformation.java:102)
>  ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at 
> org.apache.cassandra.db.filter.RowFilter$CQLFilter$1IsSatisfiedFilter.applyToPartition(RowFilter.java:233)
>  ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at 
> org.apache.cassandra.db.filter.RowFilter$CQLFilter$1IsSatisfiedFilter.applyToPartition(RowFilter.java:227)
>  ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at 
> org.apache.cassandra.db.transform.BasePartitions.hasNext(BasePartitions.java:76)
>  ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at 
> org.apache.cassandra.db.partitions.UnfilteredPartitionIterators$Serializer.serialize(UnfilteredPartitionIterators.java:293)
>  ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at 
> org.apache.cassandra.db.ReadResponse$LocalDataResponse.build(ReadResponse.java:136)
>  ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at 
> org.apache.cassandra.db.ReadResponse$LocalDataResponse.(ReadResponse.java:128)
>  ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at 
> org.apache.cassandra.db.ReadResponse$LocalDataResponse.(ReadResponse.java:123)
>  ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at 
> org.apache.cassandra.db.ReadResponse.createDataResponse(ReadResponse.java:65) 
> ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at 
> org.apache.cassandra.db.ReadCommand.createResponse(ReadCommand.java:288) 
> ~[apache-cassandra-3.0.0.jar:3.0.0]
>   at 
>

[jira] [Assigned] (CASSANDRA-17762) LWT IF col = NULL is inconsistent with SQL NULL

[Ekaterina Dimitrova (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ekaterina Dimitrova reassigned CASSANDRA-17762:
---

Assignee: Ekaterina Dimitrova

> LWT IF col = NULL is inconsistent with SQL NULL
> ---
>
> Key: CASSANDRA-17762
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17762
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL/Semantics
>Reporter: Avi Kivity
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> In SQL, any comparison with NULL is NULL, which is interpreted as FALSE in a 
> condition. To test for NULLness, you use IS NULL or IS NOT NULL.
> But LWT uses IF col = NULL as a NULLness test. This is likely to confuse 
> people coming from SQL and hamper attempts to extend the dialect.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-17858) Allow or Block CIDR block

[Adriano Bonacin (Jira)]

Adriano Bonacin created CASSANDRA-17858:
---

 Summary: Allow or Block CIDR block
 Key: CASSANDRA-17858
 URL: https://issues.apache.org/jira/browse/CASSANDRA-17858
 Project: Cassandra
  Issue Type: Improvement
  Components: Feature/Guardrails
Reporter: Adriano Bonacin


Today there's no way to block specific unwanted source connection.

Some other technologies can handle it, like MySQL or Postgres.

 

Example:

My app has ip range: 20.0.2.0/24. I want to allow connection only from this 
source.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra-website] branch asf-staging updated (c44d0ac3 -> 82fec7cc)

[git-site-role]

This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git


 discard c44d0ac3 generate docs for 8cf784cf
 new 82fec7cc generate docs for 8cf784cf

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   (c44d0ac3)
\
 N -- N -- N   refs/heads/asf-staging (82fec7cc)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 content/search-index.js |   2 +-
 site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes
 2 files changed, 1 insertion(+), 1 deletion(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRASC-42) Introduce new handler for Keyspaces/ColumnFamily operations

[Francisco Guerrero (Jira)]

Francisco Guerrero created CASSANDRASC-42:
-

 Summary: Introduce new handler for Keyspaces/ColumnFamily 
operations
 Key: CASSANDRASC-42
 URL: https://issues.apache.org/jira/browse/CASSANDRASC-42
 Project: Sidecar for Apache Cassandra
  Issue Type: New Feature
  Components: Rest API
Reporter: Francisco Guerrero
Assignee: Francisco Guerrero


Keyspace information is required when doing bulk reads and writes from 
Cassandra, including ColumnFamily (table) information. For example, column type 
information can be used to determine a mapping to a different system such as 
Spark. Checking whether a keyspace/column family exists before starting an 
import operation is desired.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRASC-42) Introduce new handler for Keyspaces/ColumnFamily operations

[Francisco Guerrero (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRASC-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francisco Guerrero updated CASSANDRASC-42:
--
Change Category: Operability
 Complexity: Normal
 Status: Open  (was: Triage Needed)

> Introduce new handler for Keyspaces/ColumnFamily operations
> ---
>
> Key: CASSANDRASC-42
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-42
> Project: Sidecar for Apache Cassandra
>  Issue Type: New Feature
>  Components: Rest API
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
>
> Keyspace information is required when doing bulk reads and writes from 
> Cassandra, including ColumnFamily (table) information. For example, column 
> type information can be used to determine a mapping to a different system 
> such as Spark. Checking whether a keyspace/column family exists before 
> starting an import operation is desired.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17857) upsert with adder support is not consistent with numbers and strings in LWT

[David Capwell (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Capwell updated CASSANDRA-17857:
--
Test and Documentation Plan: new tests
 Status: Patch Available  (was: Open)

> upsert with adder support is not consistent with numbers and strings in LWT
> ---
>
> Key: CASSANDRA-17857
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17857
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL/Semantics, Feature/Lightweight Transactions
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.1.x
>
>
> In 4.1 UPDATE name = name + offset support got extended to numbers and 
> strings (not just counters) but the behavior isn’t consistent
> Number: throws a error due to Int32Type.add(null, 42) failing
> String: returns the non-null updated values
> What Postgres does is keeps the value null
> {code}
> postgres=# create table x (pk int PRIMARY KEY, a int, b text);
> CREATE TABLE
> postgres=# insert into x (pk, a, b) values(0, null, null);
> INSERT 0 1
> postgres=# UPDATE x SET a = a + 1 WHERE pk = 0;
> UPDATE 1
> postgres=# select * from x;
>  pk | a | b
> +---+---
>   0 |   |
> (1 row)
> postgres=# UPDATE x SET b = b + 'one' WHERE pk = 0;
> ERROR:  operator does not exist: text + unknown
> LINE 1: UPDATE x SET b = b + 'one' WHERE pk = 0;
>^
> HINT:  No operator matches the given name and argument types. You might need 
> to add explicit type casts.
> postgres=# UPDATE x SET b = b + CAST('one' as text) WHERE pk = 0;
> ERROR:  operator does not exist: text + text
> LINE 1: UPDATE x SET b = b + CAST('one' as text) WHERE pk = 0;
>^
> HINT:  No operator matches the given name and argument types. You might need 
> to add explicit type casts.
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17857) 4.1's upsert with adder support is not consistent with numbers and strings

[David Capwell (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Capwell updated CASSANDRA-17857:
--
 Bug Category: Parent values: Correctness(12982)Level 1 values: 
Unrecoverable Corruption / Loss(13161)
   Complexity: Low Hanging Fruit
Discovered By: Code Inspection
Fix Version/s: 4.1.x
 Severity: Critical
   Status: Open  (was: Triage Needed)

> 4.1's upsert with adder support is not consistent with numbers and strings
> --
>
> Key: CASSANDRA-17857
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17857
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL/Semantics, Feature/Lightweight Transactions
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.1.x
>
>
> In 4.1 UPDATE name = name + offset support got extended to numbers and 
> strings (not just counters) but the behavior isn’t consistent
> Number: throws a error due to Int32Type.add(null, 42) failing
> String: returns the non-null updated values
> What Postgres does is keeps the value null
> {code}
> postgres=# create table x (pk int PRIMARY KEY, a int, b text);
> CREATE TABLE
> postgres=# insert into x (pk, a, b) values(0, null, null);
> INSERT 0 1
> postgres=# UPDATE x SET a = a + 1 WHERE pk = 0;
> UPDATE 1
> postgres=# select * from x;
>  pk | a | b
> +---+---
>   0 |   |
> (1 row)
> postgres=# UPDATE x SET b = b + 'one' WHERE pk = 0;
> ERROR:  operator does not exist: text + unknown
> LINE 1: UPDATE x SET b = b + 'one' WHERE pk = 0;
>^
> HINT:  No operator matches the given name and argument types. You might need 
> to add explicit type casts.
> postgres=# UPDATE x SET b = b + CAST('one' as text) WHERE pk = 0;
> ERROR:  operator does not exist: text + text
> LINE 1: UPDATE x SET b = b + CAST('one' as text) WHERE pk = 0;
>^
> HINT:  No operator matches the given name and argument types. You might need 
> to add explicit type casts.
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17857) upsert with adder support is not consistent with numbers and strings in LWT

[David Capwell (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Capwell updated CASSANDRA-17857:
--
Summary: upsert with adder support is not consistent with numbers and 
strings in LWT  (was: 4.1's upsert with adder support is not consistent with 
numbers and strings)

> upsert with adder support is not consistent with numbers and strings in LWT
> ---
>
> Key: CASSANDRA-17857
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17857
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL/Semantics, Feature/Lightweight Transactions
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.1.x
>
>
> In 4.1 UPDATE name = name + offset support got extended to numbers and 
> strings (not just counters) but the behavior isn’t consistent
> Number: throws a error due to Int32Type.add(null, 42) failing
> String: returns the non-null updated values
> What Postgres does is keeps the value null
> {code}
> postgres=# create table x (pk int PRIMARY KEY, a int, b text);
> CREATE TABLE
> postgres=# insert into x (pk, a, b) values(0, null, null);
> INSERT 0 1
> postgres=# UPDATE x SET a = a + 1 WHERE pk = 0;
> UPDATE 1
> postgres=# select * from x;
>  pk | a | b
> +---+---
>   0 |   |
> (1 row)
> postgres=# UPDATE x SET b = b + 'one' WHERE pk = 0;
> ERROR:  operator does not exist: text + unknown
> LINE 1: UPDATE x SET b = b + 'one' WHERE pk = 0;
>^
> HINT:  No operator matches the given name and argument types. You might need 
> to add explicit type casts.
> postgres=# UPDATE x SET b = b + CAST('one' as text) WHERE pk = 0;
> ERROR:  operator does not exist: text + text
> LINE 1: UPDATE x SET b = b + CAST('one' as text) WHERE pk = 0;
>^
> HINT:  No operator matches the given name and argument types. You might need 
> to add explicit type casts.
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-17857) 4.1's upsert with adder support is not consistent with numbers and strings

[David Capwell (Jira)]

David Capwell created CASSANDRA-17857:
-

 Summary: 4.1's upsert with adder support is not consistent with 
numbers and strings
 Key: CASSANDRA-17857
 URL: https://issues.apache.org/jira/browse/CASSANDRA-17857
 Project: Cassandra
  Issue Type: Bug
  Components: CQL/Semantics, Feature/Lightweight Transactions
Reporter: David Capwell
Assignee: David Capwell


In 4.1 UPDATE name = name + offset support got extended to numbers and strings 
(not just counters) but the behavior isn’t consistent

Number: throws a error due to Int32Type.add(null, 42) failing
String: returns the non-null updated values

What Postgres does is keeps the value null

{code}
postgres=# create table x (pk int PRIMARY KEY, a int, b text);
CREATE TABLE
postgres=# insert into x (pk, a, b) values(0, null, null);
INSERT 0 1
postgres=# UPDATE x SET a = a + 1 WHERE pk = 0;
UPDATE 1
postgres=# select * from x;
 pk | a | b
+---+---
  0 |   |
(1 row)
postgres=# UPDATE x SET b = b + 'one' WHERE pk = 0;
ERROR:  operator does not exist: text + unknown
LINE 1: UPDATE x SET b = b + 'one' WHERE pk = 0;
   ^
HINT:  No operator matches the given name and argument types. You might need to 
add explicit type casts.
postgres=# UPDATE x SET b = b + CAST('one' as text) WHERE pk = 0;
ERROR:  operator does not exist: text + text
LINE 1: UPDATE x SET b = b + CAST('one' as text) WHERE pk = 0;
   ^
HINT:  No operator matches the given name and argument types. You might need to 
add explicit type casts.
{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17856) Unable to Access Convenience Package Download Sites

[Brandon Williams (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584473#comment-17584473
 ] 

Brandon Williams commented on CASSANDRA-17856:
--

INFRA-23628 has been resolved and everything should be up again.

> Unable to Access Convenience Package Download Sites
> ---
>
> Key: CASSANDRA-17856
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17856
> Project: Cassandra
>  Issue Type: Bug
>  Components: Packaging
>Reporter: Ben Dalling
>Priority: Normal
>
> The web addresses setup in CASSANDRA-17748 don't seem to be accessible.  The 
> specific download sites are:
>  * [https://redhat.cassandra.apache.org/]
>  * [https://debian.cassandra.apache.org|https://debian.cassandra.apache.org/]
> They were definitely working on the 16th of August (when I last ran a test 
> installation) but have been failing since at least 2022-08-22T07:24Z and are 
> still failing now.
> Attempting to access the raw [https://redhat.cassandra.apache.org/] results 
> in a connection timeout, but accessing the underlying 
> [https://apache.jfrog.io/ui/native/cassandra-rpm] works OK.
> These affected web addresses are also referred to in the installation 
> documentation at:
>  * 
> [https://cassandra.apache.org/doc/latest/cassandra/getting_started/installing.html#installing-the-rpm-packages]
>  * 
> [https://cassandra.apache.org/doc/latest/cassandra/getting_started/installing.html#installing-the-debian-packages]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-10383) Disable auto snapshot on selected tables.

[Stefan Miklosovic (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-10383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584459#comment-17584459
 ] 

Stefan Miklosovic edited comment on CASSANDRA-10383 at 8/24/22 8:44 PM:


Hi [~fibersel] are you going to work on this? I see you as the assignee, 
otherwise I would like to finish this or explore where we stand as 4.0 is 
already out.


was (Author: smiklosovic):
Hi [~fibersel] are you going to work on this? I see you as the assignee, 
otherwise I would like to finish this or explore where we stands as 4.0 is 
already out.

> Disable auto snapshot on selected tables.
> -
>
> Key: CASSANDRA-10383
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10383
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Config, Local/Snapshots
>Reporter: Tommy Stendahl
>Assignee: Abuli Palagashvili
>Priority: Normal
>  Labels: doc-impacting, messaging-service-bump-required
> Fix For: 4.x
>
> Attachments: 10383.txt
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> I have a use case where I would like to turn off auto snapshot for selected 
> tables, I don't want to turn it off completely since its a good feature. 
> Looking at the code I think it would be relatively easy to fix.
> My plan is to create a new table property named something like 
> "disable_auto_snapshot". If set to true it will prevent auto snapshot on the 
> table, if set to false auto snapshot will be controlled by the 
> "auto_snapshot" property in the cassandra.yaml. Default would be false.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-10383) Disable auto snapshot on selected tables.

[Stefan Miklosovic (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-10383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584459#comment-17584459
 ] 

Stefan Miklosovic edited comment on CASSANDRA-10383 at 8/24/22 8:34 PM:


Hi [~fibersel] are you going to work on this? I see you as the assignee, 
otherwise I would like to finish this or explore where we stands as 4.0 is 
already out.


was (Author: smiklosovic):
Hi [~fibersel] are you going to work on this? I see you as a reviewer, 
otherwise I would like to finish this or explore where we stands as 4.0 is 
already out.

> Disable auto snapshot on selected tables.
> -
>
> Key: CASSANDRA-10383
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10383
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Config, Local/Snapshots
>Reporter: Tommy Stendahl
>Assignee: Abuli Palagashvili
>Priority: Normal
>  Labels: doc-impacting, messaging-service-bump-required
> Fix For: 4.x
>
> Attachments: 10383.txt
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> I have a use case where I would like to turn off auto snapshot for selected 
> tables, I don't want to turn it off completely since its a good feature. 
> Looking at the code I think it would be relatively easy to fix.
> My plan is to create a new table property named something like 
> "disable_auto_snapshot". If set to true it will prevent auto snapshot on the 
> table, if set to false auto snapshot will be controlled by the 
> "auto_snapshot" property in the cassandra.yaml. Default would be false.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-10383) Disable auto snapshot on selected tables.

[Stefan Miklosovic (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-10383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584459#comment-17584459
 ] 

Stefan Miklosovic commented on CASSANDRA-10383:
---

Hi [~fibersel] are you going to work on this? I see you as a reviewer, 
otherwise I would like to finish this or explore where we stands as 4.0 is 
already out.

> Disable auto snapshot on selected tables.
> -
>
> Key: CASSANDRA-10383
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10383
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Config, Local/Snapshots
>Reporter: Tommy Stendahl
>Assignee: Abuli Palagashvili
>Priority: Normal
>  Labels: doc-impacting, messaging-service-bump-required
> Fix For: 4.x
>
> Attachments: 10383.txt
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> I have a use case where I would like to turn off auto snapshot for selected 
> tables, I don't want to turn it off completely since its a good feature. 
> Looking at the code I think it would be relatively easy to fix.
> My plan is to create a new table property named something like 
> "disable_auto_snapshot". If set to true it will prevent auto snapshot on the 
> table, if set to false auto snapshot will be controlled by the 
> "auto_snapshot" property in the cassandra.yaml. Default would be false.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17750) Remove dependency on Maven Ant Tasks

[David Capwell (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584456#comment-17584456
 ] 

David Capwell commented on CASSANDRA-17750:
---

[~mck] on the conflict it was found that some build.xml properties were used 
that we missed, so Abe just pushed that fix.  If you are cool with the change 
will merge once builds are good.

> Remove dependency on Maven Ant Tasks
> 
>
> Key: CASSANDRA-17750
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17750
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Build, Dependencies, Packaging
>Reporter: Abe Ratnofsky
>Assignee: Abe Ratnofsky
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10h 10m
>  Remaining Estimate: 0h
>
> Apache Cassandra depends on Maven Ant Tasks (MAT) during build, for declaring 
> dependencies and generating POM files from within build.xml. MAT has long 
> been retired (no commits since maintenance in 2015), has registered CVEs in 
> dependencies (CVE-2017-1000487), and encourages migration to its successor, 
> Maven Artifact Resolver Ant Tasks (MARAT).
> As part of CASSANDRA-16391 
> , mck migrated 
> dependency resolution to MARAT, but MAT is still included in our build for 
> generating POMs since MARAT does not have an alternative to the writepom task 
> provided by MAT. I have a patch ready that removes MAT completely, with a 
> workaround for POM generation.
> I am not advocating for any kind of migration away from Ant to an alternative 
> like Gradle or Maven, just to be extra clear.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17750) Remove dependency on Maven Ant Tasks

[David Capwell (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584455#comment-17584455
 ] 

David Capwell commented on CASSANDRA-17750:
---

Starting commit

CI Results (pending):
||Branch||Source||Circle CI||Jenkins||
|trunk|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17750-trunk-2F0A6859-72CD-465E-B8DF-1B160DE69E5E]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17750-trunk-2F0A6859-72CD-465E-B8DF-1B160DE69E5E]|[build|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1890/]|


> Remove dependency on Maven Ant Tasks
> 
>
> Key: CASSANDRA-17750
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17750
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Build, Dependencies, Packaging
>Reporter: Abe Ratnofsky
>Assignee: Abe Ratnofsky
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10h 10m
>  Remaining Estimate: 0h
>
> Apache Cassandra depends on Maven Ant Tasks (MAT) during build, for declaring 
> dependencies and generating POM files from within build.xml. MAT has long 
> been retired (no commits since maintenance in 2015), has registered CVEs in 
> dependencies (CVE-2017-1000487), and encourages migration to its successor, 
> Maven Artifact Resolver Ant Tasks (MARAT).
> As part of CASSANDRA-16391 
> , mck migrated 
> dependency resolution to MARAT, but MAT is still included in our build for 
> generating POMs since MARAT does not have an alternative to the writepom task 
> provided by MAT. I have a patch ready that removes MAT completely, with a 
> workaround for POM generation.
> I am not advocating for any kind of migration away from Ant to an alternative 
> like Gradle or Maven, just to be extra clear.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17856) Unable to Access Convenience Package Download Sites

[Brandon Williams (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-17856:
-
Resolution: Invalid
Status: Resolved  (was: Triage Needed)

We don't have control over the hosting, but I've created INFRA-23628 to look 
into this.

> Unable to Access Convenience Package Download Sites
> ---
>
> Key: CASSANDRA-17856
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17856
> Project: Cassandra
>  Issue Type: Bug
>  Components: Packaging
>Reporter: Ben Dalling
>Priority: Normal
>
> The web addresses setup in CASSANDRA-17748 don't seem to be accessible.  The 
> specific download sites are:
>  * [https://redhat.cassandra.apache.org/]
>  * [https://debian.cassandra.apache.org|https://debian.cassandra.apache.org/]
> They were definitely working on the 16th of August (when I last ran a test 
> installation) but have been failing since at least 2022-08-22T07:24Z and are 
> still failing now.
> Attempting to access the raw [https://redhat.cassandra.apache.org/] results 
> in a connection timeout, but accessing the underlying 
> [https://apache.jfrog.io/ui/native/cassandra-rpm] works OK.
> These affected web addresses are also referred to in the installation 
> documentation at:
>  * 
> [https://cassandra.apache.org/doc/latest/cassandra/getting_started/installing.html#installing-the-rpm-packages]
>  * 
> [https://cassandra.apache.org/doc/latest/cassandra/getting_started/installing.html#installing-the-debian-packages]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-16792) Add snapshot_before_compaction_ttl configuration

[Stefan Miklosovic (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584453#comment-17584453
 ] 

Stefan Miklosovic commented on CASSANDRA-16792:
---

I think it is logical expansion of CASSANDRA-16791. If we figure out that one, 
this one should be rather easy to cover as well.

> Add snapshot_before_compaction_ttl configuration
> 
>
> Key: CASSANDRA-16792
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16792
> Project: Cassandra
>  Issue Type: Sub-task
>Reporter: Paulo Motta
>Assignee: Abuli Palagashvili
>Priority: Normal
>
> This property should take a human readable parameter (ie. 6h, 3days). When 
> specified and snapshot_before_compaction_ttl: true, snapshots created before 
> compaction should use the specified TTL.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-16875) Add signature to snapshot manifest json

[Stefan Miklosovic (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584452#comment-17584452
 ] 

Stefan Miklosovic commented on CASSANDRA-16875:
---

This is interesting ticket [~paulo], would you mind to exapand that and provide 
some example and how it would work in practice?

> Add signature to snapshot manifest json
> ---
>
> Key: CASSANDRA-16875
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16875
> Project: Cassandra
>  Issue Type: Sub-task
>  Components: Tool/nodetool
>Reporter: Paulo Motta
>Priority: Normal
>
> TTL Snapshot cleanup gets the snapshot expiration date from the plain-text 
> manifest.json file stored along with the snapshot. 
> We need to add a simple signature scheme to validate the manifest was not 
> tampered or corrupted.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17845) Typo in https://cassandra.apache.org/doc/trunk/cassandra/cql/ddl.html

[Ben Dalling (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584446#comment-17584446
 ] 

Ben Dalling commented on CASSANDRA-17845:
-

Patch available on 
[https://github.com/dallinb/cassandra/tree/bugfix/CASSANDRA-17845] and 
representative pull request (more for visualisation) at 
https://github.com/apache/cassandra/pull/1815

> Typo in https://cassandra.apache.org/doc/trunk/cassandra/cql/ddl.html
> -
>
> Key: CASSANDRA-17845
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17845
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Yaniv Kaul
>Priority: Normal
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> It is common for a cluster to define only one keyspace for an actie 
> application
>  
> should be:
>  
> It is common for a cluster to define only one keyspace for an active 
> application



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-17856) Unable to Access Convenience Package Download Sites

[Ben Dalling (Jira)]

Ben Dalling created CASSANDRA-17856:
---

 Summary: Unable to Access Convenience Package Download Sites
 Key: CASSANDRA-17856
 URL: https://issues.apache.org/jira/browse/CASSANDRA-17856
 Project: Cassandra
  Issue Type: Bug
  Components: Packaging
Reporter: Ben Dalling


The web addresses setup in CASSANDRA-17748 don't seem to be accessible.  The 
specific download sites are:
 * [https://redhat.cassandra.apache.org/]
 * [https://debian.cassandra.apache.org|https://debian.cassandra.apache.org/]

They were definitely working on the 16th of August (when I last ran a test 
installation) but have been failing since at least 2022-08-22T07:24Z and are 
still failing now.

Attempting to access the raw [https://redhat.cassandra.apache.org/] results in 
a connection timeout, but accessing the underlying 
[https://apache.jfrog.io/ui/native/cassandra-rpm] works OK.

These affected web addresses are also referred to in the installation 
documentation at:
 * 
[https://cassandra.apache.org/doc/latest/cassandra/getting_started/installing.html#installing-the-rpm-packages]
 * 
[https://cassandra.apache.org/doc/latest/cassandra/getting_started/installing.html#installing-the-debian-packages]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17840) IndexOutOfBoundsException in Paging State Version Inference (V3 State Received on V4 Connection)

[Josh McKenzie (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh McKenzie updated CASSANDRA-17840:
--
  Fix Version/s: 3.11.14
 4.0.6
 4.1
 4.2
 (was: 4.x)
 (was: 3.11.x)
 (was: 4.0.x)
 (was: 4.1.x)
  Since Version: 3.11.0
Source Control Link: 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=commit;h=ab481be81da0f06a80e099ca7502b7453ff568d3
 Resolution: Fixed
 Status: Resolved  (was: Ready to Commit)

> IndexOutOfBoundsException in Paging State Version Inference (V3 State 
> Received on V4 Connection)
> 
>
> Key: CASSANDRA-17840
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17840
> Project: Cassandra
>  Issue Type: Bug
>  Components: Messaging/Client
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 3.11.14, 4.0.6, 4.1, 4.2
>
>
> In {{PagingState.java}}, {{index}} is an integer field, and we add long 
> values to it without a {{Math.toIntExact}} check. While we’re checking for 
> negative return values returned by {{getUnsignedVInt}}, there's a chance that 
> the value returned by it is so large that addition operation would cause 
> integer overflow, or the value itself is large enough to cause overflow.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] 01/01: Merge branch 'cassandra-4.1' into trunk

[jmckenzie]

This is an automated email from the ASF dual-hosted git repository.

jmckenzie pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git

commit 616ddf812a05c6bddf7ca176c26b33a8ba11864a
Merge: dbadd08585 704141541a
Author: Josh McKenzie 
AuthorDate: Wed Aug 24 15:24:40 2022 -0400

Merge branch 'cassandra-4.1' into trunk

 CHANGES.txt|   1 +
 .../cassandra/service/pager/PagingState.java   |  54 ---
 .../apache/cassandra/utils/vint/VIntCoding.java|   3 +
 .../service/pager/RandomizedPagingStateTest.java   | 104 +
 4 files changed, 150 insertions(+), 12 deletions(-)



-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] branch cassandra-4.1 updated (f4deef9d58 -> 704141541a)

[jmckenzie]

This is an automated email from the ASF dual-hosted git repository.

jmckenzie pushed a change to branch cassandra-4.1
in repository https://gitbox.apache.org/repos/asf/cassandra.git


from f4deef9d58 Fix 
test/distributed/org/apache/cassandra/distributed/test/IncRepairCoordinatorErrorTest
 new ab481be81d Fix potential IndexOutOfBoundsException in PagingState in 
mixed mode clusters
 new 73bea0ac1e Merge branch 'cassandra-3.11' into cassandra-4.0
 new 704141541a Merge branch 'cassandra-4.0' into cassandra-4.1

The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 CHANGES.txt|   1 +
 .../cassandra/service/pager/PagingState.java   |  54 ---
 .../apache/cassandra/utils/vint/VIntCoding.java|   3 +
 .../service/pager/RandomizedPagingStateTest.java   | 104 +
 4 files changed, 150 insertions(+), 12 deletions(-)
 create mode 100644 
test/unit/org/apache/cassandra/service/pager/RandomizedPagingStateTest.java


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] 01/01: Merge branch 'cassandra-4.0' into cassandra-4.1

[jmckenzie]

This is an automated email from the ASF dual-hosted git repository.

jmckenzie pushed a commit to branch cassandra-4.1
in repository https://gitbox.apache.org/repos/asf/cassandra.git

commit 704141541a0ff4f2a00e98b3f8c4b3d5c809c562
Merge: f4deef9d58 73bea0ac1e
Author: Josh McKenzie 
AuthorDate: Wed Aug 24 15:24:11 2022 -0400

Merge branch 'cassandra-4.0' into cassandra-4.1

 CHANGES.txt|   1 +
 .../cassandra/service/pager/PagingState.java   |  54 ---
 .../apache/cassandra/utils/vint/VIntCoding.java|   3 +
 .../service/pager/RandomizedPagingStateTest.java   | 104 +
 4 files changed, 150 insertions(+), 12 deletions(-)

diff --cc CHANGES.txt
index dcba191672,67a78a0a7e..b49e7dd801
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -52,8 -10,8 +52,9 @@@ Merged from 4.0
   * Clean up ScheduledExecutors, CommitLog, and MessagingService shutdown for 
in-JVM dtests (CASSANDRA-17731)
   * Remove extra write to system table for prepared statements 
(CASSANDRA-17764)
  Merged from 3.11:
+  * Fix potential IndexOutOfBoundsException in PagingState in mixed mode 
clusters (CASSANDRA-17840)
   * Document usage of closed token intervals in manual compaction 
(CASSANDRA-17575)
 + * Creating of a keyspace on insufficient number of replicas should filter 
out gosspping-only members (CASSANDRA-17759)
  Merged from 3.0:
   * Improve libjemalloc resolution in bin/cassandra (CASSANDRA-15767)
   * Fix restarting of services on gossipping-only member (CASSANDRA-17752)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] 01/01: Merge branch 'cassandra-3.11' into cassandra-4.0

[jmckenzie]

This is an automated email from the ASF dual-hosted git repository.

jmckenzie pushed a commit to branch cassandra-4.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git

commit 73bea0ac1e7d5d3dd35c50cb9bb4e691c9f5cd14
Merge: 0353df7542 ab481be81d
Author: Josh McKenzie 
AuthorDate: Wed Aug 24 15:17:53 2022 -0400

Merge branch 'cassandra-3.11' into cassandra-4.0

-s ours; applying 4.0+ patch for CASSANDRA-17840

 CHANGES.txt|   1 +
 .../cassandra/service/pager/PagingState.java   |  54 ---
 .../apache/cassandra/utils/vint/VIntCoding.java|   3 +
 .../service/pager/RandomizedPagingStateTest.java   | 104 +
 4 files changed, 150 insertions(+), 12 deletions(-)

diff --cc CHANGES.txt
index d1fb5626dd,c9f3b7630a..67a78a0a7e
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,16 -1,8 +1,17 @@@
 -3.11.14
 +4.0.6
 + * Prevent infinite loop in repair coordinator on FailSession 
(CASSANDRA-17834)
 + * Fix race condition on updating cdc size and advancing to next segment 
(CASSANDRA-17792)
 + * Add 'noboolean' rpm build for older distros like CentOS7 (CASSANDRA-17765)
 + * Fix default value for compaction_throughput_mb_per_sec in Config class to 
match  the one in cassandra.yaml (CASSANDRA-17790)
 + * Fix Setting Virtual Table - update after startup config properties 
gc_log_threshold_in_ms, gc_warn_threshold_in_ms,
 +   conf.index_summary_capacity_in_mb, prepared_statements_cache_size_mb, 
key_cache_size_in_mb, counter_cache_size_in_mb
 +   (CASSANDRA-17737)
 + * Fix Settings Virtual Table - index_summary_resize_interval and 
index_summary_capacity were not updated after startup (CASSANDRA-17735)
 + * Clean up ScheduledExecutors, CommitLog, and MessagingService shutdown for 
in-JVM dtests (CASSANDRA-17731)
 + * Remove extra write to system table for prepared statements 
(CASSANDRA-17764)
 +Merged from 3.11:
+  * Fix potential IndexOutOfBoundsException in PagingState in mixed mode 
clusters (CASSANDRA-17840)
   * Document usage of closed token intervals in manual compaction 
(CASSANDRA-17575)
 - * Creating of a keyspace on insufficient number of replicas should filter 
out gosspping-only members (CASSANDRA-17759)
 - * Only use statically defined subcolumns when determining column definition 
for supercolumn cell (CASSANDRA-14113)
  Merged from 3.0:
   * Improve libjemalloc resolution in bin/cassandra (CASSANDRA-15767)
   * Fix restarting of services on gossipping-only member (CASSANDRA-17752)
diff --cc src/java/org/apache/cassandra/utils/vint/VIntCoding.java
index 6961d9f191,68ebf42aea..c35f8345b3
--- a/src/java/org/apache/cassandra/utils/vint/VIntCoding.java
+++ b/src/java/org/apache/cassandra/utils/vint/VIntCoding.java
@@@ -103,8 -94,12 +103,11 @@@ public class VIntCodin
  {
  return getUnsignedVInt(input, readerIndex, input.limit());
  }
 -
  public static long getUnsignedVInt(ByteBuffer input, int readerIndex, int 
readerLimit)
  {
+ if (readerIndex < 0)
+ throw new IllegalArgumentException("Reader index should be 
non-negative, but was " + readerIndex);
+ 
  if (readerIndex >= readerLimit)
  return -1;
  
diff --cc 
test/unit/org/apache/cassandra/service/pager/RandomizedPagingStateTest.java
index 00,4c9592a25d..1ef3b956d2
mode 00,100644..100644
--- 
a/test/unit/org/apache/cassandra/service/pager/RandomizedPagingStateTest.java
+++ 
b/test/unit/org/apache/cassandra/service/pager/RandomizedPagingStateTest.java
@@@ -1,0 -1,103 +1,104 @@@
+ /*
+  * Licensed to the Apache Software Foundation (ASF) under one
+  * or more contributor license agreements.  See the NOTICE file
+  * distributed with this work for additional information
+  * regarding copyright ownership.  The ASF licenses this file
+  * to you under the Apache License, Version 2.0 (the
+  * "License"); you may not use this file except in compliance
+  * with the License.  You may obtain a copy of the License at
+  *
+  * http://www.apache.org/licenses/LICENSE-2.0
+  *
+  * Unless required by applicable law or agreed to in writing, software
+  * distributed under the License is distributed on an "AS IS" BASIS,
+  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  * See the License for the specific language governing permissions and
+  * limitations under the License.
+  */
+ package org.apache.cassandra.service.pager;
+ 
+ import java.nio.ByteBuffer;
+ import java.util.Random;
+ 
+ import org.junit.Assert;
++import org.junit.BeforeClass;
+ import org.junit.Test;
+ 
 -import org.apache.cassandra.config.CFMetaData;
+ import org.apache.cassandra.config.DatabaseDescriptor;
 -import org.apache.cassandra.db.BufferClustering;
++import org.apache.cassandra.cql3.ColumnIdentifier;
+ import org.apache.cassandra.db.Clustering;
+ import org.apache.cassandra.db.marshal.BytesType;
+ import org.apache.cassandra.db.marshal.LongType;
+ import org.apache.cassandra.db.rows.BTreeRow;
+ i

[cassandra] branch cassandra-4.0 updated (0353df7542 -> 73bea0ac1e)

[jmckenzie]

This is an automated email from the ASF dual-hosted git repository.

jmckenzie pushed a change to branch cassandra-4.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git


from 0353df7542 Prevent infinite loop in repair coordinator on FailSession
 new ab481be81d Fix potential IndexOutOfBoundsException in PagingState in 
mixed mode clusters
 new 73bea0ac1e Merge branch 'cassandra-3.11' into cassandra-4.0

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 CHANGES.txt|   1 +
 .../cassandra/service/pager/PagingState.java   |  54 ---
 .../apache/cassandra/utils/vint/VIntCoding.java|   3 +
 .../service/pager/RandomizedPagingStateTest.java   | 104 +
 4 files changed, 150 insertions(+), 12 deletions(-)
 create mode 100644 
test/unit/org/apache/cassandra/service/pager/RandomizedPagingStateTest.java


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] branch cassandra-3.11 updated: Fix potential IndexOutOfBoundsException in PagingState in mixed mode clusters

[jmckenzie]

This is an automated email from the ASF dual-hosted git repository.

jmckenzie pushed a commit to branch cassandra-3.11
in repository https://gitbox.apache.org/repos/asf/cassandra.git


The following commit(s) were added to refs/heads/cassandra-3.11 by this push:
 new ab481be81d Fix potential IndexOutOfBoundsException in PagingState in 
mixed mode clusters
ab481be81d is described below

commit ab481be81da0f06a80e099ca7502b7453ff568d3
Author: Josh McKenzie 
AuthorDate: Tue Aug 23 14:37:17 2022 -0400

Fix potential IndexOutOfBoundsException in PagingState in mixed mode 
clusters

Patch by Alex Petrov; reviewed by Josh McKenzie, Sam Tunnicliffe, and 
Aleksey Yeschenko for CASSANDRA-17840

Co-authored-by: Alex Petrov 
Co-authored-by: Josh McKenzie 
---
 CHANGES.txt|   1 +
 .../org/apache/cassandra/db/BufferClustering.java  |   5 +-
 .../cassandra/service/pager/PagingState.java   |  54 ---
 .../apache/cassandra/utils/vint/VIntCoding.java|   3 +
 .../service/pager/RandomizedPagingStateTest.java   | 103 +
 5 files changed, 153 insertions(+), 13 deletions(-)

diff --git a/CHANGES.txt b/CHANGES.txt
index bacd5b0767..c9f3b7630a 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 3.11.14
+ * Fix potential IndexOutOfBoundsException in PagingState in mixed mode 
clusters (CASSANDRA-17840)
  * Document usage of closed token intervals in manual compaction 
(CASSANDRA-17575)
  * Creating of a keyspace on insufficient number of replicas should filter out 
gosspping-only members (CASSANDRA-17759)
  * Only use statically defined subcolumns when determining column definition 
for supercolumn cell (CASSANDRA-14113)
diff --git a/src/java/org/apache/cassandra/db/BufferClustering.java 
b/src/java/org/apache/cassandra/db/BufferClustering.java
index 7ca91320e8..8cb8a59902 100644
--- a/src/java/org/apache/cassandra/db/BufferClustering.java
+++ b/src/java/org/apache/cassandra/db/BufferClustering.java
@@ -19,6 +19,8 @@ package org.apache.cassandra.db;
 
 import java.nio.ByteBuffer;
 
+import com.google.common.annotations.VisibleForTesting;
+
 import org.apache.cassandra.utils.ByteBufferUtil;
 
 /**
@@ -35,7 +37,8 @@ import org.apache.cassandra.utils.ByteBufferUtil;
  */
 public class BufferClustering extends AbstractBufferClusteringPrefix 
implements Clustering
 {
-BufferClustering(ByteBuffer... values)
+@VisibleForTesting
+public BufferClustering(ByteBuffer... values)
 {
 super(Kind.CLUSTERING, values);
 }
diff --git a/src/java/org/apache/cassandra/service/pager/PagingState.java 
b/src/java/org/apache/cassandra/service/pager/PagingState.java
index 9b7eccf321..10044a822d 100644
--- a/src/java/org/apache/cassandra/service/pager/PagingState.java
+++ b/src/java/org/apache/cassandra/service/pager/PagingState.java
@@ -134,39 +134,68 @@ public class PagingState
 return out.buffer(false);
 }
 
-private static boolean isModernSerialized(ByteBuffer bytes)
+@VisibleForTesting
+static boolean isModernSerialized(ByteBuffer bytes)
 {
 int index = bytes.position();
 int limit = bytes.limit();
 
-long partitionKeyLen = getUnsignedVInt(bytes, index, limit);
+int partitionKeyLen = toIntExact(getUnsignedVInt(bytes, index, limit));
 if (partitionKeyLen < 0)
 return false;
-index += computeUnsignedVIntSize(partitionKeyLen) + partitionKeyLen;
-if (index >= limit)
+index = addNonNegative(index, 
computeUnsignedVIntSize(partitionKeyLen), partitionKeyLen);
+if (index >= limit || index < 0)
 return false;
 
-long rowMarkerLen = getUnsignedVInt(bytes, index, limit);
+int rowMarkerLen = toIntExact(getUnsignedVInt(bytes, index, limit));
 if (rowMarkerLen < 0)
 return false;
-index += computeUnsignedVIntSize(rowMarkerLen) + rowMarkerLen;
-if (index >= limit)
+index = addNonNegative(index, computeUnsignedVIntSize(rowMarkerLen), 
rowMarkerLen);
+if (index >= limit || index < 0)
 return false;
 
-long remaining = getUnsignedVInt(bytes, index, limit);
+int remaining = toIntExact(getUnsignedVInt(bytes, index, limit));
 if (remaining < 0)
 return false;
-index += computeUnsignedVIntSize(remaining);
-if (index >= limit)
+index = addNonNegative(index, computeUnsignedVIntSize(remaining));
+if (index >= limit || index < 0)
 return false;
 
 long remainingInPartition = getUnsignedVInt(bytes, index, limit);
 if (remainingInPartition < 0)
 return false;
-index += computeUnsignedVIntSize(remainingInPartition);
+index = addNonNegative(index, 
computeUnsignedVIntSize(remainingInPartition));
 return index == limit;
 }
 
+// Following operations are similar to Math.{addExact/toIntExact}, but 
without using

[cassandra] branch trunk updated (dbadd08585 -> 616ddf812a)

[jmckenzie]

This is an automated email from the ASF dual-hosted git repository.

jmckenzie pushed a change to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git


from dbadd08585 Update ASM(9.1 to 9.3), Mockito(1.10.10 to 1.12.13) and 
ByteBuddy(3.2.4 to 4.7.0) patch by Ekaterina Dimitrova; reviewed by Brandon 
Williams for CASSANDRA-17835
 new ab481be81d Fix potential IndexOutOfBoundsException in PagingState in 
mixed mode clusters
 new 73bea0ac1e Merge branch 'cassandra-3.11' into cassandra-4.0
 new 704141541a Merge branch 'cassandra-4.0' into cassandra-4.1
 new 616ddf812a Merge branch 'cassandra-4.1' into trunk

The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 CHANGES.txt|   1 +
 .../cassandra/service/pager/PagingState.java   |  54 ---
 .../apache/cassandra/utils/vint/VIntCoding.java|   3 +
 .../service/pager/RandomizedPagingStateTest.java   | 104 +
 4 files changed, 150 insertions(+), 12 deletions(-)
 create mode 100644 
test/unit/org/apache/cassandra/service/pager/RandomizedPagingStateTest.java


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-17750) Remove dependency on Maven Ant Tasks

[David Capwell (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584430#comment-17584430
 ] 

David Capwell edited comment on CASSANDRA-17750 at 8/24/22 7:21 PM:


build was fine, but it now conflicts, [~aratnofsky] can you resolve?

Also see that build.xml includes version info and this wasn't ported to the pom

{code}
















{code}


was (Author: dcapwell):
build was fine, but it now conflicts, [~aratnofsky] can you resolve?

Also see that build.xml includes version info and this wasn't ported to the pom

{code}





















{code}

> Remove dependency on Maven Ant Tasks
> 
>
> Key: CASSANDRA-17750
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17750
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Build, Dependencies, Packaging
>Reporter: Abe Ratnofsky
>Assignee: Abe Ratnofsky
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10h 10m
>  Remaining Estimate: 0h
>
> Apache Cassandra depends on Maven Ant Tasks (MAT) during build, for declaring 
> dependencies and generating POM files from within build.xml. MAT has long 
> been retired (no commits since maintenance in 2015), has registered CVEs in 
> dependencies (CVE-2017-1000487), and encourages migration to its successor, 
> Maven Artifact Resolver Ant Tasks (MARAT).
> As part of CASSANDRA-16391 
> , mck migrated 
> dependency resolution to MARAT, but MAT is still included in our build for 
> generating POMs since MARAT does not have an alternative to the writepom task 
> provided by MAT. I have a patch ready that removes MAT completely, with a 
> workaround for POM generation.
> I am not advocating for any kind of migration away from Ant to an alternative 
> like Gradle or Maven, just to be extra clear.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17750) Remove dependency on Maven Ant Tasks

[David Capwell (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584430#comment-17584430
 ] 

David Capwell commented on CASSANDRA-17750:
---

build was fine, but it now conflicts, [~aratnofsky] can you resolve?

Also see that build.xml includes version info and this wasn't ported to the pom

{code}





















{code}

> Remove dependency on Maven Ant Tasks
> 
>
> Key: CASSANDRA-17750
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17750
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Build, Dependencies, Packaging
>Reporter: Abe Ratnofsky
>Assignee: Abe Ratnofsky
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10h 10m
>  Remaining Estimate: 0h
>
> Apache Cassandra depends on Maven Ant Tasks (MAT) during build, for declaring 
> dependencies and generating POM files from within build.xml. MAT has long 
> been retired (no commits since maintenance in 2015), has registered CVEs in 
> dependencies (CVE-2017-1000487), and encourages migration to its successor, 
> Maven Artifact Resolver Ant Tasks (MARAT).
> As part of CASSANDRA-16391 
> , mck migrated 
> dependency resolution to MARAT, but MAT is still included in our build for 
> generating POMs since MARAT does not have an alternative to the writepom task 
> provided by MAT. I have a patch ready that removes MAT completely, with a 
> workaround for POM generation.
> I am not advocating for any kind of migration away from Ant to an alternative 
> like Gradle or Maven, just to be extra clear.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17835) Upgrade ASM, ByteBuddy and Mockito on trunk

[Ekaterina Dimitrova (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ekaterina Dimitrova updated CASSANDRA-17835:

  Fix Version/s: 4.2
 (was: 4.x)
Source Control Link: 
https://github.com/apache/cassandra/commit/dbadd08585e78fbfc0c2f26575fd6ce68e8d7ba2
 Resolution: Fixed
 Status: Resolved  (was: Ready to Commit)

> Upgrade ASM, ByteBuddy and Mockito on trunk
> ---
>
> Key: CASSANDRA-17835
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17835
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.2
>
>
> In preparation to support Java 17 I would like to update ASM, ByteBuddy and 
> Mockito on trunk.
>  * ASM - from 9.1 to 9.3; From the [release 
> notes|https://asm.ow2.io/versions.html] I don't see anything disturbing for 
> us; 
>  * ByteBuddy - 1.10.10 to 1.12.13; [Release 
> notes|https://github.com/raphw/byte-buddy/blob/master/release-notes.md]; they 
> support Java 17 since 1.12.0 but I did not see an issue updating to the 
> latest version; 
>  * Mockito - 3.2.4 to 4.7.0; [Release 
> notes|https://github.com/mockito/mockito/releases/]. The bump in the major 
> version was due to removing outdated deprecated APIs which it doesn't seem 
> that we use so this is not a breaking change for us. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17835) Upgrade ASM, ByteBuddy and Mockito on trunk

[Ekaterina Dimitrova (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584350#comment-17584350
 ] 

Ekaterina Dimitrova commented on CASSANDRA-17835:
-

Committed, thanks!

To https://github.com/apache/cassandra.git

   17810295ca..dbadd08585  trunk -> trunk

> Upgrade ASM, ByteBuddy and Mockito on trunk
> ---
>
> Key: CASSANDRA-17835
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17835
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> In preparation to support Java 17 I would like to update ASM, ByteBuddy and 
> Mockito on trunk.
>  * ASM - from 9.1 to 9.3; From the [release 
> notes|https://asm.ow2.io/versions.html] I don't see anything disturbing for 
> us; 
>  * ByteBuddy - 1.10.10 to 1.12.13; [Release 
> notes|https://github.com/raphw/byte-buddy/blob/master/release-notes.md]; they 
> support Java 17 since 1.12.0 but I did not see an issue updating to the 
> latest version; 
>  * Mockito - 3.2.4 to 4.7.0; [Release 
> notes|https://github.com/mockito/mockito/releases/]. The bump in the major 
> version was due to removing outdated deprecated APIs which it doesn't seem 
> that we use so this is not a breaking change for us. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] branch trunk updated: Update ASM(9.1 to 9.3), Mockito(1.10.10 to 1.12.13) and ByteBuddy(3.2.4 to 4.7.0) patch by Ekaterina Dimitrova; reviewed by Brandon Williams for CASSANDRA-17835

[edimitrova]

This is an automated email from the ASF dual-hosted git repository.

edimitrova pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git


The following commit(s) were added to refs/heads/trunk by this push:
 new dbadd08585 Update ASM(9.1 to 9.3), Mockito(1.10.10 to 1.12.13) and 
ByteBuddy(3.2.4 to 4.7.0) patch by Ekaterina Dimitrova; reviewed by Brandon 
Williams for CASSANDRA-17835
dbadd08585 is described below

commit dbadd08585e78fbfc0c2f26575fd6ce68e8d7ba2
Author: Ekaterina Dimitrova 
AuthorDate: Thu Aug 18 15:14:56 2022 -0400

Update ASM(9.1 to 9.3), Mockito(1.10.10 to 1.12.13) and ByteBuddy(3.2.4 to 
4.7.0)
patch by Ekaterina Dimitrova; reviewed by Brandon Williams for 
CASSANDRA-17835
---
 CHANGES.txt | 1 +
 build.xml   | 6 +++---
 2 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/CHANGES.txt b/CHANGES.txt
index dee8a5e741..1375729e76 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 4.2
+ * Update ASM(9.1 to 9.3), Mockito(1.10.10 to 1.12.13) and ByteBuddy(3.2.4 to 
4.7.0) (CASSANDRA-17835)
  * Add the ability for operators to loosen the definition of "empty" for edge 
cases (CASSANDRA-17842)
  * Fix potential out of range exception on column index downsampling 
(CASSANDRA-17839)
  * Introduce target directory to vtable output for sstable_tasks and for 
compactionstats (CASSANDRA-13010)
diff --git a/build.xml b/build.xml
index 32b3fec87b..ba9b81d4bc 100644
--- a/build.xml
+++ b/build.xml
@@ -134,9 +134,9 @@
 
 
 
-
+
 
-
+
 
 
 
@@ -550,7 +550,7 @@
   
 
   
-  
+  
   
   
 


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-14715) Read repairs can result in bogus timeout errors to the client

[Jai Bheemsen Rao Dhanwada (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-14715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584057#comment-17584057
 ] 

Jai Bheemsen Rao Dhanwada edited comment on CASSANDRA-14715 at 8/24/22 4:15 PM:


[~stefan.miklosovic] do you have any estimate if this will be released anytime 
sooner? thank you


was (Author: jaid):
[~stefan.miklosovic] do you have any estimate if this will be released anything 
sooner? thank you

> Read repairs can result in bogus timeout errors to the client
> -
>
> Key: CASSANDRA-14715
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14715
> Project: Cassandra
>  Issue Type: Bug
>  Components: Legacy/Local Write-Read Paths
>Reporter: Cameron Zemek
>Priority: Low
>
> In RepairMergeListener:close() it does the following:
>  
> {code:java}
> try
> {
> FBUtilities.waitOnFutures(repairResults, 
> DatabaseDescriptor.getWriteRpcTimeout());
> }
> catch (TimeoutException ex)
> {
> // We got all responses, but timed out while repairing
> int blockFor = consistency.blockFor(keyspace);
> if (Tracing.isTracing())
> Tracing.trace("Timed out while read-repairing after receiving all {} 
> data and digest responses", blockFor);
> else
> logger.debug("Timeout while read-repairing after receiving all {} 
> data and digest responses", blockFor);
> throw new ReadTimeoutException(consistency, blockFor-1, blockFor, true);
> }
> {code}
> This propagates up and gets sent to the client and we have customers get 
> confused cause they see timeouts for CL ALL requiring ALL replicas even 
> though they have read_repair_chance = 0 and using a LOCAL_* CL.
> At minimum I suggest instead of using the consistency level of DataResolver 
> (which is always ALL with read repairs) for the timeout it instead use 
> repairResults.size(). That is blockFor = repairResults.size() . But saying it 
> received _blockFor - 1_ is bogus still. Fixing that would require more 
> changes. I was thinking maybe like so:
>  
> {code:java}
> public static void waitOnFutures(List results, long ms, 
> MutableInt counter) throws TimeoutException
> {
> for (AsyncOneResponse result : results)
> {
> result.get(ms, TimeUnit.MILLISECONDS);
> counter.increment();
> }
> }
> {code}
>  
>  
>  
> Likewise in SinglePartitionReadLifecycle:maybeAwaitFullDataRead() it says 
> _blockFor - 1_ for how many were received, which is also bogus.
>  
> Steps used to reproduce was modify RepairMergeListener:close() to always 
> throw timeout exception.  With schema:
> {noformat}
> CREATE KEYSPACE weather WITH replication = {'class': 
> 'NetworkTopologyStrategy', 'dc1': '3', 'dc2': '3'}  AND durable_writes = true;
> CREATE TABLE weather.city (
> cityid int PRIMARY KEY,
> name text
> ) WITH bloom_filter_fp_chance = 0.01
> AND dclocal_read_repair_chance = 0.0
> AND read_repair_chance = 0.0
> AND speculative_retry = 'NONE';
> {noformat}
> Then using the following steps:
>  # ccm node1 cqlsh
>  # INSERT INTO weather.city(cityid, name) VALUES (1, 'Canberra');
>  # exit;
>  # ccm node1 flush
>  # ccm node1 stop
>  # rm -rf 
> ~/.ccm/test_repair/node1/data0/weather/city-ff2fade0b18d11e8b1cd097acbab1e3d/mc-1-big-*
>  # remove the sstable with the insert
>  # ccm node1 start
>  # ccm node1 cqlsh
>  # CONSISTENCY LOCAL_QUORUM;
>  # select * from weather.city where cityid = 1;
> You get result of:
> {noformat}
> ReadTimeout: Error from server: code=1200 [Coordinator node timed out waiting 
> for replica nodes' responses] message="Operation timed out - received only 5 
> responses." info={'received_responses': 5, 'required_responses': 6, 
> 'consistency': 'ALL'}{noformat}
> But was expecting:
> {noformat}
> ReadTimeout: Error from server: code=1200 [Coordinator node timed out waiting 
> for replica nodes' responses] message="Operation timed out - received only 1 
> responses." info={'received_responses': 1, 'required_responses': 2, 
> 'consistency': 'LOCAL_QUORUM'}{noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17855) Add rat and licenses to Accord

[David Capwell (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Capwell updated CASSANDRA-17855:
--
Change Category: Code Clarity
 Complexity: Low Hanging Fruit
  Fix Version/s: NA
   Priority: Low  (was: Normal)
 Status: Open  (was: Triage Needed)

> Add rat and licenses to Accord
> --
>
> Key: CASSANDRA-17855
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17855
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Accord, Build
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Low
> Fix For: NA
>
>
> Right now accord doesn’t include rat to validate files come with a license so 
> non-licensed files may leak in; we should block the build on this.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-17855) Add rat and licenses to Accord

[David Capwell (Jira)]

David Capwell created CASSANDRA-17855:
-

 Summary: Add rat and licenses to Accord
 Key: CASSANDRA-17855
 URL: https://issues.apache.org/jira/browse/CASSANDRA-17855
 Project: Cassandra
  Issue Type: Improvement
  Components: Accord, Build
Reporter: David Capwell
Assignee: David Capwell


Right now accord doesn’t include rat to validate files come with a license so 
non-licensed files may leak in; we should block the build on this.




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-17853) Sporadic CL switch from LOCAL_QUORUM to ALL

[Manjunath Angadi (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584329#comment-17584329
 ] 

Manjunath Angadi edited comment on CASSANDRA-17853 at 8/24/22 4:07 PM:
---

Thanks [~brandon.williams] , will have a word with community

https://stackoverflow.com/questions/73476397/sporadic-consistency-level-switch-from-local-quorum-to-all


was (Author: JIRAUSER294866):
Thanks [~brandon.williams] , will have a word with community

> Sporadic CL switch from LOCAL_QUORUM to ALL
> ---
>
> Key: CASSANDRA-17853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17853
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Manjunath Angadi
>Priority: Normal
>
> Team - we see that the Consitency Level is changing to ALL, when there is a 
> read timeout.
> Used Cassandra session has next main properties:
>  * Load balancing policy - DCAwareRoundRobinPolicy(localDc, 
> usedHostPerRemoteDc = 3, allowRemoteDcForLocalConsistencyLevel = true)
>  * Retry policy - DefaultRetryPolicy
>  * Query options - QueryOptions with set consistency level to 
> ConsistencyLevel.{*}LOCAL_QUORUM{*}
>  
> we have the table as defined below.
> {code:java}
> CREATE TABLE table_name (
> key text,
> column1 text,
> column2 text,
> value text,
> PRIMARY KEY (key, column1, column2)
> ) WITH COMPACT STORAGE
> AND CLUSTERING ORDER BY (column1 ASC, column2 ASC)
> AND bloom_filter_fp_chance = 0.1
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = ''
> AND compaction = {'class': 
> 'org.apache.cassandra.db.compaction.LeveledCompactionStrategy', 
> 'sstable_size_in_mb': '180'}
> AND compression = {'chunk_length_in_kb': '64', 'class': 
> 'org.apache.cassandra.io.compress.SnappyCompressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.0
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99PERCENTILE'; {code}
>  
> On Read Timeout, below exception is observed.
> {code:java}
> Caused by: com.datastax.driver.core.exceptions.ReadTimeoutException: 
> Cassandra timeout during read query at consistency ALL (5 responses were 
> required but only 4 replica responded)
>     at 
> com.datastax.driver.core.exceptions.ReadTimeoutException.copy(ReadTimeoutException.java:88)
>  ~[cassandra-driver-core-3.1.4.jar!/:?]
>     at 
> com.datastax.driver.core.exceptions.ReadTimeoutException.copy(ReadTimeoutException.java:25)
>  ~[cassandra-driver-core-3.1.4.jar!/:?]
>     at 
> com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37)
>  ~[cassandra-driver-core-3.1.4.jar!/:?]
>     at 
> com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:245)
>  ~[cassandra-driver-core-3.1.4.jar!/:?]
>     at 
> com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:68) 
> ~[cassandra-driver-core-3.1.4.jar!/:?] {code}
> This could be an issue re-occurred in Cassandra 3.11.0, which is the version 
> used currently.Also - this could be related to 
> https://issues.apache.org/jira/browse/CASSANDRA-7868
> Please provide your feedback on the same.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-17835) Upgrade ASM, ByteBuddy and Mockito on trunk

[Ekaterina Dimitrova (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584337#comment-17584337
 ] 

Ekaterina Dimitrova edited comment on CASSANDRA-17835 at 8/24/22 4:07 PM:
--

The CI runs completed. Python DTests job marked as failed but when we open [the 
results|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1877/workflows/71dfcea3-69f5-42a6-a8e6-86d0d7e22c3e/jobs/14750]
 all tests have passed and the number is the same as in the previous  
[run|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1876/workflows/f64b3ed2-161b-43df-a0f9-af4b2429e86a/jobs/14707]
 so I don't think we need to spend more time on that.

The unit tests - I didn't find it failing in Butler or a ticket filed but I 
found it mentioned as failing on another ticket CASSANDRA-17416. It doesn't 
fail locally for me so it seems as just another flaky test...

I will see to file a Jira ticket- testNonFrozenEmptyCollection[0: 
clusterMinVersion=3.0]

Starting commit


was (Author: e.dimitrova):
The CI runs completed. Python DTests job marked as failed but when we open the 
results all tests have passed and the number is the same as in the previous 
green run so I don't think we need to spend more time on that.

The unit tests - I didn't find it failing in Butler or a ticket filed but I 
found it mentioned as failing on another ticket CASSANDRA-17416. It doesn't 
fail locally for me so it seems as just another flaky test...

I will see to file a Jira ticket- testNonFrozenEmptyCollection[0: 
clusterMinVersion=3.0]

Starting commit

> Upgrade ASM, ByteBuddy and Mockito on trunk
> ---
>
> Key: CASSANDRA-17835
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17835
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> In preparation to support Java 17 I would like to update ASM, ByteBuddy and 
> Mockito on trunk.
>  * ASM - from 9.1 to 9.3; From the [release 
> notes|https://asm.ow2.io/versions.html] I don't see anything disturbing for 
> us; 
>  * ByteBuddy - 1.10.10 to 1.12.13; [Release 
> notes|https://github.com/raphw/byte-buddy/blob/master/release-notes.md]; they 
> support Java 17 since 1.12.0 but I did not see an issue updating to the 
> latest version; 
>  * Mockito - 3.2.4 to 4.7.0; [Release 
> notes|https://github.com/mockito/mockito/releases/]. The bump in the major 
> version was due to removing outdated deprecated APIs which it doesn't seem 
> that we use so this is not a breaking change for us. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17835) Upgrade ASM, ByteBuddy and Mockito on trunk

[Ekaterina Dimitrova (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584337#comment-17584337
 ] 

Ekaterina Dimitrova commented on CASSANDRA-17835:
-

The CI runs completed. Python DTests job marked as failed but when we open the 
results all tests have passed and the number is the same as in the previous 
green run so I don't think we need to spend more time on that.

The unit tests - I didn't find it failing in Butler or a ticket filed but I 
found it mentioned as failing on another ticket CASSANDRA-17416. It doesn't 
fail locally for me so it seems as just another flaky test...

I will see to file a Jira ticket- testNonFrozenEmptyCollection[0: 
clusterMinVersion=3.0]

Starting commit

> Upgrade ASM, ByteBuddy and Mockito on trunk
> ---
>
> Key: CASSANDRA-17835
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17835
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> In preparation to support Java 17 I would like to update ASM, ByteBuddy and 
> Mockito on trunk.
>  * ASM - from 9.1 to 9.3; From the [release 
> notes|https://asm.ow2.io/versions.html] I don't see anything disturbing for 
> us; 
>  * ByteBuddy - 1.10.10 to 1.12.13; [Release 
> notes|https://github.com/raphw/byte-buddy/blob/master/release-notes.md]; they 
> support Java 17 since 1.12.0 but I did not see an issue updating to the 
> latest version; 
>  * Mockito - 3.2.4 to 4.7.0; [Release 
> notes|https://github.com/mockito/mockito/releases/]. The bump in the major 
> version was due to removing outdated deprecated APIs which it doesn't seem 
> that we use so this is not a breaking change for us. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17853) Sporadic CL switch from LOCAL_QUORUM to ALL

[Manjunath Angadi (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584329#comment-17584329
 ] 

Manjunath Angadi commented on CASSANDRA-17853:
--

Thanks [~brandon.williams] , will have a word with community

> Sporadic CL switch from LOCAL_QUORUM to ALL
> ---
>
> Key: CASSANDRA-17853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17853
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Manjunath Angadi
>Priority: Normal
>
> Team - we see that the Consitency Level is changing to ALL, when there is a 
> read timeout.
> Used Cassandra session has next main properties:
>  * Load balancing policy - DCAwareRoundRobinPolicy(localDc, 
> usedHostPerRemoteDc = 3, allowRemoteDcForLocalConsistencyLevel = true)
>  * Retry policy - DefaultRetryPolicy
>  * Query options - QueryOptions with set consistency level to 
> ConsistencyLevel.{*}LOCAL_QUORUM{*}
>  
> we have the table as defined below.
> {code:java}
> CREATE TABLE table_name (
> key text,
> column1 text,
> column2 text,
> value text,
> PRIMARY KEY (key, column1, column2)
> ) WITH COMPACT STORAGE
> AND CLUSTERING ORDER BY (column1 ASC, column2 ASC)
> AND bloom_filter_fp_chance = 0.1
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = ''
> AND compaction = {'class': 
> 'org.apache.cassandra.db.compaction.LeveledCompactionStrategy', 
> 'sstable_size_in_mb': '180'}
> AND compression = {'chunk_length_in_kb': '64', 'class': 
> 'org.apache.cassandra.io.compress.SnappyCompressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.0
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99PERCENTILE'; {code}
>  
> On Read Timeout, below exception is observed.
> {code:java}
> Caused by: com.datastax.driver.core.exceptions.ReadTimeoutException: 
> Cassandra timeout during read query at consistency ALL (5 responses were 
> required but only 4 replica responded)
>     at 
> com.datastax.driver.core.exceptions.ReadTimeoutException.copy(ReadTimeoutException.java:88)
>  ~[cassandra-driver-core-3.1.4.jar!/:?]
>     at 
> com.datastax.driver.core.exceptions.ReadTimeoutException.copy(ReadTimeoutException.java:25)
>  ~[cassandra-driver-core-3.1.4.jar!/:?]
>     at 
> com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37)
>  ~[cassandra-driver-core-3.1.4.jar!/:?]
>     at 
> com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:245)
>  ~[cassandra-driver-core-3.1.4.jar!/:?]
>     at 
> com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:68) 
> ~[cassandra-driver-core-3.1.4.jar!/:?] {code}
> This could be an issue re-occurred in Cassandra 3.11.0, which is the version 
> used currently.Also - this could be related to 
> https://issues.apache.org/jira/browse/CASSANDRA-7868
> Please provide your feedback on the same.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17854) Add JDK17 to our test docker images

[Ekaterina Dimitrova (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584315#comment-17584315
 ] 

Ekaterina Dimitrova commented on CASSANDRA-17854:
-

Change to our docker image suggested 
[here|https://github.com/apache/cassandra-builds/pull/80]

I can push an image to docker hub and test all branches in CircleCI and Jenkins 
when I get confirmation I didn't miss anything. (It is time and resource 
consuming so I would prefer to wait)

[~mck] , can you, please, take a look when you have a few minutes? Thanks in 
advance!

PS A few months ago I built an 
[image|https://hub.docker.com/layers/192193364/edimitrova86/cassandra-testing-base-w-dependencies/latest/images/sha256-2f7eb506b4ad57e5a314be4b1c708cdd39bfa28f608d6df9117b1a5e7e8892c3?context=repo]
 and I did [testing 
|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1481/workflows/9f065c12-4c3d-4d6e-b9fc-ee4eb8c5f38b]with
 the 4.1 branch so I have the baseline to think this should be the change we 
need :) 

> Add JDK17 to our test docker images
> ---
>
> Key: CASSANDRA-17854
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17854
> Project: Cassandra
>  Issue Type: Task
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> In preparation to support JDK 17 I want to add JDK 17 to our test images to 
> enable our CIs for testing with JDK 17
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17854) Add JDK17 to our test docker images

[Ekaterina Dimitrova (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ekaterina Dimitrova updated CASSANDRA-17854:

Fix Version/s: 4.x

> Add JDK17 to our test docker images
> ---
>
> Key: CASSANDRA-17854
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17854
> Project: Cassandra
>  Issue Type: Task
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> In preparation to support JDK 17 I want to add JDK 17 to our test images to 
> enable our CIs for testing with JDK 17
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-17854) Add JDK17 to our test docker images

[Ekaterina Dimitrova (Jira)]

Ekaterina Dimitrova created CASSANDRA-17854:
---

 Summary: Add JDK17 to our test docker images
 Key: CASSANDRA-17854
 URL: https://issues.apache.org/jira/browse/CASSANDRA-17854
 Project: Cassandra
  Issue Type: Task
Reporter: Ekaterina Dimitrova


In preparation to support JDK 17 I want to add JDK 17 to our test images to 
enable our CIs for testing with JDK 17

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17854) Add JDK17 to our test docker images

[Ekaterina Dimitrova (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ekaterina Dimitrova updated CASSANDRA-17854:

Change Category: Quality Assurance
 Complexity: Low Hanging Fruit
Component/s: CI
   Assignee: Ekaterina Dimitrova
 Status: Open  (was: Triage Needed)

> Add JDK17 to our test docker images
> ---
>
> Key: CASSANDRA-17854
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17854
> Project: Cassandra
>  Issue Type: Task
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
>
> In preparation to support JDK 17 I want to add JDK 17 to our test images to 
> enable our CIs for testing with JDK 17
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17835) Upgrade ASM, ByteBuddy and Mockito on trunk

[Brandon Williams (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584281#comment-17584281
 ] 

Brandon Williams commented on CASSANDRA-17835:
--

I concur, it's not necessary.

> Upgrade ASM, ByteBuddy and Mockito on trunk
> ---
>
> Key: CASSANDRA-17835
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17835
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> In preparation to support Java 17 I would like to update ASM, ByteBuddy and 
> Mockito on trunk.
>  * ASM - from 9.1 to 9.3; From the [release 
> notes|https://asm.ow2.io/versions.html] I don't see anything disturbing for 
> us; 
>  * ByteBuddy - 1.10.10 to 1.12.13; [Release 
> notes|https://github.com/raphw/byte-buddy/blob/master/release-notes.md]; they 
> support Java 17 since 1.12.0 but I did not see an issue updating to the 
> latest version; 
>  * Mockito - 3.2.4 to 4.7.0; [Release 
> notes|https://github.com/mockito/mockito/releases/]. The bump in the major 
> version was due to removing outdated deprecated APIs which it doesn't seem 
> that we use so this is not a breaking change for us. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17835) Upgrade ASM, ByteBuddy and Mockito on trunk

[Ekaterina Dimitrova (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584280#comment-17584280
 ] 

Ekaterina Dimitrova commented on CASSANDRA-17835:
-

{quote}Well, it was an upgrade test so it seemed worth checking :)
{quote}
Always! Thanks :) 

I noticed the branch is already 6 days old so I rebased and pushed the 
pre-commit tests in CircleCI for last sanity check. Let me know if you want me 
still to push again to Jenkins, looking into the changes in the past week I 
think it will be overkill.

[J8|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1877/workflows/71dfcea3-69f5-42a6-a8e6-86d0d7e22c3e],
 
[J11|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1877/workflows/fad8cfb6-9d14-412b-ad07-b72ce38cd402]

> Upgrade ASM, ByteBuddy and Mockito on trunk
> ---
>
> Key: CASSANDRA-17835
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17835
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> In preparation to support Java 17 I would like to update ASM, ByteBuddy and 
> Mockito on trunk.
>  * ASM - from 9.1 to 9.3; From the [release 
> notes|https://asm.ow2.io/versions.html] I don't see anything disturbing for 
> us; 
>  * ByteBuddy - 1.10.10 to 1.12.13; [Release 
> notes|https://github.com/raphw/byte-buddy/blob/master/release-notes.md]; they 
> support Java 17 since 1.12.0 but I did not see an issue updating to the 
> latest version; 
>  * Mockito - 3.2.4 to 4.7.0; [Release 
> notes|https://github.com/mockito/mockito/releases/]. The bump in the major 
> version was due to removing outdated deprecated APIs which it doesn't seem 
> that we use so this is not a breaking change for us. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17835) Upgrade ASM, ByteBuddy and Mockito on trunk

[Brandon Williams (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584264#comment-17584264
 ] 

Brandon Williams commented on CASSANDRA-17835:
--

Well, it was an upgrade test so it seemed worth checking :)

> Upgrade ASM, ByteBuddy and Mockito on trunk
> ---
>
> Key: CASSANDRA-17835
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17835
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> In preparation to support Java 17 I would like to update ASM, ByteBuddy and 
> Mockito on trunk.
>  * ASM - from 9.1 to 9.3; From the [release 
> notes|https://asm.ow2.io/versions.html] I don't see anything disturbing for 
> us; 
>  * ByteBuddy - 1.10.10 to 1.12.13; [Release 
> notes|https://github.com/raphw/byte-buddy/blob/master/release-notes.md]; they 
> support Java 17 since 1.12.0 but I did not see an issue updating to the 
> latest version; 
>  * Mockito - 3.2.4 to 4.7.0; [Release 
> notes|https://github.com/mockito/mockito/releases/]. The bump in the major 
> version was due to removing outdated deprecated APIs which it doesn't seem 
> that we use so this is not a breaking change for us. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17835) Upgrade ASM, ByteBuddy and Mockito on trunk

[Ekaterina Dimitrova (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584262#comment-17584262
 ] 

Ekaterina Dimitrova commented on CASSANDRA-17835:
-

Thanks [~brandon.williams], I also do not really expect the Python Dtests to be 
affected but who knows. :) Thanks for testing 

> Upgrade ASM, ByteBuddy and Mockito on trunk
> ---
>
> Key: CASSANDRA-17835
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17835
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> In preparation to support Java 17 I would like to update ASM, ByteBuddy and 
> Mockito on trunk.
>  * ASM - from 9.1 to 9.3; From the [release 
> notes|https://asm.ow2.io/versions.html] I don't see anything disturbing for 
> us; 
>  * ByteBuddy - 1.10.10 to 1.12.13; [Release 
> notes|https://github.com/raphw/byte-buddy/blob/master/release-notes.md]; they 
> support Java 17 since 1.12.0 but I did not see an issue updating to the 
> latest version; 
>  * Mockito - 3.2.4 to 4.7.0; [Release 
> notes|https://github.com/mockito/mockito/releases/]. The bump in the major 
> version was due to removing outdated deprecated APIs which it doesn't seem 
> that we use so this is not a breaking change for us. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17852) WEBSITE - Community page - encourage users to search answered questions on Stack Overflow, Stack Exchange

[Ekaterina Dimitrova (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584261#comment-17584261
 ] 

Ekaterina Dimitrova commented on CASSANDRA-17852:
-

One last thing - you change User Slack to Chat but we keep Developer Slack, I 
think User Slack was fine and the flow will be more consistent

> WEBSITE - Community page - encourage users to search answered questions on 
> Stack Overflow, Stack Exchange
> -
>
> Key: CASSANDRA-17852
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17852
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: 4.0.x
>
> Attachments: c17852-01-community-discussions-v1.png
>
>
> We need to encourage users to first search the {{[cassandra]}} tag on [Stack 
> Overflow|http://stackoverflow.com/questions/tagged/cassandra] and [Stack 
> Exchange|https://dba.stackexchange.com/questions/tagged/cassandra] before 
> asking a question so contributors are not repeatedly asking the same 
> questions over and over.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17852) WEBSITE - Community page - encourage users to search answered questions on Stack Overflow, Stack Exchange

[Ekaterina Dimitrova (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584257#comment-17584257
 ] 

Ekaterina Dimitrova commented on CASSANDRA-17852:
-

Overall LGTM, thanks! I left just two comments.

I have two questions:

1) How hard it is to have a bot to cross post new stack questions in Slack? Not 
sure it is feasible

2) I remember some time ago you were preparing a template for new questions 
that people can use. Is this finished and can we link it on this page?

> WEBSITE - Community page - encourage users to search answered questions on 
> Stack Overflow, Stack Exchange
> -
>
> Key: CASSANDRA-17852
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17852
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: 4.0.x
>
> Attachments: c17852-01-community-discussions-v1.png
>
>
> We need to encourage users to first search the {{[cassandra]}} tag on [Stack 
> Overflow|http://stackoverflow.com/questions/tagged/cassandra] and [Stack 
> Exchange|https://dba.stackexchange.com/questions/tagged/cassandra] before 
> asking a question so contributors are not repeatedly asking the same 
> questions over and over.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17835) Upgrade ASM, ByteBuddy and Mockito on trunk

[Brandon Williams (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-17835:
-
Status: Ready to Commit  (was: Review In Progress)

> Upgrade ASM, ByteBuddy and Mockito on trunk
> ---
>
> Key: CASSANDRA-17835
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17835
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> In preparation to support Java 17 I would like to update ASM, ByteBuddy and 
> Mockito on trunk.
>  * ASM - from 9.1 to 9.3; From the [release 
> notes|https://asm.ow2.io/versions.html] I don't see anything disturbing for 
> us; 
>  * ByteBuddy - 1.10.10 to 1.12.13; [Release 
> notes|https://github.com/raphw/byte-buddy/blob/master/release-notes.md]; they 
> support Java 17 since 1.12.0 but I did not see an issue updating to the 
> latest version; 
>  * Mockito - 3.2.4 to 4.7.0; [Release 
> notes|https://github.com/mockito/mockito/releases/]. The bump in the major 
> version was due to removing outdated deprecated APIs which it doesn't seem 
> that we use so this is not a breaking change for us. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17852) WEBSITE - Community page - encourage users to search answered questions on Stack Overflow, Stack Exchange

[Ekaterina Dimitrova (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ekaterina Dimitrova updated CASSANDRA-17852:

Reviewers: Ekaterina Dimitrova
   Status: Review In Progress  (was: Patch Available)

> WEBSITE - Community page - encourage users to search answered questions on 
> Stack Overflow, Stack Exchange
> -
>
> Key: CASSANDRA-17852
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17852
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: 4.0.x
>
> Attachments: c17852-01-community-discussions-v1.png
>
>
> We need to encourage users to first search the {{[cassandra]}} tag on [Stack 
> Overflow|http://stackoverflow.com/questions/tagged/cassandra] and [Stack 
> Exchange|https://dba.stackexchange.com/questions/tagged/cassandra] before 
> asking a question so contributors are not repeatedly asking the same 
> questions over and over.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17840) IndexOutOfBoundsException in Paging State Version Inference (V3 State Received on V4 Connection)

[Sam Tunnicliffe (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sam Tunnicliffe updated CASSANDRA-17840:

Status: Ready to Commit  (was: Review In Progress)

LGTM. The test failures on the 3.11 branch are unrelated and/or unreproducible 
locally.

> IndexOutOfBoundsException in Paging State Version Inference (V3 State 
> Received on V4 Connection)
> 
>
> Key: CASSANDRA-17840
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17840
> Project: Cassandra
>  Issue Type: Bug
>  Components: Messaging/Client
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 3.11.x, 4.0.x, 4.1.x, 4.x
>
>
> In {{PagingState.java}}, {{index}} is an integer field, and we add long 
> values to it without a {{Math.toIntExact}} check. While we’re checking for 
> negative return values returned by {{getUnsignedVInt}}, there's a chance that 
> the value returned by it is so large that addition operation would cause 
> integer overflow, or the value itself is large enough to cause overflow.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17840) IndexOutOfBoundsException in Paging State Version Inference (V3 State Received on V4 Connection)

[Sam Tunnicliffe (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sam Tunnicliffe updated CASSANDRA-17840:

Reviewers: Sam Tunnicliffe, Sam Tunnicliffe
   Sam Tunnicliffe, Sam Tunnicliffe  (was: Sam Tunnicliffe)
   Status: Review In Progress  (was: Patch Available)

> IndexOutOfBoundsException in Paging State Version Inference (V3 State 
> Received on V4 Connection)
> 
>
> Key: CASSANDRA-17840
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17840
> Project: Cassandra
>  Issue Type: Bug
>  Components: Messaging/Client
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 3.11.x, 4.0.x, 4.1.x, 4.x
>
>
> In {{PagingState.java}}, {{index}} is an integer field, and we add long 
> values to it without a {{Math.toIntExact}} check. While we’re checking for 
> negative return values returned by {{getUnsignedVInt}}, there's a chance that 
> the value returned by it is so large that addition operation would cause 
> integer overflow, or the value itself is large enough to cause overflow.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17852) WEBSITE - Community page - encourage users to search answered questions on Stack Overflow, Stack Exchange

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17852:
--
Test and Documentation Plan: Verify changes to the "user" section of the 
Community page.
 Status: Patch Available  (was: In Progress)

||Branch||PR||
|{{trunk}}|[#167|https://github.com/apache/cassandra-website/pull/167]|

 !c17852-01-community-discussions-v1.png|width=300!

> WEBSITE - Community page - encourage users to search answered questions on 
> Stack Overflow, Stack Exchange
> -
>
> Key: CASSANDRA-17852
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17852
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: 4.0.x
>
> Attachments: c17852-01-community-discussions-v1.png
>
>
> We need to encourage users to first search the {{[cassandra]}} tag on [Stack 
> Overflow|http://stackoverflow.com/questions/tagged/cassandra] and [Stack 
> Exchange|https://dba.stackexchange.com/questions/tagged/cassandra] before 
> asking a question so contributors are not repeatedly asking the same 
> questions over and over.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17040) Upgrade Snappy version to support Apple M1

[Sebastian Albrecht (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584185#comment-17584185
 ] 

Sebastian Albrecht commented on CASSANDRA-17040:


Nvm, found it in 
https://github.com/apache/cassandra/blob/cassandra-4.1-alpha1/build.xml#L575 so 
i am confident it will be included in 4.1.

> Upgrade Snappy version to support Apple M1
> --
>
> Key: CASSANDRA-17040
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17040
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Feature/Compression
>Reporter: Yuqi Gu
>Assignee: Yuqi Gu
>Priority: Normal
> Fix For: 4.1, 4.1-alpha1
>
> Attachments: UTs.txt, UTs_2.txt
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Some Unit test cases were failed in Apple M1:
>  
> {code:java}
> [junit-timeout] Testcase: 
> testTableOptions(org.apache.cassandra.cql3.validation.miscellaneous.OverflowTest):
>  Caused an ERROR
> [junit-timeout] SnappyCompressor.create() threw an error: 
> java.lang.NoClassDefFoundError Could not initialize class 
> org.xerial.snappy.Snappy
> [junit-timeout] org.apache.cassandra.exceptions.ConfigurationException: 
> SnappyCompressor.create() threw an error: java.lang.NoClassDefFoundError 
> Could not initialize class org.xerial.snappy.Snappy
> [junit-timeout] at 
> org.apache.cassandra.schema.CompressionParams.createCompressor(CompressionParams.java:344)
> [junit-timeout] at 
> org.apache.cassandra.schema.CompressionParams.(CompressionParams.java:211)
> [junit-timeout] at 
> org.apache.cassandra.schema.CompressionParams.fromMap(CompressionParams.java:124)
> [junit-timeout] at 
> org.apache.cassandra.cql3.statements.schema.TableAttributes.build(TableAttributes.java:110)
> [junit-timeout] at 
> org.apache.cassandra.cql3.statements.schema.TableAttributes.validate(TableAttributes.java:58)
> [junit-timeout] at
> 
> ...
> ..
>  
> {code}
>  
> Snappy-java added M1 support since 
> 1.1.8.2.([https://github.com/xerial/snappy-java/pull/268).]
> So  let's upgrade snappy-java dependency to the latest release 1.1.8.4.
>  
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17040) Upgrade Snappy version to support Apple M1

[Sebastian Albrecht (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584179#comment-17584179
 ] 

Sebastian Albrecht commented on CASSANDRA-17040:


[~yqGu] Can you please explain why in the commit 
https://github.com/apache/cassandra/commit/2043cb9fb6b25ff34afb90467b9476a09acc3933
 the JNA  was updated to 5.9.0 but in the PR 
https://github.com/apache/cassandra/pull/1268/files not anymore?

> Upgrade Snappy version to support Apple M1
> --
>
> Key: CASSANDRA-17040
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17040
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Feature/Compression
>Reporter: Yuqi Gu
>Assignee: Yuqi Gu
>Priority: Normal
> Fix For: 4.1, 4.1-alpha1
>
> Attachments: UTs.txt, UTs_2.txt
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Some Unit test cases were failed in Apple M1:
>  
> {code:java}
> [junit-timeout] Testcase: 
> testTableOptions(org.apache.cassandra.cql3.validation.miscellaneous.OverflowTest):
>  Caused an ERROR
> [junit-timeout] SnappyCompressor.create() threw an error: 
> java.lang.NoClassDefFoundError Could not initialize class 
> org.xerial.snappy.Snappy
> [junit-timeout] org.apache.cassandra.exceptions.ConfigurationException: 
> SnappyCompressor.create() threw an error: java.lang.NoClassDefFoundError 
> Could not initialize class org.xerial.snappy.Snappy
> [junit-timeout] at 
> org.apache.cassandra.schema.CompressionParams.createCompressor(CompressionParams.java:344)
> [junit-timeout] at 
> org.apache.cassandra.schema.CompressionParams.(CompressionParams.java:211)
> [junit-timeout] at 
> org.apache.cassandra.schema.CompressionParams.fromMap(CompressionParams.java:124)
> [junit-timeout] at 
> org.apache.cassandra.cql3.statements.schema.TableAttributes.build(TableAttributes.java:110)
> [junit-timeout] at 
> org.apache.cassandra.cql3.statements.schema.TableAttributes.validate(TableAttributes.java:58)
> [junit-timeout] at
> 
> ...
> ..
>  
> {code}
>  
> Snappy-java added M1 support since 
> 1.1.8.2.([https://github.com/xerial/snappy-java/pull/268).]
> So  let's upgrade snappy-java dependency to the latest release 1.1.8.4.
>  
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17853) Sporadic CL switch from LOCAL_QUORUM to ALL

[Brandon Williams (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-17853:
-
Resolution: Invalid
Status: Resolved  (was: Triage Needed)

This jira is for the development of Apache Cassandra and makes for a poor 
vehicle for support, so I recommend contacting the community via slack or the 
user ML for assisstance: https://cassandra.apache.org/_/community.html

> Sporadic CL switch from LOCAL_QUORUM to ALL
> ---
>
> Key: CASSANDRA-17853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17853
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Manjunath Angadi
>Priority: Normal
>
> Team - we see that the Consitency Level is changing to ALL, when there is a 
> read timeout.
> Used Cassandra session has next main properties:
>  * Load balancing policy - DCAwareRoundRobinPolicy(localDc, 
> usedHostPerRemoteDc = 3, allowRemoteDcForLocalConsistencyLevel = true)
>  * Retry policy - DefaultRetryPolicy
>  * Query options - QueryOptions with set consistency level to 
> ConsistencyLevel.{*}LOCAL_QUORUM{*}
>  
> we have the table as defined below.
> {code:java}
> CREATE TABLE table_name (
> key text,
> column1 text,
> column2 text,
> value text,
> PRIMARY KEY (key, column1, column2)
> ) WITH COMPACT STORAGE
> AND CLUSTERING ORDER BY (column1 ASC, column2 ASC)
> AND bloom_filter_fp_chance = 0.1
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = ''
> AND compaction = {'class': 
> 'org.apache.cassandra.db.compaction.LeveledCompactionStrategy', 
> 'sstable_size_in_mb': '180'}
> AND compression = {'chunk_length_in_kb': '64', 'class': 
> 'org.apache.cassandra.io.compress.SnappyCompressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.0
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99PERCENTILE'; {code}
>  
> On Read Timeout, below exception is observed.
> {code:java}
> Caused by: com.datastax.driver.core.exceptions.ReadTimeoutException: 
> Cassandra timeout during read query at consistency ALL (5 responses were 
> required but only 4 replica responded)
>     at 
> com.datastax.driver.core.exceptions.ReadTimeoutException.copy(ReadTimeoutException.java:88)
>  ~[cassandra-driver-core-3.1.4.jar!/:?]
>     at 
> com.datastax.driver.core.exceptions.ReadTimeoutException.copy(ReadTimeoutException.java:25)
>  ~[cassandra-driver-core-3.1.4.jar!/:?]
>     at 
> com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37)
>  ~[cassandra-driver-core-3.1.4.jar!/:?]
>     at 
> com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:245)
>  ~[cassandra-driver-core-3.1.4.jar!/:?]
>     at 
> com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:68) 
> ~[cassandra-driver-core-3.1.4.jar!/:?] {code}
> This could be an issue re-occurred in Cassandra 3.11.0, which is the version 
> used currently.Also - this could be related to 
> https://issues.apache.org/jira/browse/CASSANDRA-7868
> Please provide your feedback on the same.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17835) Upgrade ASM, ByteBuddy and Mockito on trunk

[Brandon Williams (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584173#comment-17584173
 ] 

Brandon Williams commented on CASSANDRA-17835:
--

The only new failure was a timeout, and I confirmed it was environmental by 
running the upgrade test locally. +1

> Upgrade ASM, ByteBuddy and Mockito on trunk
> ---
>
> Key: CASSANDRA-17835
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17835
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> In preparation to support Java 17 I would like to update ASM, ByteBuddy and 
> Mockito on trunk.
>  * ASM - from 9.1 to 9.3; From the [release 
> notes|https://asm.ow2.io/versions.html] I don't see anything disturbing for 
> us; 
>  * ByteBuddy - 1.10.10 to 1.12.13; [Release 
> notes|https://github.com/raphw/byte-buddy/blob/master/release-notes.md]; they 
> support Java 17 since 1.12.0 but I did not see an issue updating to the 
> latest version; 
>  * Mockito - 3.2.4 to 4.7.0; [Release 
> notes|https://github.com/mockito/mockito/releases/]. The bump in the major 
> version was due to removing outdated deprecated APIs which it doesn't seem 
> that we use so this is not a breaking change for us. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-17853) Sporadic CL switch from LOCAL_QUORUM to ALL

[Manjunath Angadi (Jira)]

Manjunath Angadi created CASSANDRA-17853:


 Summary: Sporadic CL switch from LOCAL_QUORUM to ALL
 Key: CASSANDRA-17853
 URL: https://issues.apache.org/jira/browse/CASSANDRA-17853
 Project: Cassandra
  Issue Type: Bug
Reporter: Manjunath Angadi


Team - we see that the Consitency Level is changing to ALL, when there is a 
read timeout.

Used Cassandra session has next main properties:
 * Load balancing policy - DCAwareRoundRobinPolicy(localDc, usedHostPerRemoteDc 
= 3, allowRemoteDcForLocalConsistencyLevel = true)
 * Retry policy - DefaultRetryPolicy
 * Query options - QueryOptions with set consistency level to 
ConsistencyLevel.{*}LOCAL_QUORUM{*}

 

we have the table as defined below.
{code:java}
CREATE TABLE table_name (
key text,
column1 text,
column2 text,
value text,
PRIMARY KEY (key, column1, column2)
) WITH COMPACT STORAGE
AND CLUSTERING ORDER BY (column1 ASC, column2 ASC)
AND bloom_filter_fp_chance = 0.1
AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND comment = ''
AND compaction = {'class': 
'org.apache.cassandra.db.compaction.LeveledCompactionStrategy', 
'sstable_size_in_mb': '180'}
AND compression = {'chunk_length_in_kb': '64', 'class': 
'org.apache.cassandra.io.compress.SnappyCompressor'}
AND crc_check_chance = 1.0
AND dclocal_read_repair_chance = 0.0
AND default_time_to_live = 0
AND gc_grace_seconds = 864000
AND max_index_interval = 2048
AND memtable_flush_period_in_ms = 0
AND min_index_interval = 128
AND read_repair_chance = 0.0
AND speculative_retry = '99PERCENTILE'; {code}
 

On Read Timeout, below exception is observed.
{code:java}
Caused by: com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra 
timeout during read query at consistency ALL (5 responses were required but 
only 4 replica responded)
    at 
com.datastax.driver.core.exceptions.ReadTimeoutException.copy(ReadTimeoutException.java:88)
 ~[cassandra-driver-core-3.1.4.jar!/:?]
    at 
com.datastax.driver.core.exceptions.ReadTimeoutException.copy(ReadTimeoutException.java:25)
 ~[cassandra-driver-core-3.1.4.jar!/:?]
    at 
com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37)
 ~[cassandra-driver-core-3.1.4.jar!/:?]
    at 
com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:245)
 ~[cassandra-driver-core-3.1.4.jar!/:?]
    at 
com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:68) 
~[cassandra-driver-core-3.1.4.jar!/:?] {code}
This could be an issue re-occurred in Cassandra 3.11.0, which is the version 
used currently.Also - this could be related to 
https://issues.apache.org/jira/browse/CASSANDRA-7868

Please provide your feedback on the same.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra-website] branch asf-staging updated (0b926df5 -> c44d0ac3)

[git-site-role]

This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git


 discard 0b926df5 generate docs for 8cf784cf
 new c44d0ac3 generate docs for 8cf784cf

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   (0b926df5)
\
 N -- N -- N   refs/heads/asf-staging (c44d0ac3)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Assigned] (CASSANDRA-14715) Read repairs can result in bogus timeout errors to the client

[Stefan Miklosovic (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic reassigned CASSANDRA-14715:
-

Assignee: Stefan Miklosovic

> Read repairs can result in bogus timeout errors to the client
> -
>
> Key: CASSANDRA-14715
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14715
> Project: Cassandra
>  Issue Type: Bug
>  Components: Legacy/Local Write-Read Paths
>Reporter: Cameron Zemek
>Assignee: Stefan Miklosovic
>Priority: Low
>
> In RepairMergeListener:close() it does the following:
>  
> {code:java}
> try
> {
> FBUtilities.waitOnFutures(repairResults, 
> DatabaseDescriptor.getWriteRpcTimeout());
> }
> catch (TimeoutException ex)
> {
> // We got all responses, but timed out while repairing
> int blockFor = consistency.blockFor(keyspace);
> if (Tracing.isTracing())
> Tracing.trace("Timed out while read-repairing after receiving all {} 
> data and digest responses", blockFor);
> else
> logger.debug("Timeout while read-repairing after receiving all {} 
> data and digest responses", blockFor);
> throw new ReadTimeoutException(consistency, blockFor-1, blockFor, true);
> }
> {code}
> This propagates up and gets sent to the client and we have customers get 
> confused cause they see timeouts for CL ALL requiring ALL replicas even 
> though they have read_repair_chance = 0 and using a LOCAL_* CL.
> At minimum I suggest instead of using the consistency level of DataResolver 
> (which is always ALL with read repairs) for the timeout it instead use 
> repairResults.size(). That is blockFor = repairResults.size() . But saying it 
> received _blockFor - 1_ is bogus still. Fixing that would require more 
> changes. I was thinking maybe like so:
>  
> {code:java}
> public static void waitOnFutures(List results, long ms, 
> MutableInt counter) throws TimeoutException
> {
> for (AsyncOneResponse result : results)
> {
> result.get(ms, TimeUnit.MILLISECONDS);
> counter.increment();
> }
> }
> {code}
>  
>  
>  
> Likewise in SinglePartitionReadLifecycle:maybeAwaitFullDataRead() it says 
> _blockFor - 1_ for how many were received, which is also bogus.
>  
> Steps used to reproduce was modify RepairMergeListener:close() to always 
> throw timeout exception.  With schema:
> {noformat}
> CREATE KEYSPACE weather WITH replication = {'class': 
> 'NetworkTopologyStrategy', 'dc1': '3', 'dc2': '3'}  AND durable_writes = true;
> CREATE TABLE weather.city (
> cityid int PRIMARY KEY,
> name text
> ) WITH bloom_filter_fp_chance = 0.01
> AND dclocal_read_repair_chance = 0.0
> AND read_repair_chance = 0.0
> AND speculative_retry = 'NONE';
> {noformat}
> Then using the following steps:
>  # ccm node1 cqlsh
>  # INSERT INTO weather.city(cityid, name) VALUES (1, 'Canberra');
>  # exit;
>  # ccm node1 flush
>  # ccm node1 stop
>  # rm -rf 
> ~/.ccm/test_repair/node1/data0/weather/city-ff2fade0b18d11e8b1cd097acbab1e3d/mc-1-big-*
>  # remove the sstable with the insert
>  # ccm node1 start
>  # ccm node1 cqlsh
>  # CONSISTENCY LOCAL_QUORUM;
>  # select * from weather.city where cityid = 1;
> You get result of:
> {noformat}
> ReadTimeout: Error from server: code=1200 [Coordinator node timed out waiting 
> for replica nodes' responses] message="Operation timed out - received only 5 
> responses." info={'received_responses': 5, 'required_responses': 6, 
> 'consistency': 'ALL'}{noformat}
> But was expecting:
> {noformat}
> ReadTimeout: Error from server: code=1200 [Coordinator node timed out waiting 
> for replica nodes' responses] message="Operation timed out - received only 1 
> responses." info={'received_responses': 1, 'required_responses': 2, 
> 'consistency': 'LOCAL_QUORUM'}{noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Assigned] (CASSANDRA-14715) Read repairs can result in bogus timeout errors to the client

[Stefan Miklosovic (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic reassigned CASSANDRA-14715:
-

Assignee: (was: Stefan Miklosovic)

> Read repairs can result in bogus timeout errors to the client
> -
>
> Key: CASSANDRA-14715
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14715
> Project: Cassandra
>  Issue Type: Bug
>  Components: Legacy/Local Write-Read Paths
>Reporter: Cameron Zemek
>Priority: Low
>
> In RepairMergeListener:close() it does the following:
>  
> {code:java}
> try
> {
> FBUtilities.waitOnFutures(repairResults, 
> DatabaseDescriptor.getWriteRpcTimeout());
> }
> catch (TimeoutException ex)
> {
> // We got all responses, but timed out while repairing
> int blockFor = consistency.blockFor(keyspace);
> if (Tracing.isTracing())
> Tracing.trace("Timed out while read-repairing after receiving all {} 
> data and digest responses", blockFor);
> else
> logger.debug("Timeout while read-repairing after receiving all {} 
> data and digest responses", blockFor);
> throw new ReadTimeoutException(consistency, blockFor-1, blockFor, true);
> }
> {code}
> This propagates up and gets sent to the client and we have customers get 
> confused cause they see timeouts for CL ALL requiring ALL replicas even 
> though they have read_repair_chance = 0 and using a LOCAL_* CL.
> At minimum I suggest instead of using the consistency level of DataResolver 
> (which is always ALL with read repairs) for the timeout it instead use 
> repairResults.size(). That is blockFor = repairResults.size() . But saying it 
> received _blockFor - 1_ is bogus still. Fixing that would require more 
> changes. I was thinking maybe like so:
>  
> {code:java}
> public static void waitOnFutures(List results, long ms, 
> MutableInt counter) throws TimeoutException
> {
> for (AsyncOneResponse result : results)
> {
> result.get(ms, TimeUnit.MILLISECONDS);
> counter.increment();
> }
> }
> {code}
>  
>  
>  
> Likewise in SinglePartitionReadLifecycle:maybeAwaitFullDataRead() it says 
> _blockFor - 1_ for how many were received, which is also bogus.
>  
> Steps used to reproduce was modify RepairMergeListener:close() to always 
> throw timeout exception.  With schema:
> {noformat}
> CREATE KEYSPACE weather WITH replication = {'class': 
> 'NetworkTopologyStrategy', 'dc1': '3', 'dc2': '3'}  AND durable_writes = true;
> CREATE TABLE weather.city (
> cityid int PRIMARY KEY,
> name text
> ) WITH bloom_filter_fp_chance = 0.01
> AND dclocal_read_repair_chance = 0.0
> AND read_repair_chance = 0.0
> AND speculative_retry = 'NONE';
> {noformat}
> Then using the following steps:
>  # ccm node1 cqlsh
>  # INSERT INTO weather.city(cityid, name) VALUES (1, 'Canberra');
>  # exit;
>  # ccm node1 flush
>  # ccm node1 stop
>  # rm -rf 
> ~/.ccm/test_repair/node1/data0/weather/city-ff2fade0b18d11e8b1cd097acbab1e3d/mc-1-big-*
>  # remove the sstable with the insert
>  # ccm node1 start
>  # ccm node1 cqlsh
>  # CONSISTENCY LOCAL_QUORUM;
>  # select * from weather.city where cityid = 1;
> You get result of:
> {noformat}
> ReadTimeout: Error from server: code=1200 [Coordinator node timed out waiting 
> for replica nodes' responses] message="Operation timed out - received only 5 
> responses." info={'received_responses': 5, 'required_responses': 6, 
> 'consistency': 'ALL'}{noformat}
> But was expecting:
> {noformat}
> ReadTimeout: Error from server: code=1200 [Coordinator node timed out waiting 
> for replica nodes' responses] message="Operation timed out - received only 1 
> responses." info={'received_responses': 1, 'required_responses': 2, 
> 'consistency': 'LOCAL_QUORUM'}{noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Assigned] (CASSANDRA-14715) Read repairs can result in bogus timeout errors to the client

[Stefan Miklosovic (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic reassigned CASSANDRA-14715:
-

Assignee: (was: Stefan Miklosovic)

> Read repairs can result in bogus timeout errors to the client
> -
>
> Key: CASSANDRA-14715
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14715
> Project: Cassandra
>  Issue Type: Bug
>  Components: Legacy/Local Write-Read Paths
>Reporter: Cameron Zemek
>Priority: Low
>
> In RepairMergeListener:close() it does the following:
>  
> {code:java}
> try
> {
> FBUtilities.waitOnFutures(repairResults, 
> DatabaseDescriptor.getWriteRpcTimeout());
> }
> catch (TimeoutException ex)
> {
> // We got all responses, but timed out while repairing
> int blockFor = consistency.blockFor(keyspace);
> if (Tracing.isTracing())
> Tracing.trace("Timed out while read-repairing after receiving all {} 
> data and digest responses", blockFor);
> else
> logger.debug("Timeout while read-repairing after receiving all {} 
> data and digest responses", blockFor);
> throw new ReadTimeoutException(consistency, blockFor-1, blockFor, true);
> }
> {code}
> This propagates up and gets sent to the client and we have customers get 
> confused cause they see timeouts for CL ALL requiring ALL replicas even 
> though they have read_repair_chance = 0 and using a LOCAL_* CL.
> At minimum I suggest instead of using the consistency level of DataResolver 
> (which is always ALL with read repairs) for the timeout it instead use 
> repairResults.size(). That is blockFor = repairResults.size() . But saying it 
> received _blockFor - 1_ is bogus still. Fixing that would require more 
> changes. I was thinking maybe like so:
>  
> {code:java}
> public static void waitOnFutures(List results, long ms, 
> MutableInt counter) throws TimeoutException
> {
> for (AsyncOneResponse result : results)
> {
> result.get(ms, TimeUnit.MILLISECONDS);
> counter.increment();
> }
> }
> {code}
>  
>  
>  
> Likewise in SinglePartitionReadLifecycle:maybeAwaitFullDataRead() it says 
> _blockFor - 1_ for how many were received, which is also bogus.
>  
> Steps used to reproduce was modify RepairMergeListener:close() to always 
> throw timeout exception.  With schema:
> {noformat}
> CREATE KEYSPACE weather WITH replication = {'class': 
> 'NetworkTopologyStrategy', 'dc1': '3', 'dc2': '3'}  AND durable_writes = true;
> CREATE TABLE weather.city (
> cityid int PRIMARY KEY,
> name text
> ) WITH bloom_filter_fp_chance = 0.01
> AND dclocal_read_repair_chance = 0.0
> AND read_repair_chance = 0.0
> AND speculative_retry = 'NONE';
> {noformat}
> Then using the following steps:
>  # ccm node1 cqlsh
>  # INSERT INTO weather.city(cityid, name) VALUES (1, 'Canberra');
>  # exit;
>  # ccm node1 flush
>  # ccm node1 stop
>  # rm -rf 
> ~/.ccm/test_repair/node1/data0/weather/city-ff2fade0b18d11e8b1cd097acbab1e3d/mc-1-big-*
>  # remove the sstable with the insert
>  # ccm node1 start
>  # ccm node1 cqlsh
>  # CONSISTENCY LOCAL_QUORUM;
>  # select * from weather.city where cityid = 1;
> You get result of:
> {noformat}
> ReadTimeout: Error from server: code=1200 [Coordinator node timed out waiting 
> for replica nodes' responses] message="Operation timed out - received only 5 
> responses." info={'received_responses': 5, 'required_responses': 6, 
> 'consistency': 'ALL'}{noformat}
> But was expecting:
> {noformat}
> ReadTimeout: Error from server: code=1200 [Coordinator node timed out waiting 
> for replica nodes' responses] message="Operation timed out - received only 1 
> responses." info={'received_responses': 1, 'required_responses': 2, 
> 'consistency': 'LOCAL_QUORUM'}{noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14715) Read repairs can result in bogus timeout errors to the client

[Stefan Miklosovic (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-14715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584077#comment-17584077
 ] 

Stefan Miklosovic commented on CASSANDRA-14715:
---

I do not plan to work on this. I am not sure how to move forward.

> Read repairs can result in bogus timeout errors to the client
> -
>
> Key: CASSANDRA-14715
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14715
> Project: Cassandra
>  Issue Type: Bug
>  Components: Legacy/Local Write-Read Paths
>Reporter: Cameron Zemek
>Assignee: Stefan Miklosovic
>Priority: Low
>
> In RepairMergeListener:close() it does the following:
>  
> {code:java}
> try
> {
> FBUtilities.waitOnFutures(repairResults, 
> DatabaseDescriptor.getWriteRpcTimeout());
> }
> catch (TimeoutException ex)
> {
> // We got all responses, but timed out while repairing
> int blockFor = consistency.blockFor(keyspace);
> if (Tracing.isTracing())
> Tracing.trace("Timed out while read-repairing after receiving all {} 
> data and digest responses", blockFor);
> else
> logger.debug("Timeout while read-repairing after receiving all {} 
> data and digest responses", blockFor);
> throw new ReadTimeoutException(consistency, blockFor-1, blockFor, true);
> }
> {code}
> This propagates up and gets sent to the client and we have customers get 
> confused cause they see timeouts for CL ALL requiring ALL replicas even 
> though they have read_repair_chance = 0 and using a LOCAL_* CL.
> At minimum I suggest instead of using the consistency level of DataResolver 
> (which is always ALL with read repairs) for the timeout it instead use 
> repairResults.size(). That is blockFor = repairResults.size() . But saying it 
> received _blockFor - 1_ is bogus still. Fixing that would require more 
> changes. I was thinking maybe like so:
>  
> {code:java}
> public static void waitOnFutures(List results, long ms, 
> MutableInt counter) throws TimeoutException
> {
> for (AsyncOneResponse result : results)
> {
> result.get(ms, TimeUnit.MILLISECONDS);
> counter.increment();
> }
> }
> {code}
>  
>  
>  
> Likewise in SinglePartitionReadLifecycle:maybeAwaitFullDataRead() it says 
> _blockFor - 1_ for how many were received, which is also bogus.
>  
> Steps used to reproduce was modify RepairMergeListener:close() to always 
> throw timeout exception.  With schema:
> {noformat}
> CREATE KEYSPACE weather WITH replication = {'class': 
> 'NetworkTopologyStrategy', 'dc1': '3', 'dc2': '3'}  AND durable_writes = true;
> CREATE TABLE weather.city (
> cityid int PRIMARY KEY,
> name text
> ) WITH bloom_filter_fp_chance = 0.01
> AND dclocal_read_repair_chance = 0.0
> AND read_repair_chance = 0.0
> AND speculative_retry = 'NONE';
> {noformat}
> Then using the following steps:
>  # ccm node1 cqlsh
>  # INSERT INTO weather.city(cityid, name) VALUES (1, 'Canberra');
>  # exit;
>  # ccm node1 flush
>  # ccm node1 stop
>  # rm -rf 
> ~/.ccm/test_repair/node1/data0/weather/city-ff2fade0b18d11e8b1cd097acbab1e3d/mc-1-big-*
>  # remove the sstable with the insert
>  # ccm node1 start
>  # ccm node1 cqlsh
>  # CONSISTENCY LOCAL_QUORUM;
>  # select * from weather.city where cityid = 1;
> You get result of:
> {noformat}
> ReadTimeout: Error from server: code=1200 [Coordinator node timed out waiting 
> for replica nodes' responses] message="Operation timed out - received only 5 
> responses." info={'received_responses': 5, 'required_responses': 6, 
> 'consistency': 'ALL'}{noformat}
> But was expecting:
> {noformat}
> ReadTimeout: Error from server: code=1200 [Coordinator node timed out waiting 
> for replica nodes' responses] message="Operation timed out - received only 1 
> responses." info={'received_responses': 1, 'required_responses': 2, 
> 'consistency': 'LOCAL_QUORUM'}{noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17852) WEBSITE - Community page - encourage users to search answered questions on Stack Overflow, Stack Exchange

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17852:
--
Attachment: c17852-01-community-discussions-v1.png

> WEBSITE - Community page - encourage users to search answered questions on 
> Stack Overflow, Stack Exchange
> -
>
> Key: CASSANDRA-17852
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17852
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: 4.0.x
>
> Attachments: c17852-01-community-discussions-v1.png
>
>
> We need to encourage users to first search the {{[cassandra]}} tag on [Stack 
> Overflow|http://stackoverflow.com/questions/tagged/cassandra] and [Stack 
> Exchange|https://dba.stackexchange.com/questions/tagged/cassandra] before 
> asking a question so contributors are not repeatedly asking the same 
> questions over and over.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org