This is an old issue with sstable2json
https://issues.apache.org/jira/browse/CASSANDRA-4054
Internally the tomstone is associated with the o.a.c.db.AbstractColumnContainer
see o.a.c.db.RowMutation.delete() to see how a row level delete works.
Cheers
-
Aaron Morton
Freelance D
*I was taking a look at tombstones stored at SSTable and I noticed that if
I perform a key deletion, the tombstone doesn’t have any timestamp, he has
this appearance:
“key”:[ ]
In all the other deletions granularities the tombstone have a
timestamp.Without this information seems to be not possible
> -Is there any other way to stract the contect of SSTable, writing a
> java program for example instead of using sstable2json?
Look at the code in sstale2json and copy it :)
> -I tried to get tombstons using the thrift API, but seems to be not
> possible, is it right? When I try, the program thro
I have further questions:
-Is there any other way to stract the contect of SSTable, writing a
java program for example instead of using sstable2json?
-I tried to get tombstons using the thrift API, but seems to be not
possible, is it right? When I try, the program throws an exception.
thanks in ad
> Ok... it's really strange to me that Cassandra doesn't support data
> versioning cause all of other key-value databases support it (at least
> those who I know).
You can design it into your data model if you need it.
> I have one remaining question:
> -in the case that I have more than 1 SSTabl
Ok... it's really strange to me that Cassandra doesn't support data
versioning cause all of other key-value databases support it (at least
those who I know).
I have one remaining question:
-in the case that I have more than 1 SSTable in the disk for the same
column but with different data versions
You're in for a world of hurt going down that rabbit hole. If you truely
want version data then you should think about changing your keying to
perhaps be a composite key where key is of form
NaturalKey/VersionId
Or if you want the versioning at the column level, use composite columns
with Col
That was very helpfull, thank you very much!
I still have some questions:
-it is possible to make Cassandra keep old value data after flushing?
The same question for the memTable, before flushing. Seems to me that
when I update some tuple, the old data will be overwrited in memTable,
even before f
Cassandra does not provide access to multiple versions of the same column. It
is essentially implementation detail.
All mutations are written to the commit log in a binary format, see the
o.a.c.db.RowMutation.getSerializedBuffer() (If you want to tail it for analysis
you may want to change com
Yes, I need this information just for academic purposes.
So, to read old data values, I tried to open the Commitlog using tail
-f and also the log files viewer of Ubuntu, but I can not see many
informations inside of the log!
Is there any other way to open this log? I didn't find any Cassandra
API
After compaciton, the old version data will gone!
zhangcheng2
From: Felipe Schmidt
Date: 2012-05-14 05:33
To: user
Subject: Retrieving old data version for a given row
I'm trying to retrieve old data version for some row but it seems not
be possible. I'm a beginner with Cassandra and the uniq
The only way you could get the old value for a column would be to insert
the column value, then flush, then insert the new column, then before
compaction look at the old sstable.
If you insert the value twice in a row without a flush, the old value is
gone, as it only exists in memtables (and
12 matches
Mail list logo
