nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-2968) Need better error logging when ExecuteSQL hits an unknown SQL type
Date Wed, 15 Feb 2017 04:39:42 GMT

    [ https://issues.apache.org/jira/browse/NIFI-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867235#comment-15867235
] 

ASF GitHub Bot commented on NIFI-2968:
--------------------------------------

Github user joewitt commented on the issue:

    https://github.com/apache/nifi/pull/1377
  
    +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)

Mime
View raw message