data modeling - Choosing a partition key for a Cassandra table -- how many is too many partitions? -


i have application 'natural' partition key cassandra table seems 'customer'. primary way want query data, data distribution, etc.

but if there on 1 million customers, many different partitions?

should choose partition key results in smaller number of partition keys?

i've looked @ number of related questions on topic none seem address particular point.

but if there on 1 million customers, many different partitions?

no. murmur3partitioner can handle 2^64 (-2^63 +2^63) partitions. cassandra designed @ storing large amounts of data , retrieving partition key. there restrictions on number of columns within partition (2 billion), total number of partitions think you'll fine have.

should choose partition key results in smaller number of partition keys?

definitely not. cause partitions grow big, and/or develop "hot spots" in cluster.

the main task behind picking partition key, find 1 (both) offers data distribution in cluster, , matches query patterns. , i'm reading, sounds have done that.


Comments

Popular posts from this blog

Magento/PHP - Get phones on all members in a customer group -

php - Bypass Geo Redirect for specific directories -

php - .htaccess mod_rewrite for dynamic url which has domain names -