Is doing full scan a antipattern in cassandra , what about multi-table , is that anti pattern ?
This question was
closed
by
Erick Ramirez for the following reason: The question is answered, right answer was accepted
@ashok.dcosta_187920, Yes, doing a full table scan is a definite anti-pattern and is not efficient for a distributed NoSQL database like Apache Cassandra™. Having said that, it might be okay to perform a scan within a partition based on circumstances. I am going to have you refer to the below resources for additional context,
- https://academy.datastax.com/units/22024-data-model-anti-patterns-practical-application-data-modeling-apache-cassandra
- https://www.datastax.com/blog/2013/04/cassandra-anti-patterns-queues-and-queue-datasets
- https://nblair.github.io/2017/02/16/cassandra-full-table-scan/
- https://www.datastax.com/blog/2015/03/how-do-joins-apache-cassandratm-and-datastax-enterprise
- http://www.batey.info/cassandra-anti-pattern-distributed.html
- https://community.datastax.com/answers/4306/view.html
Could you update your original question elaborating what do you mean by "multi-table" for additional clarity? Alternatively, you can accept this answer if you're good.
7 People are following this question.
