[
https://issues.apache.org/jira/browse/NIFI-14572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18012366#comment-18012366
]
super dachuan commented on NIFI-14572:
--------------------------------------
[~pvillard] Thanks for your reply. It does seem that the root cause is related
to the timezone name — specifically the ambiguity of "CST". In my case, the
frontend sends "CST", which should mean China Standard Time in my timezone.
However, since "CST" can represent multiple timezones, it's possible that the
backend is interpreting it as a different timezone, causing the offset.
The workaround mentioned in the issue comments (add `user.languages` JVM
options) cannot solve my case, because the resulting timezone string is still
"CST".
> Provenance search request date/time is inconsistent with the date/time shown
> in the UI
> --------------------------------------------------------------------------------------
>
> Key: NIFI-14572
> URL: https://issues.apache.org/jira/browse/NIFI-14572
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0, 2.5.0
> Reporter: super dachuan
> Priority: Critical
> Labels: dateformat, datetime, provenance
> Attachments: 2025-05-16_16-42-12.png, 2025-05-16_16-47-46.png
>
>
> When using the Provenance UI to perform a search — for example, entering the
> date/time range *5/16/2025 00:00:00 - 5/16/2025 23:59:59 (CST)* — and
> clicking the *Search* button, the actual provenance request generated
> contains an incorrect date/time range:
> {{{}startDate: "05/18/2025 04:00:00 CST"{}}},
> {{{}endDate: "05/19/2025 03:59:59 CST"{}}}.
> As a result, the search returns incorrect results.
> Please refer to the attached screenshot for both the UI input and the
> resulting request.
> We encountered this issue in version 2.4.0, but it is unclear whether the
> problem also exists in earlier 2.x versions.
>
> Update:
> I also tested a deployment without any explicit timezone configuration (i.e.,
> using the default UTC timezone), and it worked as expected. However, after
> setting the server timezone to my local timezone ({*}Asia/Shanghai{*}), the
> issue described above started to occur.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
