Have to admit I was very excited about this when I first saw the experimental release.
Sadly I ran into a problem right away with partial word matching. Yes I know this is not supposed to work and I have code that executes datastore "starts with" queries when we get 0 results for a short single word query. The more interesting problem occurs at one fully matched word and a partial match on the second word of a query. Example: I have a document with a "name" field set to "foo bar" and about 999 other documents with the "name" field set to "foo <any word that doesn't contain "bar" in it>" When I do a query for "foo ba" I get 0 results from the Search API. and when I do a query for "foo" I get 1000 results. Out of those 1000 results I really want "foo bar" to be at the top but since it's only a partial match it can end up anywhere in the result set. The only way I've come up to get around this is do result merging that breaks up the query into individual words and if still not finding much then uses datastore "starts with" queries. If anyone has suggestions/ideas for other ways this can be implemented I'm all ears. - Dennis. -- 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.
