[
https://issues.apache.org/jira/browse/NIFI-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988701#comment-15988701
]
Joseph Witt commented on NIFI-3719:
-----------------------------------
Thanks for your contribution.
Have removed fix version until there is review traction/close to merge.
Given the utility nature of this method I dont think we can simply force it to
use UTC as it might cause behavior changes elsewhere. We should consider
adding new method signatures that let the effective timezone be set explicitly,
based on UTC, or whatever comes from the local system.
> Timezone error in 5-minute statistics processing time
> -----------------------------------------------------
>
> Key: NIFI-3719
> URL: https://issues.apache.org/jira/browse/NIFI-3719
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 1.2.0, 1.1.1
> Environment: Windows 10 and Java 1.8.0_121.
> Also CentOS 7 with unknown Java version, but at least 1.7.
> Reporter: Michael Hopton
> Priority: Minor
> Labels: patch
> Attachments: 0001-Nifi-3719-Fix-timezone-for-durations.patch
>
>
> With timezone set to Australia\Sydney (AEST, UCT+10), each processor shows
> Task / Time of 0 / 00:00:00.000.
> With timezone set to Australia\Adelaide (ACST, UCT+9:30), each processor
> shows Task / Time of 0 / 00:30:00.000.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
