[
https://issues.apache.org/jira/browse/LUCENE-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991130#comment-12991130
]
Uwe Schindler commented on LUCENE-2907:
---------------------------------------
Have you found out what happens or where a thread-safety issue could be? Each
thread and each query should have its own TermsEnum! Is there maybe a cache on
codec-level involved? At least there are no multiple-instance (static) caches
in the search-side of the TermsEnums, so there must be a multi-threading issue
in the underlying SegmentReaders.
To conclude: At least Robert found out that FieldCacheTermsEnum always works
correct? Is this true? The information on this issue is too small, there seems
to be lots of IRC/GTalk communication in parallel.
> termsenum bug when running with multithreaded search
> ----------------------------------------------------
>
> Key: LUCENE-2907
> URL: https://issues.apache.org/jira/browse/LUCENE-2907
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Robert Muir
> Attachments: LUCENE-2907_repro.patch, correct_seeks.txt,
> incorrect_seeks.txt, seeks_diff.txt
>
>
> This one popped in hudson (with a test that runs the same query against
> fieldcache, and with a filter rewrite, and compares results)
> However, its actually worse and unrelated to the fieldcache: you can set both
> to filter rewrite and it will still fail.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
