You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2013/04/18 08:13:15 UTC
[jira] [Created] (LUCENE-4939) Join's TermsIncludingScoreQuery
Weight has wrong normalization
David Smiley created LUCENE-4939:
------------------------------------
Summary: Join's TermsIncludingScoreQuery Weight has wrong normalization
Key: LUCENE-4939
URL: https://issues.apache.org/jira/browse/LUCENE-4939
Project: Lucene - Core
Issue Type: Bug
Components: modules/join
Reporter: David Smiley
Priority: Minor
In the Join module, TermsIncludingScoreQuery's Weight implementation looks suspiciously wrong. It creates a Weight based on the original query and delegates a couple calls to it in getValueForNormalization() and normalize() -- ok fine. But then it doesn't do anything with it! Furthermore, the original query has already been run by this point anyway.
Question: Should the original query, which currently runs separately (see JoinUtil), participate in the Weight normalization of the main query? It would be tricky to wire all this together based on the current structure but arguably that is more correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org