[ 
https://issues.apache.org/jira/browse/LUCENE-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991133#comment-12991133
 ] 

Robert Muir commented on LUCENE-2907:
-------------------------------------

bq. Have you found out what happens or where a thread-safety issue could be?

Yes, i found the bug... unfortunately it is actually my automaton problem :(
I will create a nice patch today.

bq. The information on this issue is too small, there seems to be lots of 
IRC/GTalk communication in parallel.

what do you mean? mike was working a long time on the bug, but quickly had to 
stop working on it, so he emailed me all of his state. I took over from there 
for a while, and i opened this issue with my debugging... though I didn't have 
much time to work on it yesterday (only like 1 hour), because I already had 
plans.

I tried to be completely open and dump all of my state/debugging 
information/brainstorming on this JIRA issue, but it only resulted in me 
reporting misleading and confusing information... so I think the information on 
this issue is actually too much?


> 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]

Reply via email to