cool, will check into it some more via testing -- *John Blythe* Product Manager & Lead Developer
251.605.3071 | j...@curvolabs.com www.curvolabs.com 58 Adams Ave Evansville, IN 47713 On Wed, May 20, 2015 at 3:22 PM, Walter Underwood <wun...@wunderwood.org> wrote: > I believe that boost is a superset of the bq functionality. > > wunder > Walter Underwood > wun...@wunderwood.org > http://observer.wunderwood.org/ (my blog) > > On May 20, 2015, at 1:16 PM, John Blythe <j...@curvolabs.com> wrote: > > > could i do that the same way as my mention of using bq? the docs aren't > > very rich in their example or explanation of boost= here: > > > https://cwiki.apache.org/confluence/display/solr/The+Extended+DisMax+Query+Parser > > > > thanks! > > > > -- > > *John Blythe* > > Product Manager & Lead Developer > > > > 251.605.3071 | j...@curvolabs.com > > www.curvolabs.com > > > > 58 Adams Ave > > Evansville, IN 47713 > > > > On Wed, May 20, 2015 at 3:13 PM, Walter Underwood <wun...@wunderwood.org > > > > wrote: > > > >> I highly recommend using boost= in edismax rather than bq=. The > >> multiplicative boost is stable with a wide range of scores. bq is > additive > >> and has problems with high or low scores. > >> > >> wunder > >> Walter Underwood > >> wun...@wunderwood.org > >> http://observer.wunderwood.org/ (my blog) > >> > >> On May 20, 2015, at 1:04 PM, John Blythe <j...@curvolabs.com> wrote: > >> > >>> Hi all, > >>> > >>> I've been fine tuning our current Solr implementation the last week or > >> two > >>> to get more precise results. We are trying to get our implementation > >>> accurate enough to serve as a lightweight machine learning (obviously a > >>> misnomer) implementation of sorts. Actual user generated searching is > far > >>> secondary for our purposes. > >>> > >>> I've gotten our results to go from confidence scores of ~40-60 for good > >>> results to the 700s. So far so good. Edismax seems like it has some > >>> promising features, but I'm wondering if it'll be very helpful for our > >>> purposes. The only thing that jumps out immediately to me is the bq > >> ability > >>> in which one of our non-primary fields is used as a means of boosting. > In > >>> other words, when using our three fields—manufacturer, part number, and > >>> description—to find a part, we could bq the category or size field to > >> help > >>> eliminate false positives from appearing. > >>> > >>> Is there anything else that you think I should look into regarding > >> edismax > >>> that could be helpful to our end game? > >>> > >>> Thanks for any ideas! > >> > >> > >
