You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/12/10 09:28:00 UTC

[jira] [Commented] (NIFI-9471) PutKudu Row Object to String Conversion uses Incorrect Format

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

ASF subversion and git services commented on NIFI-9471:
-------------------------------------------------------

Commit 3d3f6ac070a10a951073829c61e88d9f938af915 in nifi's branch refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3d3f6ac ]

NIFI-9471 Corrected PutKudu usage of DataTypeUtils.toString()

Signed-off-by: Pierre Villard <pi...@gmail.com>

This closes #5590.


> PutKudu Row Object to String Conversion uses Incorrect Format
> -------------------------------------------------------------
>
>                 Key: NIFI-9471
>                 URL: https://issues.apache.org/jira/browse/NIFI-9471
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.12.0, 1.11.3, 1.15.0
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Improvements to timestamp handling for {{PutKudu}} in NIFI-6551 introduced several other changes to use {{DataTypeUtils.toString()}} for Kudu Types that required String values.  The second parameter of the {{DataTypeUtils.toString()}} method should be a format pattern to use when converting Date and Timestamp objects to strings, however, the {{AbstractKuduProcessor.buildPartialRow()}} method incorrectly passes the record field name as the second parameter, creating the potential for an {{IllegalArgumentException}} when {{PutKudu}} attempts to convert a Date or Timestamp to a String.  Passing the optional format property for the Record Field Data Type should correct the behavior.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)