or “unset” support with JSON values and
> omitted columns so you can control is omitted columns have a “null” value or
> an “unset” value.
>
>
>
>
> From: Ralf Steppacher [mailto:ralf.viva...@gmail.com]
> Sent: Thursday, March 24, 2016 11:36 AM
> To: user@cassandra.a
Ralf,
Thank YOU very much Ralf. You are the first one who could finally shed some
light on something I observed, but I could not put my finger on what exactly is
causing my Tombstones.
I cannot judge your method for evaluating the amount of tombstone. It seems
valid to me.
Jean
On 24 Mar 2016,
AM
To: user@cassandra.apache.org
Subject: Re: Large number of tombstones without delete or update
How does this improvement apply to inserting JSON? The prepared statement has
exactly one parameter and it is always bound to the JSON message:
INSERT INTO event_by_patient_timestamp JSON ?
How w
Jean,
yes, I am using the native protocol v4 (auto-negotiated between java driver
3.0.0 and C* 2.2.4, verified by logging
cluster.getConfiguration().getProtocolOptions().getProtocolVersion() ).
My first approach for testing for tombstones was “brute force”. Add records and
soon enough (after a
to:ralf.viva...@gmail.com]
Sent: Thursday, March 24, 2016 11:19 AM
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: Re: Large number of tombstones without delete or update
I did some more tests with my particular schema/message structure:
A null text field inside a UDT insta
> To: user@cassandra.apache.org
> Subject: Re: Large number of tombstones without delete or update
>
> I did some more tests with my particular schema/message structure:
>
> A null text field inside a UDT instance does NOT yield tombstones.
> A null map does NOT yield tom
rated)."
From: Ralf Steppacher [mailto:ralf.viva...@gmail.com]
Sent: Thursday, March 24, 2016 11:19 AM
To: user@cassandra.apache.org
Subject: Re: Large number of tombstones without delete or update
I did some more tests with my particular schema/message structure:
A null text field inside a U
I did some more tests with my particular schema/message structure:
A null text field inside a UDT instance does NOT yield tombstones.
A null map does NOT yield tombstones.
A null text field does yield tombstones.
Ralf
> On 24.03.2016, at 09:42, Ralf Steppacher wrote:
>
> I can confirm that if
I can confirm that if I send JSON messages that always cover all schema fields
the tombstone issue is not reported by Cassandra.
So, is there a way to work around this issue other than to always populate
every column of the schema with every insert? That would be a pain in the
backside, really.
Same for me. Only inserts not replacing old records.
On 24 Mar,2016, at 07:42, Ralf Steppacher
mailto:ralf.viva...@gmail.com>> wrote:
Eric,
I am writing the whole record in a single INSERT INTO ... JSON. I am not
"insert-updating" over an existing record nor do I run any UPDATE statements.
R
Eric,
I am writing the whole record in a single INSERT INTO … JSON. I am not
"insert-updating" over an existing record nor do I run any UPDATE statements.
Ralf
> On 24.03.2016, at 01:47, Eric Stevens wrote:
>
> In addition to writing null values acting as tombstones, also INSERTing a
> coll
Hi,
I also have loads of tombstones while only inserting new rows without ever
deleting rows.
My rows contain null columns and also collections.
How can I avoid the creation of these tombstones?
Thanks for your help.
On 24 Mar,2016, at 02:08, Steve Robenalt
mailto:sroben...@highwire.org>> wr
Yes. In this particular test there are four fields null., one of them in a UDT
instance.
I don’t set fields to null explicitly. I insert as JSON and those fields are
not in the particular message. But when I select the record the fields are
shown as null.
In real live almost all fields are opti
Hi Henry,
Since new values are written without checking for previous values, the only
way to assure that a nulled column blocks a previously valid one is to
write a tombstone to occlude whatever value might have been present. I
believe there are some recent changes as to the handling of null value
What is the reason for the tombstone for a brand new insert? Do the fields
get written as a whole (both nulls and non-nulls?
I understand the rationale for tombstones for deletes and updates but it
does not make sense for an insert (I am trying to make sense of it). I
understand Cassandra writes t
In addition to writing null values acting as tombstones, also INSERTing a
collection (or UPDATE where you set the collection rather than append to
it) are also operations which will create tombstones.
On Wed, Mar 23, 2016 at 12:09 PM Robert Coli wrote:
> On Wed, Mar 23, 2016 at 9:50 AM, Ralf Ste
On Wed, Mar 23, 2016 at 9:50 AM, Ralf Steppacher
wrote:
> How come I end up with that large a number of tombstones?
>
Are you inserting NULLs?
=Rob
Hi all,
I started running “stress tests” against my application which writes event data
to a local single-node Cassandra cluster (C* v2.2.4). After inserting a couple
thousand rows (all for the same partition key) I am starting to get warnings in
the C* log informing me about large numbers of t
No worries! They're a data type that was introduced in 1.2:
http://www.datastax.com/dev/blog/cql3_collections
On Fri, Jan 2, 2015 at 12:07 PM, Nikolay Mihaylov wrote:
> Hi Tyler,
>
> sorry for very stupid question - what is a collection ?
>
> Nick
>
> On Wed, Dec 31, 2014 at 6:27 PM, Tyler Hobb
Hi Tyler,
sorry for very stupid question - what is a collection ?
Nick
On Wed, Dec 31, 2014 at 6:27 PM, Tyler Hobbs wrote:
> Overwriting an entire collection also results in a tombstone being
> inserted.
>
> On Wed, Dec 24, 2014 at 7:09 AM, Ryan Svihla wrote:
>
>> You should probably ask on t
Overwriting an entire collection also results in a tombstone being inserted.
On Wed, Dec 24, 2014 at 7:09 AM, Ryan Svihla wrote:
> You should probably ask on the Cassandra user mailling list.
>
> However, TTL is the only other case I can think of.
>
> On Tue, Dec 23, 2014 at 1:36 PM, Davide D'Ag
You should probably ask on the Cassandra user mailling list.
However, TTL is the only other case I can think of.
On Tue, Dec 23, 2014 at 1:36 PM, Davide D'Agostino wrote:
> Hi there,
>
> Following this:
> https://groups.google.com/a/lists.datastax.com/forum/#!searchin/java-driver-user/tombstone
22 matches
Mail list logo
