Just wanted to confirm that this:
...works beautifully for untokenized lowercase values. Starting spaces and
spaces in the middle work fine.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Untokenized-lowercase-string-tp4010296p4010351.html
Sent from the
That sounds right, thanks! I missed KeywordTokenizerFactory, with a name like
that it did not sound like what I wanted. I expected NullTokenizerFactory or
something standing out like that :)
Jack Krupansky-2 wrote
> Use the KeywordTokenizerFactory for your text field tokenizer to keep the
> text
Alexandre Rafalovitch wrote
> Each field has a type. Each type defines what happens with the text.
> You can certainly select to do one thing but not another.
Understood. But it seemed to me that only TextField allows adding filters to
it and filters go in conjunction with tokenizers. I could not
Use the KeywordTokenizerFactory for your text field tokenizer to keep the
text from being tokenized, and then use the LowerCaseFilterFactory token
filter to do the lowercasing. Unfortunately, "string" (StrField) does not
support analysis.
-- Jack Krupansky
-Original Message-
From: am
Each field has a type. Each type defines what happens with the text.
You can certainly select to do one thing but not another.
Just look towards the bottom of the schema.xml and compare field types
definition for string and text, it should be fairly obvious. You'll
most probably make up a new type
