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 <[email protected]> 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: > > <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? >
