On Fri, Aug 29, 2014 at 3:48 PM, Drew Kutcharian <d...@venarc.com> wrote:
> AFAIK, currently Cassandra partitions (thrift) rows using the row key, > basically uses the hash(row_key) to decide what node that row needs to be > stored on. Now there are times when there is a need to shard a wide row, > say storing events per sensor, so you’d have sensorId-datetime row key so > you don’t end up with very large rows. Is there a way to have the > partitioner use only the “sensorId” part of the row key for the hash? This > way we would be able to store all the data relating to a sensor in one node. > As a general statement, if you believe you need to create a custom Partitioner in order to handle your use case, you are almost certainly wrong or Doing It Wrong. =Rob
