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

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

Github user ijokarumawak commented on the issue:

    https://github.com/apache/nifi/pull/1798
  
    **NOTE** This PR contains 3 commits, but only the last commit 
[6c3080f](https://github.com/apache/nifi/pull/1798/commits/6c3080f5cc9662f45cf8792831eb25ee235a75dd)
 is needed for NIFI-2624. NIFI-3873 (#1788) and NIFI-3895 (#1797) have 
separated PRs those are under review currently and those can make it easier to 
work with NIFI-2624 so I included those in this PR just for convenience.
    
    Added 'Use Logical Types' property to ExecuteSQL and QueryDatabaseTable so 
that user can choose from staying with the old behavior (outputs as string) or 
as Logical types.
    
    I've tested logical types with MySQL, PostgreSQL and Oracle databases. 
Details for the test and database setup is written in this 
[Gist](https://gist.github.com/ijokarumawak/69b29fa7b11c2ada656823db614af373).
    
    I haven't touched HiveJdbcCommon yet and I think it should be done after 
normal JdbcCommon is finished.
    
    Thanks for reviewing!


> JDBC-to-Avro processors handle BigDecimals as Strings
> -----------------------------------------------------
>
>                 Key: NIFI-2624
>                 URL: https://issues.apache.org/jira/browse/NIFI-2624
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Toivo Adams
>
> The original SQL processors implemented BigDecimal values as Strings for 
> Avro, as the version of Avro it used (1.7.6) did not support DECIMAL type.
> As of Avro 1.7.7 (AVRO-1402), this type is supported and so the SQL/HiveQL 
> processors should be updated to handle BigDecimals correctly if possible.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to