Re: Comment on query performance

Thanks DuyHai once again :-) On Thu, Dec 29, 2016 at 3:35 PM, DuyHai Doan wrote: > No full table scan because you specify all the partition key columns in > your WHERE clause. > > On Thu, Dec 29, 2016 at 11:02 AM, Ashutosh Dhundhara < > ashutoshdhundh...@yahoo.com> wrote:

Re: Comment on query performance

No full table scan because you specify all the partition key columns in your WHERE clause. On Thu, Dec 29, 2016 at 11:02 AM, Ashutosh Dhundhara < ashutoshdhundh...@yahoo.com> wrote: > Thanks DuyHai. > > One more thing, is it going to be a full table scan across all the nodes > in cluster? > > On

Re: Comment on query performance

Thanks DuyHai. One more thing, is it going to be a full table scan across all the nodes in cluster? On Thu, Dec 29, 2016 at 3:30 PM, DuyHai Doan wrote: > In your case, ALLOW FILTERING will require Cassandra to scan linearly on > disk and fetch all the partition data into

Re: Comment on query performance

In your case, ALLOW FILTERING will require Cassandra to scan linearly on disk and fetch all the partition data into memory so the performance depends on how "large" your partition is. For small partitions it should be fine. On Thu, Dec 29, 2016 at 10:00 AM, Ashutosh Dhundhara <

Comment on query performance

Hi All, I have a table like this: CREATE TABLE IF NOT EXISTS Posts ( idObject int, objectType text, idParent int, id int, idResolution int, PRIMARY KEY ((idObject, objectType, idParent), id) ); Now have a look at the following query: SELECT * FROM POSTS WHERE idobject =