You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Sascha Szott (JIRA)" <ji...@apache.org> on 2009/11/09 15:44:34 UTC
[jira] Created: (SOLR-1549) SqlEntityProcessor does not recognize
onError attribute
SqlEntityProcessor does not recognize onError attribute
-------------------------------------------------------
Key: SOLR-1549
URL: https://issues.apache.org/jira/browse/SOLR-1549
Project: Solr
Issue Type: Improvement
Components: contrib - DataImportHandler
Affects Versions: 1.4, 1.5
Reporter: Sascha Szott
Priority: Minor
Unfortunately, the SqlEntityProcessor does not recognize the value of an entity's onError attribute in DIH's data config file. Therefore, in cases where SQL exceptions are 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.
In my opinion, use cases exist that will profit from database related exception handling inside of Solr (e.g., in cases where the existence of certain database tables or views is not predictable).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SOLR-1549) SqlEntityProcessor does not recognize
onError attribute
Posted by "Noble Paul (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Noble Paul reassigned SOLR-1549:
--------------------------------
Assignee: Noble Paul
> SqlEntityProcessor does not recognize onError attribute
> -------------------------------------------------------
>
> Key: SOLR-1549
> URL: https://issues.apache.org/jira/browse/SOLR-1549
> Project: Solr
> Issue Type: Improvement
> Components: contrib - DataImportHandler
> Affects Versions: 1.4, 1.5
> Reporter: Sascha Szott
> Assignee: Noble Paul
> Priority: Minor
> Fix For: 1.5
>
>
> Unfortunately, the SqlEntityProcessor does not recognize the value of an entity's onError attribute in DIH's data config file. Therefore, in cases where SQL exceptions are 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.
> In my opinion, use cases exist that will profit from database related exception handling inside of Solr (e.g., in cases where the existence of certain database tables or views is not predictable).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-1549) SqlEntityProcessor does not recognize
onError attribute
Posted by "Noble Paul (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Noble Paul updated SOLR-1549:
-----------------------------
Fix Version/s: 1.5
> SqlEntityProcessor does not recognize onError attribute
> -------------------------------------------------------
>
> Key: SOLR-1549
> URL: https://issues.apache.org/jira/browse/SOLR-1549
> Project: Solr
> Issue Type: Improvement
> Components: contrib - DataImportHandler
> Affects Versions: 1.4, 1.5
> Reporter: Sascha Szott
> Assignee: Noble Paul
> Priority: Minor
> Fix For: 1.5
>
>
> Unfortunately, the SqlEntityProcessor does not recognize the value of an entity's onError attribute in DIH's data config file. Therefore, in cases where SQL exceptions are 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.
> In my opinion, use cases exist that will profit from database related exception handling inside of Solr (e.g., in cases where the existence of certain database tables or views is not predictable).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.