Re: Problems with elevation component configuration
Hi, Well, if I understand correctly, only the search term is important for elevation, not the query. Anyway, we ended up modifying QueryElevationComponent class, extracting the search term from the query using regex. After that, it turned out that elevation doesn't work with grouped results, so we had to separate sorting for groups and non-groups in prepare() method of the same class. That was not the end of problems, because we need to show elevated results with a different styling, so we upgraded to Solr4 and now it seems to be working as expected. -- View this message in context: http://lucene.472066.n3.nabble.com/Problems-with-elevation-component-configuration-tp3993204p3995692.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Problems with elevation component configuration
Hi, Thanks Chris, but actually, it turns out that query text from elevate.xml has to match the query (q=...). So in this case, elevation works only for http://localhost:8080/solr/elevate?q=brain, but not for http://localhost:8080/solr/elevate?q=indexingabstract:brain type of queries. This could be solved by using DisMax query parser (http://localhost:8080/solr/elevate?q=brainqf=indexingabstractdefType=dismax), but we have way more complicated queries which cannot be reduced just to q=searchterm... Can anything be done about that without modifying QueryElevationComponent class? Thanks, Igor -- View this message in context: http://lucene.472066.n3.nabble.com/Problems-with-elevation-component-configuration-tp3993204p3994595.html Sent from the Solr - User mailing list archive at Nabble.com.
