[
https://issues.apache.org/jira/browse/NIFI-14572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17979855#comment-17979855
]
super dachuan edited comment on NIFI-14572 at 6/17/25 6:37 AM:
---------------------------------------------------------------
Additional information: The "CST" label displayed on the Search Events time
input may cause confusion — for example, it might be interpreted as *Central
Standard Time (U.S.)* rather than {*}China Standard Time{*}, which could
contribute to the incorrect time range being used in the request.
was (Author: super_dachuan):
Additional information: The "CST" label displayed on the Search Provenance time
input may cause confusion — for example, it might be interpreted as *Central
Standard Time (U.S.)* rather than {*}China Standard Time{*}, which could
contribute to the incorrect time range being used in the request.
> 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, Core UI
> Affects Versions: 2.4.0
> Reporter: super dachuan
> Priority: Major
> 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)
