lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doug Cutting <cutt...@apache.org>
Subject Re: question on design for ordering of field names written to FieldInfos object
Date Thu, 03 Jun 2004 04:44:05 GMT
Peter M Cipollone wrote:
> I have a question about the following code from
> org.apache.lucene.index.SegmentMerger.  I would like to know if the ordering
> of the fields as they are stored to the FieldInfos object is critical to
> some other purpose.
> 
> In the code below (from a week+/- ago CVS pull), the fields are stored in
> the following order:
> 1. fields indexed=true, termVectors=true
> 2. fields indexed=true, termVectors=false
> 3. fields stored=true, indexed=false

I don't think it is critical to any other purpose, but nor do I think 
one should require these to always be ordered the same way without a 
very good reason.  They didn't used to be ordered this way, and 
implementations of Lucene in other language might order them differently.

Doug



---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org


Mime
View raw message