You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2017/02/15 04:39:42 UTC
[jira] [Updated] (NIFI-2968) Need better error logging when
ExecuteSQL hits an unknown SQL type
[ https://issues.apache.org/jira/browse/NIFI-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Witt updated NIFI-2968:
------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
+1 merged to master.
> Need better error logging when ExecuteSQL hits an unknown SQL type
> ------------------------------------------------------------------
>
> Key: NIFI-2968
> URL: https://issues.apache.org/jira/browse/NIFI-2968
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Daniel Einspanjer
> Assignee: Pierre Villard
> Priority: Minor
> Labels: easyfix
> Fix For: 1.2.0
>
>
> If the JDBC driver returns SQL type 1111 (other) for a column, NiFi throws the following error:
> o.a.nifi.processors.standard.ExecuteSQL ExecuteSQL[id=17c33327-0158-1000-421f-605f45c66679] ExecuteSQL[id=17c33327-0158-1000-421f-605f45c66679] failed to process session due to java.lang.IllegalArgumentException: createSchema: Unknown SQL type 1111 cannot be converted to Avro type: java.lang.IllegalArgumentException: createSchema: Unknown SQL type 1111 cannot be converted to Avro type
> It would be useful to include some information such as the table name and column name that caused the problem.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)