hi guys! "merge join" queries like these, ie queries that have equals filters on multiple properties but no inequality filters or sort orders, *usually* don't require an index. that's described in http://code.google.com/appengine/docs/datastore/queriesandindexes.html#Defining_Indexes_With_index_yaml .
however, in cases with unusually shaped data, these queries can sometimes require an index. these cases are exceedingly rare, but they're somewhat more common with apphosting.ext.search. also, you need an index for each number of keywords that you expect in a query. for example, if you support three-word search queries, you need this index: - kind: Post properties: - name: __searchable_text_index - name: __searchable_text_index - name: __searchable_text_index - name: approved more in the ext.search docstring, http://code.google.com/p/googleappengine/source/browse/trunk/google/appengine/ext/search/__init__.py . also, unfortunately, these kinds of indices are likely to explode, as described in http://code.google.com/appengine/docs/datastore/queriesandindexes.html#Big_Entities_and_Exploding_Indexes . the upshot of all of this, as we've mentioned before, is that appengine.ext.search is a hack. it's not scalable, mature, or anywhere near industrial strength, which is why it's not officially supported or documented. we're well aware that it's not good enough, and we dearly hope to offer a real full text search solution in the future. i don't have any details or timeline, though. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
