This happened with version 3.11.10.
We were analyzing impact until now as this happened only on our production
systems. There was probably not enough concurrency on our staging environments
so it did not happen there.
We will start to write a reproducer and file an issue afterwards.
Thanks for
If you don't have an explicit goal of dropping compact storage, it's not necessary to as a
prerequisite to upgrading to 4.x+. Development community members recognized that
introducing mandatory schema changes as a prerequisite to upgrading to 4.x would increase
operator + user overhead and limi
This sounds a lot like cassandra-13004 which was fixed, but broke data being
read-repaired during an alter statement
I suspect it’s not actually that same bug, but may be close/related.
Reproducing it reliably would be a huge help.
- Jeff
> On May 7, 2024, at 1:50 AM, Matthias Pfau via user
patterns, I encourage them to use other technologies. Otherwise the pain
will be great.
Sean Durity
From: Erick Ramirez
Sent: Wednesday, February 19, 2020 6:58 PM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Null values in sasi indexed column
Rahul, in my opinion SASI is an experimental
Rahul, in my opinion SASI is an experimental feature and isn't ready for
primetime yet. It has some advantages over secondary indexes but if it were
me, I'd stick with native secondary indexes. But test, test and test so you
can make an informed decision on what works for your use case. Cheers!
Er
Ok so eventually the row which has only the initial key will disappear?
-Original Message-
From: Tristan Seligmann [mailto:mithra...@mithrandi.net]
Sent: woensdag 27 februari 2013 11:02
To: user@cassandra.apache.org
Subject: Re: NULL values
Cassandra only stores keys, not columns
W dniu 27.02.2013 10:57, Marco Matarazzo pisze:> You may also be
interested in this:
>
> https://issues.apache.org/jira/browse/CASSANDRA-3783
CASSANDRA-3783 might not be the case here. The question is about using
null in SELECT statements, which will require modifications in secondary
indexes
ing
> will be removed except the key.
>
> How can I determine the keys that have no additional columns and delete
> them?
>
>
>
>
>
> From: Alain RODRIGUEZ [mailto:arodr...@gmail.com]
> Sent: woensdag 27 februari 2013 10:35
> To: user@cassandra.apache.org
> Subjec
?
From: Alain RODRIGUEZ [mailto:arodr...@gmail.com]
Sent: woensdag 27 februari 2013 10:35
To: user@cassandra.apache.org
Subject: Re: NULL values
Cassandra (C*) has no NULL values. C* is column schemaless, meaning you can
have different columns on each row of the same ColumnFamily (CF).
So if you
You may also be interested in this:
https://issues.apache.org/jira/browse/CASSANDRA-3783
Also, I *guess* that a deleted column takes some (very small?) space with its
tombstone, until it's removed. But I leave the details to someone else, as I'm
definitely not an expert.
Il giorno 27/feb/20
Cassandra (C*) has no NULL values. C* is column schemaless, meaning you can
have different columns on each row of the same ColumnFamily (CF).
So if you want to check if a certain column is NULL for a row, you just
check if it exist. By the way, you can store a column with a name and no
value (empt
11 matches
Mail list logo
