Return-Path: X-Original-To: apmail-lucene-general-archive@www.apache.org Delivered-To: apmail-lucene-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C563BDCEE for ; Thu, 15 Nov 2012 21:09:07 +0000 (UTC) Received: (qmail 15445 invoked by uid 500); 15 Nov 2012 21:09:07 -0000 Delivered-To: apmail-lucene-general-archive@lucene.apache.org Received: (qmail 15400 invoked by uid 500); 15 Nov 2012 21:09:07 -0000 Mailing-List: contact general-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@lucene.apache.org Delivered-To: mailing list general@lucene.apache.org Received: (qmail 15391 invoked by uid 99); 15 Nov 2012 21:09:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Nov 2012 21:09:07 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dalyea@gmail.com designates 209.85.212.48 as permitted sender) Received: from [209.85.212.48] (HELO mail-vb0-f48.google.com) (209.85.212.48) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Nov 2012 21:09:00 +0000 Received: by mail-vb0-f48.google.com with SMTP id l22so36494vbn.35 for ; Thu, 15 Nov 2012 13:08:39 -0800 (PST) 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=w7DCaLT3hcsIGXNyaMwdwayJgKXTzfE23jiTTUj0Fdg=; b=Oq/FBZJL7u0Fho0JFJ1IkSKc7lUXVolE95zkrLtMcG2LG1NpjjpdYEF3sTqhJkSEdQ 0DbYUZea4PfGz2dsSb4B/8W0nN4gGD5A2W3pcZZnqYSQRFzDxdJmTOWt/FwR/lpUUdcG wvNvhbjvuARxbAsvpgzPHeeZJ1J+PiyP1VZE7DFgDZKzIRlk9ycCoTE2mtu/mWLv0yKD 7g84f5O1qCbEgWXU7iVT4JZZRqN+fgvefGFZ+R7e8XxkJYcat6NKrHKVEdigLPVeytVO aEIpDmS8EFztLHEx0hSuRb38DHIpGjjsRXxO/0quQXgh/V65PzNNUPHtMgLBQzNVguS9 sQpw== MIME-Version: 1.0 Received: by 10.59.13.135 with SMTP id ey7mr960960ved.37.1353013718987; Thu, 15 Nov 2012 13:08:38 -0800 (PST) Received: by 10.58.161.10 with HTTP; Thu, 15 Nov 2012 13:08:38 -0800 (PST) In-Reply-To: <1353012866.22758.140661154181841.60B2D853@webmail.messagingengine.com> References: <1353012866.22758.140661154181841.60B2D853@webmail.messagingengine.com> Date: Thu, 15 Nov 2012 16:08:38 -0500 Message-ID: Subject: Re: How to wildcard From: David Alyea To: general@lucene.apache.org Content-Type: multipart/alternative; boundary=089e011767dd18b43104ce8f0e92 X-Virus-Checked: Checked by ClamAV on apache.org --089e011767dd18b43104ce8f0e92 Content-Type: text/plain; charset=ISO-8859-1 Thanks for the suggestion. I tried that, putting it in my index section. I deleted the entire collection, stopped solr, restarted it, added back all my documents, and committed. Basically, I followed the exact same protocol I always do. When I searched for "sm3 carbon" I got nothing - if I just searched for "carbon", nothing. Looking at the solr admin panel, the document count was right. But any select I ran returned 0 results. So something about that in the index section didn't work. Any ideas? I definitely like the way this would potentially work. On Thu, Nov 15, 2012 at 3:54 PM, Upayavira wrote: > You could use a solr.EdgeNGramFilterFactory, which would index > edge-ngrams, thus: > > Exustar: > ex > exu > exus > exust > exusta > exustar > > SM312 > sm > sm3 > sm31 > sm312 > > etc > > This would make your indexing slower, and your index bigger, but your > queries would be faster and you wouldn't need to infix wildcard * > characters within your query string (which is always risky). > > Upayavira > > On Thu, Nov 15, 2012, at 05:44 PM, David Alyea wrote: > > I'm coming from the world of having perfected grep searching, > > and now I'm using solr with great results so far. Still, I have some > > searches I'm trying to figure out. > > > > My users might be searching for: > > > > Exustar SM312 Carbon Mountain Bike Shoes > > > > by typing in the search "sm3 carbon". Then want to see > > all the SM312, SM345, SM389 and other matching shoes. > > > > Right now, my solr search misses all of these shoes. My solr > > setup is pretty standard, I've only added these filters to my > > main text search field: > > > > to index: > > > > > > > > > > to query: > > > > > > Any recommendations on how to handle wildcarding in this case? > --089e011767dd18b43104ce8f0e92--