Are client joins recommended in Cassandra Since query joins are not supported ?
Bringing together the Apache Cassandra experts from the community and DataStax.
Want to learn? Have a question? Want to share your expertise? You are in the right place!
Not sure where to begin? Getting Started
Queries which require joins are not recommended in Cassandra because they don't perform or scale well. If you have to do a JOIN to satisfy an application request, it implies that you didn't get your data model right.
You need to design your data model such that each app query maps to one table. If you have to do a client-side JOIN it means that you had to query the database multiple times to get the data. It may work for you but it will never perform as well as making a single read request to one table. Cheers!
6 People are following this question.
How can I minimise the impact of a full table scan running Spark against Cassandra?
Has anyone done a migration from Marklogic to Cassandra?
Why are results inconsistent when reading with consistency ALL compared to ONE?
COPY FROM command returns error "field larger than field limit (131072)"
Getting key cache error on startup, "UTFDataFormatException: malformed input around byte 10"
DataStax Enterprise is powered by the best distribution of Apache Cassandra ™
© 2022 DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.
Privacy Policy Terms of Use