Well, by definition, using an analyzer that removes stopwords *should* do this at query time. This assumes that you used an analyzer that removed stopwords at index and query time. The stopwords are not in the index.
You can get the behavior you expect by using an analyzer at query time that does NOT remove stopwords, and one at indexing time that *does* remove stopwords. Gut I'm having a hard time imagining that this would result in a good user experience. I mean anytime that you had a stopword in the query where the stopword was required, no results would be returned. Which would be hard to explain to a user.... What is it you're trying to accomplish? Best Erick On Tue, Mar 17, 2009 at 7:40 AM, revas <revas...@gmail.com> wrote: > Hi, > > I have a query like this > > content:the AND iuser_id:5 > > which means return all docs of user id 5 which have the word "the" in > content .Since 'the' is a stop word ,this query executes as just user_id :5 > inspite of the "AND" clause ,Whereas the expected result here is since > there > is no result for "the " ,no results shloud be returned. > > Am i missing anythin here? > > Regards >
