I just tried this on trunk and both with and without a field selector
it parses to a PhraseQuery. I have trouble believing even Solr 1.3
behaved like you reported, something seems fishy.
Erik
On Sep 18, 2009, at 9:02 AM, DHast wrote:
well it seems what is happening is solr is not being consistent,
DHast wrote:
hi,
if i do a search: text:"law order"~40
i get this:
<str name="rawquerystring">text:"law order"~40</str>
<str name="querystring">text:"law order"~40</str>
<str name="parsedquery">PhraseQuery(text:"law order"~40)</str>
<str name="parsedquery_toString">text:"law order"~40</str>
<str name="QParser">OldLuceneQParser</str>
However if i do: "law order"~40
i get this:
<str name="rawquerystring">"law order"~40</str>
<str name="querystring">"law order"~40</str>
<str name="parsedquery">text:law order</str>
<str name="parsedquery_toString">text:law order</str>
<lst name="explain"/>
<str name="QParser">OldLuceneQParser</str>
my Schema xml:
<field name="text" type="string" indexed="true" stored="false" />
.....
<defaultSearchField>text</defaultSearchField>
what should i be doing differently to get the second results like the
first?
--
View this message in context:
http://www.nabble.com/solr-isnt-using-default-field-correctly-tp25507985p25508264.html
Sent from the Solr - User mailing list archive at Nabble.com.
