[
https://issues.apache.org/jira/browse/NIFI-8749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17377602#comment-17377602
]
Matt Burgess commented on NIFI-8749:
------------------------------------
I can't reproduce this, I have two Docker containers each running MySQL 5.7.19,
each with a table definition of:
create table DT_TEST (
ID INT,
DT DATETIME
);
The source instance has a timezone of -0500 and the target has a timezone of
-0800. When I do an ExecuteSQL from the source and PutDatabaseRecord to the
target, I get the same values in the DB when I do a SELECT * from DT_TEST. Can
you describe more about your environment?
> PutDatabaseRecord Insert Datetime Type Time Zone Issue
> ------------------------------------------------------
>
> Key: NIFI-8749
> URL: https://issues.apache.org/jira/browse/NIFI-8749
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.13.2
> Reporter: adg
> Priority: Critical
> Attachments: cc1.png, cc2.png, cc3.png, cc4.png,
> image-2021-07-01-15-17-38-035.png
>
>
> when I query a record from Mysql to get an AVRO Flowfile, then use
> PutDatabaseRecord(version 1.13.2) insert to another table (with same table
> structure), the data of the 'datetime' type column will change. The original
> data of the first table I query from is '2021-06-28
> {color:#FF0000}13{color}:14:20.0'. and the data of the second table which I
> insert to becomes '2021-06-28 {color:#FF0000}06{color}:14:20.0'.The gap is
> {color:#FF0000}7 hours{color}.
> our local timezone is PDT ({color:#FF0000}-7:00{color}). It seems that Nifi
> has done some timezone conversion work. But the 'datetime' type in mysql
> should have no relation to timezone
>
> when we use version 1.7.1 ,it works fine.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
