Hi Furkan,

Further to UpdateRequestHandler applying XSL you can configure the
UpdateRequestProcessor to handle input using a scripting language of your
choice (http://wiki.apache.org/solr/ScriptUpdateProcessor).

As of 4.0 you can send json <http://wiki.apache.org/solr/UpdateJSON> using
the default UpdateRequestHandler by specifying the content type:


curl 'http://localhost:8983/solr/update?commit=true' --data-binary
@books.json -H 'Content-type:application/json

or


curl http://localhost:8983/solr/update -H
'Content-type:application/json' -d '[ {"id" : "TestDoc1", "title" :
"test1"}, {"id" : "TestDoc2", "title" : "another test"}]'

Regards,
Tricia

On Tue, Dec 17, 2013 at 6:14 AM, Uwe Schindler <[email protected]> wrote:

> UpdateRequestHandler can apply an XSL that is applied to the data coming
> in. This does everything you would like to use here:
> http://wiki.apache.org/solr/XsltUpdateRequestHandler
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> H.-H.-Meier-Allee 63, D-28213 Bremen
>
> http://www.thetaphi.de
>
> eMail: [email protected]
>
>
>
> *From:* Furkan KAMACI [mailto:[email protected]]
> *Sent:* Tuesday, December 17, 2013 1:50 PM
> *To:* [email protected]
> *Subject:* Tranforming Index Data
>
>
>
> Hi;
>
>
>
> Can we put a transformer (not the transformer of DIH) in front of the
> indexing mechanism and let people index arbitrary style data?
>
> I mean that: people may send data that does not obey the schema.
> Transformer includes XPath for XML data and something like JSON Path
> for JSON Data. So, we can transform the data that fits schema.
>
>
>
> Such kind of improvement may remove some people's client side developments
> that is only responsible for transforming data to make it ready for
> indexing according to schema. If you think so I can fire a Jira issue and I
> can be responsible to make a contribution for it.
>
>
>
> Thanks;
>
> Furkan KAMACI
>

Reply via email to