: yes my default search field is text_sync.
fields and fieldTypes are differnet things -- you've shows us the
<fieldType />
for "text_sync" but not the <field /> ... with out that we can't be sure
you have things configured properly.
you also having shown us the debugQuery output to help us know exactly
what query is getting constructed in your tests.
: I think due to stemming I am not getting expected result. However when I am
: checking result from the analysis.jsp,
analysis.jsp only shows you what the *analyzer* produces at index time vs
query time, it doesn't tell you anything how the query parser is going to
behave (and the query parser decides wich analyzer to use and how/when)
In particular whitespace is "special" to the default query parser, so even
though you have a KeywordTokenizer in your "query" analyzer, a query like
this...
/select?q=what+is+the+question?
..is going to result in the individual chunks of input "what", "is", and
"the" being passed to your analyzer ("question?" won't even be analyzed,
because the "?" mark is also special syntax that gets converted to a wild
card query)
the only way this will posisble work the way you want is if you quote the
entire input and/or use something like the the "field" or "raw"
QParserPlugin...
/select?q="what+is+the+question?"
/select?q={field}what+is+the+question?
/select?q={raw}what+is+the+question?
furthermore: assuming the field type you showed us is getting used, there
is no possibility that stemming is entering the equaion -- you have no
stemming configured, it's not used magically.
-Hoss
