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
:
Subject: Order of fields within a Document in Lucene 2.4+
The Lucene FAQ says...
What is the order of fields returned by Document.fields()?
* Fields are returned in the same order they were added to the document.
(now getFields() as fields is deprecated)
However I think this may no longer be the
The Lucene FAQ says...
What is the order of fields returned by Document.fields()?
* Fields are returned in the same order they were added to the document.
(now getFields() as fields is deprecated)
However I think this may no longer be the case in 2.4
We are indexing documents in a specific
