All must queries (and the rest of course) work ok when i search MAINK, MAINL, 
MAINQ,..., MAINT etc.. for street name
with all consonants except S is used and all other fields are the same for all 
queries (NASUA, HILLSBOROUGH, NEW HAMPSHIRE, UNITED STATES)

ie., working means: the top result is correct with MAIN.

But, with street name MAINS, and MAINO (with wovels) i cant get MAIN as top 
result.

I have two theories:

either my query plan is too complex to handle MAINS (as there are some other 
MAINS street in the index in other cities and states)
so maybe i need to run each component of booleanquery separately and then 
manually post process them.

or my query plan is still not good enough to catch MAIN when i search with 
street MAINS, city NASUA, municipality HILLSBOROUGH, state NEW HAMPSHIRE, 
cuntry UNITED STATES
where the first two are fuzzy as they are have errors in them and  the rest is 
phrase query as they are correct

that is why i want to see each score from each of the component of the 
booleanquery.
so far i checked Lucene but could not find a way to see each contributing score 
to the total score for each result hit document.

Best regards
 

----- Original Message -----
From: a...@apache.org
To: java-user@lucene.apache.org
Sent: Wednesday, June 26, 2019 1:09:36 PM GMT -05:00 US/Canada Eastern
Subject: Re: how to find out each score contribution from booleanquery 
components

It seems evident that multiple of your Must clauses are not matching any
document, hence no results are being returned?

On Wed, 26 Jun 2019 at 6:51 PM, <baris.ka...@oracle.com> wrote:

> Sure, here is the query plan: (i cant run explain plan as it does not
> give me anything)
>
> [+streetDFLT:maink~2 (streetDFLT:"maine")^0.35, +cityDFLT:nasua~2
> (cityDFLT:"nasuh")^0.35, ++regionDFLT:"new-hampshire"
> (regionDFLT:"new-hammpshire")^0.98, ++countryDFLT:"united"
> (countryDFLT:"uniten")^0.42000002 +countryDFLT:"states"
> (countryDFLT:"statesir")^0.56]
>
>
> explain plan gives:
>
> Explanation expl = is.explain(booleanQuery.build(), 10);
> System.out.println(expl);
>
> This prints:
>
> 0.0 = Failure to meet condition(s) of required/prohibited clause(s)
>    0.0 = no match on required clause (+regionDFLT:new-hampshire
> (regionDFLT:new-hammpshire)^0.98)
>      0.0 = Failure to meet condition(s) of required/prohibited clause(s)
>        0.0 = no match on required clause (regionDFLT:new-hampshire)
>          0.0 = no matching term
>    0.0 = no match on required clause (+countryDFLT:united
> (countryDFLT:uniten)^0.42000002 +countryDFLT:states
> (countryDFLT:statesir)^0.56)
>      0.0 = Failure to meet condition(s) of required/prohibited clause(s)
>        0.0 = no match on required clause (countryDFLT:united)
>          0.0 = no matching term
>        0.0 = no match on required clause (countryDFLT:states)
>          0.0 = no matching term
>
>
> Best regards
>
>
> On 6/26/19 12:48 PM, Atri Sharma wrote:
> > It depends a lot on the actual clauses (whether they are SHOULD, MUST,
> > MUST_NOT), each query’s type (phrase, term etc).
> >
> > Could you post your query and the explain plan of IndexSearcher post the
> > rewrite?
> >
> > On Wed, 26 Jun 2019 at 6:46 PM, <baris.ka...@oracle.com> wrote:
> >
> >> Hi,-
> >>
> >>    how can one find out each score contribution from booleanquery
> >> components?
> >>
> >> Best regards
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> >> For additional commands, e-mail: java-user-h...@lucene.apache.org
> >>
> >> --
> > Regards,
> >
> > Atri
> > Apache Concerted
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-user-h...@lucene.apache.org
>
> --
Regards,

Atri
Apache Concerted

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org

Reply via email to