know your data in advance. know your queries, you must aware what all queries are going to be executed on your data. Hence, find below partition per query - ideal partition+ per query - acceptable ex. find movies that match one of multiple genres table scan - anti-pattern multi-table - anti-pattern ex. retrieve all data in a database nest data - denormalization organizes multiple entities into a single partition supports partition per query access mechanisms clustering columns collection columns user-defined type columns duplicate data - denormalization better than join join on write
Question : In Cassandra, following scenarios can be considered as an ideal.
To fetch the data, Query needs to access all the partitions in a table, to retrieve results.
1. True 2. False
Correct Answer : Get Lastest Questions and Answer : Explanation: Its not at all correct, it is considered worst design in Cassandra. Ideal case is your query must read one partition and return the required result.
Question : Cassandra prefer space compare to time , while designing data modeling? 1. True 2. False
Correct Answer : Get Lastest Questions and Answer : Explanation: Yes, in Cassandra database , it is ok you duplicate data and acquire more space. Because, query response time is more important the space and data join will be completely avoided.