[
https://issues.apache.org/jira/browse/LUCENE-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757263#action_12757263
]
Jason Rutherglen commented on LUCENE-1919:
------------------------------------------
For SOLR-908, I can try out the patch, though we've reverted
back to Solr trunk from 8/31, unfortunately, I can't reproduce
the bug using a multithreaded query parsing unit test.
I decided the best avenue, given it must be thread related to
behave so randomly, is to alter QueryParser.getFieldQuery to not
call analyzer.reusableTokenStream and only use
analyzer.tokenStream.
This effectively avoids the use of threadlocal reusable
tokenstreams for query parsing. I am left wondering about the
state of our index using reusable tokenstreams but luckily we
have so many documents, that this is less of a concern.
The queries being truncated is of course very serious as users
see irrelevant results and assume that Lucene/Solr 2.9/1.4 is no
good.
> Analysis back compat break
> --------------------------
>
> Key: LUCENE-1919
> URL: https://issues.apache.org/jira/browse/LUCENE-1919
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Yonik Seeley
> Assignee: Uwe Schindler
> Fix For: 2.9
>
> Attachments: LUCENE-1919.patch, LUCENE-1919.patch, LUCENE-1919.patch,
> LUCENE-1919.patch, LUCENE-1919.patch, LUCENE-1919.patch
>
>
> Old and new style token streams don't mix well.
--
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
