Is it ok to have multiple tables with same partition key and different primary keys with Clustering order change? For example in Table 2 and Table 3 the hash will be on enterprise_id and will lead to same node. However only the clustering key order has changed and will allow me to query directly on the required key.
Yes, you can have multiple tables with the same partition key. The partition key of one table has nothing to do with the partition key of another table.
The partition key of a table simply determines the node where each partition is stored. The partitioner (the default is Murmur3Partitioner) runs a hash function on the partition key to convert it into a token. Whichever node in the cluster owns the token (based on its token range ownership) is responsible for storing the partition.
I've explained how the partitioner works in a bit more detail in my answer to question #5944. Cheers!
5 People are following this question.
