[jira] [Commented] (NIFI-14572) Provenance search request date/time is inconsistent with the date/time shown in the UI

["super dachuan (Jira)" <ji...@apache.org>]

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

super dachuan commented on NIFI-14572:
--------------------------------------

The root cause of this issue is that {{DateTimeAdapter.java}} uses {{ZonedDateTime}} in the {{unmarshal}} method, which leads to ambiguity when parsing CST time zones.

The root cause of [NIFI-14581], on the other hand, lies in the difference between the time zone identifier returned by {{TimezoneAdapter}} and the server’s default locale/language settings. Although the two issues are related, they are not identical.

It is possible that the suggestion mentioned in the NIFI-14581 discussion—using standardized time zone IDs—could address both problems. However, I would prefer to align the implementation of {{DateTimeAdapter#unmarshal}} with {{{}TimestampAdapter{}}}, in order to fix the time offset issue described in this issue. Please assign it to me.

> 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)