date:20230208

[jira] [Updated] (CASSANDRA-18249) Docker image for releases

2023-02-08 Thread Berenguer Blasi (Jira)



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

Berenguer Blasi updated CASSANDRA-18249:

Description: 
The release process is currently driven bu this 
[doc|https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/release_process.adoc]
 mainly.

Some of the requirements are a Debian based distro and a number of packages. As 
recently discovered this could be a problem, Ubuntu 20.04 LTS doesn't have 
createrepo available i.e.

To avoid such problems, add repeatability, have a controlled env where releases 
are cut, enable more people to cut them, etc [~mck] suggested creating a docker 
image to that purpose probably based off 
[this|https://github.com/apache/cassandra-builds/blob/trunk/docker/bullseye-image.docker]

  was:
The release process is currently driven bu this 
[doc|https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/release_process.adoc]
 mainly.

Some of the requirements are a Debian based distro and a number of packages. As 
recently discovered this could be a problem, Ubuntu 20.04 LTS doesn't have 
createrepo available i.e.

To avoid such problems, add repeatability, have a controlled env where releases 
are cut etc [~mck] suggested creating a docker image to that purpose probably 
based off 
[this|https://github.com/apache/cassandra-builds/blob/trunk/docker/bullseye-image.docker]


> Docker image for releases
> -
>
> Key: CASSANDRA-18249
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18249
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Berenguer Blasi
>Priority: Normal
>
> The release process is currently driven bu this 
> [doc|https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/release_process.adoc]
>  mainly.
> Some of the requirements are a Debian based distro and a number of packages. 
> As recently discovered this could be a problem, Ubuntu 20.04 LTS doesn't have 
> createrepo available i.e.
> To avoid such problems, add repeatability, have a controlled env where 
> releases are cut, enable more people to cut them, etc [~mck] suggested 
> creating a docker image to that purpose probably based off 
> [this|https://github.com/apache/cassandra-builds/blob/trunk/docker/bullseye-image.docker]



--
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-18249) Docker image for releases

2023-02-08 Thread Berenguer Blasi (Jira)

Berenguer Blasi created CASSANDRA-18249:
---

 Summary: Docker image for releases
 Key: CASSANDRA-18249
 URL: https://issues.apache.org/jira/browse/CASSANDRA-18249
 Project: Cassandra
  Issue Type: Task
  Components: Build
Reporter: Berenguer Blasi


The release process is currently driven bu this 
[doc|https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/release_process.adoc]
 mainly.

Some of the requirements are a Debian based distro and a number of packages. As 
recently discovered this could be a problem, Ubuntu 20.04 LTS doesn't have 
createrepo available i.e.

To avoid such problems, add repeatability, have a controlled env where releases 
are cut etc [~mck] suggested creating a docker image to that purpose probably 
based off 
[this|https://github.com/apache/cassandra-builds/blob/trunk/docker/bullseye-image.docker]



--
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-18248) Avoid streams usage in potential hot paths

2023-02-08 Thread Berenguer Blasi (Jira)



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

Berenguer Blasi updated CASSANDRA-18248:

Labels: low-hanging-fruit  (was: )

> Avoid streams usage in potential hot paths
> --
>
> Key: CASSANDRA-18248
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18248
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Berenguer Blasi
>Priority: Normal
>  Labels: low-hanging-fruit
>
> During the review of CASSANDRA-18068 it was discussed whether preparing 
> queries might be considered a hot path or not. Seen in isolation it isn't. 
> But given multi-tenancy setups i.e. and coming from the experience of seeing 
> how prepare is used by some customers as per some bug reports this might not 
> be 100% true
> Let's discuss here if removing streams would make any sense. Most rewrites I 
> expect wouldn't impact readability. [~adelapena] took a first stab and 
> compiled a first list of candidates:
>  * 
> [o.a.c.cql3/CQL3Type.java#L840|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/CQL3Type.java#L840]
>  * 
> [o.a.c.cql3/CQL3Type.java#L876|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/CQL3Type.java#L876]
>  * 
> [o.a.c.cql3/Lists.java#L133|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/Lists.java#L133]
>  * 
> [o.a.c.cql3/Sets.java#L123|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/Sets.java#L123]
>  * 
> [o.a.c.cql3/MultiColumnRelation.java#L225|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/MultiColumnRelation.java#L225]
>  * 
> [o.a.c.cql3/QueryProcessor.java#L481|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/QueryProcessor.java#L481]
>  * 
> [o.a.c.cql3/TokenRelation.java#L138|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/TokenRelation.java#L138]
>  * 
> [o.a.c.cql3/conditions/ColumnConditions.java#L75|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/conditions/ColumnConditions.java#L75]
>  * 
> [o.a.c.cql3/functions/AbstractFunction.java#L69|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/functions/AbstractFunction.java#L69]
>  * 
> [o.a.c.cql3/functions/FunctionResolver.java#L203|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/functions/FunctionResolver.java#L203]
>  * 
> [o.a.c.cql3/functions/UDAggregate.java#L97|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/functions/UDAggregate.java#L97]
>  * 
> [o.a.c.cql3/restrictions/StatementRestrictions.java#L380|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/restrictions/StatementRestrictions.java#L380]
>  * 
> [o.a.c.cql3/selection/AbstractFunctionSelector.java#L72|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/selection/AbstractFunctionSelector.java#L72]
>  * 
> [o.a.c.cql3/selection/MapSelector.java#L113|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/selection/MapSelector.java#L113]
>  * 
> [o.a.c.cql3/selection/Selectable.java#L708|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/selection/Selectable.java#L708]
>  * 
> [o.a.c.cql3/selection/Selectable.java#L793|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/selection/Selectable.java#L793]
>  * 
> [o.a.c.cql3/selection/Selectable.java#L886|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/selection/Selectable.java#L886]
>  * 
> [o.a.c.cql3/selection/Selectable.java#L954|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/selection/Selectable.java#L954]
>  * 
> [o.a.c.cql3/selection/Selectable.java#L1024|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/selection/Selectable.java#L1024]
>  * 
> [o.a.c.cql3/statements/SelectStatement.java#L1278|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/statements/SelectStatement.java#L1278]



--
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-18248) Avoid streams usage in potential hot paths

2023-02-08 Thread Berenguer Blasi (Jira)

Berenguer Blasi created CASSANDRA-18248:
---

 Summary: Avoid streams usage in potential hot paths
 Key: CASSANDRA-18248
 URL: https://issues.apache.org/jira/browse/CASSANDRA-18248
 Project: Cassandra
  Issue Type: Improvement
Reporter: Berenguer Blasi


During the review of CASSANDRA-18068 it was discussed whether preparing queries 
might be considered a hot path or not. Seen in isolation it isn't. But given 
multi-tenancy setups i.e. and coming from the experience of seeing how prepare 
is used by some customers as per some bug reports this might not be 100% true

Let's discuss here if removing streams would make any sense. Most rewrites I 
expect wouldn't impact readability. [~adelapena] took a first stab and compiled 
a first list of candidates:
 * 
[o.a.c.cql3/CQL3Type.java#L840|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/CQL3Type.java#L840]
 * 
[o.a.c.cql3/CQL3Type.java#L876|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/CQL3Type.java#L876]
 * 
[o.a.c.cql3/Lists.java#L133|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/Lists.java#L133]
 * 
[o.a.c.cql3/Sets.java#L123|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/Sets.java#L123]
 * 
[o.a.c.cql3/MultiColumnRelation.java#L225|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/MultiColumnRelation.java#L225]
 * 
[o.a.c.cql3/QueryProcessor.java#L481|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/QueryProcessor.java#L481]
 * 
[o.a.c.cql3/TokenRelation.java#L138|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/TokenRelation.java#L138]
 * 
[o.a.c.cql3/conditions/ColumnConditions.java#L75|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/conditions/ColumnConditions.java#L75]
 * 
[o.a.c.cql3/functions/AbstractFunction.java#L69|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/functions/AbstractFunction.java#L69]
 * 
[o.a.c.cql3/functions/FunctionResolver.java#L203|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/functions/FunctionResolver.java#L203]
 * 
[o.a.c.cql3/functions/UDAggregate.java#L97|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/functions/UDAggregate.java#L97]
 * 
[o.a.c.cql3/restrictions/StatementRestrictions.java#L380|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/restrictions/StatementRestrictions.java#L380]
 * 
[o.a.c.cql3/selection/AbstractFunctionSelector.java#L72|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/selection/AbstractFunctionSelector.java#L72]
 * 
[o.a.c.cql3/selection/MapSelector.java#L113|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/selection/MapSelector.java#L113]
 * 
[o.a.c.cql3/selection/Selectable.java#L708|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/selection/Selectable.java#L708]
 * 
[o.a.c.cql3/selection/Selectable.java#L793|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/selection/Selectable.java#L793]
 * 
[o.a.c.cql3/selection/Selectable.java#L886|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/selection/Selectable.java#L886]
 * 
[o.a.c.cql3/selection/Selectable.java#L954|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/selection/Selectable.java#L954]
 * 
[o.a.c.cql3/selection/Selectable.java#L1024|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/selection/Selectable.java#L1024]
 * 
[o.a.c.cql3/statements/SelectStatement.java#L1278|https://github.com/apache/cassandra/blob/cassandra-4.1.0/src/java/org/apache/cassandra/cql3/statements/SelectStatement.java#L1278]



--
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-18244) Improve documentation about releases for Cassandra website.

2023-02-08 Thread Erick Ramirez (Jira)



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

Erick Ramirez commented on CASSANDRA-18244:
---

I've made a single minor change from {{Empirically testing}} to {{Empirical 
testing}} and accepted [~polandll]'s suggestions. Thanks for keeping the docs 
up-to-date [~smiklosovic] ! 

> Improve documentation about releases for Cassandra website.
> ---
>
> Key: CASSANDRA-18244
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18244
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
>  Labels: pull-request-available
> Fix For: NA
>
>
> The documentation is lacking some details so a respective developers can have 
> more smooth release experience when setting up their system for the first 
> time.



--
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-18068) Allow to attach native masking functions to table columns

2023-02-08 Thread Berenguer Blasi (Jira)



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

Berenguer Blasi updated CASSANDRA-18068:

Reviewers: Benjamin Lerer, Berenguer Blasi  (was: Benjamin Lerer)

> Allow to attach native masking functions to table columns
> -
>
> Key: CASSANDRA-18068
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18068
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Feature/Dynamic Data Masking
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>  Time Spent: 3h
>  Remaining Estimate: 0h
>
> Allow to attach the native masking functions added by CASSANDRA-17941 to 
> table columns, as defined by 
> [CEP-20|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-20%3A+Dynamic+Data+Masking].
>  
> {{CREATE TABLE}} statements would look like:
> {code}
> > CREATE TABLE patients (
>   id timeuuid PRIMARY KEY,
>   name text MASKED WITH partial(2, 1),
>   birth date MASKED WITH default()
>   );
> > INSERT INTO patients(id, name, birth) VALUES (now(), 'alice', '1982-12-21);
>  
> > SELECT name, birth FROM patients;
>  
>  name| birth
> -+
>  ale | 1900-01-01
> {code}
> {{ALTER TABLE}} statements would look like:
> {code}
> > ALTER TABLE patients ALTER name MASKED WITH partial(2, 1);
> > ALTER TABLE patients ALTER name WITHOUT MASK;
> {code}
> It won't be possible to use masked columns in the WHERE and IF clauses of 
> SELECT and UPDATE statements.



--
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-18212) Reduce memory allocations of calls to ByteBufer.duplicate() made in org.apache.cassandra.transport.CBUtil#writeValue

2023-02-08 Thread Benedict Elliott Smith (Jira)



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

Benedict Elliott Smith commented on CASSANDRA-18212:


This isn't what we discussed? Having a thread local direct buffer we duplicate 
the contents into is costlier than just casting to 
{{BufferPoolAllocator.Wrapped}} as we discussed on slack, so I am unclear why 
we are going this route instead?

I am fine with grabbing the array if it's there, but I don't see why would we 
do the rest when it is unnecessary.

> Reduce memory allocations of calls to ByteBufer.duplicate() made in 
> org.apache.cassandra.transport.CBUtil#writeValue
> 
>
> Key: CASSANDRA-18212
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18212
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Local Write-Read Paths
>Reporter: Natnael Adere
>Assignee: Natnael Adere
>Priority: Normal
> Attachments: DiskBased.png, MemoryBased.png, allocations-after.html, 
> allocations-before.html
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Currently, 
> org.apache.cassandra.transport.CBUtil#writeValue(java.nio.ByteBuffer, 
> io.netty.buffer.ByteBuf) calls ByteBufer.duplicate() and is found to be 20% 
> of memory allocations in production. No changes have been made to reduce this 
> but there is discussion related to the issue in CASSANDRA-13741. Attached 
> below are the performance result for disk based queries and mostly memory 
> based queries. 



--
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-18212) Reduce memory allocations of calls to ByteBufer.duplicate() made in org.apache.cassandra.transport.CBUtil#writeValue

2023-02-08 Thread David Capwell (Jira)



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

David Capwell commented on CASSANDRA-18212:
---

bq. I thought we had discussed either using the byte[] or casting to 
BufferPoolAllocator.Wrapped on slack?

That is what the patch does.  If the BB is a heap based one, then we use the 
array (due to a CMS bug, Nate will update the code explaining that issue), if 
the BB is direct, then it uses the same "duplicate" logic used in other logic 
and calls MemoryUtil.duplicateDirectByteBuffer...  If a new type of BB is added 
(not heap and not direct) then we fall back to duplicate.

> Reduce memory allocations of calls to ByteBufer.duplicate() made in 
> org.apache.cassandra.transport.CBUtil#writeValue
> 
>
> Key: CASSANDRA-18212
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18212
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Local Write-Read Paths
>Reporter: Natnael Adere
>Assignee: Natnael Adere
>Priority: Normal
> Attachments: DiskBased.png, MemoryBased.png, allocations-after.html, 
> allocations-before.html
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Currently, 
> org.apache.cassandra.transport.CBUtil#writeValue(java.nio.ByteBuffer, 
> io.netty.buffer.ByteBuf) calls ByteBufer.duplicate() and is found to be 20% 
> of memory allocations in production. No changes have been made to reduce this 
> but there is discussion related to the issue in CASSANDRA-13741. Attached 
> below are the performance result for disk based queries and mostly memory 
> based queries. 



--
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-18212) Reduce memory allocations of calls to ByteBufer.duplicate() made in org.apache.cassandra.transport.CBUtil#writeValue

2023-02-08 Thread David Capwell (Jira)



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

David Capwell edited comment on CASSANDRA-18212 at 2/9/23 12:06 AM:


bq. I thought we had discussed either using the byte[] or casting to 
BufferPoolAllocator.Wrapped on slack?

That is what the patch does.  If the BB is a heap based one, then we use the 
array (due to a CMS bug, Nate will update the code explaining that issue), if 
the BB is direct, then it uses the same "duplicate" logic used in other logic 
and calls MemoryUtil.duplicateDirectByteBuffer...  If a new type of BB is added 
(not heap and not direct) then we fall back to duplicate.

{code}
if (src.hasArray())
{
  byte[] array = src.array();
  dest.writeBytes(array, src.arrayOffset() + src.position(), length);
}
else if (src.isDirect())
{
  ByteBuffer local = getLocalDirectBuffer();
  MemoryUtil.duplicateDirectByteBuffer(src, local);
  dest.writeBytes(local);
}
else
{
  dest.writeBytes(src.duplicate());
}
{code}


was (Author: dcapwell):
bq. I thought we had discussed either using the byte[] or casting to 
BufferPoolAllocator.Wrapped on slack?

That is what the patch does.  If the BB is a heap based one, then we use the 
array (due to a CMS bug, Nate will update the code explaining that issue), if 
the BB is direct, then it uses the same "duplicate" logic used in other logic 
and calls MemoryUtil.duplicateDirectByteBuffer...  If a new type of BB is added 
(not heap and not direct) then we fall back to duplicate.

> Reduce memory allocations of calls to ByteBufer.duplicate() made in 
> org.apache.cassandra.transport.CBUtil#writeValue
> 
>
> Key: CASSANDRA-18212
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18212
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Local Write-Read Paths
>Reporter: Natnael Adere
>Assignee: Natnael Adere
>Priority: Normal
> Attachments: DiskBased.png, MemoryBased.png, allocations-after.html, 
> allocations-before.html
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Currently, 
> org.apache.cassandra.transport.CBUtil#writeValue(java.nio.ByteBuffer, 
> io.netty.buffer.ByteBuf) calls ByteBufer.duplicate() and is found to be 20% 
> of memory allocations in production. No changes have been made to reduce this 
> but there is discussion related to the issue in CASSANDRA-13741. Attached 
> below are the performance result for disk based queries and mostly memory 
> based queries. 



--
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-18212) Reduce memory allocations of calls to ByteBufer.duplicate() made in org.apache.cassandra.transport.CBUtil#writeValue

2023-02-08 Thread Benedict Elliott Smith (Jira)



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

Benedict Elliott Smith commented on CASSANDRA-18212:


I thought we had discussed either using the {{byte[]}} or casting to 
{{BufferPoolAllocator.Wrapped}} on slack?

https://the-asf.slack.com/archives/CK23JSY2K/p1675285925529819?thread_ts=1675279019.024139=CK23JSY2K
https://the-asf.slack.com/archives/CK23JSY2K/p1675287376825619?thread_ts=1675279019.024139=CK23JSY2K

> Reduce memory allocations of calls to ByteBufer.duplicate() made in 
> org.apache.cassandra.transport.CBUtil#writeValue
> 
>
> Key: CASSANDRA-18212
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18212
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Local Write-Read Paths
>Reporter: Natnael Adere
>Assignee: Natnael Adere
>Priority: Normal
> Attachments: DiskBased.png, MemoryBased.png, allocations-after.html, 
> allocations-before.html
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Currently, 
> org.apache.cassandra.transport.CBUtil#writeValue(java.nio.ByteBuffer, 
> io.netty.buffer.ByteBuf) calls ByteBufer.duplicate() and is found to be 20% 
> of memory allocations in production. No changes have been made to reduce this 
> but there is discussion related to the issue in CASSANDRA-13741. Attached 
> below are the performance result for disk based queries and mostly memory 
> based queries. 



--
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-18212) Reduce memory allocations of calls to ByteBufer.duplicate() made in org.apache.cassandra.transport.CBUtil#writeValue

2023-02-08 Thread Natnael Adere (Jira)



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

Natnael Adere updated CASSANDRA-18212:
--
Test and Documentation Plan: Performance testing and circle ci testing done
 Status: Patch Available  (was: In Progress)

Patch: [https://github.com/apache/cassandra/pull/2122]

CircleCi: 
[https://app.circleci.com/pipelines/github/NateAdere/cassandra?branch=CASSANDRA-18212-trunk]

 

> Reduce memory allocations of calls to ByteBufer.duplicate() made in 
> org.apache.cassandra.transport.CBUtil#writeValue
> 
>
> Key: CASSANDRA-18212
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18212
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Local Write-Read Paths
>Reporter: Natnael Adere
>Assignee: Natnael Adere
>Priority: Normal
> Attachments: DiskBased.png, MemoryBased.png, allocations-after.html, 
> allocations-before.html
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Currently, 
> org.apache.cassandra.transport.CBUtil#writeValue(java.nio.ByteBuffer, 
> io.netty.buffer.ByteBuf) calls ByteBufer.duplicate() and is found to be 20% 
> of memory allocations in production. No changes have been made to reduce this 
> but there is discussion related to the issue in CASSANDRA-13741. Attached 
> below are the performance result for disk based queries and mostly memory 
> based queries. 



--
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-18212) Reduce memory allocations of calls to ByteBufer.duplicate() made in org.apache.cassandra.transport.CBUtil#writeValue

2023-02-08 Thread Natnael Adere (Jira)



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

Natnael Adere updated CASSANDRA-18212:
--
Attachment: allocations-after.html
allocations-before.html

> Reduce memory allocations of calls to ByteBufer.duplicate() made in 
> org.apache.cassandra.transport.CBUtil#writeValue
> 
>
> Key: CASSANDRA-18212
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18212
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Local Write-Read Paths
>Reporter: Natnael Adere
>Assignee: Natnael Adere
>Priority: Normal
> Attachments: DiskBased.png, MemoryBased.png, allocations-after.html, 
> allocations-before.html
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Currently, 
> org.apache.cassandra.transport.CBUtil#writeValue(java.nio.ByteBuffer, 
> io.netty.buffer.ByteBuf) calls ByteBufer.duplicate() and is found to be 20% 
> of memory allocations in production. No changes have been made to reduce this 
> but there is discussion related to the issue in CASSANDRA-13741. Attached 
> below are the performance result for disk based queries and mostly memory 
> based queries. 



--
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-15254) Allow UPDATE on settings virtual table to change running configurations

2023-02-08 Thread David Capwell (Jira)



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

David Capwell commented on CASSANDRA-15254:
---

bq. Once such a property is loaded, its old name is no longer available at 
runtime for usage, right? 

Incorrect, they are exposed in the settings table.  The JMX names (for 
backwards compatibility reasons) tend to be the old names and not the new 
names...  so on a rename you tend to be lacking JMX names that match the new 
name, and the settings table exposes both.  DD may use w/e it wants as the 
names don't matter to authors.

bq.  it is correct not to have setter and getter methods for them in the 
DatabaseDescriptor class.

To lower the size of a diff, its not uncommon for DD to be left alone on 
renames (outside of changing the field referenced), so DD may have the old 
name, the new name, or any other name.  So it is not "correct" to say that it's 
not "correct" for DD to reference older names.

bq. The properties that are NOT changed at runtime.
bq. An example of such a property might be Config.cluster_name or 
Config.storage_port. These types of properties are not changed during a node 
lifecycle and MUST NOT be changed at runtime.

Yep, those are some examples.

bq. The properties that can be changed at runtime and are responsible for 
managing a node's internal processes or state during the node lifecycle.

what does this mean?

bq. No matter how we intend to update a particular property using the setter 
method or reflection, it's currently impossible to determine from the source 
code we have whether that property is updatable or not

It's complex to get a 100% correct answer (need something to look at all code 
paths), but just checking if a field is volatile solves for 80% of the cases.  
You might mutate something that isn't mutable (we can always just remove 
volatile in those known cases), and some people make a field mutable without 
volatile... but that isn't 100% safe...

So yeah, the cheapest way is to check for "volatile"; its not 100% correct but 
generally works

bq. Enforce the contract between the filed name and the setter method name, 
with the field type and the method input type. It differs now for almost 
everything - setRepairRpcTimeout and repair_request_timeout, but we must have 
setRepairRequestTimeout and repair_request_timeout to ensure the field is 
changeable;

does this mean the build fails if we mess up and can't have a match?  Any idea 
how many methods don't match the "new" name?

To see the impact, wrote a quick test to show the current state.

{code}
@Test
public void test()
{
Field[] fields = Config.class.getDeclaredFields();
Method[] methods = DatabaseDescriptor.class.getDeclaredMethods();
long empty = 0, immutable = 0, mutable = 0;
for (Field field : fields)
{
if (Modifier.isStatic(field.getModifiers())) continue;
String name = FBUtilities.snakeToCamel(field.getName());
name = name.substring(0, 1).toUpperCase() + name.substring(1);
String getter = "get" + name;
String setter = "set" + name;

long numGetters = Stream.of(methods).filter(m -> 
m.getName().equals(getter)).count();
long numSetters = Stream.of(methods).filter(m -> 
m.getName().equals(setter)).count();
if (numGetters == 0)
{
System.out.println("No getter found for " + name);
empty++;
}
else if (numSetters == 0)
{
System.out.println("Immutable " + name);
immutable++;
}
else
{
System.out.println("Mutable " + name);
mutable++;
}
}
double total = empty + mutable + immutable;
System.out.println("Empty configs: " + empty + "(" + (empty / total * 
100) + "%)");
System.out.println("Immutable configs: " + empty + "(" + (immutable / 
total * 100) + "%)");
System.out.println("Mutable configs: " + empty + "(" + (mutable / total 
* 100) + "%)");
}
{code}

Here we see the following sample cases that stand out

{code}
INFO  [main] 2023-02-08 11:21:10,176 SubstituteLogger.java:169 - Immutable 
ClusterName
INFO  [main] 2023-02-08 11:21:10,177 SubstituteLogger.java:169 - Mutable 
Authenticator // not actually mutable, used only in 
org.apache.cassandra.auth.AuthConfig#applyAuth
INFO  [main] 2023-02-08 11:21:10,178 SubstituteLogger.java:169 - No getter 
found for AutoBootstrap
INFO  [main] 2023-02-08 11:21:10,178 SubstituteLogger.java:169 - No getter 
found for HintedHandoffEnabled
INFO  [main] 2023-02-08 11:21:10,178 SubstituteLogger.java:169 - No getter 
found for HintedHandoffDisabledDatacenters
INFO  [main] 2023-02-08 11:21:10,179 SubstituteLogger.java:169 - No getter 
found for

[jira] [Commented] (CASSANDRA-18244) Improve documentation about releases for Cassandra website.

2023-02-08 Thread Lorina Poland (Jira)



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

Lorina Poland commented on CASSANDRA-18244:
---

I made a number of suggestions to make the changes more readable. Please 
consider committing the changes before merging.

> Improve documentation about releases for Cassandra website.
> ---
>
> Key: CASSANDRA-18244
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18244
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
>  Labels: pull-request-available
> Fix For: NA
>
>
> The documentation is lacking some details so a respective developers can have 
> more smooth release experience when setting up their system for the first 
> time.



--
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-18239) Remove eclipse warnings task

2023-02-08 Thread Ekaterina Dimitrova (Jira)



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

Ekaterina Dimitrova edited comment on CASSANDRA-18239 at 2/8/23 7:29 PM:
-

One thing I noticed is [this 
comment.|https://github.com/apache/cassandra/blob/trunk/build.xml#L1910] 
Indeed, we run that task only with Java 8 in CI but what I find confusing is 
that I can run it with Java 11 and it says BUILD SUCCESSFUL... I didn't have 
the time to investigate it but if someone will be looking into this task here, 
I figured it will be the right place to share this observation


was (Author: e.dimitrova):
One thing I noticed is [this 
comment.|https://github.com/apache/cassandra/blob/trunk/build.xml#L1910] 
Indeed, we run that task only with Java 8 in CI but what I find confusing is 
that I can run it with Java 11 and it says BUILD SUCCESSFUL...

> Remove eclipse warnings task
> 
>
> Key: CASSANDRA-18239
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18239
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Jacek Lewandowski
>Priority: Normal
>
> Eclipse warnings is used for static code analysis. However, it does not fit 
> well into Cassandra code and practically we end up explicitly adding 
> suppressions in many places just to satisfy that tool rather than fix the 
> real issues.
> This is an incomplete list of reasons to remove it:
> - not closed resources are detected incorrectly
> - does not recognize custom utility methods used to close the resources, 
> which use use heavily in the code, like {{Throwables.close}}, 
> {{FileUtils.close}}, {{closeQuietly}}...
> - because of the above, we cannot make important things like {{Ref}} to 
> implement {{Closeable}} as it would make the tool to explode with tons of 
> warnings
> - it complains about correct generics - something like "method X is not 
> applicable for ..." when the code compiles successfully is not acceptable
> - it is old and not maintained
> There are better tools like IntelliJ inspections for example, which can also 
> be run in headless mode



--
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-18239) Remove eclipse warnings task

2023-02-08 Thread Ekaterina Dimitrova (Jira)



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

Ekaterina Dimitrova commented on CASSANDRA-18239:
-

One thing I noticed is [this 
comment.|https://github.com/apache/cassandra/blob/trunk/build.xml#L1910] 
Indeed, we run that task only with Java 8 in CI but what I find confusing is 
that I can run it with Java 11 and it says BUILD SUCCESSFUL...

> Remove eclipse warnings task
> 
>
> Key: CASSANDRA-18239
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18239
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Jacek Lewandowski
>Priority: Normal
>
> Eclipse warnings is used for static code analysis. However, it does not fit 
> well into Cassandra code and practically we end up explicitly adding 
> suppressions in many places just to satisfy that tool rather than fix the 
> real issues.
> This is an incomplete list of reasons to remove it:
> - not closed resources are detected incorrectly
> - does not recognize custom utility methods used to close the resources, 
> which use use heavily in the code, like {{Throwables.close}}, 
> {{FileUtils.close}}, {{closeQuietly}}...
> - because of the above, we cannot make important things like {{Ref}} to 
> implement {{Closeable}} as it would make the tool to explode with tons of 
> warnings
> - it complains about correct generics - something like "method X is not 
> applicable for ..." when the code compiles successfully is not acceptable
> - it is old and not maintained
> There are better tools like IntelliJ inspections for example, which can also 
> be run in headless mode



--
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-18238) Implicitly enable ALLOW FILTERING on virtual tables

2023-02-08 Thread Stefan Miklosovic (Jira)



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

Stefan Miklosovic commented on CASSANDRA-18238:
---

builds look good, upgrade tests timeouted because of my Circle CI plan so I 
tested in in Jenkins here 
https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/2265/

> Implicitly enable ALLOW FILTERING on virtual tables
> ---
>
> Key: CASSANDRA-18238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18238
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Feature/Virtual Tables
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Ticket to track work / discussion of this thread (1)
> (1) https://lists.apache.org/thread/104fld746d6qtggq5132n3hqtjqqpkjp



--
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-18238) Implicitly enable ALLOW FILTERING on virtual tables

2023-02-08 Thread Stefan Miklosovic (Jira)



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

Stefan Miklosovic updated CASSANDRA-18238:
--
Status: Ready to Commit  (was: Review In Progress)

> Implicitly enable ALLOW FILTERING on virtual tables
> ---
>
> Key: CASSANDRA-18238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18238
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Feature/Virtual Tables
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Ticket to track work / discussion of this thread (1)
> (1) https://lists.apache.org/thread/104fld746d6qtggq5132n3hqtjqqpkjp



--
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-18068) Allow to attach native masking functions to table columns

2023-02-08 Thread Jira



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

Andres de la Peña commented on CASSANDRA-18068:
---

I'm splitting some of the slowest tests into smaller tests. While those 
survived the multiplexer in a normal run, they might be among those demanding 
tests that timeout in an unusually slow run.

> Allow to attach native masking functions to table columns
> -
>
> Key: CASSANDRA-18068
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18068
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Feature/Dynamic Data Masking
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>  Time Spent: 3h
>  Remaining Estimate: 0h
>
> Allow to attach the native masking functions added by CASSANDRA-17941 to 
> table columns, as defined by 
> [CEP-20|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-20%3A+Dynamic+Data+Masking].
>  
> {{CREATE TABLE}} statements would look like:
> {code}
> > CREATE TABLE patients (
>   id timeuuid PRIMARY KEY,
>   name text MASKED WITH partial(2, 1),
>   birth date MASKED WITH default()
>   );
> > INSERT INTO patients(id, name, birth) VALUES (now(), 'alice', '1982-12-21);
>  
> > SELECT name, birth FROM patients;
>  
>  name| birth
> -+
>  ale | 1900-01-01
> {code}
> {{ALTER TABLE}} statements would look like:
> {code}
> > ALTER TABLE patients ALTER name MASKED WITH partial(2, 1);
> > ALTER TABLE patients ALTER name WITHOUT MASK;
> {code}
> It won't be possible to use masked columns in the WHERE and IF clauses of 
> SELECT and UPDATE statements.



--
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-18179) Update build.xml for experimental JDK17 use

2023-02-08 Thread Ekaterina Dimitrova (Jira)



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

Ekaterina Dimitrova edited comment on CASSANDRA-18179 at 2/8/23 6:58 PM:
-

In the meantime [~stefan.miklosovic] sent me a heads up about a recent change 
that was done and we will need to take into consideration here. Please be aware 
that test/anttasks/JdkProperties.java should be moved to 
test/anttasks/org/apache/cassandra/anttasks directory 
The custom ant tasks were moved into package dir in CASSANDRA-17964


was (Author: e.dimitrova):
In the meantime [~stefan.miklosovic] sent me a heads up about a recent change 
that was done and we will need to take into consideration here.please beware 
that test/anttasks/JdkProperties.java should be moved to 
test/anttasks/org/apache/cassandra/anttasks directory 
The custom ant tasks were moved into package dir in CASSANDRA-17964

> Update build.xml for experimental JDK17 use
> ---
>
> Key: CASSANDRA-18179
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18179
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.x
>
>
> To support JDK17 we need to make changes to build.xml and our scripts. There 
> is a preliminary patch which makes a switch from JDK8+JDK11 to JDK11+JDK17 
> but it will need a change considering CASSANDRA-18133
> CC [~mck] 



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

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

[jira] [Commented] (CASSANDRA-18179) Update build.xml for experimental JDK17 use

2023-02-08 Thread Ekaterina Dimitrova (Jira)



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

Ekaterina Dimitrova commented on CASSANDRA-18179:
-

In the meantime [~stefan.miklosovic] sent me a heads up about a recent change 
that was done and we will need to take into consideration here.please beware 
that test/anttasks/JdkProperties.java should be moved to 
test/anttasks/org/apache/cassandra/anttasks directory 
The custom ant tasks were moved into package dir in CASSANDRA-17964

> Update build.xml for experimental JDK17 use
> ---
>
> Key: CASSANDRA-18179
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18179
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.x
>
>
> To support JDK17 we need to make changes to build.xml and our scripts. There 
> is a preliminary patch which makes a switch from JDK8+JDK11 to JDK11+JDK17 
> but it will need a change considering CASSANDRA-18133
> CC [~mck] 



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

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

[jira] [Comment Edited] (CASSANDRA-18247) Add CircleCI config file for J11+J17

2023-02-08 Thread Ekaterina Dimitrova (Jira)



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

Ekaterina Dimitrova edited comment on CASSANDRA-18247 at 2/8/23 6:44 PM:
-

[~danlangford] , thank you for your interest into this ticket but I already 
assigned it myself and I have preliminary patch to be posted later today or 
tomorrow.


was (Author: e.dimitrova):
[~danlangford] , thank you for your interest into this ticket but I already 
assigned it and I have preliminary patch to be posted later today or tomorrow.

> Add CircleCI config file for J11+J17
> 
>
> Key: CASSANDRA-18247
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18247
> Project: Cassandra
>  Issue Type: Task
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> Based on the direction of [this 
> discussion|https://lists.apache.org/thread/hchv59c1sntgb74clynj0zfd8jvwdmgy], 
> I would like to propose a CircleCI config file which can be used to test 
> current trunk with JDK 17 (after I blindly remove the scripted UDFs in 
> another ticket, to be opened soon)



--
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-18247) Add CircleCI config file for J11+J17

2023-02-08 Thread Ekaterina Dimitrova (Jira)



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

Ekaterina Dimitrova commented on CASSANDRA-18247:
-

[~danlangford] , thank you for your interest into this ticket but I already 
assigned it and I have preliminary patch to be posted later today or tomorrow.

> Add CircleCI config file for J11+J17
> 
>
> Key: CASSANDRA-18247
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18247
> Project: Cassandra
>  Issue Type: Task
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> Based on the direction of [this 
> discussion|https://lists.apache.org/thread/hchv59c1sntgb74clynj0zfd8jvwdmgy], 
> I would like to propose a CircleCI config file which can be used to test 
> current trunk with JDK 17 (after I blindly remove the scripted UDFs in 
> another ticket, to be opened soon)



--
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-18247) Add CircleCI config file for J11+J17

2023-02-08 Thread Ekaterina Dimitrova (Jira)



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

Ekaterina Dimitrova reassigned CASSANDRA-18247:
---

Assignee: Ekaterina Dimitrova  (was: Dan Langford)

> Add CircleCI config file for J11+J17
> 
>
> Key: CASSANDRA-18247
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18247
> Project: Cassandra
>  Issue Type: Task
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> Based on the direction of [this 
> discussion|https://lists.apache.org/thread/hchv59c1sntgb74clynj0zfd8jvwdmgy], 
> I would like to propose a CircleCI config file which can be used to test 
> current trunk with JDK 17 (after I blindly remove the scripted UDFs in 
> another ticket, to be opened soon)



--
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-18247) Add CircleCI config file for J11+J17

2023-02-08 Thread Dan Langford (Jira)



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

Dan Langford reassigned CASSANDRA-18247:


Assignee: Dan Langford  (was: Ekaterina Dimitrova)

> Add CircleCI config file for J11+J17
> 
>
> Key: CASSANDRA-18247
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18247
> Project: Cassandra
>  Issue Type: Task
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Dan Langford
>Priority: Normal
> Fix For: 4.x
>
>
> Based on the direction of [this 
> discussion|https://lists.apache.org/thread/hchv59c1sntgb74clynj0zfd8jvwdmgy], 
> I would like to propose a CircleCI config file which can be used to test 
> current trunk with JDK 17 (after I blindly remove the scripted UDFs in 
> another ticket, to be opened soon)



--
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-18051) Optimize test_network_topology_strategy and test_network_topology_strategy_each_quorum for large containers in CircleCI

2023-02-08 Thread Ekaterina Dimitrova (Jira)



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

Ekaterina Dimitrova commented on CASSANDRA-18051:
-

It seems those are failing on 3.0 and 3.11 with 1 container XLarge, but not on 
other branches. For more info - CASSANDRA-18001.

I suggest we edit this ticket to fix those tests as I am not sure that the 
failures we see are related to the resources. Needs investigation

> Optimize test_network_topology_strategy and 
> test_network_topology_strategy_each_quorum for large containers in CircleCI
> ---
>
> Key: CASSANDRA-18051
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18051
> Project: Cassandra
>  Issue Type: Task
>  Components: Test/dtest/python
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
>
> As pointed in CASSANDRA-18001, there are two Python Large DTests that fail 
> because of not enough resources with large containers. [~adelapena] looked 
> into them and suggested that the tests themselves can be optimized for 
> running on Large containers instead of using XLarge containers for only two 
> tests from the whole suite. 
> {quote}As for the two tests starting nine nodes each, 
> {{test_network_topology_strategy}} and 
> {{{}test_network_topology_strategy_each_quorum{}}}, I think they were added 
> by CASSANDRA-10584 to test multi-DC consistency levels. I wonder if they 
> actually need to start 3 data centers with 3 nodes each. Would two data 
> centers with 3 nodes be enough to test multi-DC consistency levels with 
> multiple data centers? 6 nodes should be doable on Circle with the current 
> resources.
> {quote}



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

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

[jira] [Updated] (CASSANDRA-18247) Add CircleCI config file for J11+J17

2023-02-08 Thread Ekaterina Dimitrova (Jira)



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

Ekaterina Dimitrova updated CASSANDRA-18247:

Fix Version/s: 4.x

> Add CircleCI config file for J11+J17
> 
>
> Key: CASSANDRA-18247
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18247
> Project: Cassandra
>  Issue Type: Task
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> Based on the direction of [this 
> discussion|https://lists.apache.org/thread/hchv59c1sntgb74clynj0zfd8jvwdmgy], 
> I would like to propose a CircleCI config file which can be used to test 
> current trunk with JDK 17 (after I blindly remove the scripted UDFs in 
> another ticket, to be opened soon)



--
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-18247) Add CircleCI config file for J11+J17

2023-02-08 Thread Ekaterina Dimitrova (Jira)



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

Ekaterina Dimitrova updated CASSANDRA-18247:

Description: Based on the direction of [this 
discussion|https://lists.apache.org/thread/hchv59c1sntgb74clynj0zfd8jvwdmgy], I 
would like to propose a CircleCI config file which can be used to test current 
trunk with JDK 17 (after I blindly remove the scripted UDFs in another ticket, 
to be opened soon)  (was: Based on the direction of this discussion, I would 
like to propose a CircleCI config file which can be used to test current trunk 
with JDK 17 (after I blindly remove the scripted UDFs in another ticket, to be 
opened soon))

> Add CircleCI config file for J11+J17
> 
>
> Key: CASSANDRA-18247
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18247
> Project: Cassandra
>  Issue Type: Task
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
>
> Based on the direction of [this 
> discussion|https://lists.apache.org/thread/hchv59c1sntgb74clynj0zfd8jvwdmgy], 
> I would like to propose a CircleCI config file which can be used to test 
> current trunk with JDK 17 (after I blindly remove the scripted UDFs in 
> another ticket, to be opened soon)



--
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-18247) Add CircleCI config file for J11+J17

2023-02-08 Thread Ekaterina Dimitrova (Jira)



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

Ekaterina Dimitrova updated CASSANDRA-18247:

Change Category: Quality Assurance
 Complexity: Low Hanging Fruit
 Status: Open  (was: Triage Needed)

> Add CircleCI config file for J11+J17
> 
>
> Key: CASSANDRA-18247
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18247
> Project: Cassandra
>  Issue Type: Task
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
>
> Based on the direction of this discussion, I would like to propose a CircleCI 
> config file which can be used to test current trunk with JDK 17 (after I 
> blindly remove the scripted UDFs in another ticket, to be opened soon)



--
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-18247) Add CircleCI config file for J11+J17

2023-02-08 Thread Ekaterina Dimitrova (Jira)

Ekaterina Dimitrova created CASSANDRA-18247:
---

 Summary: Add CircleCI config file for J11+J17
 Key: CASSANDRA-18247
 URL: https://issues.apache.org/jira/browse/CASSANDRA-18247
 Project: Cassandra
  Issue Type: Task
  Components: CI
Reporter: Ekaterina Dimitrova
Assignee: Ekaterina Dimitrova


Based on the direction of this discussion, I would like to propose a CircleCI 
config file which can be used to test current trunk with JDK 17 (after I 
blindly remove the scripted UDFs in another ticket, to be opened soon)



--
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-18001) Add missing tests suites to CircleCI

2023-02-08 Thread Ekaterina Dimitrova (Jira)



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

Ekaterina Dimitrova edited comment on CASSANDRA-18001 at 2/8/23 6:28 PM:
-

{quote}Yes, I was hitting the same problem with CircleCI yesterday. It seems 
that something is broken on their side.
{quote}
Thanks for confirming!
{quote}Otherwise the changes look good to me, let's see if we can get a good 
run from Circle.
{quote}
I think I got that:
||PR||LOWRES||MIDRES||HIGHRES||
|[3.0|https://github.com/apache/cassandra/pull/2136]| |[CircleCI 
#2265|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-3.0-final-mid]|[CircleCI
 
#2264|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-3.0-final-high]|
|[3.11|https://github.com/apache/cassandra/pull/2137]| |[CircleCI 
#2268|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-3.11-final-mid]|[CircleCI
 
#2267|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-3.11-final-high]|
|[4.0|https://github.com/apache/cassandra/pull/2138]| |[CircleCI 
#2274|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-4.0-final-mid]|[CircleCI
 
#2275|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-4.0-final-high]|
|[4.1|https://github.com/apache/cassandra/pull/2139]| |[CircleCI 
#2256|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-4.1-final-mid]|[CircleCI
 
#2258|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-4.1-final-high]|
|[trunk|https://github.com/apache/cassandra/pull/2140]| |[CircleCI 
#2263|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-trunk-final2-mid]|[CircleCI
 
#2262|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-trunk-final2-high]|

 

3.0 and 3.11 with HIGH Resources XLarge containers and parallelism 1 fail the 
two tests we discussed. From what I see I am not sure it is a resource issue 
though. 

At this point I think we have to change CASSANDRA-18051 to optimize and fix 
probably? 

Also, FYI, I kept the PRs not squashed but already squashed the commits for the 
branches where I test with the different resources


was (Author: e.dimitrova):
{quote}Yes, I was hitting the same problem with CircleCI yesterday. It seems 
that something is broken on their side.
{quote}
Thanks for confirming!
{quote}Otherwise the changes look good to me, let's see if we can get a good 
run from Circle.
{quote}
I think I got that:
||PR||LOWRES||MIDRES||HIGHRES||
|[3.0|https://github.com/apache/cassandra/pull/2136]| |[CircleCI 
#2265|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-3.0-final-mid]|[CircleCI
 
#2264|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-3.0-final-high]|
|[3.11|https://github.com/apache/cassandra/pull/2137]| |[CircleCI 
#2268|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-3.11-final-mid]|[CircleCI
 
#2267|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-3.11-final-high]|
|[4.0|https://github.com/apache/cassandra/pull/2138]| |[CircleCI 
#2274|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-4.0-final-mid]|[CircleCI
 
#2275|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-4.0-final-high]|
|[4.1|https://github.com/apache/cassandra/pull/2139]| |[CircleCI 
#2256|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-4.1-final-mid]|[CircleCI
 
#2258|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-4.1-final-high]|
|[trunk|https://github.com/apache/cassandra/pull/2140]| |[CircleCI 
#2263|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-trunk-final2-mid]|[CircleCI
 
#2262|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-trunk-final2-high]|

 

3.0 and 3.11 with HIGH Resources XLarge containers and parallelism 1 fail the 
two tests we discussed. From what I see I am not sure it is a resource issue 
though. 

At this point I think we have to change CASSANDRA-18051 to optimize and fix 
probably? 

> Add missing tests suites to CircleCI
> 
>
> Key: CASSANDRA-18001
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18001
> Project: Cassandra
>  Issue Type: Task
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Urgent
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1-rc1,

[jira] [Commented] (CASSANDRA-18001) Add missing tests suites to CircleCI

2023-02-08 Thread Ekaterina Dimitrova (Jira)



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

Ekaterina Dimitrova commented on CASSANDRA-18001:
-

{quote}Yes, I was hitting the same problem with CircleCI yesterday. It seems 
that something is broken on their side.
{quote}
Thanks for confirming!
{quote}Otherwise the changes look good to me, let's see if we can get a good 
run from Circle.
{quote}
I think I got that:
||PR||LOWRES||MIDRES||HIGHRES||
|[3.0|https://github.com/apache/cassandra/pull/2136]| |[CircleCI 
#2265|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-3.0-final-mid]|[CircleCI
 
#2264|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-3.0-final-high]|
|[3.11|https://github.com/apache/cassandra/pull/2137]| |[CircleCI 
#2268|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-3.11-final-mid]|[CircleCI
 
#2267|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-3.11-final-high]|
|[4.0|https://github.com/apache/cassandra/pull/2138]| |[CircleCI 
#2274|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-4.0-final-mid]|[CircleCI
 
#2275|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-4.0-final-high]|
|[4.1|https://github.com/apache/cassandra/pull/2139]| |[CircleCI 
#2256|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-4.1-final-mid]|[CircleCI
 
#2258|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-4.1-final-high]|
|[trunk|https://github.com/apache/cassandra/pull/2140]| |[CircleCI 
#2263|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-trunk-final2-mid]|[CircleCI
 
#2262|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18001-trunk-final2-high]|

 

3.0 and 3.11 with HIGH Resources XLarge containers and parallelism 1 fail the 
two tests we discussed. From what I see I am not sure it is a resource issue 
though. 

At this point I think we have to change CASSANDRA-18051 to optimize and fix 
probably? 

> Add missing tests suites to CircleCI
> 
>
> Key: CASSANDRA-18001
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18001
> Project: Cassandra
>  Issue Type: Task
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Urgent
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1-rc1, 4.1, 4.1.x, 4.2, 4.x
>
>
> Burn tests to all branches, large Python DTests (with/without vnodes), 
> cqlshlib not tested in all branches and with all jdks; Java distributed tests 
> not running with J8/J11 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] [Updated] (CASSANDRA-18198) "AttributeError: module 'py' has no attribute 'io'" reported in multiple tests

2023-02-08 Thread Brandon Williams (Jira)



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

Brandon Williams updated CASSANDRA-18198:
-
Resolution: Fixed
Status: Resolved  (was: Open)

I don't see anything related to this ticket, please open a new one.

> "AttributeError: module 'py' has no attribute 'io'" reported in multiple tests
> --
>
> Key: CASSANDRA-18198
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18198
> Project: Cassandra
>  Issue Type: Bug
>  Components: Test/dtest/python
>Reporter: Claude Warren
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.29, 3.11.15, 4.0.8, 4.1.1, 4.2
>
>
> {{title = 'Timeout'}}
> {{stream = <_io.TextIOWrapper name='' mode='w' encoding='utf-8'>}}
> {{{}sep = '+'{}}}{{{}def write_title(title, stream=None, sep="~"):{}}}
> {{{}"""Write a section title.{}}}{{{}If *stream* is None sys.stderr will be 
> used, *sep* is used to{}}}
> {{draw the line.}}
> {{"""}}
> {{if stream is None:}}
> {{stream = sys.stderr}}
> {{> width = py.io.get_terminal_width()}}
> {{E AttributeError: module 'py' has no attribute 'io}}
>  
> is reported in multiple tests as noted below.
> possibly a class loader issue associated with CASSANDRA-18150
> 4.1
> [https://ci-cassandra.apache.org/job/Cassandra-4.1/256/testReport/dtest-offheap.repair_tests.incremental_repair_test/TestIncRepair/test_multiple_full_repairs_lcs]
> 3.11
> [https://ci-cassandra.apache.org/job/Cassandra-3.11/424/testReport/dtest.bootstrap_test/TestBootstrap/test_simultaneous_bootstrap/]
> 3.0
> [https://ci-cassandra.apache.org/job/Cassandra-3.0/328/testReport/dtest-upgrade.upgrade_tests.upgrade_supercolumns_test/TestSCUpgrade/test_upgrade_super_columns_through_all_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] [Updated] (CASSANDRA-17349) Fix flaky test - dtest-novnode.repair_tests.repair_test.TestRepair.test_simple_sequential_repair

2023-02-08 Thread Brandon Williams (Jira)



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

Brandon Williams updated CASSANDRA-17349:
-
Resolution: Fixed
Status: Resolved  (was: Open)

A new ticket should be opened for that failure.

> Fix flaky test - 
> dtest-novnode.repair_tests.repair_test.TestRepair.test_simple_sequential_repair
> 
>
> Key: CASSANDRA-17349
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17349
> Project: Cassandra
>  Issue Type: Bug
>  Components: Consistency/Repair
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.27
>
>
> Failed 2 times in the last 9 runs. Flakiness: 37%, Stability: 77%
> Error Message
> cassandra.DriverException: ID mismatch while trying to reprepare (expected 
> b'ba2c66a4f13080265ea718e037637d4a', got 
> b'52faf62235132756a26828817a81168d'). This prepared statement won't work 
> anymore. This usually happens when you run a 'USE...' query after the 
> statement was prepared.
> Stacktrace
> self = 
> def test_simple_sequential_repair(self):
> """
> Calls simple repair test with a sequential repair
> """
> >   self._simple_repair(sequential=True)
> repair_tests/repair_test.py:363: 



--
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-17349) Fix flaky test - dtest-novnode.repair_tests.repair_test.TestRepair.test_simple_sequential_repair

2023-02-08 Thread German Eichberger (Jira)



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

German Eichberger updated CASSANDRA-17349:
--
Resolution: (was: Fixed)
Status: Open  (was: Resolved)

h1. 2/8/23 - seen once
h1.  
h1. Regression

dtest-offheap.repair_tests.repair_test.TestRepair.test_simple_sequential_repair 
(from Cassandra dtests)
Failing for the past 1 build (Since 
[#540|https://ci-cassandra.apache.org/job/Cassandra-4.0/540/] )
[Took 3 min 45 
sec.|https://ci-cassandra.apache.org/job/Cassandra-4.0/540/testReport/dtest-offheap.repair_tests.repair_test/TestRepair/test_simple_sequential_repair/history]
 
!https://ci-cassandra.apache.org/static/f3f9be2d/images/32x32/health-80plus.png!
 Failed 1 times in the last 30 runs. Flakiness: 3%, Stability: 96%
h3. Error Message

failed on teardown with "Unexpected error found in node logs (see stdout for 
full details). Errors: [[node2] 'ERROR [MemtableReclaimMemory:2] 2023-02-08 
06:05:59,669 CassandraDaemon.java:581 - Exception in thread 
Thread[MemtableReclaimMemory:2,5,main]\njava.lang.AssertionError: null\n\tat 
org.apache.cassandra.utils.memory.MemtablePool$SubPool.released(MemtablePool.java:193)\n\tat
 
org.apache.cassandra.utils.memory.MemtableAllocator$SubAllocator.releaseAll(MemtableAllocator.java:151)\n\tat
 
org.apache.cassandra.utils.memory.MemtableAllocator$SubAllocator.setDiscarded(MemtableAllocator.java:142)\n\tat
 
org.apache.cassandra.utils.memory.MemtableAllocator.setDiscarded(MemtableAllocator.java:93)\n\tat
 
org.apache.cassandra.utils.memory.NativeAllocator.setDiscarded(NativeAllocator.java:203)\n\tat
 org.apache.cassandra.db.Memtable.setDiscarded(Memtable.java:212)\n\tat 
org.apache.cassandra.db.ColumnFamilyStore$Flush$1.runMayThrow(ColumnFamilyStore.java:1216)\n\tat
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)\n\tat 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat
 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\n\tat
 
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
 java.lang.Thread.run(Thread.java:750)']"
h3. Stacktrace

Unexpected error found in node logs (see stdout for full details). Errors: 
[[node2] 'ERROR [MemtableReclaimMemory:2] 2023-02-08 06:05:59,669 
CassandraDaemon.java:581 - Exception in thread 
Thread[MemtableReclaimMemory:2,5,main]\njava.lang.AssertionError: null\n\tat 
org.apache.cassandra.utils.memory.MemtablePool$SubPool.released(MemtablePool.java:193)\n\tat
 
org.apache.cassandra.utils.memory.MemtableAllocator$SubAllocator.releaseAll(MemtableAllocator.java:151)\n\tat
 
org.apache.cassandra.utils.memory.MemtableAllocator$SubAllocator.setDiscarded(MemtableAllocator.java:142)\n\tat
 
org.apache.cassandra.utils.memory.MemtableAllocator.setDiscarded(MemtableAllocator.java:93)\n\tat
 
org.apache.cassandra.utils.memory.NativeAllocator.setDiscarded(NativeAllocator.java:203)\n\tat
 org.apache.cassandra.db.Memtable.setDiscarded(Memtable.java:212)\n\tat 
org.apache.cassandra.db.ColumnFamilyStore$Flush$1.runMayThrow(ColumnFamilyStore.java:1216)\n\tat
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)\n\tat 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat
 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\n\tat
 
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
 java.lang.Thread.run(Thread.java:750)']

> Fix flaky test - 
> dtest-novnode.repair_tests.repair_test.TestRepair.test_simple_sequential_repair
> 
>
> Key: CASSANDRA-17349
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17349
> Project: Cassandra
>  Issue Type: Bug
>  Components: Consistency/Repair
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.27
>
>
> Failed 2 times in the last 9 runs. Flakiness: 37%, Stability: 77%
> Error Message
> cassandra.DriverException: ID mismatch while trying to reprepare (expected 
> b'ba2c66a4f13080265ea718e037637d4a', got 
> b'52faf62235132756a26828817a81168d'). This prepared statement won't work 
> anymore. This usually happens when you run a 'USE...' query after the 
> statement was prepared.
> Stacktrace
> self = 
> def test_simple_sequential_repair(self):
> """
> Calls simple repair test with a sequential repair
> """
> >   self._simple_repair(sequential=True)
> repair_tests/repair_test.py:363: 



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

-
To unsubscribe, e-mail:

[jira] [Created] (CASSANDRA-18246) Test Failures: org.apache.cassandra.cql3.validation.operations.TTLTest.testCapNoWarnExpirationOverflowPolicy

2023-02-08 Thread German Eichberger (Jira)

German Eichberger created CASSANDRA-18246:
-

 Summary: Test Failures: 
org.apache.cassandra.cql3.validation.operations.TTLTest.testCapNoWarnExpirationOverflowPolicy
 Key: CASSANDRA-18246
 URL: https://issues.apache.org/jira/browse/CASSANDRA-18246
 Project: Cassandra
  Issue Type: Bug
  Components: Test/unit
Reporter: German Eichberger


Filed 2/8/23 - seen once

 
h1. Regression

org.apache.cassandra.cql3.validation.operations.TTLTest.testCapNoWarnExpirationOverflowPolicy-compression
 (from org.apache.cassandra.cql3.validation.operations.TTLTest-compression)
Failing for the past 1 build (Since 
[#428|https://ci-cassandra.apache.org/job/Cassandra-3.11/428/] )
[Took 1.2 
sec.|https://ci-cassandra.apache.org/job/Cassandra-3.11/428/testReport/org.apache.cassandra.cql3.validation.operations/TTLTest/testCapNoWarnExpirationOverflowPolicy_compression/history]
 
!https://ci-cassandra.apache.org/static/f3f9be2d/images/32x32/health-80plus.png!
 Failed 1 times in the last 30 runs. Flakiness: 3%, Stability: 96%
h3. Stacktrace

junit.framework.AssertionFailedError at 
org.apache.cassandra.cql3.validation.operations.TTLTest.checkTTLIsCapped(TTLTest.java:320)
 at 
org.apache.cassandra.cql3.validation.operations.TTLTest.verifyData(TTLTest.java:302)
 at 
org.apache.cassandra.cql3.validation.operations.TTLTest.testCapExpirationDateOverflowPolicy(TTLTest.java:247)
 at 
org.apache.cassandra.cql3.validation.operations.TTLTest.testCapExpirationDateOverflowPolicy(TTLTest.java:200)
 at 
org.apache.cassandra.cql3.validation.operations.TTLTest.testCapNoWarnExpirationOverflowPolicy(TTLTest.java:148)
h3. Standard Output

INFO [main] 2023-01-30 22:33:09,069 YamlConfigurationLoader.java:93 - 
Configuration location: 
file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml DEBUG 
[main] 2023-01-30 22:33:09,077 YamlConfigurationLoader.java:112 - Loading 
settings from 
file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml INFO 
[main] 2023-01-30 22:33:09,558 Config.java:555 - Node 
configuration:[allocate_tokens_for_keyspace=null; 
allow_extra_insecure_udfs=false; allow_insecure_udfs=false; authenticator=null; 
authorizer=null; auto_bootstrap=true; auto_snapshot=true; 
back_pressure_enabled=false; back_pressure_strategy=null; 
batch_size_fail_threshold_in_kb=50; batch_size_warn_threshold_in_kb=5; 
batchlog_replay_throttle_in_kb=1024; broadcast_address=null; 
broadcast_rpc_address=null; buffer_pool_use_heap_if_exhausted=true; 
cache_load_timeout_seconds=30; cas_contention_timeout_in_ms=1000; 
cdc_enabled=false; cdc_free_space_check_interval_ms=250; 
cdc_raw_directory=build/test/cassandra/cdc_raw; cdc_total_space_in_mb=0; 
check_for_duplicate_rows_during_compaction=true; 
check_for_duplicate_rows_during_reads=true; 
client_encryption_options=; cluster_name=Test Cluster; 
column_index_cache_size_in_kb=2; column_index_size_in_kb=4; 
commit_failure_policy=stop; commitlog_compression=LZ4Compressor; 
commitlog_directory=build/test/cassandra/commitlog; 
commitlog_max_compression_buffers_in_pool=3; commitlog_periodic_queue_size=-1; 
commitlog_segment_size_in_mb=5; commitlog_sync=batch; 
commitlog_sync_batch_window_in_ms=1.0; commitlog_sync_period_in_ms=0; 
commitlog_total_space_in_mb=null; 
compaction_large_partition_warning_threshold_mb=100; 
compaction_throughput_mb_per_sec=0; concurrent_compactors=4; 
concurrent_counter_writes=32; concurrent_materialized_view_writes=32; 
concurrent_reads=32; concurrent_replicates=null; concurrent_writes=32; 
counter_cache_keys_to_save=2147483647; counter_cache_save_period=7200; 
counter_cache_size_in_mb=null; counter_write_request_timeout_in_ms=5000; 
credentials_cache_max_entries=1000; credentials_update_interval_in_ms=-1; 
credentials_validity_in_ms=2000; cross_node_timeout=false; 
data_file_directories=[Ljava.lang.String;@ef9296d; disk_access_mode=mmap; 
disk_failure_policy=ignore; disk_optimization_estimate_percentile=0.95; 
disk_optimization_page_cross_chance=0.1; disk_optimization_strategy=ssd; 
dynamic_snitch=true; dynamic_snitch_badness_threshold=0.1; 
dynamic_snitch_reset_interval_in_ms=60; 
dynamic_snitch_update_interval_in_ms=100; enable_drop_compact_storage=true; 
enable_materialized_views=true; enable_sasi_indexes=true; 
enable_scripted_user_defined_functions=true; 
enable_user_defined_functions=true; enable_user_defined_functions_threads=true; 
encryption_options=; 
endpoint_snitch=org.apache.cassandra.locator.SimpleSnitch; 
file_cache_round_up=null; file_cache_size_in_mb=null; 
force_new_prepared_statement_behaviour=false; gc_log_threshold_in_ms=200; 
gc_warn_threshold_in_ms=0; hinted_handoff_disabled_datacenters=[]; 
hinted_handoff_enabled=true; hinted_handoff_throttle_in_kb=1024; 
hints_compression=null; hints_directory=build/test/cassandra/hints; 
hints_flush_period_in_ms=1; incremental_backups=true; index_interval=null;

[jira] [Updated] (CASSANDRA-18246) Test Failures: org.apache.cassandra.cql3.validation.operations.TTLTest.testCapNoWarnExpirationOverflowPolicy

2023-02-08 Thread German Eichberger (Jira)



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

German Eichberger updated CASSANDRA-18246:
--
Bug Category: Parent values: Correctness(12982)Level 1 values: Test 
Failure(12990)

> Test Failures: 
> org.apache.cassandra.cql3.validation.operations.TTLTest.testCapNoWarnExpirationOverflowPolicy
> 
>
> Key: CASSANDRA-18246
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18246
> Project: Cassandra
>  Issue Type: Bug
>  Components: Test/unit
>Reporter: German Eichberger
>Priority: Normal
>
> Filed 2/8/23 - seen once
>  
> h1. Regression
> org.apache.cassandra.cql3.validation.operations.TTLTest.testCapNoWarnExpirationOverflowPolicy-compression
>  (from org.apache.cassandra.cql3.validation.operations.TTLTest-compression)
> Failing for the past 1 build (Since 
> [#428|https://ci-cassandra.apache.org/job/Cassandra-3.11/428/] )
> [Took 1.2 
> sec.|https://ci-cassandra.apache.org/job/Cassandra-3.11/428/testReport/org.apache.cassandra.cql3.validation.operations/TTLTest/testCapNoWarnExpirationOverflowPolicy_compression/history]
>  
> !https://ci-cassandra.apache.org/static/f3f9be2d/images/32x32/health-80plus.png!
>  Failed 1 times in the last 30 runs. Flakiness: 3%, Stability: 96%
> h3. Stacktrace
> junit.framework.AssertionFailedError at 
> org.apache.cassandra.cql3.validation.operations.TTLTest.checkTTLIsCapped(TTLTest.java:320)
>  at 
> org.apache.cassandra.cql3.validation.operations.TTLTest.verifyData(TTLTest.java:302)
>  at 
> org.apache.cassandra.cql3.validation.operations.TTLTest.testCapExpirationDateOverflowPolicy(TTLTest.java:247)
>  at 
> org.apache.cassandra.cql3.validation.operations.TTLTest.testCapExpirationDateOverflowPolicy(TTLTest.java:200)
>  at 
> org.apache.cassandra.cql3.validation.operations.TTLTest.testCapNoWarnExpirationOverflowPolicy(TTLTest.java:148)
> h3. Standard Output
> INFO [main] 2023-01-30 22:33:09,069 YamlConfigurationLoader.java:93 - 
> Configuration location: 
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml DEBUG 
> [main] 2023-01-30 22:33:09,077 YamlConfigurationLoader.java:112 - Loading 
> settings from 
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml INFO 
> [main] 2023-01-30 22:33:09,558 Config.java:555 - Node 
> configuration:[allocate_tokens_for_keyspace=null; 
> allow_extra_insecure_udfs=false; allow_insecure_udfs=false; 
> authenticator=null; authorizer=null; auto_bootstrap=true; auto_snapshot=true; 
> back_pressure_enabled=false; back_pressure_strategy=null; 
> batch_size_fail_threshold_in_kb=50; batch_size_warn_threshold_in_kb=5; 
> batchlog_replay_throttle_in_kb=1024; broadcast_address=null; 
> broadcast_rpc_address=null; buffer_pool_use_heap_if_exhausted=true; 
> cache_load_timeout_seconds=30; cas_contention_timeout_in_ms=1000; 
> cdc_enabled=false; cdc_free_space_check_interval_ms=250; 
> cdc_raw_directory=build/test/cassandra/cdc_raw; cdc_total_space_in_mb=0; 
> check_for_duplicate_rows_during_compaction=true; 
> check_for_duplicate_rows_during_reads=true; 
> client_encryption_options=; cluster_name=Test Cluster; 
> column_index_cache_size_in_kb=2; column_index_size_in_kb=4; 
> commit_failure_policy=stop; commitlog_compression=LZ4Compressor; 
> commitlog_directory=build/test/cassandra/commitlog; 
> commitlog_max_compression_buffers_in_pool=3; 
> commitlog_periodic_queue_size=-1; commitlog_segment_size_in_mb=5; 
> commitlog_sync=batch; commitlog_sync_batch_window_in_ms=1.0; 
> commitlog_sync_period_in_ms=0; commitlog_total_space_in_mb=null; 
> compaction_large_partition_warning_threshold_mb=100; 
> compaction_throughput_mb_per_sec=0; concurrent_compactors=4; 
> concurrent_counter_writes=32; concurrent_materialized_view_writes=32; 
> concurrent_reads=32; concurrent_replicates=null; concurrent_writes=32; 
> counter_cache_keys_to_save=2147483647; counter_cache_save_period=7200; 
> counter_cache_size_in_mb=null; counter_write_request_timeout_in_ms=5000; 
> credentials_cache_max_entries=1000; credentials_update_interval_in_ms=-1; 
> credentials_validity_in_ms=2000; cross_node_timeout=false; 
> data_file_directories=[Ljava.lang.String;@ef9296d; disk_access_mode=mmap; 
> disk_failure_policy=ignore; disk_optimization_estimate_percentile=0.95; 
> disk_optimization_page_cross_chance=0.1; disk_optimization_strategy=ssd; 
> dynamic_snitch=true; dynamic_snitch_badness_threshold=0.1; 
> dynamic_snitch_reset_interval_in_ms=60; 
> dynamic_snitch_update_interval_in_ms=100; enable_drop_compact_storage=true; 
> enable_materialized_views=true; enable_sasi_indexes=true; 
> enable_scripted_user_defined_functions=true; 
> enable_user_defined_functions=true; 
> enable_user_defined_functions_threads=true;

[jira] [Updated] (CASSANDRA-18245) Test Failures: org.apache.cassandra.db.compaction.CompactionsTest.testDontPurgeAccidentally

2023-02-08 Thread German Eichberger (Jira)



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

German Eichberger updated CASSANDRA-18245:
--
Bug Category: Parent values: Correctness(12982)Level 1 values: Test 
Failure(12990)
 Component/s: Test/unit
  (was: Local/Compaction)

> Test Failures:  
> org.apache.cassandra.db.compaction.CompactionsTest.testDontPurgeAccidentally 
> -
>
> Key: CASSANDRA-18245
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18245
> Project: Cassandra
>  Issue Type: Bug
>  Components: Test/unit
>Reporter: German Eichberger
>Priority: Normal
>
> h1. Regression
> org.apache.cassandra.db.compaction.CompactionsTest.testDontPurgeAccidentally
> Failing for the past 1 build (Since 
> [#428|https://ci-cassandra.apache.org/job/Cassandra-3.11/428/] )
> [Took 1 
> sec.|https://ci-cassandra.apache.org/job/Cassandra-3.11/428/testReport/org.apache.cassandra.db.compaction/CompactionsTest/testDontPurgeAccidentally/history]
>  
> !https://ci-cassandra.apache.org/static/f3f9be2d/images/32x32/health-40to59.png!
>  Failed 1 times in the last 3 runs. Flakiness: 50%, Stability: 66%
> h3. Stacktrace
> java.util.NoSuchElementException at 
> org.apache.cassandra.utils.AbstractIterator.next(AbstractIterator.java:64) at 
> org.apache.cassandra.db.compaction.CompactionsTest.testDontPurgeAccidentally(CompactionsTest.java:446)
>  at 
> org.apache.cassandra.db.compaction.CompactionsTest.testDontPurgeAccidentally(CompactionsTest.java:291)
> h3. Filed: 2/8/23 - saw it once
> h3.  
> h3. Standard Output
> INFO [main] 2023-01-30 22:26:13,249 YamlConfigurationLoader.java:93 - 
> Configuration location: 
> file:/home/cassandra/cassandra/test/conf/cassandra.yaml DEBUG [main] 
> 2023-01-30 22:26:13,256 YamlConfigurationLoader.java:112 - Loading settings 
> from file:/home/cassandra/cassandra/test/conf/cassandra.yaml INFO [main] 
> 2023-01-30 22:26:13,626 Config.java:555 - Node 
> configuration:[allocate_tokens_for_keyspace=null; 
> allow_extra_insecure_udfs=false; allow_insecure_udfs=false; 
> authenticator=null; authorizer=null; auto_bootstrap=true; auto_snapshot=true; 
> back_pressure_enabled=false; back_pressure_strategy=null; 
> batch_size_fail_threshold_in_kb=50; batch_size_warn_threshold_in_kb=5; 
> batchlog_replay_throttle_in_kb=1024; broadcast_address=null; 
> broadcast_rpc_address=null; buffer_pool_use_heap_if_exhausted=true; 
> cache_load_timeout_seconds=30; cas_contention_timeout_in_ms=1000; 
> cdc_enabled=false; cdc_free_space_check_interval_ms=250; 
> cdc_raw_directory=build/test/cassandra/cdc_raw; cdc_total_space_in_mb=0; 
> check_for_duplicate_rows_during_compaction=true; 
> check_for_duplicate_rows_during_reads=true; 
> client_encryption_options=; cluster_name=Test Cluster; 
> column_index_cache_size_in_kb=2; column_index_size_in_kb=4; 
> commit_failure_policy=stop; commitlog_compression=null; 
> commitlog_directory=build/test/cassandra/commitlog; 
> commitlog_max_compression_buffers_in_pool=3; 
> commitlog_periodic_queue_size=-1; commitlog_segment_size_in_mb=5; 
> commitlog_sync=batch; commitlog_sync_batch_window_in_ms=1.0; 
> commitlog_sync_period_in_ms=0; commitlog_total_space_in_mb=null; 
> compaction_large_partition_warning_threshold_mb=100; 
> compaction_throughput_mb_per_sec=0; concurrent_compactors=4; 
> concurrent_counter_writes=32; concurrent_materialized_view_writes=32; 
> concurrent_reads=32; concurrent_replicates=null; concurrent_writes=32; 
> counter_cache_keys_to_save=2147483647; counter_cache_save_period=7200; 
> counter_cache_size_in_mb=null; counter_write_request_timeout_in_ms=5000; 
> credentials_cache_max_entries=1000; credentials_update_interval_in_ms=-1; 
> credentials_validity_in_ms=2000; cross_node_timeout=false; 
> data_file_directories=[Ljava.lang.String;@19bb07ed; disk_access_mode=mmap; 
> disk_failure_policy=ignore; disk_optimization_estimate_percentile=0.95; 
> disk_optimization_page_cross_chance=0.1; disk_optimization_strategy=ssd; 
> dynamic_snitch=true; dynamic_snitch_badness_threshold=0.1; 
> dynamic_snitch_reset_interval_in_ms=60; 
> dynamic_snitch_update_interval_in_ms=100; enable_drop_compact_storage=true; 
> enable_materialized_views=true; enable_sasi_indexes=true; 
> enable_scripted_user_defined_functions=true; 
> enable_user_defined_functions=true; 
> enable_user_defined_functions_threads=true; encryption_options=; 
> endpoint_snitch=org.apache.cassandra.locator.SimpleSnitch; 
> file_cache_round_up=null; file_cache_size_in_mb=null; 
> force_new_prepared_statement_behaviour=false; gc_log_threshold_in_ms=200; 
> gc_warn_threshold_in_ms=0; hinted_handoff_disabled_datacenters=[]; 
> hinted_handoff_enabled=true; hinted_handoff_throttle_in_kb=1024; 
> hints_compression=null;

[jira] [Created] (CASSANDRA-18245) Test Failures: org.apache.cassandra.db.compaction.CompactionsTest.testDontPurgeAccidentally

2023-02-08 Thread German Eichberger (Jira)

German Eichberger created CASSANDRA-18245:
-

 Summary: Test Failures:  
org.apache.cassandra.db.compaction.CompactionsTest.testDontPurgeAccidentally 
 Key: CASSANDRA-18245
 URL: https://issues.apache.org/jira/browse/CASSANDRA-18245
 Project: Cassandra
  Issue Type: Bug
  Components: Local/Compaction
Reporter: German Eichberger


h1. Regression

org.apache.cassandra.db.compaction.CompactionsTest.testDontPurgeAccidentally
Failing for the past 1 build (Since 
[#428|https://ci-cassandra.apache.org/job/Cassandra-3.11/428/] )
[Took 1 
sec.|https://ci-cassandra.apache.org/job/Cassandra-3.11/428/testReport/org.apache.cassandra.db.compaction/CompactionsTest/testDontPurgeAccidentally/history]
 
!https://ci-cassandra.apache.org/static/f3f9be2d/images/32x32/health-40to59.png!
 Failed 1 times in the last 3 runs. Flakiness: 50%, Stability: 66%
h3. Stacktrace

java.util.NoSuchElementException at 
org.apache.cassandra.utils.AbstractIterator.next(AbstractIterator.java:64) at 
org.apache.cassandra.db.compaction.CompactionsTest.testDontPurgeAccidentally(CompactionsTest.java:446)
 at 
org.apache.cassandra.db.compaction.CompactionsTest.testDontPurgeAccidentally(CompactionsTest.java:291)
h3. Filed: 2/8/23 - saw it once
h3.  
h3. Standard Output

INFO [main] 2023-01-30 22:26:13,249 YamlConfigurationLoader.java:93 - 
Configuration location: file:/home/cassandra/cassandra/test/conf/cassandra.yaml 
DEBUG [main] 2023-01-30 22:26:13,256 YamlConfigurationLoader.java:112 - Loading 
settings from file:/home/cassandra/cassandra/test/conf/cassandra.yaml INFO 
[main] 2023-01-30 22:26:13,626 Config.java:555 - Node 
configuration:[allocate_tokens_for_keyspace=null; 
allow_extra_insecure_udfs=false; allow_insecure_udfs=false; authenticator=null; 
authorizer=null; auto_bootstrap=true; auto_snapshot=true; 
back_pressure_enabled=false; back_pressure_strategy=null; 
batch_size_fail_threshold_in_kb=50; batch_size_warn_threshold_in_kb=5; 
batchlog_replay_throttle_in_kb=1024; broadcast_address=null; 
broadcast_rpc_address=null; buffer_pool_use_heap_if_exhausted=true; 
cache_load_timeout_seconds=30; cas_contention_timeout_in_ms=1000; 
cdc_enabled=false; cdc_free_space_check_interval_ms=250; 
cdc_raw_directory=build/test/cassandra/cdc_raw; cdc_total_space_in_mb=0; 
check_for_duplicate_rows_during_compaction=true; 
check_for_duplicate_rows_during_reads=true; 
client_encryption_options=; cluster_name=Test Cluster; 
column_index_cache_size_in_kb=2; column_index_size_in_kb=4; 
commit_failure_policy=stop; commitlog_compression=null; 
commitlog_directory=build/test/cassandra/commitlog; 
commitlog_max_compression_buffers_in_pool=3; commitlog_periodic_queue_size=-1; 
commitlog_segment_size_in_mb=5; commitlog_sync=batch; 
commitlog_sync_batch_window_in_ms=1.0; commitlog_sync_period_in_ms=0; 
commitlog_total_space_in_mb=null; 
compaction_large_partition_warning_threshold_mb=100; 
compaction_throughput_mb_per_sec=0; concurrent_compactors=4; 
concurrent_counter_writes=32; concurrent_materialized_view_writes=32; 
concurrent_reads=32; concurrent_replicates=null; concurrent_writes=32; 
counter_cache_keys_to_save=2147483647; counter_cache_save_period=7200; 
counter_cache_size_in_mb=null; counter_write_request_timeout_in_ms=5000; 
credentials_cache_max_entries=1000; credentials_update_interval_in_ms=-1; 
credentials_validity_in_ms=2000; cross_node_timeout=false; 
data_file_directories=[Ljava.lang.String;@19bb07ed; disk_access_mode=mmap; 
disk_failure_policy=ignore; disk_optimization_estimate_percentile=0.95; 
disk_optimization_page_cross_chance=0.1; disk_optimization_strategy=ssd; 
dynamic_snitch=true; dynamic_snitch_badness_threshold=0.1; 
dynamic_snitch_reset_interval_in_ms=60; 
dynamic_snitch_update_interval_in_ms=100; enable_drop_compact_storage=true; 
enable_materialized_views=true; enable_sasi_indexes=true; 
enable_scripted_user_defined_functions=true; 
enable_user_defined_functions=true; enable_user_defined_functions_threads=true; 
encryption_options=; 
endpoint_snitch=org.apache.cassandra.locator.SimpleSnitch; 
file_cache_round_up=null; file_cache_size_in_mb=null; 
force_new_prepared_statement_behaviour=false; gc_log_threshold_in_ms=200; 
gc_warn_threshold_in_ms=0; hinted_handoff_disabled_datacenters=[]; 
hinted_handoff_enabled=true; hinted_handoff_throttle_in_kb=1024; 
hints_compression=null; hints_directory=build/test/cassandra/hints; 
hints_flush_period_in_ms=1; incremental_backups=true; index_interval=null; 
index_summary_capacity_in_mb=null; index_summary_resize_interval_in_minutes=60; 
initial_token=null; inter_dc_stream_throughput_outbound_megabits_per_sec=200; 
inter_dc_tcp_nodelay=true; internode_authenticator=null; 
internode_compression=none; internode_recv_buff_size_in_bytes=0; 
internode_send_buff_size_in_bytes=0; key_cache_keys_to_save=2147483647; 
key_cache_save_period=14400; key_cache_size_in_mb=null;

[jira] [Commented] (CASSANDRA-17979) Fix flaky test:org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades

2023-02-08 Thread Derek Chen-Becker (Jira)



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

Derek Chen-Becker commented on CASSANDRA-17979:
---

I've replaced both assertions with a new method to validate delivery and I've 
renamed everything to make it clear that they also test delivery. CircleCI is 
running unit tests now. I'm going to disagree with the idea that every unit 
test should be an integration test (message delivery is tested in other test 
classes), but in the interest of fixing a flaky test we can hopefully merge 
this soon.

> Fix flaky 
> test:org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades
> ---
>
> Key: CASSANDRA-17979
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17979
> Project: Cassandra
>  Issue Type: Bug
>  Components: Messaging/Internode
>Reporter: Brandon Williams
>Assignee: Derek Chen-Becker
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1339/testReport/org.apache.cassandra.net/HandshakeTest/testOutboundConnectionfFallbackDuringUpgrades_cdc/
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1336/testReport/org.apache.cassandra.net/HandshakeTest/testOutboundConnectionfFallbackDuringUpgrades_compression/
> https://app.circleci.com/pipelines/github/instaclustr/cassandra/1466/workflows/ffb52616-92d7-4089-a0c9-a9ebf28333c0/jobs/6296/tests
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.cassandra.net.HandshakeTest.testOutboundFallbackOnSSLHandshakeFailure(HandshakeTest.java:384)
>   at 
> org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades(HandshakeTest.java:243)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {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-17979) Fix flaky test:org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades

2023-02-08 Thread Ekaterina Dimitrova (Jira)



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

Ekaterina Dimitrova commented on CASSANDRA-17979:
-

My suggestion was to fix that assertion instead of removing it, it is a quick 
trivial fix. Otherwise I do not disagree with the things said here

> Fix flaky 
> test:org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades
> ---
>
> Key: CASSANDRA-17979
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17979
> Project: Cassandra
>  Issue Type: Bug
>  Components: Messaging/Internode
>Reporter: Brandon Williams
>Assignee: Derek Chen-Becker
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1339/testReport/org.apache.cassandra.net/HandshakeTest/testOutboundConnectionfFallbackDuringUpgrades_cdc/
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1336/testReport/org.apache.cassandra.net/HandshakeTest/testOutboundConnectionfFallbackDuringUpgrades_compression/
> https://app.circleci.com/pipelines/github/instaclustr/cassandra/1466/workflows/ffb52616-92d7-4089-a0c9-a9ebf28333c0/jobs/6296/tests
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.cassandra.net.HandshakeTest.testOutboundFallbackOnSSLHandshakeFailure(HandshakeTest.java:384)
>   at 
> org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades(HandshakeTest.java:243)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {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-17698) sstabledump errors when dumping data from index

2023-02-08 Thread maxwellguo (Jira)



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

maxwellguo commented on CASSANDRA-17698:


[~blambov]  [~adelapena] [~smiklosovic] any advice on my replied message 
above？If so I will open a new ticket for older branches.

> sstabledump errors when dumping data from index
> ---
>
> Key: CASSANDRA-17698
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17698
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tool/sstable
>Reporter: Stefan Miklosovic
>Assignee: maxwellguo
>Priority: Normal
> Fix For: 4.2
>
>  Time Spent: 12h 40m
>  Remaining Estimate: 0h
>
> {code:java}
> cqlsh> CREATE KEYSPACE ks1 WITH replication = {'class': 'SimpleStrategy', 
> 'replication_factor': 1};
> cqlsh> CREATE TABLE ks1.tb1 ( id text, name text, primary key (id));
> cqlsh> CREATE INDEX IF NOT EXISTS ON ks1.tb1(name);
> cqlsh> INSERT INTO ks1.tb1 (id, name ) VALUES ( '1', 'Joe');
> cqlsh> exit
> ./bin/nodetool flush
> ./tools/bin/sstabledump 
> data/data/ks1/tb1-1c3c5f10ee4711ecab82eda2f44200b3/.tb1_name_idx/nb-1-big-Data.db
>  
> [
>   {
>     "partition" : {
>       "key" : [ "Joe" ],
>       "position" : 0
>     },
>     "rows" : [
>       {
>         "type" : "row",
>         "position" : 17,
>         "clustering" : [ ] } ] } ]Exception in thread "main" 
> java.lang.UnsupportedOperationException
>         at 
> org.apache.cassandra.db.marshal.PartitionerDefinedOrder.toJSONString(PartitionerDefinedOrder.java:87)
>         at 
> org.apache.cassandra.db.marshal.AbstractType.toJSONString(AbstractType.java:187)
>         at 
> org.apache.cassandra.tools.JsonTransformer.serializeClustering(JsonTransformer.java:372)
>         at 
> org.apache.cassandra.tools.JsonTransformer.serializeRow(JsonTransformer.java:269)
>         at 
> org.apache.cassandra.tools.JsonTransformer.serializePartition(JsonTransformer.java:235)
>         at 
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
>         at 
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
>         at java.util.Iterator.forEachRemaining(Iterator.java:116)
>         at 
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
>         at 
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
>         at 
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
>         at 
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
>         at 
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
>         at 
> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
>         at 
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
>         at 
> org.apache.cassandra.tools.JsonTransformer.toJson(JsonTransformer.java:113)
>         at 
> org.apache.cassandra.tools.SSTableExport.main(SSTableExport.java:214) {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-18049) Update Chronicle Queue

2023-02-08 Thread Michael Semb Wever (Jira)



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

Michael Semb Wever commented on CASSANDRA-18049:


Related (but not blocking): 
https://issues.apache.org/jira/browse/CASSANDRA-18072?focusedCommentId=17685261=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17685261

> Update Chronicle Queue
> --
>
> Key: CASSANDRA-18049
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18049
> Project: Cassandra
>  Issue Type: Task
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> According to [this|https://chronicle.software/chronicle-support-java-17] 
> article:
> {code:java}
> Starting from chronicle-bom-2.22ea26, all new releases can be run under Java 
> 17 when run on the class path (but not yet under the module path).{code}
> This BOM is newer than what we currently have in both 4.1 and trunk. 4.1 
> points in comments to 
> [https://mvnrepository.com/artifact/net.openhft/chronicle-bom/1.16.23] which 
> I believe was just forgotten to be updated/removed. The versions we see 
> correspond to this BOM 
> [https://mvnrepository.com/artifact/net.openhft/chronicle-bom/2.20.226]
> It is still older than chronicle-bom-2.22ea26 so we need to upgrade. I 
> suggest we also add a comment again which BOM is considered, this makes 
> things easier.
> Further to running CI, review of the CHANGE logs needs to happen to ensure we 
> do not miss anything that can impact us and it is not caught by our tests.
> For testing with JDK17, please, contact [~e.dimitrova] for latest branch and 
> CI config (at this point feature branch in the cassandra repo does not exist)
>  



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

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

[jira] [Commented] (CASSANDRA-18179) Update build.xml for experimental JDK17 use

2023-02-08 Thread Michael Semb Wever (Jira)



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

Michael Semb Wever commented on CASSANDRA-18179:


bq. Thanks, do we want to open a separate thread dedicated to JDK 17 where we 
state the exact steps we propose to do it and introduce this ticket? 

I'm ok with how it is. It's been mentioned: under the context of incremental 
work; and folk know how to find and listen to the ticket.

> Update build.xml for experimental JDK17 use
> ---
>
> Key: CASSANDRA-18179
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18179
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.x
>
>
> To support JDK17 we need to make changes to build.xml and our scripts. There 
> is a preliminary patch which makes a switch from JDK8+JDK11 to JDK11+JDK17 
> but it will need a change considering CASSANDRA-18133
> CC [~mck] 



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

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

[jira] [Comment Edited] (CASSANDRA-18070) Add a new SELECT_MASKED permission

2023-02-08 Thread Jira



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

Andres de la Peña edited comment on CASSANDRA-18070 at 2/8/23 2:09 PM:
---

Here is the PR adding the new {{SELECT_MASKED}} permission, and the PR updating 
auth dtests for it:
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/2146]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/2627/workflows/3d39aa96-2ac3-4a61-a999-88fbcf2dc0fe]
 
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/2627/workflows/6034b40b-6572-4fff-af7a-cca3c87ac274]|
|[dtest|https://github.com/apache/cassandra-dtest/pull/209]|

The patch is based on CASSANDRA-18069, which is based on CASSANDRA-18068.


was (Author: adelapena):
Here is the PR adding the new {{SELECT_MASKED}} permission, and the PR updating 
auth dtests for it:
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/2146]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/2625/workflows/e9950fcd-6850-45fd-9199-8d28861cec9f]
 
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/2625/workflows/ca876e61-ab6c-4f67-ac6f-f8ea2d09aaee]|
|[dtest|https://github.com/apache/cassandra-dtest/pull/209]|

The patch is based on CASSANDRA-18069, which is based on CASSANDRA-18068.

> Add a new SELECT_MASKED permission
> --
>
> Key: CASSANDRA-18070
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18070
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Feature/Dynamic Data Masking
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add a table-level SELECT_MASKED permission allowing certain users to query 
> but not see the unmasked columns introduced by CASSANDRA-18068, assuming that 
> they also have the SELECT permission on the table, as defined by 
> [CEP-20|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-20%3A+Dynamic+Data+Masking].
>  
> It would look like:
> {code}
> > CREATE USER unprivileged_user WITH PASSWORD 'xyz';
> > CREATE USER privileged_user WITH PASSWORD 'zyx';
>  
> > GRANT SELECT ON ALL TABLE patients TO unprivileged_user;
> > GRANT SELECT ON ALL TABLE patients TO privileged_user;
> > GRANT SELECT_MASKED ON ALL TABLE patients TO privileged_user;
>  
> > LOGIN unprivileged_user
> > SELECT name, birth FROM patients WHERE name='alice' ALLOW FILTERING;
>  
> Unauthorized: Error from server: code=2100 [Unauthorized] message="User has 
> no UNMASK nor SELECT_UNMASK permission on "
>  
> > LOGIN privileged_user
> > SELECT name, birth FROM patients WHERE name='alice' ALLOW FILTERING;
>  
>  name| birth
> -+
>  ale | 1900-01-01
> {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-18244) Improve documentation about releases for Cassandra website.

2023-02-08 Thread Berenguer Blasi (Jira)



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

Berenguer Blasi commented on CASSANDRA-18244:
-

Yep I'll follow and report back

> Improve documentation about releases for Cassandra website.
> ---
>
> Key: CASSANDRA-18244
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18244
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
>  Labels: pull-request-available
> Fix For: NA
>
>
> The documentation is lacking some details so a respective developers can have 
> more smooth release experience when setting up their system for the first 
> time.



--
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-18066) Server should be started in @Before rather than @BeforeClass in CQLTester

2023-02-08 Thread Stefan Miklosovic (Jira)



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

Stefan Miklosovic updated CASSANDRA-18066:
--
Fix Version/s: 4.x

> Server should be started in @Before rather than @BeforeClass in CQLTester
> -
>
> Key: CASSANDRA-18066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18066
> Project: Cassandra
>  Issue Type: Bug
>  Components: Test/unit
>Reporter: Jacek Lewandowski
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> I can see that there is some misunderstanding in the project of 
> {{@BeforeClass}} annotated methods. 
> Given we have a static method {{@BeforeClass static void initA()}} in 
> {{CQLTester}} and {{@BeforeClass static void initB()}} in {{SomeTestClass 
> extends CQLTester}}, it will run like the following:
> 1. static initializer of {{CQLTester}}
> 2. {{initA()}}
> 3. static initializer of {{SomeTestClass}}
> 4. {{initB()}}
> Since the server is started in (2), there is essentially no way to 
> consistently set startup properties or configuration of 
> {{DatabaseDescriptor}} in {{SomeTestClass}} so that the starting server can 
> pick it consistently. That is, if something works, it is just because some 
> server class has not been used yet, but this actually cannot be guaranteed.
> When I look in the code, it seems like the understanding of JUnit was that if 
> {{initB()}} is defined, then {{initA()}} is not called, but this is not true.
> Therefore, I propose to move the server initialization from {{initA()}} (call 
> to {{SchemaLoader.prepareServer()}} to a method annotated with {{@Before}} in 
> {{CQLTester}} so that the server is started with the first test case. Then, 
> we will be sure that call to {{initB()}} will happen before the server is 
> initialized and we will be able to set configuration consistently.



--
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-18244) Improve documentation about releases for Cassandra website.

2023-02-08 Thread ASF GitHub Bot (Jira)



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

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

> Improve documentation about releases for Cassandra website.
> ---
>
> Key: CASSANDRA-18244
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18244
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
>  Labels: pull-request-available
> Fix For: NA
>
>
> The documentation is lacking some details so a respective developers can have 
> more smooth release experience when setting up their system for the first 
> time.



--
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-18244) Improve documentation about releases for Cassandra website.

2023-02-08 Thread Stefan Miklosovic (Jira)



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

Stefan Miklosovic commented on CASSANDRA-18244:
---

Thanks [~mck], I see that [~bereng] is among reviewers as well. Let's wait 
until he is also set up to do a release and goes through that guide so we have 
not forgotten anything. If, after reading that guide, Berenguer still needs to 
ask something, we know that the guide is not good enough :)

> Improve documentation about releases for Cassandra website.
> ---
>
> Key: CASSANDRA-18244
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18244
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: NA
>
>
> The documentation is lacking some details so a respective developers can have 
> more smooth release experience when setting up their system for the first 
> time.



--
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-18239) Remove eclipse warnings task

2023-02-08 Thread Michael Semb Wever (Jira)



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

Michael Semb Wever commented on CASSANDRA-18239:


I don't have much of an opinion, except the more we can automate code style the 
more we remove nit comments from PRs coming from new contributor. 

If you can bring up the numbers for suppressions and valid patterns, then it'll 
be easy to make a quantified response.

> Remove eclipse warnings task
> 
>
> Key: CASSANDRA-18239
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18239
> Project: Cassandra
>  Issue Type: Task
>  Components: Build
>Reporter: Jacek Lewandowski
>Priority: Normal
>
> Eclipse warnings is used for static code analysis. However, it does not fit 
> well into Cassandra code and practically we end up explicitly adding 
> suppressions in many places just to satisfy that tool rather than fix the 
> real issues.
> This is an incomplete list of reasons to remove it:
> - not closed resources are detected incorrectly
> - does not recognize custom utility methods used to close the resources, 
> which use use heavily in the code, like {{Throwables.close}}, 
> {{FileUtils.close}}, {{closeQuietly}}...
> - because of the above, we cannot make important things like {{Ref}} to 
> implement {{Closeable}} as it would make the tool to explode with tons of 
> warnings
> - it complains about correct generics - something like "method X is not 
> applicable for ..." when the code compiles successfully is not acceptable
> - it is old and not maintained
> There are better tools like IntelliJ inspections for example, which can also 
> be run in headless mode



--
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-18243) Add bereng's gpg key to KEYs file

2023-02-08 Thread Brandon Williams (Jira)



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

Brandon Williams commented on CASSANDRA-18243:
--

{noformat}
gpg: data source: https://keys.openpgp.org:443
gpg: armor header: Comment: CEC5 C50B 9C62 9EF0 F5AB  2706 650B 72EB 14CC D622
gpg: armor header: Comment: Berenguer Blasi (Code Signing Key) 

gpg: pub  rsa4096/650B72EB14CCD622 2023-02-08  Berenguer Blasi (Code Signing 
Key) 
gpg: using pgp trust model
gpg: key 650B72EB14CCD622: public key "Berenguer Blasi (Code Signing Key) 
" imported
gpg: Total number processed: 1
gpg:   imported: 1
{noformat}

Committed to https://dist.apache.org/repos/dist/release/cassandra/KEYS in 
r59966.


> Add bereng's gpg key to KEYs file
> -
>
> Key: CASSANDRA-18243
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18243
> Project: Cassandra
>  Issue Type: Task
>Reporter: Berenguer Blasi
>Assignee: Brandon Williams
>Priority: Normal
>
> Hi,
> I would like my key to be added 
> [https://keys.openpgp.org/vks/v1/by-fingerprint/CEC5C50B9C629EF0F5AB2706650B72EB14CCD622|https://keys.openpgp.org/vks/v1/by-fingerprint/CEC5C50B9C629EF0F5AB2706650B72EB14CCD622]
> To be able to do Cassandra releases



--
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-18243) Add bereng's gpg key to KEYs file

2023-02-08 Thread Brandon Williams (Jira)



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

Brandon Williams updated CASSANDRA-18243:
-
Resolution: Fixed
Status: Resolved  (was: Triage Needed)

> Add bereng's gpg key to KEYs file
> -
>
> Key: CASSANDRA-18243
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18243
> Project: Cassandra
>  Issue Type: Task
>Reporter: Berenguer Blasi
>Assignee: Brandon Williams
>Priority: Normal
>
> Hi,
> I would like my key to be added 
> [https://keys.openpgp.org/vks/v1/by-fingerprint/CEC5C50B9C629EF0F5AB2706650B72EB14CCD622|https://keys.openpgp.org/vks/v1/by-fingerprint/CEC5C50B9C629EF0F5AB2706650B72EB14CCD622]
> To be able to do Cassandra releases



--
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

svn commit: r59966 - /release/cassandra/KEYS

2023-02-08 Thread brandonwilliams

Author: brandonwilliams
Date: Wed Feb  8 13:38:14 2023
New Revision: 59966

Log:
Add bereng's key to KEYS

Modified:
release/cassandra/KEYS

Modified: release/cassandra/KEYS
==
--- release/cassandra/KEYS (original)
+++ release/cassandra/KEYS Wed Feb  8 13:38:14 2023
@@ -4325,3 +4325,62 @@ ca0RtIeuWK6jlM49+asgrFWHavhvcxsSNHGkjvBs
 NuIj/E4S
 =O1G2
 -END PGP PUBLIC KEY BLOCK-
+pub   rsa4096 2023-02-08 [SC]
+  CEC5C50B9C629EF0F5AB2706650B72EB14CCD622
+uid   [ unknown] Berenguer Blasi (Code Signing Key) 
+sig 3650B72EB14CCD622 2023-02-08  Berenguer Blasi (Code Signing Key) 

+sub   rsa4096 2023-02-08 [E]
+sig  650B72EB14CCD622 2023-02-08  Berenguer Blasi (Code Signing Key) 

+
+-BEGIN PGP PUBLIC KEY BLOCK-
+
+mQINBGPjnhQBEADD79gbb/ExosUyd/PeyQ4SRNm8F83bGxcgc7h0juJsuXZHfsUi
+z5JBHKNvMIWz7KP1GW6Tpcjm27OSrV8FBJ87+hO0GrfZcXBVfEowbsma5J4uRSGT
+iZEkVutL0ao7d88YFMonXcYL5RbcWMwhQfUwofkIenqBIJdprJNLKY1r99XC9pf/
+ClB313RwLQ1TvHYMh77SorpdgrPOD5pmBDTCfcSrPm4EEQWeYsXMh3S7XmjrOFgw
+LYNRmr1nlBuSis6oBDArAwD6crVSK0Z1dkqpETOS2qQdKqjQRqdrxf/Turbf94X+
+EUNgXK9UPxSDmv2NYmBVdn38JLILxWSUjnTA01/TJjvcW1oCK0e/ncQXXZXzabe8
+k5YOOtCMySCvsLgHO6bWCO9z1ZtdVypR0RtmRbobTNTrm4Yf55MdhK4G4XypJlkb
+E0HdrWgh1C+dN0WDmE59DfD1baRvnwVX+OgzExFQWBO/W99dIxuMDHvylaWOHQ35
+48mnetnbW6vqPt6PalZpMOPX4hQYi8a6Odj+ZIHe2Sq5oPe9BTxdkOyVOEBkaO8W
+zCXLMXqhUV4JOR6JpOmA/q/Yke2YmKtxtYbDU2VRp/nmzoEMbdQNtJg1YLJot8Ff
+OBaLLWAWbht+WjQ8rT7oWn0/z1JO22ma9tm7QaCpt+g8idgh6VD6vAqbrQARAQAB
+tDZCZXJlbmd1ZXIgQmxhc2kgKENvZGUgU2lnbmluZyBLZXkpIDxiZXJlbmdAYXBh
+Y2hlLm9yZz6JAk4EEwEKADgWIQTOxcULnGKe8PWrJwZlC3LrFMzWIgUCY+OeFAIb
+AwULCQgHAgYVCgkICwIEFgIDAQIeAQIXgAAKCRBlC3LrFMzWIrcpD/4tXVvTU66v
+IWxhg6QZp5I32eIyZJyUZCWrm9sDx6ln3uz8aq85r8Bzm8RKq92LK5xzgkfvfod2
+4RB35GpEd/bkgDn3CDIkjnRrLKayXi4sSlx+uZkl4ghUoSelqupTV7GdbphSzZib
+WOpCuFvuoKvqYsWR+A7jfdDRvhDnUMBPQDRIZejmFqjREVvDcjEGbidW88hXV4V1
+fMlKgcsmKv3O1IPx0v0GzV7fe7DDMvsgaqgDZVHrkGpDbFebPNDdiK4gZTfeK9ic
+O/BXvOjyXf3/nNOzUIrTtSGfPLmo4NURX6+B8IjpE02OaDq5naIUqI26PZyEhG1R
+G9DSo3m9k7x2BK+MsX67DkXSm+HPErOppKW4dyzppkvGz+g+tFcXTFarP0J82n65
+4E66+hRFksUwXj8uAf1fs0BqhD83pY0z0jHSX5+4G57ew4nnS05yfvTEPpk/Y4MV
+tU7mVLsxNl7FzbnhiZ8aAsFuJis16dKRpWaqUBbMXaM9s+1lEfpaJX38O659fssZ
+wQP0jbK+0bx36S5QtKy4QW7aTGcY/4af7T5GsuFXnjGxeMt8qR5SBJM0HJUulips
+e0x0REnM6J4E+EdAqhGOkDTOPdhQKho/OjnXow4h2cwnpa/hgD0sUBPgAbAt+ZZ/
+mJwmlSEnaKk4ea7OwjmIl8SGykHKvd0oObkCDQRj454UARAA3LPFFK9QFcwHdw8v
+LbMR/g+YbV5tkdV+811zsaFPecXCxJtJJYsHq9TbOUP/Sq9KN5aTL/K1UNgyXjDU
+4ybjy/htNv2t6FZYHdXLOxKCQOm5KNHslkwcSx6bVXBvyjIWhZl4ZmZg0vuLVhIM
+4gEvmy5G3Kc1E06592qMY+iiGRDXzLEyb0fX/fKYimB6KXqEIHNI7L3Es24uip94
+avDf4dmaSfixEfZnJqQtuTuWC1TJUwkzCjQFPqaYBQ7OaXWgcYa0qwKdIwwgkBKL
+6ULqLy3s6Ovlc7nlafs7MyTZtu7nARgVCoiKqHjX6FhHjvB6EZCVp5NcQSQa07bG
+BC3hAGhZN+SFGk0GrHA6k8tfCwEwZFIWCUbQE1/fR/8+qnstwbGQmcXPxERZdqqJ
+3QwcgGBFapX9F2bHjY43RA2NycAgwCAcrei4mAodGQLJB9wDwdyn6LyFFOvOWgmu
+24o8B6fpe+YQnddgR+WHgyJcPYkRCpjUeyO2BkZRU0ezSslQuEIsVnb7fjPSFtwC
+NXBnPiF5BNSWjGDtUw2OUMlPd9Ng9XPxY4lvK9SFs58SdzlWMk7deg3D2h9YWZtp
+M399UXo1picND+HnSta3zJuhCHaxN0+idleuxVGatsx879A0ep3wkrLkD7DPIQXm
+hqaaWdFBn4IdQZ81ZFJcZzE2770AEQEAAYkCNgQYAQoAIBYhBM7FxQucYp7w9asn
+BmULcusUzNYiBQJj454UAhsMAAoJEGULcusUzNYiJCMP/iq4eV8y5TOojTPKhxKF
+LSXCVtpkWMPQE+ADo6Md9VzBRdPKtVV8X1kHOmASz+BksHIIKCNGIZSBLjGC8FL9
+YlxfbCkAe1m7TKrp0/zzn8yX0YN01kygO+rKhQZhRKXopUEThJpZfPwifIcrJ2OZ
+9GaTjtikaSinU6GAY5uzRdMXNcTTq4YCTbw+rBJs+3MjhKJ93me1VWbPaiYRB97H
+3phBDBF77A7DveX9uT5KO8/638M1d5RRglBoTlfRiPp9xDk961h1yfwQJM7GefyY
+Wkq4mC+0WOb3YfXQO0U8abSPqx7Z0QxTJajMAnwQCtXkX1Hb4SLbdOjNdl26IY25
+xtWqMo0MVJ/7xqCBidmAaKv+MbvGKbwqO1xA1z/7xOeDU9aD0iCpVWuiHDFyKY1j
+x+VD3MbdPNj6WiYo6/13HurTv+qqWLJX789fuJK9hFjRoDC1mOZm1Y+bCds/+3Oa
+G2Wy8nAOAejRyIdGPENloamIN21y5mNGvFCIbb/hMixg49L3SK6pkH4VS8/lrbOS
+bX2jaUW6WAij4deNlOh5QIRgX/7F7GgIMr4BwdKR+GyB9xjbL5AXK5+VWvvY0lWD
+7kmmG/VZCFfVTw9oAwWQfKxBnlVDmGMFTojyBi8puRubbNBVbdjmAeVX/DIXSFqy
+V2TrBZ7se6NT5IP/MpUv+x+N
+=+vFA
+-END PGP PUBLIC KEY BLOCK-



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

[jira] [Updated] (CASSANDRA-18244) Improve documentation about releases for Cassandra website.

2023-02-08 Thread Michael Semb Wever (Jira)



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

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

+1

> Improve documentation about releases for Cassandra website.
> ---
>
> Key: CASSANDRA-18244
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18244
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: NA
>
>
> The documentation is lacking some details so a respective developers can have 
> more smooth release experience when setting up their system for the first 
> time.



--
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-18243) Add bereng's gpg key to KEYs file

2023-02-08 Thread Berenguer Blasi (Jira)



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

Berenguer Blasi updated CASSANDRA-18243:

Description: 
Hi,

I would like my key to be added 
[https://keys.openpgp.org/vks/v1/by-fingerprint/CEC5C50B9C629EF0F5AB2706650B72EB14CCD622|https://keys.openpgp.org/vks/v1/by-fingerprint/CEC5C50B9C629EF0F5AB2706650B72EB14CCD622]

To be able to do Cassandra releases

  was:
Hi,

I would like my key to be added 
[https://keys.openpgp.org/vks/v1/by-fingerprint/CEC5C50B9C629EF0F5AB2706650B72EB14CCD622|https://keys.openpgp.org/vks/v1/by-fingerprint/AB852337635AF2087BFE554F243E0F07F8CCA4B8]

To be able to do Cassandra releases


> Add bereng's gpg key to KEYs file
> -
>
> Key: CASSANDRA-18243
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18243
> Project: Cassandra
>  Issue Type: Task
>Reporter: Berenguer Blasi
>Assignee: Brandon Williams
>Priority: Normal
>
> Hi,
> I would like my key to be added 
> [https://keys.openpgp.org/vks/v1/by-fingerprint/CEC5C50B9C629EF0F5AB2706650B72EB14CCD622|https://keys.openpgp.org/vks/v1/by-fingerprint/CEC5C50B9C629EF0F5AB2706650B72EB14CCD622]
> To be able to do Cassandra releases



--
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-18243) Add bereng's gpg key to KEYs file

2023-02-08 Thread Berenguer Blasi (Jira)



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

Berenguer Blasi updated CASSANDRA-18243:

Description: 
Hi,

I would like my key to be added 
[https://keys.openpgp.org/vks/v1/by-fingerprint/CEC5C50B9C629EF0F5AB2706650B72EB14CCD622|https://keys.openpgp.org/vks/v1/by-fingerprint/AB852337635AF2087BFE554F243E0F07F8CCA4B8]

To be able to do Cassandra releases

  was:
Hi,

I would like my key to be added 
[https://keys.openpgp.org/vks/v1/by-fingerprint/AB852337635AF2087BFE554F243E0F07F8CCA4B8]

To be able to do Cassandra releases


> Add bereng's gpg key to KEYs file
> -
>
> Key: CASSANDRA-18243
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18243
> Project: Cassandra
>  Issue Type: Task
>Reporter: Berenguer Blasi
>Assignee: Brandon Williams
>Priority: Normal
>
> Hi,
> I would like my key to be added 
> [https://keys.openpgp.org/vks/v1/by-fingerprint/CEC5C50B9C629EF0F5AB2706650B72EB14CCD622|https://keys.openpgp.org/vks/v1/by-fingerprint/AB852337635AF2087BFE554F243E0F07F8CCA4B8]
> To be able to do Cassandra releases



--
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-17979) Fix flaky test:org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades

2023-02-08 Thread Brandon Williams (Jira)



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

Brandon Williams commented on CASSANDRA-17979:
--

I think [~edimitrova] had a concern here, is that still the case?

> Fix flaky 
> test:org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades
> ---
>
> Key: CASSANDRA-17979
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17979
> Project: Cassandra
>  Issue Type: Bug
>  Components: Messaging/Internode
>Reporter: Brandon Williams
>Assignee: Derek Chen-Becker
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1339/testReport/org.apache.cassandra.net/HandshakeTest/testOutboundConnectionfFallbackDuringUpgrades_cdc/
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1336/testReport/org.apache.cassandra.net/HandshakeTest/testOutboundConnectionfFallbackDuringUpgrades_compression/
> https://app.circleci.com/pipelines/github/instaclustr/cassandra/1466/workflows/ffb52616-92d7-4089-a0c9-a9ebf28333c0/jobs/6296/tests
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.cassandra.net.HandshakeTest.testOutboundFallbackOnSSLHandshakeFailure(HandshakeTest.java:384)
>   at 
> org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades(HandshakeTest.java:243)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {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-18066) Server should be started in @Before rather than @BeforeClass in CQLTester

2023-02-08 Thread Stefan Miklosovic (Jira)



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

Stefan Miklosovic updated CASSANDRA-18066:
--
Test and Documentation Plan: run CI
 Status: Patch Available  (was: Open)

List of classes which extend CQLTester, contain BeforeClass and prepareServer is

{code}
for i in $(find . -type f -name '*.java' | xargs grep  'extends CQLTester' | 
cut -d":" -f1 ); do if [ $(grep '@BeforeClass' $i | wc -l) != "0" -a $(grep 
'prepareServer' $i | wc -l) != "0" ]; then echo $i; fi ; done
{code}

which yields

{code}
./unit/org/apache/cassandra/db/rows/ThrottledUnfilteredIteratorTest.java
./unit/org/apache/cassandra/db/memtable/MemtableQuickTest.java
./unit/org/apache/cassandra/tools/nodetool/VerifyTest.java
./unit/org/apache/cassandra/cql3/selection/SelectionColumnMappingTest.java
./unit/org/apache/cassandra/cql3/CustomNowInSecondsTest.java
./unit/org/apache/cassandra/cql3/validation/operations/SelectLimitTest.java
./unit/org/apache/cassandra/cql3/validation/entities/JsonTest.java
./unit/org/apache/cassandra/cql3/validation/entities/FrozenCollectionsTest.java
./unit/org/apache/cassandra/cql3/validation/entities/UserTypesTest.java
{code}

I fixed these classes here:

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

[~jlewandowski] would you mind to take a look?

> Server should be started in @Before rather than @BeforeClass in CQLTester
> -
>
> Key: CASSANDRA-18066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18066
> Project: Cassandra
>  Issue Type: Bug
>  Components: Test/unit
>Reporter: Jacek Lewandowski
>Assignee: Stefan Miklosovic
>Priority: Normal
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> I can see that there is some misunderstanding in the project of 
> {{@BeforeClass}} annotated methods. 
> Given we have a static method {{@BeforeClass static void initA()}} in 
> {{CQLTester}} and {{@BeforeClass static void initB()}} in {{SomeTestClass 
> extends CQLTester}}, it will run like the following:
> 1. static initializer of {{CQLTester}}
> 2. {{initA()}}
> 3. static initializer of {{SomeTestClass}}
> 4. {{initB()}}
> Since the server is started in (2), there is essentially no way to 
> consistently set startup properties or configuration of 
> {{DatabaseDescriptor}} in {{SomeTestClass}} so that the starting server can 
> pick it consistently. That is, if something works, it is just because some 
> server class has not been used yet, but this actually cannot be guaranteed.
> When I look in the code, it seems like the understanding of JUnit was that if 
> {{initB()}} is defined, then {{initA()}} is not called, but this is not true.
> Therefore, I propose to move the server initialization from {{initA()}} (call 
> to {{SchemaLoader.prepareServer()}} to a method annotated with {{@Before}} in 
> {{CQLTester}} so that the server is started with the first test case. Then, 
> we will be sure that call to {{initB()}} will happen before the server is 
> initialized and we will be able to set configuration consistently.



--
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-18066) Server should be started in @Before rather than @BeforeClass in CQLTester

2023-02-08 Thread Stefan Miklosovic (Jira)



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

Stefan Miklosovic updated CASSANDRA-18066:
--
 Bug Category: Parent values: Code(13163)
   Complexity: Normal
Discovered By: Code Inspection
 Severity: Normal
 Assignee: Stefan Miklosovic
   Status: Open  (was: Triage Needed)

> Server should be started in @Before rather than @BeforeClass in CQLTester
> -
>
> Key: CASSANDRA-18066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18066
> Project: Cassandra
>  Issue Type: Bug
>  Components: Test/unit
>Reporter: Jacek Lewandowski
>Assignee: Stefan Miklosovic
>Priority: Normal
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> I can see that there is some misunderstanding in the project of 
> {{@BeforeClass}} annotated methods. 
> Given we have a static method {{@BeforeClass static void initA()}} in 
> {{CQLTester}} and {{@BeforeClass static void initB()}} in {{SomeTestClass 
> extends CQLTester}}, it will run like the following:
> 1. static initializer of {{CQLTester}}
> 2. {{initA()}}
> 3. static initializer of {{SomeTestClass}}
> 4. {{initB()}}
> Since the server is started in (2), there is essentially no way to 
> consistently set startup properties or configuration of 
> {{DatabaseDescriptor}} in {{SomeTestClass}} so that the starting server can 
> pick it consistently. That is, if something works, it is just because some 
> server class has not been used yet, but this actually cannot be guaranteed.
> When I look in the code, it seems like the understanding of JUnit was that if 
> {{initB()}} is defined, then {{initA()}} is not called, but this is not true.
> Therefore, I propose to move the server initialization from {{initA()}} (call 
> to {{SchemaLoader.prepareServer()}} to a method annotated with {{@Before}} in 
> {{CQLTester}} so that the server is started with the first test case. Then, 
> we will be sure that call to {{initB()}} will happen before the server is 
> initialized and we will be able to set configuration consistently.



--
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-18243) Add bereng's gpg key to KEYs file

2023-02-08 Thread Brandon Williams (Jira)



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

Brandon Williams reassigned CASSANDRA-18243:


Assignee: Brandon Williams

> Add bereng's gpg key to KEYs file
> -
>
> Key: CASSANDRA-18243
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18243
> Project: Cassandra
>  Issue Type: Task
>Reporter: Berenguer Blasi
>Assignee: Brandon Williams
>Priority: Normal
>
> Hi,
> I would like my key to be added 
> [https://keys.openpgp.org/vks/v1/by-fingerprint/AB852337635AF2087BFE554F243E0F07F8CCA4B8]
> To be able to do Cassandra releases



--
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-17979) Fix flaky test:org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades

2023-02-08 Thread Stefan Miklosovic (Jira)



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

Stefan Miklosovic updated CASSANDRA-17979:
--
Status: Ready to Commit  (was: Review In Progress)

> Fix flaky 
> test:org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades
> ---
>
> Key: CASSANDRA-17979
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17979
> Project: Cassandra
>  Issue Type: Bug
>  Components: Messaging/Internode
>Reporter: Brandon Williams
>Assignee: Derek Chen-Becker
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1339/testReport/org.apache.cassandra.net/HandshakeTest/testOutboundConnectionfFallbackDuringUpgrades_cdc/
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1336/testReport/org.apache.cassandra.net/HandshakeTest/testOutboundConnectionfFallbackDuringUpgrades_compression/
> https://app.circleci.com/pipelines/github/instaclustr/cassandra/1466/workflows/ffb52616-92d7-4089-a0c9-a9ebf28333c0/jobs/6296/tests
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.cassandra.net.HandshakeTest.testOutboundFallbackOnSSLHandshakeFailure(HandshakeTest.java:384)
>   at 
> org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades(HandshakeTest.java:243)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {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-17979) Fix flaky test:org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades

2023-02-08 Thread Stefan Miklosovic (Jira)



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

Stefan Miklosovic commented on CASSANDRA-17979:
---

+1. Thanks. [~brandon.williams] I will leave committing on you.

> Fix flaky 
> test:org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades
> ---
>
> Key: CASSANDRA-17979
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17979
> Project: Cassandra
>  Issue Type: Bug
>  Components: Messaging/Internode
>Reporter: Brandon Williams
>Assignee: Derek Chen-Becker
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1339/testReport/org.apache.cassandra.net/HandshakeTest/testOutboundConnectionfFallbackDuringUpgrades_cdc/
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1336/testReport/org.apache.cassandra.net/HandshakeTest/testOutboundConnectionfFallbackDuringUpgrades_compression/
> https://app.circleci.com/pipelines/github/instaclustr/cassandra/1466/workflows/ffb52616-92d7-4089-a0c9-a9ebf28333c0/jobs/6296/tests
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.cassandra.net.HandshakeTest.testOutboundFallbackOnSSLHandshakeFailure(HandshakeTest.java:384)
>   at 
> org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades(HandshakeTest.java:243)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {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-17979) Fix flaky test:org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades

2023-02-08 Thread Stefan Miklosovic (Jira)



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

Stefan Miklosovic updated CASSANDRA-17979:
--
Reviewers: Brandon Williams, Stefan Miklosovic  (was: Brandon Williams)
   Status: Review In Progress  (was: Needs Committer)

> Fix flaky 
> test:org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades
> ---
>
> Key: CASSANDRA-17979
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17979
> Project: Cassandra
>  Issue Type: Bug
>  Components: Messaging/Internode
>Reporter: Brandon Williams
>Assignee: Derek Chen-Becker
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1339/testReport/org.apache.cassandra.net/HandshakeTest/testOutboundConnectionfFallbackDuringUpgrades_cdc/
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1336/testReport/org.apache.cassandra.net/HandshakeTest/testOutboundConnectionfFallbackDuringUpgrades_compression/
> https://app.circleci.com/pipelines/github/instaclustr/cassandra/1466/workflows/ffb52616-92d7-4089-a0c9-a9ebf28333c0/jobs/6296/tests
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.cassandra.net.HandshakeTest.testOutboundFallbackOnSSLHandshakeFailure(HandshakeTest.java:384)
>   at 
> org.apache.cassandra.net.HandshakeTest.testOutboundConnectionfFallbackDuringUpgrades(HandshakeTest.java:243)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {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-18244) Improve documentation about releases for Cassandra website.

2023-02-08 Thread Berenguer Blasi (Jira)



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

Berenguer Blasi updated CASSANDRA-18244:

Reviewers: Berenguer Blasi

> Improve documentation about releases for Cassandra website.
> ---
>
> Key: CASSANDRA-18244
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18244
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: NA
>
>
> The documentation is lacking some details so a respective developers can have 
> more smooth release experience when setting up their system for the first 
> time.



--
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-18244) Improve documentation about releases for Cassandra website.

2023-02-08 Thread Stefan Miklosovic (Jira)



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

Stefan Miklosovic commented on CASSANDRA-18244:
---

[~lor...@datastax.com] [~polandll] Would you mind to review, please?

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

> Improve documentation about releases for Cassandra website.
> ---
>
> Key: CASSANDRA-18244
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18244
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: NA
>
>
> The documentation is lacking some details so a respective developers can have 
> more smooth release experience when setting up their system for the first 
> time.



--
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-18244) Improve documentation about releases for Cassandra website.

2023-02-08 Thread Stefan Miklosovic (Jira)



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

Stefan Miklosovic updated CASSANDRA-18244:
--
Test and Documentation Plan: NA
 Status: Patch Available  (was: Open)

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

> Improve documentation about releases for Cassandra website.
> ---
>
> Key: CASSANDRA-18244
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18244
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: NA
>
>
> The documentation is lacking some details so a respective developers can have 
> more smooth release experience when setting up their system for the first 
> time.



--
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-18244) Improve documentation about releases for Cassandra website.

2023-02-08 Thread Stefan Miklosovic (Jira)



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

Stefan Miklosovic updated CASSANDRA-18244:
--
Change Category: Semantic
 Complexity: Normal
  Fix Version/s: NA
 Status: Open  (was: Triage Needed)

> Improve documentation about releases for Cassandra website.
> ---
>
> Key: CASSANDRA-18244
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18244
> Project: Cassandra
>  Issue Type: Task
>  Components: Documentation/Website
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: NA
>
>
> The documentation is lacking some details so a respective developers can have 
> more smooth release experience when setting up their system for the first 
> time.



--
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-18244) Improve documentation about releases for Cassandra website.

2023-02-08 Thread Stefan Miklosovic (Jira)

Stefan Miklosovic created CASSANDRA-18244:
-

 Summary: Improve documentation about releases for Cassandra 
website.
 Key: CASSANDRA-18244
 URL: https://issues.apache.org/jira/browse/CASSANDRA-18244
 Project: Cassandra
  Issue Type: Task
  Components: Documentation/Website
Reporter: Stefan Miklosovic
Assignee: Stefan Miklosovic


The documentation is lacking some details so a respective developers can have 
more smooth release experience when setting up their system for the first time.



--
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 (892d93c4e -> 5e9173e12)

2023-02-08 Thread 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 892d93c4e generate docs for 11d2d4b3
 new 5e9173e12 generate docs for 11d2d4b3

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   (892d93c4e)
\
 N -- N -- N   refs/heads/asf-staging (5e9173e12)

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 4970898 -> 4970898 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] [Commented] (CASSANDRA-18001) Add missing tests suites to CircleCI

2023-02-08 Thread Jira



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

Andres de la Peña commented on CASSANDRA-18001:
---

Yes, I was hitting the same problem with CircleCI yesterday. It seems that 
something is broken on their side. Otherwise the changes look good to me, let's 
see if we can get a good run from Circle.

> Add missing tests suites to CircleCI
> 
>
> Key: CASSANDRA-18001
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18001
> Project: Cassandra
>  Issue Type: Task
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Urgent
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1-rc1, 4.1, 4.1.x, 4.2, 4.x
>
>
> Burn tests to all branches, large Python DTests (with/without vnodes), 
> cqlshlib not tested in all branches and with all jdks; Java distributed tests 
> not running with J8/J11 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-18238) Implicitly enable ALLOW FILTERING on virtual tables

2023-02-08 Thread Stefan Miklosovic (Jira)



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

Stefan Miklosovic commented on CASSANDRA-18238:
---

Thanks, I am running the CI here

[https://app.circleci.com/pipelines/github/instaclustr/cassandra/1869/workflows/b2bab08b-e19a-44bf-8388-d2298b8b9801]
[https://app.circleci.com/pipelines/github/instaclustr/cassandra/1869/workflows/be50b6dc-ee4e-48ce-963b-512ad5e88186]


> Implicitly enable ALLOW FILTERING on virtual tables
> ---
>
> Key: CASSANDRA-18238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18238
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Feature/Virtual Tables
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Ticket to track work / discussion of this thread (1)
> (1) https://lists.apache.org/thread/104fld746d6qtggq5132n3hqtjqqpkjp



--
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-18238) Implicitly enable ALLOW FILTERING on virtual tables

2023-02-08 Thread Stefan Miklosovic (Jira)



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

Stefan Miklosovic updated CASSANDRA-18238:
--
Reviewers: Aleksey Yeschenko
   Status: Review In Progress  (was: Patch Available)

> Implicitly enable ALLOW FILTERING on virtual tables
> ---
>
> Key: CASSANDRA-18238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18238
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Feature/Virtual Tables
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Ticket to track work / discussion of this thread (1)
> (1) https://lists.apache.org/thread/104fld746d6qtggq5132n3hqtjqqpkjp



--
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 (2178e5c63 -> 892d93c4e)

2023-02-08 Thread 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 2178e5c63 generate docs for 11d2d4b3
 new 892d93c4e generate docs for 11d2d4b3

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   (2178e5c63)
\
 N -- N -- N   refs/heads/asf-staging (892d93c4e)

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 4970898 -> 4970898 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

73 matches

Mail list logo