Return-Path: 
 <general-return-3971-apmail-lucene-general-archive=lucene.apache.org@lucene.apache.org>
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 BBE96D146
	for <apmail-lucene-general-archive@www.apache.org>;
 Thu, 15 Nov 2012 17:45:21 +0000 (UTC)
Received: (qmail 49430 invoked by uid 500); 15 Nov 2012 17:45:21 -0000
Delivered-To: apmail-lucene-general-archive@lucene.apache.org
Received: (qmail 49347 invoked by uid 500); 15 Nov 2012 17:45:20 -0000
Mailing-List: contact general-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:general-help@lucene.apache.org>
List-Unsubscribe: <mailto:general-unsubscribe@lucene.apache.org>
List-Post: <mailto:general@lucene.apache.org>
List-Id: <general.lucene.apache.org>
Reply-To: general@lucene.apache.org
Delivered-To: mailing list general@lucene.apache.org
Received: (qmail 49331 invoked by uid 99); 15 Nov 2012 17:45:20 -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 17:45:20 +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 17:45:12 +0000
Received: by mail-vb0-f48.google.com with SMTP id e21so2278920vbm.35
        for <general@lucene.apache.org>; Thu, 15 Nov 2012 09:44:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=olVDUvxXAewRJVq+Kn6Sl5ke9FsphclpuIfpqdNscS8=;
        b=Q0+vYEOXjG+3wMukN7JxUHZd+TIioGlu41YWFqx/6IYSdFyB0bSprIXBxuaL07wmyB
         px73z06gbPCdtkfHG4tDbcekD4ufS+Ywqz6/1kQl4sc/a/augMMPg6En+iZ22yXFOx5V
         s5uXc081QFFuuFrRUjOYtMj3o2m4m2D14ND3Ozd8F8y7cj51ffvPw5h8xVzX3S0S3YNx
         th7jbN1VbpHjNj94RQlxl3Ad8ZhwkyZeZhxp5lZuL7kGLw7dl2JhxpxP5XTqYsd4ITpm
         mpfJYdeUi804Qi/dJWbYfDrZsE8cpVb6FJHobxHkR+25Ldxxz8VopLd9FtIZnb6gg/B3
         E/aA==
MIME-Version: 1.0
Received: by 10.52.64.209 with SMTP id q17mr2146376vds.32.1353001491741; Thu,
 15 Nov 2012 09:44:51 -0800 (PST)
Received: by 10.58.161.10 with HTTP; Thu, 15 Nov 2012 09:44:51 -0800 (PST)
Date: Thu, 15 Nov 2012 12:44:51 -0500
Message-ID: 
 <CA+SiMXsBfS=uane0UXfA1wcE68-TLQNN=qkgq5yJNR9PG5dWVQ@mail.gmail.com>
Subject: How to wildcard
From: David Alyea <dalyea@gmail.com>
To: general@lucene.apache.org
Content-Type: multipart/alternative; boundary=20cf307f3a9e4bbcb204ce8c356a
X-Virus-Checked: Checked by ClamAV on apache.org

--20cf307f3a9e4bbcb204ce8c356a
Content-Type: text/plain; charset=ISO-8859-1

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:
<filter class="solr.PorterStemFilterFactory"/>
<filter class="solr.KStemFilterFactory"/>
<filter class="solr.EnglishMinimalStemFilterFactory"/>

to query:
<filter class="solr.SnowballPorterFilterFactory" language="English" />

Any recommendations on how to handle wildcarding in this case?

--20cf307f3a9e4bbcb204ce8c356a--