Google Datastore Composite index issue

╄→гoц情女王★ 提交于 2019-12-01 06:43:41

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.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!