NoSQL Zone is brought to you in partnership with:

Buddhika is currently employeed as a software engineer. He received his BSc. in Computer Science and Engineering from University of Moratuwa. Being an open source enthusiast he has participated in two Google Summer of Code programs at Apache. His current interests include data mining, distributed computing and business process monitoring. Buddhika is a DZone MVB and is not an employee of DZone and has posted 10 posts at DZone. You can read more from them at their website. View Full User Profile

3 Pitfalls of Working with Cassandra

06.04.2012
| 1940 views |
  • submit to reddit

Here are some points to keep in mind when working with Cassandra.

  • Have to use ordered partitioner if you want row keys in sorted order. Be aware that if the row keys are not distributed properly it would create hot spots since most of rows will be concentrated to several nodes.
  • Columns are sorted using definitions given when creating the column family but row keys are not sorted according to them.
  • If you see only hex values in Cassandra-cli for column keys and values in the shown results use ‘as’ and ‘assume’ to get the human readable values of the column keys and values. See this thread.
Published at DZone with permission of Buddhika Chamith, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)