Actually, Field.NO_NORMS means Field.UN_TOKENIZED plus
Field.setOmitNorms(true).
Mike
John Griffin wrote:
Dimitri,
Field.TOKENIZED and Field.NO_NORMs send their field's contents
through a tokenizer and make their contents indexed and therefore
searchable. FIELD.UN_TOKENIZED does not send its field's contents
through a
tokenizer but it still indexes its contents. Only Field.NO does not
index
its field's contents.
So, regardless of whether or not a particular document has a field
tokenized while another document does not has nothing to do with
whether or
not the contents are indexed. As long as it's not Field.NO, they are.
John G.
-----Original Message-----
From: DimitriD [mailto:[EMAIL PROTECTED]
Sent: Friday, August 22, 2008 9:14 AM
To: java-user@lucene.apache.org
Subject: Field Question
I am new to lucene. Here is my question. The document has fields.
When I add
a field to the document I can specify that field is Indexed,
Tokenized,
etc.. So the same field can be Tokenized in one document and be
not-tokenized in another document. However the is a method
IndexReader.getFieldNames(IndexReader.FieldOption.INDEXED) that
returns all
index fields in the index. It seems like it assumes that FIELD
should have
the same attributes across all documents.
Can anyoen explain it?
--
View this message in context:
http://www.nabble.com/Field-Question-tp19108787p19108787.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
