Thanks Alexandre,
I solved the problem using the xslt transform and the /update handler.
I attach the xsl that I put in conf/xslt/ (for documentation)
Then the command:
curl
"http://192.168.99.100:8999/solr/solrexchange/update?commit=true&tr=updateXmlSolrExchange.xsl";
-H "Content-Type: text/x
Seem you might be right, according to the source:
https://github.com/apache/lucene-solr/blob/master/solr/contrib/dataimporthandler/src/java/org/apache/solr/handler/dataimport/DocBuilder.java#L662
Sometimes, the magic (and schemaless is rather magical) fails when
combined with older assumptions (an
I am rebuilding a new docker image with each change on the config file so solr
starts fresh every time.
add-unknown-fields-to-the-schema
solr-data-config.xml
still having document like such:
"response":{"numFound":8,"start":0,"docs":[
{
"id":"38
Ok, to reduce the magic, you can just stick "update.chain" parameter
inside the defaults of the dataimport handler directly.
You can also pass it just as a URL parameter. That's what 'defaults'
section mean.
And, just to be paranoid, you did reload the core after each of those
changes to test it?
It did not work,
I tried many things and ended up trying this:
solr-data-config.xml
add-unknown-fields-to-the-schema
Regards,
Pierre
> On 10 Aug 2016, at 18:08, Alexandre Rafalovitch wrote:
>
> Your initParams section does not apply to /dataimp
Your initParams section does not apply to /dataimport handler as
defined. Try modifying it to say:
path="/update/**,/dataimport"
Hopefully, that's all that takes.
Managed schema is enabled by default, but schemaless mode is the next
layer on top. With managed schema, you can use the API to add yo
Hi Alex,
thanks for your answer.
Yes my solrconfig.xml contains the add-unknown-fields-to-the-schema.
add-unknown-fields-to-the-schema
I created my core using this command:
curl
http://192.168.99.100:8999/solr/admin/cores?action=CREATE&name=solrexchange&instanceDir=/opt/s
Do you have the actual fields defined? If not, then I am guessing that
your 'post' test was against a different collection that had
schemaless mode enabled and your DIH one is against one where
schemaless mode is not enabled (look for
'add-unknown-fields-to-the-schema' in the solrconfig.xml to conf
Hi,It seems that using the DataImportHandler with a XPathEntityProcessor config with a managed-schema setup, only import the id and version field.data-config.xml processor="XPathEntityProcessor" stream="true" forEach="/posts/row/" url=""
