I debugged the query and found the query has been translated into _text_:Kate AND _text_:Winslet, which _text_ is the default search field. Because my documents use parent/child relation it appeared that if there's no exact match of Kate Winslet, solr will return all documents contains "Kate" and "Winslet" in anywhere. However it will more sense if solr can rank docs that have "Kate" and "Winslet" in the same field higher. Of course I can use some NLP tricks with named entity recognition but it would be more expensive to develop.
On Sunday, November 1, 2015, Paul Libbrecht <p...@hoplahup.net> wrote: > Alexandre, > > I guess you are talking about that post: > > > http://lucidworks.com/blog/2015/06/06/query-autofiltering-extended-language-logic-search/ > > I think it is very often impossible to solve properly. > > Words such as "direction" have very many meanings and would come in > different fields. > In IMDB, words such as the names of persons would come in at least > different roles; similarly, the actors' role's name is likely to match > the family name of persons... > > Paul > > > > > As others indicated having intelligence to recognize the terms (e.g. > > Kate should be in name) or some user indication to do so can make thing > > more precise but is rarely done. > > Alexandre Rafalovitch <mailto:arafa...@gmail.com <javascript:;>> > > 1 novembre 2015 13:07 > > Which is what I believe Ted Sullivan is working on and presented at > > the latest Lucene/Solr Revolution. His presentation does not seem to > > be up, but he was writing about it on: > > http://lucidworks.com/blog/author/tedsullivan/ > > > Erick Erickson <mailto:erickerick...@gmail.com <javascript:;>> > > 1 novembre 2015 07:40 > > Yeah, that's actually a tough one. You have no control over what the > > user types, > > you have to try to guess what they meant. > >
