[
https://issues.apache.org/jira/browse/NIFI-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17954435#comment-17954435
]
Matt Gilman commented on NIFI-14581:
------------------------------------
The UI gets the timezone that is used for the Provenance Search requests from
the server. Specifically, it is loaded from an endpoint that uses this
TimezoneAdapter [1]. The submitted timestamp goes through a different adapter
when the value is submitted in a search request. This TimestampAdapter was
updated to remove the US locale however the TimezoneAdapter wasn't. I suspect
if the TimezoneAdapter was updated to also remove the US locale like the
TimestampAdapter was, this would probably work as expected.
I do think there is lots of room for improvement here with timestamps in the
API payloads. Historically they haven't been updated to maintain backwards
capability. This should be improved in time but the update highlighted above
could prove to be a good fix in the meantime.
[1]
https://github.com/apache/nifi/blob/main/nifi-framework-bundle/nifi-framework/nifi-client-dto/src/main/java/org/apache/nifi/web/api/dto/util/TimezoneAdapter.java#L41
> Provenance Event search/filtering by date doesn't work
> ------------------------------------------------------
>
> Key: NIFI-14581
> URL: https://issues.apache.org/jira/browse/NIFI-14581
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 2.4.0
> Environment: Edge 136.0.3240.76, Windows 23H2
> Reporter: René Zeidler
> Priority: Major
> Labels: provenance, search, timestamp, ui
> Attachments: Screenshot 2025-05-21 at 12.06.53.png, Screenshot
> 2025-05-21 at 12.07.07.png, image-2025-05-20-10-07-14-329.png,
> image-2025-05-20-10-11-36-518.png, image-2025-05-21-12-41-43-487.png
>
>
> h1. Summary
> The provenance event search (Data Provenance -> Search Icon) doesn't work
> whenever the "Date Range" input has a value. This is especially a problem
> because the date range input contains the current date by default (which it
> probably shouldn't either):
> !image-2025-05-20-10-07-14-329.png!
> Clicking "Search" when the date range input is filled closes the modal, but
> the provenance events aren't filtered.
> h1. Cause
> The request to /nifi-api/provenance fails with HTTP 400 "Message body is
> malformed. Unable to map into expected format."
> The cause seems to be that the "startDate" and "endDate" values are in an
> unexpected format:
> !image-2025-05-20-10-11-36-518.png!
> Without these parameters the request succeeds.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
