Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Fri, 24 Oct 2014 09:01:35 +0000 (UTC)
From: "Alan Woodward (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12737060.1409132796000.329787.1414141295103@Atlassian.JIRA>
In-Reply-To: <JIRA.12737060.1409132796000@Atlassian.JIRA>
References: <JIRA.12737060.1409132796000@Atlassian.JIRA>
 <JIRA.12737060.1409132796940@arcas>
Subject: [jira] [Updated] (LUCENE-5911) Make MemoryIndex thread-safe for
 queries
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/LUCENE-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Woodward updated LUCENE-5911:
----------------------------------
    Fix Version/s: 4.10.2

> 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: 4.10.2, 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org