Yes, that is the best practice. All versions share the same datastore, so deploy a new "staging" version (you should do this anyway for big releases as a best practice, App Engine or otherwise), wait for the indexes to build, do your acceptance testing, and flip the default.
Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Fri, Jun 24, 2011 at 7:07 AM, Branko Vukelic <[email protected]> wrote: > On one of the apps with HR datastore, I encountered this error. When I > update an app that has new indexes, what's the best way to handle > deployment of the new version to prevent this type of error? Do I wait > for the new indexes to become ready and then make the new version > default, and if so, how long do I need to wait? > > -- > Branko Vukelić > [email protected] > > Lead Developer > Herd Hound (tm) - Travel that doesn't bite > www.herdhound.com > > -- > 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. > > -- 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.
