lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noble Paul നോബിള്‍ नोब्ळ् <noble.p...@corp.aol.com>
Subject Re: [DIH] SqlEntityProcessor does not recognize onError attribute
Date Mon, 09 Nov 2009 14:25:36 GMT
On Mon, Nov 9, 2009 at 4:24 PM, Sascha Szott <szott@zib.de> wrote:
> Hi all,
>
> as stated in the Solr-WIKI, Solr 1.4 allows it to specify an onError
> attribute for *each* entity listed in the data config file (it is considered
> as one of the default attributes).
>
> Unfortunately, the SqlEntityProcessor does not recognize the attribute's
> value -- i.e., in case an SQL exception is thrown somewhere inside the
> constructor of ResultSetIterators (which is an inner class of
> JdbcDataSource), Solr's import exits immediately, even though onError is set
> to continue or skip.
>
> Why are database related exceptions (e.g., table does not exists, or an
> error in query syntax occurs) not being covered by the onError attribute? In
> my opinion, use cases exist that will profit from such an exception handling
> inside of Solr (for example, in cases where the existence of certain
> database tables or views is not predictable).
We thought DB errors are not to be ignored because errors such as
table does not exist can be really serious.

>
> Should I raise an JIRA-issue about this?
Raise an issue it can be fixed
>
> -Sascha
>
>
>



-- 
-----------------------------------------------------
Noble Paul | Principal Engineer| AOL | http://aol.com

Mime
View raw message