Home/ Questions/Q 936941
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T21:23:39+00:00

I just tested and redeployed my application to a test instance, and it worked

  • 0

I just tested and redeployed my application to a test instance, and it worked fine, then i changed the app id and redeployed to my production instance, and I get an indexing problem. How do I avoid this in the future? I went to the effort to test it first and it worked fine!

Uncaught exception from servlet
com.google.appengine.api.datastore.DatastoreNeedIndexException: no matching index found..      <datastore-index kind="Article" ancestor="false" source="manual">
    <property name="tags" direction="asc"/>
    <property name="created" direction="asc"/>
</datastore-index>
at com.google.appengine.api.datastore.DatastoreApiHelper.translateError(DatastoreApiHelper.java:40)
at com.google.appengine.api.datastore.DatastoreApiHelper.makeSyncCall(DatastoreApiHelper.java:67)

The admin console says that it is “Building” the index. It has said that for 20 minutes now! How long does it take!?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    When you create new queries, and use them for the first time on your local machine, they always work first time. When you run these new queries for the first time on google app engine, they will return this exception because the google app engine servers take some time to generate an “index” to allow your query to work properly.

    I would recommend when you create new queries, to give them a once off run in the production environment to get the “index” built, so that when your users hit them, they work first time.

    Secondly,manually pre defining your queries before you need them and uploading them to the server, means that when you really need them they may be built on the server already.

    • 0