Colleagues, fwiw bq is a DisMax parser feature. Shawn, to approach the boosting syntax with the standard parser you need something like q=foo:bar ip:sc^1000. Specifying ^1000 in bq makes no sense ever. If you show query params and debugQuery output, it would much easier for us to help you. PS omitting termfreq's and positions doesn't impact query time boosing ever. The closes caveat is that disabling norms indexing kills _index_ time boosting.
On Fri, Jan 18, 2013 at 11:10 AM, Shawn Heisey <s...@elyograg.org> wrote: > On 1/17/2013 11:41 PM, Walter Underwood wrote: > >> As I understand it, the bq parameter is a full Lucene query, but only >> used for ranking, not for selection. This is the complement of fq. >> >> You can use weighting: provider:fred^8 >> > > I tried bq=ip:sc^1000 and it doesn't seem to be making any difference. > Even if I add fq=ip:sc, I don't see any mention of bq, ip, sc, or 1000 in > the debugQuery output. > > This is the case on both 3.5 and 4.1. In case it was caused by omitting > termfreq and positions on the field I'm using in the bq, I tried a couple > of other fields that don't omit anything and bq seems to be having no > effect at all. > > Thanks, > Shawn > > -- Sincerely yours Mikhail Khludnev Principal Engineer, Grid Dynamics <http://www.griddynamics.com> <mkhlud...@griddynamics.com>
