Re: "pf" not supported by edismax?

Hi Jack Sorry I am confused. For mycase,it seems that "pf" only work with dismax. with dismax: +((spp_keyword_exact:dvd) (spp_keyword_exact:bracket)) *(spp_keyword_exact:dvd bracket)* with edismax: +((spp_keyword_exact:dvd) (spp_keyword_exact:bracket)) () On 2/15/2016 1:26 PM, Jack

Re: "pf" not supported by edismax?

Maybe because the tokenized phrase produces only a single term it is ignored. In any case, it won't be a phrase. pf only does something useful for phrases. IOW, where a PhraseQuery can be generated. A PhraseQuery for more than a single term would never match when the field value is a single term.

Re: "pf" not supported by edismax?

It is using KeywordTokenizerFactory. It is still consider as tokenized? Here's the field definition: type="gs_keyword_exact" multiValued="true"/> positionIncrementGap="100"> On 2/15/2016 12:43 PM, Jack

Re: "pf" not supported by edismax?

pf stands for phrase boosting, which implies tokenized text... spp_keyword_exact sounds like it is not tokenized. -- Jack Krupansky On Sun, Feb 14, 2016 at 10:08 PM, Derek Poh wrote: > Hi > > Correct me If I am wrong, edismax is an extension of dismax, so it will >

"pf" not supported by edismax?

Hi Correct me If I am wrong, edismax is an extension of dismax, so it will support "pf". But from my testing I noticed "pf" is not working with edismax. From the debug information of a query using "pf" with edismax, there is no phrase match for the "pf" field "spp_keyword_exact". If I