[
https://issues.apache.org/jira/browse/NIFI-13529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864338#comment-17864338
]
ASF subversion and git services commented on NIFI-13529:
--------------------------------------------------------
Commit f338215851bcaec40b673af4ef4600b478a5c9f3 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f338215851 ]
NIFI-13529 Set Calcite Connection timeZone to UTC for Records
Calcite adjusts Timestamp objects returned from a Result Set based on the
configured Time Zone Offset in an attempt to localize the results. Framework
use of Calcite for Record processing expects input Timestamp values to remain
unchanged, so setting the timeZone property to UTC with an offset of 0
effectively avoids this Calcite localization.
This closes #9066
Signed-off-by: David Handermann <[email protected]>
> QueryRecord changes timezones of Timestamp field
> ------------------------------------------------
>
> Key: NIFI-13529
> URL: https://issues.apache.org/jira/browse/NIFI-13529
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 2.0.0-M5
>
> Attachments: TIMESTAMP_TYPE_ISSUE_WITH_QUERY_RECORD.json
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Reported in Apache Slack. It is easy to reproduce using flow attached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)