If you're deploying a new version that relies on indexes that haven't been
built yet, you should be able to deploy this to a non-default version. This
way, the indexes get built eventually but your application won't be serving
index errors in the meantime. Then, when the indexes are built, make thi
Jason,
thanks for the info, this solved the problem.
I've noticed however that the index building can take some time after
the application has been deployed - is there any way to control that /
prevent the new version of the application from being used if the
indices are not ready yet? (Otherwise
Hi Dmitry. What's your app ID?
Indexes are auto-generated by the SDK when you run a query locally that
requires a custom index. If you don't run a particular query locally and it
uses multiple sort orders or otherwise requires a custom index, then the
index won't be generated in datastore-indexes-
Hello,
our application recently started producing exceptions like:
com.google.appengine.api.datastore.DatastoreNeedIndexException: no
matching index found..
or
Server error 1:
com.google.appengine.api.datastore.DatastoreNeedIndexException: no
matching index found..
