Hi, I'm bumping into the NeedIndexErrors increasingly now with multiple (equality) filters on single (list) property. Now it seems quite clear that when one filter matches about half of the entries, it becomes expensive to comb the large intermediate set with the rest of filters.
This now affects our text search; if one of just two or three search terms is common, we get NeedIndexError and can't serve the search. And we're wondering whether we can trust the indices being efficient enough with more data. (I need to do some benchmarking on this.) I'd appreciate any information about 1) Index efficiency, is it getting better? Esp. with multiple filters on single property. Or should we immediately start building our search functions off appengine? 2) Can we do anything to help appengine to perform better? Does the ordering of filters matter? (It seems filter ordering is at least preserved.) Although, to implement this we'd need to maintain a frequency index ourselves and consulting it slows query building. And a very long shot: any hunches about any upcoming search service? Also all other tips are much appreciated! regards, Janne Savukoski http://www.netcycler.fi/ -- 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-appeng...@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.
