Short summary:
* Multiple simultaneous phrase boosts with different ps2 parameters
are working very nicely for me on a few million doc QA system.
* I've submitted an updated patch to Jira incorporating feedback
from the jira comments. Will be testing it more this week.
https://issues
Chris Hostetter wrote:
> : Perhaps fold it into the pf/pf2 syntax?
> :
> : pf=text^2// current syntax... makes phrases with a boost of 2
> : pf=text~1^2 // proposed syntax... makes phrases with a slop of 1 and
> : a boost of 2
> :
> : That actually seems pretty natural given the lucene query
: Perhaps fold it into the pf/pf2 syntax?
:
: pf=text^2// current syntax... makes phrases with a boost of 2
: pf=text~1^2 // proposed syntax... makes phrases with a slop of 1 and
: a boost of 2
:
: That actually seems pretty natural given the lucene query syntax - an
: actual boosted sloppy
On Fri, Aug 13, 2010 at 2:38 PM, Ron Mayer wrote:
> Yonik Seeley wrote:
>> Perhaps a ps2 parameter to match pf2?
>
> That might be nice.
>
> I could try to put together such a patch if people were interested.
>
> One more thing I've been contemplating is if my results might
> be even better if I h
Yonik Seeley wrote:
> Perhaps a ps2 parameter to match pf2?
That might be nice.
I could try to put together such a patch if people were interested.
One more thing I've been contemplating is if my results might
be even better if I had a couple different "pf2"s with different "ps"'s
at the same ti
Perhaps a ps2 parameter to match pf2?
-Yonik
http://www.lucidimagination.com
On Fri, Aug 13, 2010 at 2:11 PM, Ron Mayer wrote:
> Jayendra Patil wrote:
>> We pretty much had the same issue, ended up customizing the ExtendedDismax
>> code.
>>
>> In your case its just a change of a single line
>>
Jayendra Patil wrote:
> We pretty much had the same issue, ended up customizing the ExtendedDismax
> code.
>
> In your case its just a change of a single line
> addShingledPhraseQueries(query, normalClauses, phraseFields2, 2,
> tiebreaker, pslop);
> to
> addShingledPhraseQueries(q
We pretty much had the same issue, ended up customizing the ExtendedDismax
code.
In your case its just a change of a single line
addShingledPhraseQueries(query, normalClauses, phraseFields2, 2,
tiebreaker, pslop);
to
addShingledPhraseQueries(query, normalClauses, phraseFields2, 2,
Short summary:
Is there any way I can specify that I want a lot
of phrase slop for the "pf" parameter, but none
at all for the "pf2" parameter?
I find the 'pf' parameter with a pretty large 'ps' to do a very
nice job for providing a modest boost to many documents that are
quite well rela
