Hi all, To address the questions on this thread in order:
1. While we will be moving to scattered ids in production soon, we're going to limit the size of ids to the max integer that a 64-bit float can represent exactly, which will address the problem with floating-point representations. This will also be changed in the 1.7.7 SDKs. The motivation for scattered ids is that sequential ids cause hot spots in bigtable and GAE MR, which leads to significant performance limitations. More info on scattered ids: Scattered auto ids in 1.7.5 SDK<https://groups.google.com/forum/?fromgroups=#!msg/google-appengine/YlCZ3z7lwdI/j-gLCDSHfZEJ> See the section "Specifying the automatic id allocation policy": https://developers.google.com/appengine/docs/Python/tools/devserver#Using_the_Datastore<https://developers.google.com/appengine/docs/java/tools/devserver#Using_the_Datastore> https://developers.google.com/appengine/docs/java/tools/devserver#Using_the_Datastore 2. The current allocate_ids() functions will continue to allocate sequential ids. So, manually allocated sequential ids will still be available. 3. We're sorry for the inconvenience this caused with the 1.7.6 dev appserver, but we're glad we caught this early! 4. If you need small ids, you won't be able to rely on automatic ids for this. One option would be to use the allocate_ids() functions to manually allocate ids. Thanks for your feedback! On Monday, March 25, 2013 12:13:52 PM UTC-7, Mahron wrote: > > Ok, so strings it is. Upgrade complete ! > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
