[
https://issues.apache.org/jira/browse/LUCENE-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980484#action_12980484
]
Yonik Seeley commented on LUCENE-2751:
--------------------------------------
Hmmm, it looks like the committed patch serializes loading of caches of
multiple segments (for the same field?)
I had thought that the root of the problem was only when "parser" wasn't
specified and the creator attempted to guess? If so, it seems we could
synchronize only when the parser was not originally specified.
> add LuceneTestCase.newSearcher()
> --------------------------------
>
> Key: LUCENE-2751
> URL: https://issues.apache.org/jira/browse/LUCENE-2751
> Project: Lucene - Java
> Issue Type: Test
> Components: Build
> Reporter: Robert Muir
> Fix For: 3.1, 4.0
>
> Attachments: LUCENE-2751.patch, LUCENE-2751.patch
>
>
> Most tests in the search package don't care about what kind of searcher they
> use.
> we should randomly use MultiSearcher or ParallelMultiSearcher sometimes in
> tests.
--
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: [email protected]
For additional commands, e-mail: [email protected]
