Hi Rohan/Audrey
I have implemented the sow=false property with eDismax Query parser but
still it does not has any effect
on the query as it is still parsing as separate terms instead of phrased
one.
On Tue, Oct 15, 2019 at 8:25 PM Rohan Kasat wrote:
> Also check ,
> pf , pf2 , pf3
> ps , ps2, p
Also check ,
pf , pf2 , pf3
ps , ps2, ps3 parameters for phrase searches.
Regards,
Rohan K
On Tue, Oct 15, 2019 at 6:41 AM Audrey Lorberfeld -
audrey.lorberf...@ibm.com wrote:
> I'm not sure how your config file is setup, but I know that the way we do
> multi-token synonyms is to have the sow (
I'm not sure how your config file is setup, but I know that the way we do
multi-token synonyms is to have the sow (split on whitespace) parameter set to
False while using the edismax parser. I'm not sure if this would work with
PhraseQueries , but it might be worth a try!
In our config file we
