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 362A810852 for ; Tue, 8 Oct 2013 01:43:46 +0000 (UTC) Received: (qmail 57913 invoked by uid 500); 8 Oct 2013 01:43:42 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 57793 invoked by uid 500); 8 Oct 2013 01:43:42 -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 57785 invoked by uid 99); 8 Oct 2013 01:43:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Oct 2013 01:43: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 erickerickson@gmail.com designates 209.85.220.171 as permitted sender) Received: from [209.85.220.171] (HELO mail-vc0-f171.google.com) (209.85.220.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Oct 2013 01:43:37 +0000 Received: by mail-vc0-f171.google.com with SMTP id ks9so624983vcb.30 for ; Mon, 07 Oct 2013 18:43:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Y89mapquUvebrKLYWeQHPcpOaEa+whfknE5wMfYIkc4=; b=NuBsf27vLC62gQAhKRrOUFT8bS2C1UhBd9456NbAqRwMtts1uyKaoHIvx9NtcuTapz vctF21B5+OHazMGmII6sZVCrAGdB9HmtIojPSqDR/4KQGgjLe94qQZjNzRSsJKAWbpaK Xk9ml9nCspqPr7kxZLiKT1xLVfBT2UOc2jY9xrM2QKi1jNIyyj7WOur0BHwDyHP+7OyG IjDH3zcHFpECoGkJZN4pBsYeghjWBE5mdTtqZ6v59WJOxSU+jXhClEooe8soUw7f6GQT /vtG+wP/R5LSwPsBxTjWcisI/k3/0W7v4fed/vj+X+vaM1TzXkcKFwXnJAMqrpfo6QyE WDlQ== MIME-Version: 1.0 X-Received: by 10.52.243.138 with SMTP id wy10mr24599692vdc.2.1381196596270; Mon, 07 Oct 2013 18:43:16 -0700 (PDT) Received: by 10.52.186.228 with HTTP; Mon, 7 Oct 2013 18:43:16 -0700 (PDT) In-Reply-To: References: Date: Mon, 7 Oct 2013 21:43:16 -0400 Message-ID: Subject: Re: Regarding edismax parsing From: Erick Erickson To: solr-user@lucene.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org You're probably having problem with the distinction between query parsing and analysis which has been discussed many times. The issues is that the query parser breaks things up into individual tokens and _then_ sends them to the analyzer chain as individual tokens (usually). Try escaping your spaces. Best Erick On Mon, Oct 7, 2013 at 8:28 AM, Prashant Golash wrote: > Hi, > > I have a question regarding to parsing of tokens in edismax parser and > subsequently a follow up question related to same. > > - Each field has list of analyzers and tokenizers as configured in > schema.xml (Index and query time). Now, say I search for query - red shoes. > So, is it like that for forming Disjunction query on each field, edismax > will first apply analyzers configured to that field, and then form the > query. For e.g if field1 has changes red to rd and field2 changes red to > re, query will be like - (field1:rd) | (field2:re) ? > > > - If above holds true, then when I changed ordering of analyzers and put > "SynonymFilterFactory" at top of all analyzers (in schema.xml), edismax > still tokenizes the query first with respect to space and then only apply > synonym filter factory, which leads me to think that this is not happening. > My use case is like , before applying any tokenizer, I want to support > phrase level synonym replacement and do rest of analysis. > > Thanks, > Prashant Golash