Three pitfalls to avoid when using Cassandra

Cassandra is a very popular NoSQL product, it is based on the Key-value distributed storage Way is respected by many DBAs. NoSQL database products range, compared with traditional relational database, in terms of technical maturity is not perfect, so the DBA in the learning and use of the process will inevitably encounter some problems. Cassandra expert Buddhika Chamith in his blog with a concise language to explain the use of Cassandra to avoid the three misunderstandings:

1, if you want row key order, you need to use ordered partitioner. Remember that if the row key is not distributed properly, it generates a large number of hotspots (hot spots) because most rows are centered over a few nodes.

2. When creating a column family, the column will be sorted according to the definition, but the row key will not.

3. If you see only the hexadecimal value of column key in Cassandra-cli, and the value in the given result uses "as" and "assume" to display the readable (readable) value.