Google Datastore Composite index issue

Question

I am getting below exception :

Exception in thread \"main\" com.google.cloud.datastore.DatastoreException: no matching index found. recommended index is:
- k         


        

Answer 1

Property order absolutely matters for composite indexes when serving queries. The order is what allows us to serve range queries without having to scan through large sections of the index table. As a general rule, the final property is what you can do the inequality queries on, then the renaming property order defines the order by clause order you can use.

In your query send_date is what you are doing inequality on, whereas your existing composite index only allows for occasion_name.

If you create the composite index exactly as the API has returned your query will work.