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:33:00 UTC

[jira] [Commented] (NIFI-9457) Add support to microseconds in PutKudu

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

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

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

NIFI-9457 Support microseconds for String Timestamps in PutKudu

- Implemented override for Timestamp Record Field Type format handling to add support for optional microseconds
- Added FieldConverter and ObjectTimestampFieldConverter implementation for generalized Timestamp parsing using DateTimeFormatter
- Updated PutKudu unit tests for standard Timestamp and Timestamp with microseconds

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

This closes #5589.


> Add support to microseconds in PutKudu
> --------------------------------------
>
>                 Key: NIFI-9457
>                 URL: https://issues.apache.org/jira/browse/NIFI-9457
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Pierre Villard
>            Assignee: David Handermann
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Assuming the field to push into Kudu is of type String, we're currently using the DataTypeUtils.toTimestamp method to parse this String and convert it into a timestamp. We, however, rely on classes that would only keep milliseconds precision. We should provide a way to retain microseconds precision since it's supported by Kudu. Until we refactor NiFi to leverage recent classes for Date/Time handling, the best approach is to have an alternative path specific to Kudu to support this specific case.



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