: 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.
Did
: 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
: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 empty string. I would like to
isolate
: this record and remove it. This field exists solely to make sorting
: 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
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
I have an index which I cannot rebuild (it is very large). The schema
includes a field 'dateorigin_sort'. This is an integer, not an 'sint'. It
sorts very quickly but does not support range queries.
Somehow the index has acquired one record out of millions in which an
integer value has been
