And I do
> Select * from mytable where object_id = ‘’ LIMIT 1;
>
> And since query only interested in last/latest value, will cassandra need
> to scan multiple sstables or potentially skipping tombstones data just to
> get the top of the latest data?
>
> Or is it smart enoug
I have a following table(using default sized tier compaction) that its column
get TTLed every hour(as we want to keep only the last 1 hour events)
And I do
Select * from mytable where object_id = ‘’ LIMIT 1;
And since query only interested in last/latest value, will cassandra need to
scan
and then
delete the same key in the subsequent call.
When I use the CLI list, It always returns first row due to tombstone. Is
there a way I can specify to use the limit 1 and return NOT null value.
Please let me now.
Thanks and Regards.
[default@test_keyspace] list test_kms_keys
Thanks Aaron.
How do I implement that in the row? Does row will not have any tombstones?
Please let me know.
Thanks and Regards.
--- On Tue, 1/24/12, aaron morton aa...@thelastpickle.com wrote:
From: aaron morton aa...@thelastpickle.com
Subject: Re: Return list by limit 1 which is NOT null
?
Please let me know.
Thanks and Regards.
--- On Tue, 1/24/12, aaron morton aa...@thelastpickle.com wrote:
From: aaron morton aa...@thelastpickle.com
Subject: Re: Return list by limit 1 which is NOT null
To: user@cassandra.apache.org
Date: Tuesday, January 24, 2012, 3:12 AM
No, you
HI,
I am trying to create a keys list which I will fetch the key and then delete
the same key in the subsequent call.
When I use the CLI list, It always returns first row due to tombstone. Is there
a way I can specify to use the limit 1 and return NOT null value.
Please let me now.
Thanks
