[
https://issues.apache.org/jira/browse/LUCENE-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139134#comment-14139134
]
Alan Woodward commented on LUCENE-5911:
---------------------------------------
Adding synchronized is a bit brute-force though.
The lazy-sorting bit is presumably for situations like highlighting where you
want to index a single document and run only a couple of queries over it as
quickly as possible. So maybe the answer is to have a derived class,
ThreadSafeMemoryIndex, which sorts the terms in the Info constructor. That way
if you want to use this in a lazily-instantiated way you continue to use
MemoryIndex, but luwak (and the percolator) would use TSMI instead.
I'll work on a patch.
> 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
> Priority: Minor
> Attachments: 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]
