Most of what you describe sounds pretty DSE specific so I suspect your best
source for answers will be datastax
There were bugs in some versions of Cassandra that caused corruption during a
few milliseconds race of ALTER TABLE, and if you’re not using compression with
CRC checking enabled,
Hi,
I am observing a very strange behavior in our cluster. Metadata is being
prefixed in some rows.
This metadata cannot be sent by application primarily because application
writing to C* will not have this data,
and also applications use custom Java objects and this metadata doesn’t fall
Soft delete = logical delete - which is an update.
An update doesnt create a tombstone . It appends to the sstable,and when they
are compacted, the latest write is what is seen as the definitive data.
A tombstone by definition is an update which tells C* to remove the value that
was there
Thanks Affan Syed! :)
On Wed, 30 May 2018 at 11:07 sujeet jog wrote:
> Thanks Jeff & Jonathan,
>
>
> On Tue, May 29, 2018 at 10:41 PM, Jonathan Haddad
> wrote:
>
>> I wrote a post on this topic a while ago, might be worth reading over:
>>
>>
Oh, thanks Elliott for the explanation! I had no idea about that little tidbit
concerning ctime. Now it all makes sense!
- Max
> On May 28, 2018, at 10:24 pm, Elliott Sims wrote:
>
> Unix timestamps are a bit odd. "mtime/Modify" is file changes,
> "ctime/Change/(sometimes called create)"
Thanks Jeff & Jonathan,
On Tue, May 29, 2018 at 10:41 PM, Jonathan Haddad wrote:
> I wrote a post on this topic a while ago, might be worth reading over:
> http://thelastpickle.com/blog/2017/08/02/time-series-data-
> modeling-massive-scale.html
> On Tue, May 29, 2018 at 8:02 AM Jeff Jirsa
