Re: more granular updateRequestProcessorChain

2011-10-05 Thread Mikhail Khludnev
Jan, Shame on me, I was off for some time. I have a catch-all field - initially I copied n fields into the single one. But then I had to add a special payload per copied fields, and I've done it by Analyzer. for(src : srcFiledNames ){ payload = new MyPayloadTokenStream(input.get(src));

Re: more granular updateRequestProcessorChain

2011-10-05 Thread Jan Høydahl
Hi, If you want to add payloads in the UpdateChain, have a look at DelimitedPayloadTokenFilter. Put that in your FieldType, and create a Processor which annotates the text with payloads, e.g.: field name=textfoo|2.0 bar|3.0/field Using DelimitedPayloadTokenFilter with delimiter=| you can now

Re: more granular updateRequestProcessorChain

2011-08-31 Thread Yonik Seeley
On Wed, Aug 31, 2011 at 7:52 AM, Jan Høydahl jan@cominvent.com wrote: Hi, Can you explain the wanted functional result of your copy operation? I've done copying fields in processors without trouble. What do you want to do with the Lucene Document? Indeed - I've started going in the

more granular updateRequestProcessorChain

2011-08-17 Thread Mikhail Khludnev
Hello, I need to implement some tricky copyField like in http://wiki.apache.org/solr/UpdateRequestProcessor. But I need to take the SolrInputDocument field and put it into Lucene document myself by my own UpdateRequestProcessor. Unfortunately there is no room to do that because the creating