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
Hi there,
we just ran drop compact storage in order to prepare for the upgrade to version
4.
We observed that column values have been written as null, if they where
inserted while the drop compact storage statement was running. This just
happened for the couple seconds the drop compact storage
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
Hello,
We have a requirement to query based on a column which is not part of
priamry key. We are planning to create sasi index . Before creating index
want to confirm how would be index behaviour if it has 10% of data will be
null and data distribution across the nodes 6-6 nodes wth RF 3? Please
g boot Java.
>
> While we are trying to insert data into cassandra , java by default
> inserts null values in cassandra tables which is causing huge tombstones.
>
>
> Instead of changing code in java to insert null values, can you control
> anywhere at driver level ?
>
>
> Thanks,
>
> Buchi Babu
>
>
ult inserts
> null values in cassandra tables which is causing huge tombstones.
>
>
>
> Instead of changing code in java to insert null values, can you control
> anywhere at driver level ?
>
>
>
> Thanks,
>
> Buchi Babu
We are using DSE 5.1.0 & Spring boot Java.
While we are trying to insert data into cassandra , java by default inserts
null values in cassandra tables which is causing huge tombstones.
Instead of changing code in java to insert null values, can you control
anywhere at driver level ?
Th
nd I have to reset them. I just need to
>>>>>>> store
>>>>>>> the state as it artived from Kafka, there might already be an event for
>>>>>>> this happening saved before, or maybe this is the first one.
>>>>>>>
>>>>>
orrect that inserting null creates a tombstone.
>
> Can you only insert the columns that actually have new values? Just skip the
> columns with no information. (Make the insert generator a bit smarter.)
>
> Create table happening (id text primary key, event text, a text, b text, c
ed statements for
>>>>>>> each combination of set / unset values in large INSERT/UPDATE statements
>>>>>>> may be prohibitive.
>>>>>>>
>>>>>>> Instead, you can look into driver level support for UNSET values.
>>>>>
ndra 2.2 or later IIRC.
>>>>>>
>>>>>> See:
>>>>>> Java Driver:
>>>>>> https://docs.datastax.com/en/developer/java-driver/3.0/manual/statements/prepared/#parameters-and-binding
>>>>>> Python Driver:
>>>&
018 at 3:21 PM Durity, Sean R <
>>>>> sean_r_dur...@homedepot.com> wrote:
>>>>>
>>>>>> You say the events are incremental updates. I am interpreting this to
>>>>>> mean only some columns are updated. Others should keep their origina
ed. Others should keep their original
>>>>> values.
>>>>>
>>>>> You are correct that inserting null creates a tombstone.
>>>>>
>>>>> Can you only insert the columns that actually have new values? Just
>>>>> skip the
>>>>
>>>> Can you only insert the columns that actually have new values? Just
>>>> skip the columns with no information. (Make the insert generator a bit
>>>> smarter.)
>>>>
>>>> Create table happening (id text primary key, event text, a
Make the insert generator a bit smarter.)
>>>
>>> Create table happening (id text primary key, event text, a text, b text,
>>> c text);
>>> Insert into table happening (id, event, a, b, c) values
>>> ("MainEvent","The most complete i
t; Insert into table happening (id, event, a, b, c) values ("MainEvent","The
>> most complete info we have right now","Priceless","10 pm","Grand Ballroom");
>> -- b changes
>> Insert into happening (id, b) values ("MainEvent",&q
;
>
>
> Sean Durity
>
>
> -Original Message-
> From: Tomas Bartalos
> Sent: Thursday, December 27, 2018 9:27 AM
> To: user@cassandra.apache.org
> Subject: [EXTERNAL] Howto avoid tombstones when inserting NULL values
>
> Hello,
>
> I’d start with
quot;10 pm","Grand Ballroom");
-- b changes
Insert into happening (id, b) values ("MainEvent","9:30 pm");
Sean Durity
-Original Message-
From: Tomas Bartalos
Sent: Thursday, December 27, 2018 9:27 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL
tes a ... tombstone.
I was hoping there could be an option to tell Cassandra not to be so space
effective and store “unset" info without generating tombstones.
Something similar to inserting empty strings instead of null values:
CREATE TABLE happening (id text PRIMARY KEY, event text);
insert into hap
It doesn't work because of the white space. By default the NULL value is an
empty string, extra white spaces are not trimmed automatically.
This should work:
ce98d62a-3666-4d3a-ae2f-df315ad448aa,Jonsson,Malcom,,2001-01-19
17:55:17+
You can change the string representing missing values with t
Hi
I am trying to copy a file of CSV data into a table
But I get an error since sometimes one of the columns (which is a UUID) is empty
Is this a bug or what am I missing?
Here is how it looks like
Table
id uuid,
lastname text,
firstname text,
address_id uuid,
dateofbirth time
: user@cassandra.apache.org
Subject: Re: Inserting null values
I agree that inserting null is not as good as not inserting that column at all
when you have confidence that you are not shadowing any underlying data. But
pragmatically speaking it really doesn't sound like a small number of
incid
DRA-3442 takes over) is going to have any performance impact either
in your query patterns or in compaction in any practical sense.
If INSERT of null values is problematic for small portions of your data,
then it stands to reason that an INSERT option containing an instruction to
prevent tombstone
On Wed, Apr 29, 2015 at 9:16 AM, Eric Stevens wrote:
> In the end, inserting a tombstone into a non-clustered column shouldn't be
> appreciably worse (if it is at all) than inserting a value instead. Or am
> I missing something here?
>
There's thresholds (log messages, etc.) which operate on to
se the Insert query builder (
>>>> *com.datastax.driver.core.querybuilder.Insert*) which allows me to
>>>> dynamically insert as many or as few columns as I need, and doesn’t require
>>>> multiple prepared statements. Then, I will look at Ali’s suggestion – I
>>>> w
IfNotNull’ and pump all
>>> my values into that, which will then filter out the ones that are null.
>>> Should keep the code nice and neat – I will feed back if I find any
>>> problems with this approach (but please jump in if you have already spotted
>>> any :)).
>>>
‘addToInsertIfNotNull’ and pump all
>> my values into that, which will then filter out the ones that are null.
>> Should keep the code nice and neat – I will feed back if I find any
>> problems with this approach (but please jump in if you have already spotted
>> any :)).
&g
at – I will feed back if I find any
> problems with this approach (but please jump in if you have already spotted
> any :)).
>
>
>
> Thanks!
>
> Matt
>
>
>
> *From:* Robert Wille [mailto:rwi...@fold3.com]
> *Sent:* 29 April 2015 15:16
> *To:* user@cassandra.ap
:)).
Thanks!
Matt
*From:* Robert Wille [mailto:rwi...@fold3.com]
*Sent:* 29 April 2015 15:16
*To:* user@cassandra.apache.org
*Subject:* Re: Inserting null values
I’ve come across the same thing. I have a table with at least half a dozen
columns that could be null, in any combination. Having a
I’ve come across the same thing. I have a table with at least half a dozen
columns that could be null, in any combination. Having a prepared statement for
each permutation of null columns just isn’t going to happen. I don’t want to
build custom queries each time because I have a really cool syst
The problem of NULL insert is already solved long time ago with Insert
Strategy in Achilles:
https://github.com/doanduyhai/Achilles/wiki/Insert-Strategy
However, it's nice to see there will be a flag on the protocol side to
handle this problem
On Wed, Apr 29, 2015 at 2:27 PM, Ali Akhtar wrot
Have you considered adding a 'toSafe' method which checks if the item is
null, and if so, returns a default value? E.g String too = safe(bar, ""); .
On Apr 29, 2015 3:14 PM, "Matthew Johnson" wrote:
> Hi all,
>
>
>
> I have some fields that I am storing into Cassandra, but some of them
> could be
Inserting a null value creates a tombstone. Tombstones can have major
performance implications.
You can see the tombstones using sstable2json.
If you have a small number of records with null values this seems OK, otherwise
I recommend using the QueryBuilder (for Java clients) and waiting for
Hi all,
I have some fields that I am storing into Cassandra, but some of them could
be null at any given point. As there are quite a lot of them, it makes the
code much more readable if I don’t check each one for null before adding it
to the INSERT.
I can see a few Jiras around CQL 3 supporti
> I thought that C* had no null values... I use a lot of CF in which only the
> columns name are filled up and I request a range of column to see which
> references (like 1228#16866) exists. So I would like those column to simply
> disappear from the table.
Cassandra does not store
n.SizeTieredCompactionStrategy'
and caching = 'KEYS_ONLY'
and bloom_filter_fp_chance = 0.01
and compression_options = {'sstable_compression' :
'org.apache.cassandra.io.compress.SnappyCompressor'};
"The output looks correct to me. CQL table return values, in
---+--__+--+--__-+__--
>> null | null | null |
>> |
>>
>>
>>This is quite annoying since my app thinks that I have 5 columns
>>there
>>when I should have 2 only.
>>
>>I first thought that this was a visible marker of tombstones but
>>they
>>didn't vanish after a major compaction.
>>
>>How can I get rid of these null/ghost columns and why does it
>>happen ?
>>
>>
>>I do something similar but I don't see null values. Could you please
>>post the code where you delete the columns?
>>
>>Sorin
>>
>>
>
s
there
when I should have 2 only.
I first thought that this was a visible marker of tombstones but
they
didn't vanish after a major compaction.
How can I get rid of these null/ghost columns and why does it
happen ?
I do something similar but I don't see null values. Could you please
post the code where you delete the columns?
Sorin
null | null | null |
>>> |
>>>
>>>
>>> This is quite annoying since my app thinks that I have 5 columns there
>>> when I should have 2 only.
>>>
>>> I first thought that this was a visible marker of tombstones but they
>>> didn't vanish after a major compaction.
>>>
>>> How can I get rid of these null/ghost columns and why does it happen ?
>>>
>>
>> I do something similar but I don't see null values. Could you please post
>> the code where you delete the columns?
>>
>> Sorin
>>
>>
>
|
>>
>>
>> This is quite annoying since my app thinks that I have 5 columns there
>> when I should have 2 only.
>>
>> I first thought that this was a visible marker of tombstones but they
>> didn't vanish after a major compaction.
>>
>> How can I get rid of these null/ghost columns and why does it happen ?
>>
>
> I do something similar but I don't see null values. Could you please post
> the code where you delete the columns?
>
> Sorin
>
>
thing similar but I don't see null values. Could you please
post the code where you delete the columns?
Sorin
Hi, I tried to delete some columns using cql2 as well as thrift on C*1.2.2
and instead of being unreachable, deleted columns have a null value.
I am using no value in this CF, the only information I use is the existence
of the column. So when I select all the column for a given key I have the
foll
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
value). This empty value doesn't take any disk space AFAIK.
About the TTL, their point is precisely to keep them for a predefined time. C*
delete them on without any action needed by a client, it's an internal work.
Alain
2013/2/27 Sloot, Hans-Peter
Hi,
How does Cassandra handle NULL
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
rno 27/feb/2013, alle ore 10:35, Alain RODRIGUEZ ha
scritto:
> 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 ch
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
Hi,
How does Cassandra handle NULL values?
I want to know how I can see rows where a certain column has no values.
For example if I set the TTL for columns is it possible to select rows where
the ttl has expired for deletion.
Regards Hans-Peter
Dit bericht is vertrouwelijk en kan geheime
52 matches
Mail list logo
