[
https://issues.apache.org/jira/browse/LUCENE-6304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345327#comment-14345327
]
Adrien Grand commented on LUCENE-6304:
--------------------------------------
Feels wrong to me to override hashCode but not equals. I think we should move
this class part of hashCode() to Query.hashCode()? (ie. return
Float.floatToIntBits(getBoost()) ^ getClass().hashCode();)
If it is controversial then I'm happy with the previous patch that overrides
both equals and hashCode().
> Add MatchNoDocsQuery that matches no documents
> ----------------------------------------------
>
> Key: LUCENE-6304
> URL: https://issues.apache.org/jira/browse/LUCENE-6304
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Affects Versions: 5.0
> Reporter: Lee Hinman
> Priority: Minor
> Attachments: LUCENE-6304.patch, LUCENE-6304.patch, LUCENE-6304.patch
>
>
> As a followup to LUCENE-6298, it would be nice to have an explicit
> MatchNoDocsQuery to indicate that no documents should be matched. This would
> hopefully be a better indicator than a BooleanQuery with no clauses or (even
> worse) null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
