I've a field as NO_NORM, does it has to be untokenized to be able to
sort on it?
On Jan 21, 2008 12:47 PM, Antony Bowesman [EMAIL PROTECTED] wrote:
vivek sar wrote:
I need to be able to sort on optime as well, thus need to store it .
Lucene's default sorting does not need the field to be
vivek sar wrote:
I've a field as NO_NORM, does it has to be untokenized to be able to
sort on it?
NO_NORMS is the same as UNTOKENIZED + omitNorms, so you can sort on that.
Antony
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
vivek sar wrote:
I need to be able to sort on optime as well, thus need to store it .
Lucene's default sorting does not need the field to be stored, only indexed as
untokenized.
Antony
-
To unsubscribe, e-mail: [EMAIL
Hi,
Do you really need to store those dates? Why not just index them and not store
them if index size is a concern?
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: vivek sar [EMAIL PROTECTED]
To: java-user@lucene.apache.org
Sent: Saturday,
I need to be able to sort on optime as well, thus need to store it .
Isn't there any way to filter without indexing? Not sure why do I need
to index some field I need to filter on. I thought we could get all
the documents from an index and then filter out the documents from it
for a field within a
You can try to write your own HitCollector and on its collect(int doc, float
score) method read the doc's date value and decide if it passes the filter
or not.
That is an approach I use for similar tasks.
On Jan 20, 2008 6:51 AM, vivek sar [EMAIL PROTECTED] wrote:
I need to be able to sort on
