It was a surprise to discover that
dateorigin_sort:""
is a syntax error, but
dateorigin_sort:["" TO *]
is legit. This says that there's a bug in the Lucene syntax parser?
Anyway, with a little more research I discover that this query:
http://64.71.164.205:8080/solr/select/?q=*:*&version=2.2&start=0&rows=0&;
indent=on&facet=true&facet.field=dateorigin_sort&facet.mincount=0&facet.
sort=false
.../solr/select/?q=*:*&version=2.2&start=0&rows=0&indent=on&facet=true&f
acet.field=dateorigin_sort&facet.mincount=0&facet.sort=false
This query says, "Select all records in the index. For each indexed
value of dateorigin_sort, count the number of records with that value."
It yields the following output snippet:
<lst name="facet_counts">
<lst name="facet_queries"/>
<lst name="facet_fields">
<lst name="dateorigin_sort">
<int name="">0</int>
<int name="-1019087976">1</int>
<int name="-1020481693">1</int>
Ummmmmm... it has an indexed empty value that does not correspond to a
record? Is it an unanchored data item in the index? Would optimizing
make this index data go away?
Thanks,
Lance
-----Original Message-----
From: Chris Hostetter [mailto:[EMAIL PROTECTED]
Sent: Friday, March 14, 2008 4:46 PM
To: solr-user@lucene.apache.org
Subject: RE: Finding an empty field
: dateorigin_sort:"" gives a syntax error. I'm using Solr 1.2. Should
: this work in Solr 1.3? Is it legal in a newer Lucene parser?
Hmm.. not sure. did you try the range query suggestion? ...
: well, technically range queries "work" they just don't "work" on
numeric
: ranges ... they'd be lexigraphical ranges on the string value, so...
:
: dateorigin_sort:[* TO " "]
:
: ...could probably help you find anything that is lexigraphically lower
: then a string representation of an integer (assuming
dateorigin_sort:""
: doesn't work)
-Hoss
