I would consider building a lookup table instead. Something like: Create table new_lookup ( new-lookup-partition text, existing-key text PRIMARY KEY (new-lookup-partition) )
For me, these are easier to understand and reason through for Cassandra performance and availability. I would use this approach for up to 3 or 4 different lookup patterns. If it got to be more than that, I would be using DSE Search/SOLR. Just be warned, I have seen teams asking for these kind of options just because they are guessing the access patterns they want. If they cannot identify their access patterns, I encourage them to use other technologies. Otherwise the pain will be great. Sean Durity From: Erick Ramirez <erick.rami...@datastax.com> Sent: Wednesday, February 19, 2020 6:58 PM To: user@cassandra.apache.org Subject: [EXTERNAL] Re: Null values in sasi indexed column Rahul, in my opinion SASI is an experimental feature and isn't ready for primetime yet. It has some advantages over secondary indexes but if it were me, I'd stick with native secondary indexes. But test, test and test so you can make an informed decision on what works for your use case. Cheers! Erick Ramirez | Developer Relations erick.rami...@datastax.com<mailto:erick.rami...@datastax.com> | datastax.com [datastax.com]<https://urldefense.com/v3/__http:/www.datastax.com__;!!M-nmYVHPHQ!asu__hQFnCvnU3uNl5uiFPZnWYHOzeBxKlbdKVt3srbVl98JM13d_KFSKw2GzuPScqrruo4$> [https://lh4.googleusercontent.com/GivrE4j_1bWvQnZP67Zpa5eomhEeKON-X6kFljLxDatL7QPL_aineBJzM_rXzrqNQkENnZt7KyXLROlLTHuMM3OFNlZ8IrW-adjXKRiD7ojG6OjjFoLio3HbKwVwXt7_Qna02H8I][linkedin.com]<https://urldefense.com/v3/__https:/www.linkedin.com/company/datastax__;!!M-nmYVHPHQ!asu__hQFnCvnU3uNl5uiFPZnWYHOzeBxKlbdKVt3srbVl98JM13d_KFSKw2GzuPSNVaCZrI$> [https://lh6.googleusercontent.com/0juOULc-Qhs6qzVY5mN0tzIMZ4w17Jv2fiV5xboewGBH0SFiEwV0uPTO_W5OwGr0jCOXmoJLBq1aNLsr1oChLMgJNvNt1e4bHxO2KJUK-iagQ4jw9SiuTMmpktVSfygdLS_vQe6v] [facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/datastax__;!!M-nmYVHPHQ!asu__hQFnCvnU3uNl5uiFPZnWYHOzeBxKlbdKVt3srbVl98JM13d_KFSKw2GzuPSFFie4Ss$> [https://lh5.googleusercontent.com/IdGeRVBWRf50wPOny50XQ3O0rtkebOh8e2D9DCanVuy-f3a-wpI3PpQJnGtVFL5aHPOwm4hsginvqhQfTXnP_XT_8fuQWS6Mt0KKRFkRANDhS22T3UiXpGfBkMHJxy48ZQJFaXsZ] [twitter.com]<https://urldefense.com/v3/__https:/twitter.com/datastax__;!!M-nmYVHPHQ!asu__hQFnCvnU3uNl5uiFPZnWYHOzeBxKlbdKVt3srbVl98JM13d_KFSKw2GzuPS-X7gUB4$> [https://lh4.googleusercontent.com/PbPMGIQsTltjGio5a_e7dp35l6ysZMG_ib69EUHmIvbXHXzRkrNKNMfMR8uwSS1AAoQaG6xn96PH-L1wLQE8FBLSjN_g10Q8y0n1Tp5SYtKO3L1JDN_T73HgSSQJayqn7YMTFXn-] [feeds.feedburner.com]<https://urldefense.com/v3/__http:/feeds.feedburner.com/datastax__;!!M-nmYVHPHQ!asu__hQFnCvnU3uNl5uiFPZnWYHOzeBxKlbdKVt3srbVl98JM13d_KFSKw2GzuPSjOdKxH8$> [https://lh5.googleusercontent.com/Rnk5QTWTovfX-z1uRr0FQjt17VnMURyI8rDCi4rTJUY5lnX-QevuQWTFa39GS9fJCMqP0SXSkCLtKf064p0-59f80PmA2hZRqGRFFOlZlbJzXv2EevvdbeKYFq4s9g5zzP54KKQB] [github.com]<https://urldefense.com/v3/__https:/github.com/datastax/__;!!M-nmYVHPHQ!asu__hQFnCvnU3uNl5uiFPZnWYHOzeBxKlbdKVt3srbVl98JM13d_KFSKw2GzuPSC70At1g$> [https://datastax.com/sites/default/files/content/graphics/email/datastax-email-signature-2019.jpg][datastax.com]<https://urldefense.com/v3/__https:/www.datastax.com/accelerate__;!!M-nmYVHPHQ!asu__hQFnCvnU3uNl5uiFPZnWYHOzeBxKlbdKVt3srbVl98JM13d_KFSKw2GzuPS80UlBAY$> ________________________________ The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment.