Hey Venkata, This sort of question should be asked over at Stack Overflow <http://stackoverflow.com>. This forum is meant for more high level discussion of the platform and services, rather than specific-issue technical support. We also monitor Stack Overflow, and it has the benefit of being a community designed to assist with questions like these, so don't hesitate to post there in future. For now, I'll be happy to assist in this thread by giving my thoughts, however:
Creating a composite index doesn't necessarily mean that: A) you have entities in the Datastore with those properties, or which have been indexed for those properties (entities put with unindexed properties before the index was defined will need to be reindexed by being retrieved and re-put [1]) B) the entities will match the query you ran One of the above scenarios is very likely to be the cause behind why your query did not return results after creating a composite index. Let me know how it goes in testing and if you have any further questions. I'll be glad to help! Regards, Nick Cloud Platform Community Support [1] from https://cloud.google.com/appengine/docs/python/datastore/indexes#Python_Unindexed_properties: changing a property from unindexed to indexed does not affect any existing > entities that may have been created before the change. Queries filtering on > the property will not return such existing entities, because the entities > weren't written to the query's index when they were created. To make the > entities accessible by future queries, you must rewrite them to the > Datastore so that they will be entered in the appropriate indexes. That is, > you must do the following for each such existing entity: > > 1. Retrieve (get) the entity from the Datastore. > > > 1. Write (put) the entity back to the Datastore. > > Similarly, changing a property from indexed to unindexed only affects > entities subsequently written to the Datastore. The index entries for any > existing entities with that property will continue to exist until the > entities are updated or deleted. To avoid unwanted results, you must purge > your code of all queries that filter or sort by the (now unindexed) > property. On Sunday, May 1, 2016 at 11:48:13 AM UTC-4, Venkata Ramesh Babu Pasupuleti wrote: > > > DataStore Composite index is created, but there are no entries & when the > query is run null result is coming though there are valid entries for the > query in the datastore? > > Status is shown as serving when checked through admin console > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/f12921f2-b990-4f9f-984b-d753643995a7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
