[
https://issues.apache.org/jira/browse/LUCENE-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-2751:
---------------------------------
Attachment: LUCENE-2751.patch
Whew, this code is complex, and I don't really have a solution I like.
Here's a patch to IntValuesCreator that's only for brainstorming purposes...
- synchronize on the entry instead of the creator so more than one segment may
be loaded concurrently. This is needed to publish objects safely.
- when guessing the parser, don't set it until it succeeds - basically split up
setParserAndResetCounts() to set the counts first, but the parser last.
- when setting/checking the parser, we need to synchronize on the creator
I also just realized that the mere act of checking the cache creates objects
(see the base getCacheKey() ).
> 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: 4.0
>
> Attachments: LUCENE-2751.patch, 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]
