I think you meant Field.Index.NO and Field.Index.TOKENIZED, for those
two docs.
The answer is yes -- Lucene considers the field "indexed" if ever any
doc, even a single doc, had set Index.TOKENIZED or Index.UN_TOKENIZED
for that field.
However, your document A still will not have been i
AUTOMATIC REPLY
Tom Roberts is out of the office till 2nd September 2008.
LUX reopens on 1st September 2008
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
AUTOMATIC REPLY
Tom Roberts is out of the office till 2nd September 2008.
LUX reopens on 1st September 2008
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
John,
Thanks for answering.
So if I have a document "A "with field "foo" and the field has attribute
Field.NO and
I have document "B" with field "foo" and the field is Field.TOKENIZED.
Will IndexReader.getFieldNames(IndexReader.FieldOption.INDEXED) return field
"foo"?
Thanks,
Dimitri
John Gr
Thanks Mike. I stand corrected.
John G.
-Original Message-
From: Michael McCandless [mailto:[EMAIL PROTECTED]
Sent: Friday, August 22, 2008 5:40 PM
To: java-user@lucene.apache.org
Subject: Re: Field Question
Actually, Field.NO_NORMS means Field.UN_TOKENIZED plus
Field.setOmitNorms
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 n
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
it
