Hey there.. I was running into this problem for a while. I ended up implementing work-around using the GDATA Google Base Api. If you don't have sensitive data in the searchable entities, then it is easy to upload each entity as a Base Entry. Then you write a javascript client for searching. This way, you get true full-text search and save a bundle on your appengine quota.
I wrote a blog article about it here: http://blog.anekdotz.com/2010/01/efficient-full-text-search-mashup-with.html You could check it out in action here: (enter your search terms in the little box on the left, and hit retur) http://www.dontjudgemejudger.com/ On Apr 5, 7:46 am, Keith <[email protected]> wrote: > I've been trying to get text search working on app engine for some > news articles. I followed Brett Slatkin's relation indexing / keys > only query technique and I've found that it works great except that I > want to get the most recent articles first and I have to add a sort > order. > > Basically, I can search a single term in reverse order fine and I can > search multiple terms without ordering but when I want to search for > multiple terms in reverse date order it tells me I need a composite > index and I run into the exploding indexes problem. I could try > running individual queries and calculating the intersect myself but I > dont know how far back to pull articles from in order to get a > reasonable number remaining. > > At the moment I'm stuck with restricting users to search for a single > term only. Does anyone have any suggestions on how to get around this? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
