Not exactly dumb, and I can't tell you exactly what is happening here, but lucene stores some info at the index level rather than the field level, and things can get confusing if you don't use the same Field definition consistently for a field.
>From the javadocs for org.apache.lucene.document.Field: NOTE: the field type is an IndexableFieldType. Making changes to the state of the IndexableFieldType will impact any Field it is used in. It is strongly recommended that no changes be made after Field instantiation. -- Ian. On Mon, Sep 16, 2013 at 11:33 AM, Alan Burlison <alan.burli...@gmail.com> wrote: > I'm creating multiple instances of a field, some with Field.Store.YES > and some with Field.Store.NO, with Lucene 4.4. If Field.Store.YES is > set then I see multiple instances of the field in the documents in the > resulting index, if I use Field.Store.NO then I only see a single > field. Is that expected or am I doing something dumb? > > Thanks, > > -- > Alan Burlison > -- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
