No, you do not need to shut up, please! :) you may be clearing up my further misconceptions on the topic!
Anyways, the link b/w 1st and 2nd para was that since the rows distribution among nodes is not affected by key(as you rightly said) but by md5 hash of the key thus I can use just any key including the timeUUIDType key (that would be helpful in my case) with Random partition. On 1/14/11, Roshan Dawrani <roshandawr...@gmail.com> wrote: > On Fri, Jan 14, 2011 at 8:51 PM, Aklin_81 <asdk...@gmail.com> wrote: > >> I just read that cassandra internally creates a md5 hash that is used >> for distributing the load by sending it to a node reponsible for the >> range within which that md5 hash falls, so even when we create >> sequential keys, their MD5 hash is not the same & hence they are not >> sent to same node. This was my misunderstanding of this concept. >> Sorry for creating confusions ! >> >> So.. with this I think I will be able to use timeUUID as row key !? >> >> > Now, what really is the link between your corrected understanding and the > conclusion in the 2nd para? :-) > > I miss the link you are using to come from para 1 to para 2. > > Just because you use time UUID as the row key, there is no storage guarantee > because of that. Distribution of rows and ordering across nodes is only > based on what partitioner you are using - it is not (only) related to the > the type of the key. > > May be I should just shut up now as I don't seem to be understanding you > requirement :-) > > > > > > > > <#> > <#> > <#> <#> >
