Well ... DIH can.
And update processors can.
And of course client-side indexers.
But yeah... elbow grease required.
Erik
On Sep 25, 2011, at 16:32, Erick Erickson <erickerick...@gmail.com> wrote:
> Not that I know of...
>
> On Sun, Sep 25, 2011 at 11:15 AM, Jithin <jithin1...@gmail.com> wrote:
>>
>> Erick Erickson wrote:
>>>
>>> See below:
>>>
>>> On Sun, Sep 25, 2011 at 9:53 AM, Jithin <jithin1...@gmail.com>
>>> wrote:
>>>> Hi Erick, The problem I am trying to solve is to filter invalid entities.
>>>> Users might mispell or enter a new entity name. This new/invalid entities
>>>> need to pass through a KeepWordFilter so that it won't pollute our
>>>> autocomplete result.
>>>>
>>>
>>> Right. But if you have a KeepWordFilter, that implies that you have a list
>>> of known good words. Couldn't you use that file as your base for the
>>> autosuggest component?
>>>
>>
>> I think that is possible.
>> But is there any other mechanism within solr/lucene to preprocess stored
>> data.
>>
>> --
>> View this message in context:
>> http://lucene.472066.n3.nabble.com/How-to-apply-filters-to-stored-data-tp3366230p3367158.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
