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

Billy Lin commented on NIFI-8749:
---------------------------------

[~mattyb149]Thanks for the reply.Our Nifi and MySQL instances both have -0700 
timezone.The source table and target table are in the same MySQL instance. The 
content type is *AVRO*  record when we use putDatabaseRecord and executeSQL.

 

About Datetime type time zone : According to 
[https://dev.mysql.com/doc/refman/8.0/en/datetime.html|https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-reference-type-conversions.html]
{code:java}
MySQL converts TIMESTAMP values from the current time zone to UTC for storage, 
and back from UTC to the current time zone for retrieval. (This does not occur 
for other types such as DATETIME.){code}
NIFI version : 1.13.2

MySQL version :5.7.17  

> 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: Billy Lin
>            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)

Reply via email to