Thank you for the heads up! I think in some cases we will want to strip out
punctuation but in others we might need it (for example, "liquid courage."
should tokenize to "liquid" and "courage", while "1.5 oz liquid courage"
should tokenize to "1.5", "oz", "liquid" and "courage").
I'll have to do
Wow, that's really powerful! Thank you!
On Thu, Mar 16, 2017 at 11:19 AM, Charlie Hull wrote:
> Hi Mark,
>
> Open Source Connection's excellent www.splainer.io might also be useful to
> help you break down exactly what your query is doing.
>
> Cheers
>
> Charlie
>
> P.S.
Hi Mark,
Open Source Connection's excellent www.splainer.io might also be useful to
help you break down exactly what your query is doing.
Cheers
Charlie
P.S. planning a blog soon listing 'useful Solr tools'
On 16 March 2017 at 14:39, Mark Johnson
wrote:
>
Yeah, they've saved me on numerous occasions, glad to see they helped.
One caution BTW when you start changing fieldTypes is you have to
watch punctuation. StandardTokenizerFactory won't pass through most
punctuation.
WordDelimiterFilterFactory breaks on non alpha-num, including
punctuation
You're right! The fields I'm searching are all "string" type. I switched to
"text_en" and now it's working exactly as I need it to! I'll do some
research to see if "text_en" or another "text" type field is best for our
needs.
Also, those debug options are amazing! They'll help tremendously in the
My guess: Your analysis chain for the fields is different, i.e. they
have a different fieldType. In particular, watch out for the "string"
type, people are often confused about it. It does _not_ break input
into tokens, you need a text-based field type, text_en is one example
that is usually in
Oh, great! Thank you!
So if I switch over to eDisMax I'd specify the fields to query via the "qf"
parameter, right? That seems to have the same result (only matches when I
specify the exact phrase in the field, not just certain words from it).
On Thu, Mar 16, 2017 at 9:33 AM, Alexandre
df is default field - you can only give one. To search over multiple
fields, you switch to eDisMax query parser and fl parameter.
Then, the question will be what type definition your fields have. When you
search text field, you are using its definition because of copyField. Your
original fields
Forgive me if I'm missing something obvious -- I'm new to Solr, but I can't
seem to find an explanation for the behavior I'm seeing.
If I have a document that looks like this:
{
field1: "aaa bbb",
field2: "ccc ddd",
field3: "eee fff"
}
And I do a search where "q" is "aaa ccc", I get