Thanks. There is a chance of collision right? How do we handle those?
If the string is converted to: domain +"/" + md5(rest_of_url) will the chance of collision be significantly lowered? If the chance of collision is very small it's acceptable for me. On Mar 24, 8:06 am, "Nick Johnson (Google)" <[email protected]> wrote: > Hi Peter, > > On Wed, Mar 24, 2010 at 6:01 AM, Peter Liu <[email protected]> wrote: > > Is using url as a string key for an entity really inefficient for > > space? > > > Say if the url is long and it's 1k byte, each key is repeatedly stored > > with each indexed property right? If you have a list property of 5000 > > items, will the keys of those 5000 index entries consume 5M? > > That's correct (give or take some overhead factor). If you're concerned > about length, you might want to consider using the MD5 or SHA1 hash of the > URL as the key instead. > > -Nick Johnson > > > > > Thanks. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-appengine%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-appengine?hl=en. > > -- > Nick Johnson, Developer Programs Engineer, App Engine > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
