This turns out to have indeed been due to a recent, but un-announced, index 
format change.  A rebuilt index worked properly.

Thanks!
Karl

________________________________________
From: ext [email protected] [[email protected]]
Sent: Monday, January 17, 2011 10:53 AM
To: [email protected]
Subject: RE: Query parser contract changes?

Another data point: the standard query parser actually ALSO fails when you do 
anything other than a *:* query.  When you specify a field name, it returns 
zero results:

root@duck93:/data/solr-dym/solr-dym# curl 
"http://localhost:8983/solr/nose/standard?q=value_0:a*";
<?xml version="1.0" encoding="UTF-8"?>
<response>
<lst name="responseHeader"><int name="status">0</int><int name="QTime">7</int><l
st name="params"><str name="q">value_0:a*</str></lst></lst><result name="respons
e" numFound="0" start="0"/>
</response>

But:

root@duck93:/data/solr-dym/solr-dym# curl 
"http://localhost:8983/solr/nose/standard?q=*:*";
<?xml version="1.0" encoding="UTF-8"?>
<response>
<lst name="responseHeader"><int name="status">0</int><int name="QTime">244</int>
<lst name="params"><str name="q">*:*</str></lst></lst><result name="response" nu
mFound="59431646" start="0"><doc><str name="latitude">40.55856</str><str name="l
ongitude">44.37457</str><str name="reference">LANGUAGE=und|TYPE=STREET|ADDR_TOWN
SHIP_NAME=Armenia|ADDR_COUNTRY_NAME=Armenia|ADDR_STREET_NAME=A329|TITLE=A329, Ar
menia, Armenia</str></doc><doc><str name="latitude">40.7703</str><str name="long
itude">43.838</str><str name="reference">LANGUAGE=und|TYPE=STREET|ADDR_TOWNSHIP_
NAME=Armenia|ADDR_COUNTRY_NAME=Armenia|ADDR_STREET_NAME=A330|TITLE=A330, Armenia
…

The schema has not changed:

                <!-- Level 0 non-language value field -->
                <field name="othervalue_0" type="string_idx_normed" 
required="false"/>

…where string_idx_normed is declared in the following way:

                <fieldType name="string_idx_normed" class="solr.TextField"
                        indexed="true" stored="false" omitNorms="false">
                        <analyzer type="index">
                                <tokenizer class="solr.ICUTokenizerFactory" />
                                <filter class="solr.ICUFoldingFilterFactory" />
                        </analyzer>
                        <analyzer type="query">
                                <tokenizer class="solr.ICUTokenizerFactory" />
                                <filter class="solr.ICUFoldingFilterFactory" />
                        </analyzer>
                </fieldType>

… which shouldn’t matter anyway because even a simple TermQuery return from my 
query parser method doesn’t work any more.

Karl

From: ext [email protected] [mailto:[email protected]]
Sent: Monday, January 17, 2011 10:30 AM
To: [email protected]
Subject: Query parser contract changes?

Hi folks,

I’m sorely puzzled by the fact that my QParser implementation ceased to work 
after the latest Solr/Lucene trunk update.  My previous update was about ten 
days ago, right after Mike made his index changes.

The symptom is that, although the query parser is correctly called, and seems 
to have the right arguments, the Query it is returning seems to be ignored.  I 
always get zero results.  I eliminated any possibility of error by just 
hardwiring the return of a TermQuery, and that too always yields zero results.

I was able to confirm, using the standard handler with the default query 
parser, that the index is in fine shape.  So I was wondering if the contract 
for QParser had changed in some subtle way that I missed?

Karl


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to