Maybe I'm oversimplifying it, and maybe this isn't what you desire, but...
What about breaking the postcode into two (or three) different fields? Seems
easy to parse on the ingestion-side, as you just break the string at the
"middle" space. Then store "postal_area", "postal_street", and option
ssage -
From: Erick Erickson
To: java-user@lucene.apache.org ; AJ Weber
Sent: Tuesday, April 15, 2008 2:50 PM
Subject: Re: replace field in doc?
Well, "my way" would certainly be simpler to read six months from
now when you look at this code again
And I
and CPU by extracting the
existing info, concat it, then put it back, right?
(Since this is the "all" field, for 'global searching', and I'm not storing it
anyway, I'm not concerned about the positions too much.)
Thanks a bunch for the quick reply!
-AJ
- Orig
I'm curious how people are building the "all" Field (for searching "all of the
terms at once").
I understand using store=NO, Index=Tokenized is generally the way to add the
field, but what if I need to basically use multiple classes to build my
Document before adding it to the index (keeping th
