Hi James,
Have a look in Bugzilla at issue #34563. I contributed some code last
night that may be helpful to you. Have a look at the
patchTestSort.txt, which is a diff of my changes to test the classes I
created. This may help you understand how to use the classes, but I
assume based upon the valu
This was resolved by specifying Locale.US in the SortField
constructor. I guess our default locale setting is messed
up somewhere.
Thanks to everyone who responded!
James
--- James Levine <[EMAIL PROTECTED]> wrote:
> I have an index of around 3 million records, and typical queries
> can res
James åé:
Hi Che-
The presort method was our first approach but this doesn't work
in practice because we update the index incrementally and insertion order
doesn't match date ordering as we add updates.
I don't think sorting top hits only will deliver what the user is
expecting -- that is, results
Hi Che-
The presort method was our first approach but this doesn't work
in practice because we update the index incrementally and insertion order
doesn't match date ordering as we add updates.
I don't think sorting top hits only will deliver what the user is
expecting -- that is, results listed
Hi Erik,
Thanks for the reply. All dateTime fields are zero-padded and the
same length, and each indexed document has a valid dateTime value.
Regarding the sort type, INT generates a ParseException, I assume
because the string has too many digits to fit in an int. I looked
for a LONG type but
Just like Google said: full text search service is not traditional
database application. Lucene is not a database too: if you wanna sort on
some fields, you'd better pre-sort it before it indexed: like date. then
get results by doc id.
For lucene you can only sort results in top hits. if you so
On Apr 21, 2005, at 5:22 PM, James Levine wrote:
I have an index of around 3 million records, and typical queries
can result in result sets of between 1 and 400,000 results.
We have indexed "dateTime" fields in the form 20050415142, that is, to
10-minute precision.
When I try to sort queries I get
I have an index of around 3 million records, and typical queries
can result in result sets of between 1 and 400,000 results.
We have indexed "dateTime" fields in the form 20050415142, that is, to
10-minute precision.
When I try to sort queries I get something back that is roughly sorted
on index
