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 5885B17583 for ; Thu, 2 Oct 2014 16:25:37 +0000 (UTC) Received: (qmail 9362 invoked by uid 500); 2 Oct 2014 16:25:33 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 9289 invoked by uid 500); 2 Oct 2014 16:25:33 -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 9229 invoked by uid 99); 2 Oct 2014 16:25:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Oct 2014 16:25:33 +0000 X-ASF-Spam-Status: No, hits=4.5 required=5.0 tests=HTML_MESSAGE,SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of waynemailinglists@gmail.com does not designate 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Oct 2014 16:25:28 +0000 Received: from ben.nabble.com ([192.168.236.152]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1XZjBk-0001X6-0Y for solr-user@lucene.apache.org; Thu, 02 Oct 2014 09:25:08 -0700 Date: Thu, 2 Oct 2014 09:25:08 -0700 (PDT) From: waynemailinglist To: solr-user@lucene.apache.org Message-ID: In-Reply-To: <542D5344.40807@elyograg.org> References: <1412167209477-4162086.post@n3.nabble.com> <1412183455089-4162150.post@n3.nabble.com> <1412246023646-4162284.post@n3.nabble.com> <542D5344.40807@elyograg.org> Subject: Re: Wildcard search makes no sense!! MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_134445_14240835.1412267108003" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_134445_14240835.1412267108003 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Ok I think I understand your points there. Just clarify say if the term was "Large increased" and my filters went something like: Large|increased Large|increase|increased large|increase|increased the final tokens indexed would be large|increase|increased ? Once again thanks for all the help. On Thu, Oct 2, 2014 at 2:30 PM, Shawn Heisey-2 [via Lucene] < ml-node+s472066n4162306h96@n3.nabble.com> wrote: > On 10/2/2014 4:33 AM, waynemailinglist wrote: > > > Something that is still not clear in my mind is how this tokenising > works. > > For example with the filters I have when I run the analyser I get: > > Field: Hello You > > > > Hello|You > > Hello|You > > Hello|You > > hello|you > > hello|you > > > > > > Does this mean that the index is stored as 'hello|you' (the final one) > and > > that when I run a query and it goes through the filters whatever the end > > result of that is must match the 'hello|you' in order to return a > result? > > The index has two terms for this field if this is the whole input -- > hello and you -- which can be searched for individually. The tokenizer > does the initial job of separating the input into tokens (terms) ... > some filters can create additional terms, depending on exactly what's > left when the tokenizer is done. > > Thanks, > Shawn > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://lucene.472066.n3.nabble.com/Wildcard-search-makes-no-sense-tp4162069p4162306.html > To unsubscribe from Wildcard search makes no sense!!, click here > > . > NAML > > -- View this message in context: http://lucene.472066.n3.nabble.com/Wildcard-search-makes-no-sense-tp4162069p4162349.html Sent from the Solr - User mailing list archive at Nabble.com. ------=_Part_134445_14240835.1412267108003--