[jira] [Commented] (NIFI-2968) Need better error logging when ExecuteSQL hits an unknown SQL type

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user pvillard31 opened a pull request:

    https://github.com/apache/nifi/pull/1377

    NIFI-2968 Improved message when ExecuteSQL hits unsupported SQL types

    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [X] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [X] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [X] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [ ] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
    - [ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/pvillard31/nifi NIFI-2968

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1377.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1377
    
----
commit ba384fc7f661dee978c5a42f62da4d1a0b7791d3
Author: Pierre Villard <pi...@gmail.com>
Date:   2016-12-30T14:20:00Z

    NIFI-2968 Improved message when ExecuteSQL hits unsupported SQL types

----


> 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
>            Priority: Minor
>              Labels: easyfix
>
> 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.4#6332)