: I don't know how to accomplish this off the top of my head
: OOB, I'd guess your client would have to manage the
: substitutions and then just index separate fields...
an UpdateProcessor would proably be the best place to apply logic like
this to completley add/replace the value of a mapped_fi
Matej,
During/right before indexing. What is stored is the original.
Indexing ! = storing
--
Performance Monitoring - http://sematext.com/spm
On Oct 3, 2012 6:03 AM, "tech.vronk" wrote:
>
> Thank you Erick, that would explain the behaviour.
>
> But it leaves me with the question:
> When are al
Thank you Erick, that would explain the behaviour.
But it leaves me with the question:
When are all the analyzers/filters applied
when not during indexing?
I mean, if I define a lowercase filter on a field,
if it is not applied on the input stream before storing
so that I have a lowercased text
Ah, I get it (finally). OK, there's no good way to do what
you want that I know of. The problem is that the
stored="true" takes effect long before any transformations
are applied, and is always the raw input. You effectively
want to chain the fields together, i.e. apply the analysis
chain _then_ ha
the query is:
mapped_field:mapped_value1
and seems to correctly return the documents.
the mapped_field has attribute stored=true
and also appears in the result (even without requesting it explicitely
with fl),
just with the orig_value1 instead of mapped_value1
matej
Am 02.10.2012 15:46, s
What's the query you send? I'm guessing a bit here since you
haven't included it, but try insuring two things:
1> your mapped_field is has 'stored="true" '
2> you specify (either in your request handler on on the URL) fl=mapped_value
Best
Erick
On Tue, Oct 2, 2012 at 9:04 AM, tech.vronk wrote:
