OK - Slapping forehead now... D'oh! <float name="synonyms.originalBoost">1.2</float
Float, not int! Oops... It's Friday.... That's my story and I'm sticking to it... On Fri, Jun 17, 2016 at 12:15 PM, John Bickerstaff <j...@johnbickerstaff.com > wrote: > Hi all - > > I've successfully run the hon-lucene-synonyms plugin from the Admin > console by adding the following to the Raw Query Parameters field... > > > &qf=text&defType=synonym_edismax&synonyms=true&synonyms.originalBoost=1.2&synonyms.synonymBoost=1.1 > > I got those from the Read Me on the github account. > > Now I'm trying to make this work via a requestHandler in solrconfig.xml. > > I think the following should work, but it just hangs if I add the last > line referencing synonyms.originalBoost > > <requestHandler name="/test1" class="solr.SearchHandler"> > <!-- default values for query parameters can be specified, these > will be overridden by parameters in the request > --> > <lst name="defaults"> > <str name="echoParams">explicit</str> > <int name="rows">10</int> > <str name="defType">synonym_edismax</str> > <str name="qf">text</str> > <str name="synonyms">true</str> > <int name="synonyms.originalBoost">1.2</int> --> If I add this > line, the admin console just hangs when I hit /test1 > </lst> > </requestHandler> > > If I do NOT add the last line and only have the line that sets > synonyms=true, it appears to work fine. > > I see the dot notation all over the sample entries in solrconfig.xml... > Am I missing something here? > > Essentially, how do I get these variables set correctly from inside a > requestHandler configured in the solrconfig.xml file? > > On Tue, Jun 7, 2016 at 11:47 AM, Joe Lawson < > jlaw...@opensourceconnections.com> wrote: > >> MaryJo you might want to start a new thread, I think we kinda hijacked >> this >> one. Also if you are interested in tuning queries check out >> http://splainer.io/ and https://www.quepid.com which are interactive >> tools >> (both of which my company makes) to tune for search relevancy. >> >> On Tue, Jun 7, 2016 at 1:45 PM, MaryJo Sminkey <mjsmin...@gmail.com> >> wrote: >> >> > I'm really thinking this just might not be the right tool for us, what >> we >> > really need is a solution that works like the normal synonym filter >> does, >> > just with proper multi-term support, so I can apply the synonyms only on >> > certain fields (copied fields) that have their own, lower boost >> settings. >> > The way this plugin works across the entire query just seems too >> > problematic when you need to do complex queries with lots of different >> > boost settings to get good relevancy. Anyone used a different method of >> > handling multi-term synonyms that isn't as global? >> > >> > Mary Jo >> > >> > >> > >> > On Tue, Jun 7, 2016 at 1:31 PM, MaryJo Sminkey <mjsmin...@gmail.com> >> > wrote: >> > >> > > Here's the issue I am still having with getting the right search >> > relevancy >> > > with the synonym plugin in place. We typically have users searching on >> > > multiple terms, and we want matches across multiple terms, >> particularly >> > > those that appears as phrases, to appear higher than matches for the >> same >> > > term multiple times. The synonym filter makes this complicated since >> we >> > may >> > > have cases where the term the user enters, like "sbc", maps to a >> > multi-term >> > > synonym like "small block", and we always want the matches for the >> > original >> > > term to pop up first, so I'm trying to make sure the original boost is >> > high >> > > enough to override a phrase boost that the multi-term synonym would >> give. >> > > Unfortunately this then means matches on the same term multiple times >> get >> > > pushed up over my phrase matches...those aren't going to be the most >> > > relevant matches. Not sure there's a way to solve this successfully, >> > > without a completely different approach to the synonyms... or not >> > counting >> > > the number of matches on terms (I assume you can drop that ability, >> > > although that's not ideal either...just better than what I have now). >> > > >> > > MJ >> > > >> > > >> > > >> > > Sent with MailTrack >> > > < >> > >> https://mailtrack.io/install?source=signature&lang=en&referral=mjsmin...@gmail.com&idSignature=22 >> > > >> > > >> > > On Mon, Jun 6, 2016 at 9:39 PM, MaryJo Sminkey <mjsmin...@gmail.com> >> > > wrote: >> > > >> > >> >> > >> On Mon, Jun 6, 2016 at 7:36 PM, Joe Lawson < >> > >> jlaw...@opensourceconnections.com> wrote: >> > >> >> > >>> >> > >>> We were thinking, as you experimented with, that the 0.5 and 2.0 >> boosts >> > >>> were no match for the product name and keyword field boosts so that >> > would >> > >>> influence your search as well. >> > >> >> > >> >> > >> >> > >> Yeah I definitely will have to play with the values a bit as we want >> the >> > >> product name matches to always appear highest, whether original or >> > >> synonyms, but I'll have to figure out how to get that result without >> one >> > >> word terms that have multi word synonyms getting overly boosted for a >> > >> phrase match.... while still sufficiently boosting the normal phrase >> > match >> > >> stuff too. With the normal synonym filter I was able to just copy >> fields >> > >> that could have synonyms to a new field (which would be the only one >> > with >> > >> the synonym filter), and use a different, lower boost on those >> fields, >> > but >> > >> that won't work with this plugin which applies across everything in >> the >> > >> query. Makes it a bit more complicated to get everything just right. >> > >> >> > >> MJ >> > >> >> > >> >> > >> Sent with MailTrack >> > >> < >> > >> https://mailtrack.io/install?source=signature&lang=en&referral=mjsmin...@gmail.com&idSignature=22 >> > > >> > >> >> > > >> > > >> > >> > >
