gotcha, thanks for the response. will check {!boost} out for now and start
working on moving our current query builders to a dismax/edismax
configuration.
best,
--
*John Blythe*
Product Manager & Lead Developer
251.605.3071 | j...@curvolabs.com
www.curvolabs.com
58 Adams Ave
Evansville, IN 47713
On Tue, Apr 5, 2016 at 10:25 AM, Markus Jelsma <markus.jel...@openindex.io>
wrote:
> Hello - i would certainly go for edismax' boost parameter, as it
> multiplies scores. You can always do a regular boost query via {!boost ..}
> but edismax makes it much easier.
> Markus
>
>
>
> -----Original message-----
> > From:John Blythe <j...@curvolabs.com>
> > Sent: Tuesday 5th April 2016 15:36
> > To: solr-user <solr-user@lucene.apache.org>
> > Subject: using tokens to influence boost and score rather than filtering
> >
> > hi all,
> >
> > i'm trying to do something similar to a simple fq=x on my query. i'm
> using
> > the regular ol' select handler. instead of blocking out all items not
> > related to x via the filter query i'd like to simply give them priority.
> >
> > is there a way to do this? it seems like the dismax bq function may be
> > similar, but 1) i'd like to be certain before proceeding, 2) i'd prefer
> > even more to stick w my vanilla query processing instead of migrating to
> > dismax, at least for the near term.
> >
> > thanks for any pointers
> >
> > best,
> >
> > --
> > John Blythe
> >
>
