[
https://issues.apache.org/jira/browse/LUCENE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742586#action_12742586
]
Mark Miller commented on LUCENE-1791:
-------------------------------------
I'm guess the NAN failures are not a problem - looks like they fail because NAN
!= NAN ? Havn't looked closer.
I don't think the fieldcache insanity is multi-reader related - it looks to me
like some entries have a parser, and some null for the parser, even though the
default parser is being used in both cases. The FieldSource types grab a
FieldCache and may pass null as the parser, which ends up putting null in the
cache entry - but if you specifically ask for the default parser, that puts the
default parser in the fieldcache entry - same stuff now, doubled entry.
As for the out of bounds - havn't look at that one yet - odd one ...
> Enhance QueryUtils and CheckHIts to wrap everything they check in
> MultiReader/MultiSearcher
> -------------------------------------------------------------------------------------------
>
> Key: LUCENE-1791
> URL: https://issues.apache.org/jira/browse/LUCENE-1791
> Project: Lucene - Java
> Issue Type: Test
> Reporter: Hoss Man
> Fix For: 2.9
>
> Attachments: LUCENE-1791.patch
>
>
> methods in CheckHits & QueryUtils are in a good position to take any Searcher
> they are given and not only test it, but also test MultiReader &
> MultiSearcher constructs built around them
--
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
