bq: Looks like the "qf=all phonetic" would take the place of my
existing "df=all" parameter.
In fact, it may call int question whether you even want an "all" field
or just list all the
fields you _would_ have copied into "all" in the "qf" parameter.
Having a single field
to search is certainly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Erick,
(Sorry... hit sent inadvertently before completion...)
On 3/12/18 2:50 PM, Erick Erickson wrote:
> Something like:
>
> solr/collection/query?q=chris shultz=edismax=all^10
> phonetic
Interesting. Looks like the "qf=all phonetic" would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Erick,
On 3/12/18 2:50 PM, Erick Erickson wrote:
> Something like:
>
> solr/collection/query?q=chris shultz=edismax=all^10
> phonetic
Interesting. Looks like the "qf=all phonetic" would take the place of
my existing "df=all" parameter.
> The
Something like:
solr/collection/query?q=chris shultz=edismax=all^10 phonetic
The point of edismax is to take whatever the input is and distribute
it among one or more fields defined by the "qf" parameter.
In this case, it'll look for "chris" and "shultz" in both the "all"
and "phonetic"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Erick,
On 3/12/18 1:36 PM, Erick Erickson wrote:
> Did you try edismax?
Err no, and I must admit that it's a lot to take in. Did you have
a particular suggestion for how to use it?
Thanks,
- -chris
> On Mon, Mar 12, 2018 at 10:20 AM,
Did you try edismax?
On Mon, Mar 12, 2018 at 10:20 AM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> All,
>
> I have a Solr index containing application user information (username,
> first/last, etc.). I have created an "all"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I have a Solr index containing application user information (username,
first/last, etc.). I have created an "all" field for the purpose of
using it as a default. It contains most but not all fields.
I recently added phonetic searching for the