Cassandra 1.1 composite keys / columns and hierarchical queries
-
26-06-2021 - |
سؤال
So far, this is what I understand of the current Cassandra architecture:
- Super columns are not desirable any more due to performance issues.
- Composite columns (actually keys) are a good choice for indexing hierarchical keys.
- Composite columns store nested components in sorted order. There is no actual index.
I have some questions:
- Is everything I stated correct?
- Can composite columns efficiently process range queries per component (assuming logical usage)?
- Are composite columns suited to extremely large numbers of rows while still yielding rapid query results (considering they are not an index per se)?
- Can secondary indexes be created against composite columns. If yes, can range queries be efficiently performed?
Thanks in advance.
المحلول
- Yes
- Yes
- Yes, because they are sorted on write just like any other column
- Yes, secondaries can be created against composites as of 1.2. See this JIRA ticket
لا تنتمي إلى StackOverflow