Sorry, yes, this was my fault with the indexing speedups in 2.3
(LUCENE-843): as of 2.3, if any fields have term vectors enabled, the
fields are sorted lexicographically. As of 2.4 (LUCENE-1301,
refactoring the indexing core), that sort happens even without term
vectors.
Hoss I see you've opened
Yeah, I've heard rumblings about this issue before. I can't remember what
patch changed it though - one of Mike M's I think?
On Tue, Jun 30, 2009 at 8:40 PM, Chris Hostetter
wrote:
>
> Hmmm... i'm not an expert on the internals of indexing, and i don't use
> FieldSelectors much, but this seems li
Hmmm... i'm not an expert on the internals of indexing, and i don't use
FieldSelectors much, but this seems like a pretty big bug to me ... or at
the very least: a change in behavior that completely eliminates the value
of LOAD_AND_BREAK.
https://issues.apache.org/jira/browse/LUCENE-1727
:
I agree. Using Lucene 2.4.1 doc.getFields() returns in alpha order and
not the order in which they were added.
Sincerely,
Sithu D Sudarsan
-Original Message-
From: Matt Turner [mailto:m4tt_tur...@hotmail.com]
Sent: Thursday, June 25, 2009 4:33 PM
To: java-user@lucene.apache.org
Subje
