I haven't tested that specifically, but I haven't bumped into any
particular optimization that allows it to skip reading an sstable where the
entire relevant partition has been row-tombstoned. It's possible that
something like that could happen by examining min/max timestamps on
sstables, and not
I think Aaron Morton may have talked about a couple optimizations that went
into 3.0 for these use cases. I don't have a link handy (on my phone,
typing quickly) but I think it's on the last pickle blog.
On Fri, Jul 29, 2016 at 1:37 PM DuyHai Doan wrote:
> @Eric
>
> Very
@Eric
Very interesting example. But then what is the case of row (should I say
partition ?) tombstones ?
Suppose that in your example, I issued a DELETE FROM foo WHERE pk='a'
With the same SELECT statement than before, would C* be clever enough to
skip reading at all the whole partition (let's
> Sai was describing a timeout, not a failure due to the 100 K tombstone
limit from cassandra.yaml. But I still might be missing things about
tombstones.
The trouble with tombstones is not the tombstones themselves, rather it's
that Cassandra has a lot of deleted data to read through in sstables
Hi Jakub,
You can read the mail thread on how to extract clustering columns in
trigger.
https://mail-archives.apache.org/mod_mbox/cassandra-user/201605.mbox/%3CCAAam9ssYf0LvBgJ86M1Phb0ak7=jnh_acoanr8ofov4kvbr...@mail.gmail.com%3E
Extracting partition key for the operation is mentioned in the
On Fri, Jul 29, 2016 at 12:28 AM, Jacob Willoughby
wrote:
> Adjacency lists would work except the delimiter can be an arbitrary
> character...
Are you trying to build something compatible with s3, or something
that works like it? Is it necessary that the delimiter
Wanted to let everyone know that if you go to the Cassandra website
(cassandra.apache.org), you'll notice that there has been some change.
Outside
of a face lift, the main change is a much improved documentation section
(http://cassandra.apache.org/doc/). As indicated, that documentation is a