I just wanted other readers to be clear about what can be made to work quite
easily.
As to "speedPost" as a quoted phrase, that's a different beast entirely due
to the semantics of phrases, which is that they are an implicit "AND"
operator - all tokens must match - and you and your users must be aware that
camel case is generating multiple tokens. So, ALL of the generated WDF
tokens must match - which does in fact happen if the content has the term
"speedPost", but not in the case of content only containing "speedpost".
The WDF does not have any magic and cannot make all cases work. It's up to
you, the Solr app developer to decide which cases have the highest priority
for you and then to accept the cases that won't work given your priorities.
Maybe that caveat wasn't made clearly enough for you early enough on.
And if really need to get an absolute 100% of all cases, which most Solr
applications do not, you will need to do application-specific query
filtering in your application layer in front of Solr.
-- Jack Krupansky
-----Original Message-----
From: vicky desai
Sent: Tuesday, August 20, 2013 8:28 AM
To: solr-user@lucene.apache.org
Subject: Re: struggling with solr.WordDelimiterFilterFactory
Hi Jack,
As mentioned earliear a part of the issue was resolved by the two fixes I
mentioned above and for the query u mentioned I am getting the same result
as yours.
What is not working though is the query *q=content:"speedPost"* with the
text enclosed in inverted commas
--
View this message in context:
http://lucene.472066.n3.nabble.com/struggling-with-solr-WordDelimiterFilterFactory-tp4085021p4085658.html
Sent from the Solr - User mailing list archive at Nabble.com.
