On Thu, Sep 8, 2011 at 5:12 PM, Dean Hiller <d...@alvazan.com> wrote:
> I was wondering something. Since I can take OPP and I can create a layer > that for certain column families, I hash the key so that some column > families are just like RP but on top of OPP and some of my other column > families are then on OPP directly so I could use lucandra, why not make RP > deprecated and instead allow users to create OPP by column family or RP > where RP == doing the hash of the key on my behalf and prefixing my key with > that hashcode and stripping it back off when I read it in again. > > ie. why have RP when you could do RP per column family with the above > reasoning on top of OPP and have the best of both worlds????? > > ie. I think of having some column families random and then some column > famiiles ordered so I could range query or use lucandra on top of those > ones. > > thoughts? I was just curious. > thanks, > Dean > > You can use ByteOrderPartitioner and hash data yourself. However that makes every row key will be 128bits larger as the key has to be: md5+originalkey http://www.datastax.com/wp-content/uploads/2011/07/Scaling_Solr_with_Cassandra-CassandraSF2011.pdf Solandra now uses a 'modified' RandomPartitioner.
