Ok, that was stupid, I pasted the wrong quote. I meant this: "The longer the keys are the worse performance is so I would just add a single known character prefix to your keys."
Now I didn't know this, and I can't find anything about that in the docs. Can anyone verify this? - Koen On Jun 23, 12:57 pm, Koen Bok <k...@madebysofa.com> wrote: > Great, thanks Nick. > > "No, having all your keys have the same prefix will not impact > performance. > Bigtable is smart enough to handle this. :) " > > Now I didn't know this, and I can't find anything about that in the > docs. Can anyone verify this? > > - Koen > > On Jun 23, 12:31 pm, "Nick Johnson (Google)" <nick.john...@google.com> > wrote: > > > > > Hi Koen, > > > No, having all your keys have the same prefix will not impact performance. > > Bigtable is smart enough to handle this. :) > > > -Nick Johnson > > > On Tue, Jun 23, 2009 at 11:14 AM, Koen Bok <k...@madebysofa.com> wrote: > > > > I want my datastore keys to be uuid's (hex presentation), but they can > > > start with a digit which is not allowed. So I figured I'd add a > > > constant prefix. > > > > Could that have a negative impact on the index the datastore builds? > > > It shouldn't right? Just double checking :-) > > > -- > > Nick Johnson, App Engine Developer Programs Engineer > > Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: > > 368047 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
