Yes,
DIH (and used to be Solr schema parser too) is great at ignoring the
things it does not know about and just using defaults instead.
Regards,
Alex.
Personal: http://www.outerthoughts.com/ and @arafalov
Solr resources and newsletter: http://www.solr-start.com/ and @solrstart
Solr popularize
All,
The problem here was that I gave driver="BinURLDataSource" rather than
type="BinURLDataSource". Of course, saying driver="BinURLDataSource"
caused it not to be able to find it.
it out, mention the Solr version on
> the next email. Sometimes it makes difference, though DIH has been
> largely unchanged for a while.
>
> -- Forwarded message --
> From: Dan Davis
> Date: 10 October 2014 15:00
> Subject: Re: Tika Integration problem wit
er 2014 15:00
Subject: Re: Tika Integration problem with DIH and JDBC
To: Alexandre Rafalovitch
The definition of dataSource name="bin" type="BinURLDataSource" is in
each of the dih-*.xml files.
But only the xml version has the definition at the top, above the document.
Mov
You say "dataSource='bin'" but I don't see you defining that datasource. E.g.:
So, there might be some weird default fallback that's just causes
strange problems.
Regards,
Alex.
Personal: http://www.outerthoughts.com/ and @arafalov
Solr resources and newsletter: http://www.solr-start.com/
What I want to do is to pull an URL out of an Oracle database, and then use
TikaEntityProcessor and BinURLDataSource to go fetch and process that
URL. I'm having a problem with this that seems general to JDBC with Tika
- I get an exception as follows:
Exception in entity :
extract:org.apache.sol
