Not in general, no. There are places, like indexing, that need to use a local partitioner rather than the global one.
Which uses of the DK constructor looked erroneous to you? On Mon, Apr 22, 2013 at 10:54 AM, Desimpel, Ignace <ignace.desim...@nuance.com> wrote: > Hi, > > > > I was trying to implement my own ordered partitioner and got into problems. > > The current DecoratedKey is using a ByteBufferUtil.compareUnsigned for > comparing the key. I was thinking of having a signed comparison, so I > thought of making my own DecoratedKey, Token and Partitioner. That way I > would have complete control… > > So made a partitioner whith a function decorateKey(…) returning > MyDecoratedKey in stead of DecoratedKey > > But when making my own MyDecoratedKey, the database get into trouble when > adding a key space due to the fact that some code in Cassandra is using the > ‘new DecoratedKey(…)’ statement and is not using the partitioner function > decorateKey(…). > > > > Would it be logical to always call the partitioner function decorateKey such > that the creation of an own partitioner and key decoration is possible? > > > > Ignace Desimpel > > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
