This is caused by the word delimiter filter - it breaks multi-part terms
(the hyphens trigger it) into multiple terms. Wildcards simply don't work
consistently well in such a situation. The basic problem is that the
presence of the wildcard causes all but the simplest token filtering stages
to be b
Hi,
Have a look at the generated terms to see how they look.
Simon
On Thu, Apr 2, 2015 at 9:43 AM, Palagiri, Jayasankar <
jayashankar.palag...@honeywell.com> wrote:
> Hello Team,
>
> Below is my field type
>
> positionIncrementGap="100" autoGeneratePhraseQueries="true">
>
>
>
Hello Team,
Below is my field type
And my field is
I have few docunets in my index
Like 1234-305, 1234-308,1234-318.
In case it helps, here's what I have currently, but I've been messing with
different options:
-Original Message-
From: Carr, Adrian [mailto:adrian.c...@jtv.com]
Sent: Friday, September 25, 2009 9:28 AM
To: solr-user@lucene.apache.org
Subject: RE: Alphanumeric Wild C
. There has got to be a simple solution for
this, but it is sure eluding me.
Thanks,
Adrian
-Original Message-
From: Ensdorf Ken [mailto:ensd...@zoominfo.com]
Sent: Thursday, September 24, 2009 5:03 PM
To: solr-user@lucene.apache.org
Subject: RE: Alphanumeric Wild Card Search Questi
> Here's my question:
> I have some products that I want to allow people to search for with
> wild cards. For example, if my product is YBM354, I'd like for users to
> be able to search on "YBM*", "YBM3*", "YBM35*" and for any of these
> searches to return that product. I've found that I can search
