I think you're really writing a custom update processor that creates its own
analysis chain to do what you want. Likely this would be somewhat expensive
unless you could batch together user's documents so you'd only have to fetch
the stopwords once.
Then you'd have to do something equivalent at qu
My main goal creating custom stop word filter which will connect to my db and
get stopwords list which will be different for each user. This filter will
be attached to deal_title field and during indexing my documents I need to
know which user is owner of this document (I can get this info from use
You could pre-process the field values in an update processor. You can even
write a snippet in JavaScript. You could check one field and then redirect
a field to an alternate field which has a different analyzer.
What expectations do you have as to what analysis should occur at query
time?
-- Jac
I am trying to write a custom analyzer , whose execution is determined by
the value of another field within the document.
For example if the locale field in the document has 'de' as the value, then
the analizer would use the German set of tokenizers/filters to process the
value of a field.
My que
