[
https://issues.apache.org/jira/browse/NIFI-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16906129#comment-16906129
]
Nicolas De Amicis commented on NIFI-5091:
-----------------------------------------
Please correct this problem, nifi is unusable when CaptureChangeMysql reads
datetime columns not in UTC
> nifi CaptureChangeMySQL should consider timezone
> ------------------------------------------------
>
> Key: NIFI-5091
> URL: https://issues.apache.org/jira/browse/NIFI-5091
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Jasee Tao
> Priority: Minor
>
> MySQL's binlog doesn't log timezone。For example if I have a mysql using
> timezone CST(GMT+8)，and insert a create_time '2018-04-18 08:00:00’ (already
> in CST)，in the binlog the create_time is '2018-04-18 08:00:00' (without
> timezone information)，and in the output of CaptureChangeMySQL the create_time
> becomes '2018-04-18 16:00:00 CST'。Perhaps should add a configurable
> "timezone" property to identify the binlog's timezone?
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
