> > struggling to see how this change could have made any
> > difference.
> >
> > -Original Message-
> > From: Mordo, Aviran (EXP N-NANNATEK) [mailto:[EMAIL PROTECTED]
> > Sent: Thu 9/14/2006 17:18
> > To: java-user@lucene.apache.org
&g
ould preserve those
fields and hence sorting would proceed as normal.
Does that make sense?
Thanks
Alan
-Original Message-
From: Erick Erickson [mailto:[EMAIL PROTECTED]
Sent: Thu 9/14/2006 18:00
To: java-user@lucene.apache.org
Cc:
Subject: Re: Newbie question: lucene sort
On 9/14/06, Alan Boshier <[EMAIL PROTECTED]> wrote:
That was my understanding (that they had to be indexed) but
making them stored seems to have fixed the problem we were
seeing, which is odd.
Not being an expert on how lucene works internally, I'm
struggling to see how this change could have ma
Original Message-
From: Mordo, Aviran (EXP N-NANNATEK) [mailto:[EMAIL PROTECTED]
Sent: Thu 9/14/2006 17:18
To: java-user@lucene.apache.org
Cc:
Subject: RE: Newbie question: lucene sorting problems and stored
fields
AFIK, the field has to be indexed, but I don't think it
On 9/14/06, Alan Boshier <[EMAIL PROTECTED]> wrote:
Is it a requirement when creating a field for sorting to
make it stored?
No, stored doesn't matter... it must be indexed though.
-Yonik
http://incubator.apache.org/solr Solr, the open-source Lucene search server
-
ssage-
From: Mordo, Aviran (EXP N-NANNATEK) [mailto:[EMAIL PROTECTED]
Sent: Thu 9/14/2006 17:18
To: java-user@lucene.apache.org
Cc:
Subject: RE: Newbie question: lucene sorting problems and stored fields
AFIK, the field has to be indexed, but I don't think it has to be stored
apache.org
Subject: Newbie question: lucene sorting problems and stored fields
Hi
We are seeing intermittent problems with searches that use sorted fields
(in lucene 1.4.3).
If we add the fields to our Documents as 'unstored' then we start to see
results that have been sorted by Document I
Hi
We are seeing intermittent problems with searches that use
sorted fields (in lucene 1.4.3).
If we add the fields to our Documents as 'unstored' then
we start to see results that have been sorted by Document ID.
The problem goes away if we add the fields as 'stored'.
Is it a requirement when
