Explanation:
Using hash values of existing primary keys and bit-reversed sequential values are effective strategies for distributing keys evenly and preventing hot-spotting. Conversely, auto-incrementing values, timestamps, and starting primary keys with low cardinality attributes can exacerbate hot-spotting issues. For more details, refer to Cloud Spanner schema design documentation.
Ultimate access to all questions.
To address hot-spotting in a Cloud Spanner database, changing the primary keys of tables is suggested. Which two methods would you consider for defining new keys to mitigate this issue?
A
Big-reversed sequential values
B
Timestamps
C
Hash value of existing primary key
D
Start primary key with low cardinality attribute
E
Auto-incrementing values
No comments yet.