I have a value "blume2000.de" in a field with the fieldtype above. If I issue a query with select?q=blume2000&qt=dismax (yes the provided field gets searched by dismax handler) and
the result is empty. Only if I enter the query select?q=blume+2000&qt=dismax I get the result I want.
So I used the debugQuery=true to find out what's wrong. The interesting thing is, that the rawquerystring is still correct, but the
+DisjunctionMaxQuery((name:"blume 2000" | teaser:"blume 2000")) DisjunctionMaxQuery((teaser:"blume 2000"~3 | name:"blume 2000"~3))
Now I gotta ask, where does the whitespace come from and why isn't the document matched?
If I analyze the query using the admin backend: Field(name): name Fieldvalue(Index): blume2000.de and Fieldvalue(Query): blume2000.de it works...
No, it didn't solve the problem, bit I got a different solution. I make
a second field in schema.xml and copy the content. This field gets
analyzed by the keywordtokenizer factory.
Am 24.08.2010 21:53, schrieb MitchK:
> try to remove the wordDelimiterFilter from the query-analyzer of your
> If your index-analyzer-wordDelimiterFilter is well configured, it will find
> everything you want.
> Does this solve the problem?
> Kind regards,
> - Mitch
keywordtokenizerfactory interprets the entire input as a single token, so
be a problem for you. For instance, the text:
bloom2000.de is some text
will get indexed as a single token. Seaches on "some" or "text" won't match.
may be what you're looking for, but....
I really think Mitch pointed you in the right direction.
was probably part of your problem. The stemmer might have done interesting
Also, if you didn't re-index after changing your schema, you might have had
the admin/analysis page can help you a lot in these situations.
On Tue, Aug 31, 2010 at 6:34 AM, Johann Höchtl <[hidden email]> wrote:
> No, it didn't solve the problem, bit I got a different solution. I make a
> second field in schema.xml and copy the content. This field gets analyzed by
> the keywordtokenizer factory.
> Am 24.08.2010 21:53, schrieb MitchK:
>> try to remove the wordDelimiterFilter from the query-analyzer of your
>> If your index-analyzer-wordDelimiterFilter is well configured, it will
>> everything you want.
>> Does this solve the problem?
>> Kind regards,
>> - Mitch