Just escape them with a backslash. Or put each term in quotes.
-- Jack Krupansky
On Sun, Jan 24, 2016 at 5:21 AM, Jian Mou wrote:
> Hi Jack，
>
> Thanks! Do you know how to disable wildcards, What I want is if input is
> wildcards, just treat it as a normal char. I other words,
> I just want to
One option is to use the dismax (not edismax) as it does not support wild card
queries.
Erik
> On Jan 24, 2016, at 05:21, Jian Mou wrote:
>
> Hi Jack，
>
> Thanks! Do you know how to disable wildcards, What I want is if input is
> wildcards, just treat it as a normal char. I other words
Hi Jack，
Thanks! Do you know how to disable wildcards, What I want is if input is
wildcards, just treat it as a normal char. I other words,
I just want to disable wildcard search.
Thanks,
Jian
On Fri, Jan 22, 2016 at 1:55 PM, Jack Krupansky
wrote:
> The Lucene WildcardQuery class does have an
The Lucene WildcardQuery class does have an additional constructor that has
a maxDeterminizedStates parameter to limit the size of the FSM generated by
a wildcard queery, and the QueryParserBase class does have a method to set
that parameter, setMaxDeterminizedStates, but there is no Solr support f
We are using Solr as our search engine, and recently notice some user input
wildcard query can lead to Solr dead loop in
org.apache.lucene.util.automaton.Operations.determinize()
, and it also eats memory and finally OOM.
the wildcard query seems like **?-???o·???è??**。
Although we
