se a separate query parser for this obvious, common case is...
> absurd.
>
> (What does Elasticsearch do for this case??)
>
> -- Jack Krupansky
>
> -Original Message- From: Erick Erickson
> Sent: Tuesday, June 24, 2014 11:38 AM
> To: solr-user@lucene.apache.org ; A
o for this case??)
-- Jack Krupansky
-Original Message-
From: Erick Erickson
Sent: Tuesday, June 24, 2014 11:38 AM
To: solr-user@lucene.apache.org ; Ahmet Arslan
Subject: Re: No results for a wildcard query for text_general field in solr
4.1
Wildcards are a tough thing to get your head a
Wildcards are a tough thing to get your head around. I
think my first post on the users list was titled
"I just don't get wildcards at all" or something like that...
Right, wildcards aren't tokenized. So by getting your term
through the query parsing as a single token, including the
hyphen, when t
Hi Sven,
StandardTokenizerFactory splits it into two pieces. You can confirm this at
analysis page.
If this is something you don't want, lets us know.
We can help you to create an analysis chain that suits your needs.
Ahmet
On Tuesday, June 24, 2014 10:39 AM, Sven Schönfeldt
wrote:
Hi Erick
Hi Erick,
that is what i did, tried that input on analysis page.
The index field splitting the value into two words: „test“ and „or123"
Now checking the query at analysis page, and there are the word ist splitting
into „test“ and „or123“.
By doing the query and look into the debug result, i se
Well, you can do more than guess by looking at the admin/analysis page
and trying your input on the field in question. That'll show you what
actual transformations are performed.
You're probably right though. Try adding &debug=query to your URL to
see what the actual parsed query looks like and co
Hi Solr-Users,
i am trying to do a wildcard query on a dynamic textfield (_t), but don’t get
the right result.
The configuration for the field type is „text_general“, the default
configuration:
I
