: 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?
If it was, it was in the old parser ... using trunk Solr (with Lucene
2.3.1) they both work for me.
D
mpty 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.or
: 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 le
--Original Message-
From: Chris Hostetter [mailto:[EMAIL PROTECTED]
Sent: Friday, March 14, 2008 11:38 AM
To: solr-user@lucene.apache.org
Subject: Re: Finding an empty field
: Somehow the index has acquired one record out of millions in which an
: integer value has been populated by an empt
: Somehow the index has acquired one record out of millions in which an
: integer value has been populated by an empty string. I would like to isolate
: this record and remove it. This field exists solely to make sorting faster,
: and since it has an empty record, sorting blows up.
:
: Is it po
