From solr-user-return-100084-apmail-lucene-solr-user-archive=lucene.apache.org@lucene.apache.org Sun May 11 03:16:23 2014 Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3DCEC11319 for ; Sun, 11 May 2014 03:16:23 +0000 (UTC) Received: (qmail 55705 invoked by uid 500); 10 May 2014 23:23:39 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 3758 invoked by uid 500); 10 May 2014 23:03:49 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 7458 invoked by uid 99); 10 May 2014 22:56:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 May 2014 22:56:51 +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 msokolov@safaribooksonline.com designates 209.85.216.174 as permitted sender) Received: from [209.85.216.174] (HELO mail-qc0-f174.google.com) (209.85.216.174) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 May 2014 13:08:18 +0000 Received: by mail-qc0-f174.google.com with SMTP id x13so4416339qcv.5 for ; Fri, 09 May 2014 06:07:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=safaribooksonline.com; s=google; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=1Gb2n2+xGn7E0u7NZHN8fqoYJdkljHd1hI6BcKTn0o0=; b=MnaHGyHxkKhxW8TpJt53nOvDqEqp56w+cY1rUPL82DaD+QuupbNZkBIo9UAkrObqG5 OE4GRZLJe/EeHVxIM5k818k9ZvvBlSw4dDd1sr6N535qTV5ySJSwxRxsLOW2TGr/kujf CUjW7A9agj+3dRKdWeksX/qenz0EfYbaL006c= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=1Gb2n2+xGn7E0u7NZHN8fqoYJdkljHd1hI6BcKTn0o0=; b=UPG6lqZm5DfvtoWFSKAnGFfq/Jwmoo2FowGemPpFQHqVQ4rTrZX9rnxCxWcXP4HLIH TKa7vU1gG1eudnvblpCG4SglcDaPune0smNGVDiqMmyMXGuLx1hXQhWXc7CgnExaG1Ma avYQmsAx8nG48gPk8ESxgvTjykBtOHzQHNYI7dtbTI6rJ+EIGEl34qJyNPnXfO31OCnW nx0gIa/UQVqs2RNTKRBjIvMEOLKj4HVrbmoFIS4KHroUlc1zcuZiRijsC/VrTZcABYWl UoUyOdA2aj75esjWHpB88ISBBiJMYb46ZiXmf1sPtkt4Soj+JVWD5Y7CqaMoDksLrDHt z3EA== X-Gm-Message-State: ALoCoQn18wrhLpX9xrHUIQYzQjvkWCem87ENXguwLZkb7y26ykYumJEIVo9NcdO4IK8kLHyrWA2L X-Received: by 10.229.89.65 with SMTP id d1mr14283579qcm.14.1399640877756; Fri, 09 May 2014 06:07:57 -0700 (PDT) Received: from [192.168.1.3] (pool-71-174-254-95.bstnma.fios.verizon.net. [71.174.254.95]) by mx.google.com with ESMTPSA id w14sm6553980qaw.11.2014.05.09.06.07.56 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 09 May 2014 06:07:56 -0700 (PDT) Message-ID: <536CD32E.40000@safaribooksonline.com> Date: Fri, 09 May 2014 09:07:58 -0400 From: Michael Sokolov User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "solr-user@lucene.apache.org" Subject: AnalyzingInfixLookupFactory with multiple cores Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org It seems as if the location of the suggester dictionary directory is not core-specific, so when the suggester is defined for multiple cores, they collide: you get exceptions attempting to obtain the lock, and the suggestions bleed from one core to the other. There is an (undocumented) "indexPath" parameter that can be used to control this, so I think I can work around the problem using that, but it would be a nice feature if the suggester index directory were relative to the core directory rather than the current working directory of the process. Question: is the current core directory (or even its name) available as a variable that gets substituted in solrconfig.xml? I.e. ${core-name} or something? -Mike