ick, thank you so much for this. I'm going to try to implement with
>>> PatternReplaceCharFilterFactory as you recommended.
>>> What you mentioned about re-indexing from an empty state made sense to me
>>> (in terms of the observed behavior) but also surprised me.
> Teresa
> >
> >
> > -Original Message-
> > From: Erick Erickson
> > Sent: Friday, April 3, 2020 7:16 PM
> > To: solr-user@lucene.apache.org
> > Subject: Re: match string fields with embedded hyphens
> >
> > First, thanks for takin
he reindex, does it *not* start from an empty state?
Thanks!!
Teresa
-Original Message-
From: Erick Erickson
Sent: Friday, April 3, 2020 7:16 PM
To: solr-user@lucene.apache.org
Subject: Re: match string fields with embedded hyphens
First, thanks for taking the time to write up a cle
: I am working with a customer who needs to be able to query various
: account/customer ID fields which may or may not have embedded dashes.
: But they want to be able to search by entering the dashes or not and by
: entering partial values or not.
:
: So we may have an account or customer
First, thanks for taking the time to write up a clear problem statement.
Putting in the field type is _really_ helpful.
By “partial string match”, I’m assuming you’re using wildcards, i.e. 123*. The
problem is that wildcards are tricky, and this trips everybody up at one time
or another.
The
Forgive me if this is unclear, I am very much new here.
I am working with a customer who needs to be able to query various
account/customer ID fields which may or may not have embedded dashes. But they
want to be able to search by entering the dashes or not and by entering partial
values or