On Jun 28, 7:20 am, Robert Kluin <[email protected]> wrote: > I am not sure this would be a good idea, since indexes are global > to the app. How would you handle the case when you are just uploading > an index and not a version? Perhaps your rule would only apply when > uploading indexes with a new version?
Yes. It would just be an automatization on the manual process of uploading a new version, waiting for the indexes to build and then setting that version as the default. If there was no new version then the indexes would just be updated. Being an internal process, perhaps it could be done with the internal minor version number, so that no visible version change would occur. In any case, the dashboard would have to be updated to show that a new version was ready to be deployed as soon as the indexes were fully built. -- 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.
