Very good video series, I love that you took time to illustrate the different examples. I have a question.. instead of creating different tables with the cluster key of ascending/descending order.. is it possible for cassandra to do SQL like queries where SELECT * FROM simple_temp_v2 ORDER BY time_created ASC Cheers
You can, if time_created is part of the clustering key. Also, the sort order has to be the same as the cluster key order you gave when creating the table. Additionally, your query needs a WHERE clause on a partition key AFAIK. Otherwise, Cassandra won't be happy needing to sort across partitions.
Best explanation sir I am stuck on a table which is branch_by_region_country_city but then when I saw this video about compound partition key I understand how to fix my problem , really helppp sir Thanks
Unorganized so wasting time unnecessarily. Doesn't explain why one may need a compound partitioning key. Doesn't explain the impact of clustering keys (i.e., in WHERE clause, although effect in ORDER BY clause is kinda implicitly mentioned).
Hi! Appreciate the feedback. I thought of explaining those but the video was getting too long. I am still learning what's the best way to present the content. Thanks for your patience!
This happens to be the simplest Cassandra DB tutorial I've watched so far, thank you !
Glad it was helpful! I will start posting again soon, so please let me know what type of content interests you the most.
Best explanation for Partition keys. I have spent a lot if time trying to find this. Thanks!!
So glad it helped you understand better : )
Very good video series, I love that you took time to illustrate the different examples.
I have a question.. instead of creating different tables with the cluster key of ascending/descending order.. is it possible for cassandra to do SQL like queries where
SELECT * FROM simple_temp_v2 ORDER BY time_created ASC
Cheers
You can, if time_created is part of the clustering key. Also, the sort order has to be the same as the cluster key order you gave when creating the table.
Additionally, your query needs a WHERE clause on a partition key AFAIK. Otherwise, Cassandra won't be happy needing to sort across partitions.
@@irtizahafiz oh yes.. thanks for pointing that out! would have been a very expensive query without including the partition key!
Excellent and precise explanation
nice and simple, Thanks so much
Great explanation !
Thank you!
Very nice explanation ...!
Best explanation sir I am stuck on a table which is branch_by_region_country_city but then when I saw this video about compound partition key I understand how to fix my problem , really helppp sir Thanks
Thank you! I will start posting again soon, so please let me know what type of content interests you the most.
Thanks for the explanation, very helpful.
wow! happy learning!! thanks
Your videos are just amazing
Thank you so much 😀
Awsome content keep going
Appreciate it!
Great explanation
Glad it was helpful!
great explaination👌
20:26 I think you meant to type simple_temperature_v3.
so why they call it as cluster key and not a sort key?
LOL that's a good question.
very good video
Thanks!
Good stuff man
Thank you for watching!
Unorganized so wasting time unnecessarily. Doesn't explain why one may need a compound partitioning key. Doesn't explain the impact of clustering keys (i.e., in WHERE clause, although effect in ORDER BY clause is kinda implicitly mentioned).
Hi! Appreciate the feedback.
I thought of explaining those but the video was getting too long. I am still learning what's the best way to present the content. Thanks for your patience!