[
https://issues.apache.org/jira/browse/LUCENE-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781804#action_12781804
]
Uwe Schindler commented on LUCENE-2092:
---------------------------------------
bq. Well, if it's been there since 1.9 and this is the first time it's been
reported, it hasn't caused the world to stop yet. So I don't think it's worth
the work unless we have to spin another 3.0 for additional reasons.
+1
But you can commit to *3.0* branch and also *2.9* branch. I did'nt want to have
commits in 3.0, because if I respin a release, I would not be able to only take
*some* of the fixes into 3.0.0. That was the reason.
For now i marked this issue as fix for 3.1, 3.0.1, 2.9.2
> BooleanQuery.hashCode and equals ignore isCoordDisabled
> -------------------------------------------------------
>
> Key: LUCENE-2092
> URL: https://issues.apache.org/jira/browse/LUCENE-2092
> Project: Lucene - Java
> Issue Type: Bug
> Components: Query/Scoring
> Affects Versions: 1.9, 2.0.0, 2.1, 2.2, 2.3, 2.3.1, 2.3.2, 2.4, 2.4.1,
> 2.9, 2.9.1
> Reporter: Hoss Man
> Assignee: Michael McCandless
> Fix For: 2.9.2, 3.0.1, 3.1
>
> Attachments: LUCENE-2092.patch
>
>
> BooleanQuery.isCoordDisabled() is not considered by BooleanQuery's hashCode()
> or equals() methods ... this can cause serious badness to happen when caching
> BooleanQueries.
> bug traces back to at least 1.9
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
