: Anyone who *wants* a phrase query can ask for one with double quotes.
: If you force this option on, users have no way to turn it off.
:
: I'm strongly opposed. I could care less about english.
Hold on a minute and think about what jack is pointing out here.
I can understand your argument against Jack's examples that refer to WDF,
because the only places WDF is used in the example schema is in fieldTypes
where we already include autoGeneratePhraseQueries="true"
But i didn't realize until Jack's email that StandardTokenizerFactory
splits on "-" .. meaning that any hypenated word is split into multiple
tokens, and (by default) produces a BooleanQuery with all SHOULD clauses.
It's easy to say users who want a phrase query can use quotes, but i
suspect most people aren't going to realize they need to explicitly ask
for a phrase query, because they have no idea that their input is going to
be split up.
Can you honestly say you think it makes sense that someone who types
in...
fly-fishing
...will get match on documents containing either "fly" or "fishing" using
the example "text_general" fieldType?
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
