On Thu, 18 Mar 2010 19:26:06 +0100 Sylvain Lebresne <sylv...@yakaz.com> wrote:
SL> Given how Cassandra works, I don't think that the server can do much SL> better than the read, write, delete your client already do SL> (basically everything is immutable, you only 'add' new versions). As SL> this cannot be done efficiently (I can be wrong on that but if so, I SL> *really* would be interested to know why), a model that require a SL> lot of renames of SuperColumn is probably not a super good fit for SL> Cassandra (I'm not sure why you need a lot of rename though, maybe SL> you really have no choice). So I lean in the same direction as SL> Jonathan. Adding an API call that 'promote' an operation not very SL> efficient is not a good idea. Thanks for explaining, Sylvain. I could go into details about my model but it's not so important (it's evolving as I find the best fit between the model and Cassandra). As long as I know Cassandra is not a good fit for this kind of operation I can design a better data model. Ted
