[
https://issues.apache.org/jira/browse/LUCENE-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Woodward updated LUCENE-5911:
----------------------------------
Attachment: LUCENE-5911-2.patch
Good catch, David.
Here's a patch implementing Rob's idea (although I've used a map of
String->NumericDocValues rather than an Array). It also changes how
Similarities are set, because you now need the Similarity to be known before
freeze() is called. This is a bit nicer than the current API, I think, whereby
if you want to change the Similarity you have to get an IndexSearcher and then
call setSimilarity on it.
> Make MemoryIndex thread-safe for queries
> ----------------------------------------
>
> Key: LUCENE-5911
> URL: https://issues.apache.org/jira/browse/LUCENE-5911
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Priority: Minor
> Fix For: 5.0, Trunk
>
> Attachments: LUCENE-5911-2.patch, LUCENE-5911.patch, LUCENE-5911.patch
>
>
> We want to be able to run multiple queries at once over a MemoryIndex in
> luwak (see
> https://github.com/flaxsearch/luwak/commit/49a8fba5764020c2f0e4dc29d80d93abb0231191),
> but this isn't possible with the current implementation. However, looking
> at the code, it seems that it would be relatively simple to make MemoryIndex
> thread-safe for reads/queries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
