RE: boost parameter produces garbage hits

2019-04-30 Thread Baloo
To answer your question "Why does the boost parameter return garbage hits with 0 score?" >> Syntax for Solr's query function is query(subquery, default) it returns >> the score for the given subquery, or the default value for documents not >> matching the query. In your case for the documents wher

Re: Document Score seen in debug section and in main results section dont match

2019-02-12 Thread Baloo
Thanks Erick, We will stick to Solr 7.2.1 which works fine with multiple boost queries. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Document Score seen in debug section and in main results section dont match

2019-02-12 Thread Baloo
r than 1st and 2nd document. So I am wondering why Solr ignored score which is coming from boost query section? Solr Response : https://gist.github.com/baloo-solr/73add39132c8f3688a20d4f64fe93279 -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Document Score seen in debug section and in main results section dont match

2019-02-11 Thread Baloo
Thanks Erick to answer your question "What is "Y"?" Score that we see in debug section actually looks correct and if we order documents by that score we can get similar ranking of results that we were getting for solr 6.4.2. But With the score field that we get with each record it looks like boo

Document Score seen in debug section and in main results section dont match

2019-02-11 Thread Baloo
HI All, Currently I am migrating Solr 6.4.2 to Solr 7.4. We pass multiple boost queries (multiplicative boost queries, Solr's 'boost' parameter) to Solr with each query. We have migrated all our custom components and solr configurations to Solr 7.4.2 but during verification we have seen differen

Query construction in custom Solr component plugin

2017-02-27 Thread Baloo
Hi, I have developed a solr component which expands users query and adds additional clauses to the query. For this expansion we are making request to external REST api's. This query expansion logic is mainly in prepare() method. Everything works as expected in standalone mode. When we deploy this