Return-Path: X-Original-To: apmail-lucene-java-user-archive@www.apache.org Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1482611A9C for ; Fri, 22 Aug 2014 15:53:44 +0000 (UTC) Received: (qmail 31987 invoked by uid 500); 22 Aug 2014 15:53:42 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 31923 invoked by uid 500); 22 Aug 2014 15:53:42 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 31903 invoked by uid 99); 22 Aug 2014 15:53:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2014 15:53:42 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rolf.veen@gmail.com designates 209.85.160.169 as permitted sender) Received: from [209.85.160.169] (HELO mail-yk0-f169.google.com) (209.85.160.169) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2014 15:53:36 +0000 Received: by mail-yk0-f169.google.com with SMTP id 131so8778090ykp.0 for ; Fri, 22 Aug 2014 08:53:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=iJ3TFac1LYeKgOuUv7hZ1BX+fb25vPo/CE60m0jRFKo=; b=pYSRHKktILyTjOD3zTndRQ2shE5YhRY7Dl+tertJCw8RIpQoX/O5gQ4V/g8NC1uOPN o2yDfFJUex3FNOU2jnXEJkVvFyFmLGaevqquEn3aUOwTO0c0DvQ8REc42rR3HMQeGBNl kCm20VpfxF53xiRTMLYDV+HlcSMIT9NW2wYDfgv4cTQudxxrI9nj1ngEh3wdTsVgdP4K 9rmTtJu3OZpiCb7wUFDbzQW6zD3NO/gFd2Va+rf5v1OtOqvXcui6zlcGBF8Tb3bcEnEL LtQDrCzhu9E08w463wmtsnhEad6Gb50Fcc7/SxARxTLEu0WIP+eUFZmPOK9pHWgjU2oY v6oQ== X-Received: by 10.236.203.134 with SMTP id f6mr2791494yho.125.1408722796079; Fri, 22 Aug 2014 08:53:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.203.193 with HTTP; Fri, 22 Aug 2014 08:52:56 -0700 (PDT) From: Rolf Veen Date: Fri, 22 Aug 2014 17:52:56 +0200 Message-ID: Subject: IndexSearcher creation policy question To: java-user@lucene.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org I've this scenario in a web application: 1. many users query a Lucene index concurrently (obvious) 2. one user can make several queries (she may have different browser windows open) 3. all those queries need to have a consistent paging behavior (next, previous buttons) 4. The index can be updated at any time by users. What I understand is that: - I need a fresh IndexSearcher for each initial query (DirectoryReader.open -> reader -> searcher) and cannot use Search(Lifetime)Manager's. - I cannot share IndexSearchers in the depicted scenario; even for the same user, a different IndexSearcher is needed for each window. Is my understanding true ? What would be the best approach to handle this scenario ? Kind regards, Rolf. --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org