[
https://issues.apache.org/jira/browse/SOLR-9217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954201#comment-15954201
]
gopikannan venugopalsamy commented on SOLR-9217:
------------------------------------------------
Great
Mikhail,
I am unable to understand from code what exactly is inefficient here,
Rewrite and createWeight are called one after another from
createNormalizedWeight {IndexSearcher.java}, Could you please shed some more
light at the inefficiency part?
I debugged below queries, The inefficiency is when join is part of filter
query(fq) right?
http://localhost:8983/solr/techproducts/select?q=*:*&fq={!join%20from=id%20to=id%20score=max}*:*&fl=score,price
http://localhost:8983/solr/techproducts/select?q={!join%20from=id%20to=id%20score=max}*:*&fl=score,price
> {!join score=..}.. should delay join to createWeight
> ----------------------------------------------------
>
> Key: SOLR-9217
> URL: https://issues.apache.org/jira/browse/SOLR-9217
> Project: Solr
> Issue Type: Improvement
> Components: query parsers
> Affects Versions: 6.1
> Reporter: Mikhail Khludnev
> Priority: Minor
> Labels: newbie, newdev
>
> {{ScoreJoinQParserPlugin.XxxCoreJoinQuery}} executes
> {{JoinUtil.createJoinQuery}} on {{rewrite()}}, but it's inefficient in
> {{filter(...)}} syntax or fq. It's better to do that in {{createWeigh()}} as
> it's done in classic Solr {{JoinQuery}}, {{JoinQParserPlugin}}.
> All existing tests is enough, we just need to assert rewrite behavior - it
> should rewrite on enclosing range query or so, and doesn't on plain term
> query.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
