Jochen Franz created NIFI-15504:
-----------------------------------
Summary: Data Provenance in clustered mode not properly sorting by
timestamp
Key: NIFI-15504
URL: https://issues.apache.org/jira/browse/NIFI-15504
Project: Apache NiFi
Issue Type: Bug
Components: Core UI
Affects Versions: 2.7.2, 2.7.1, 2.7.0, 2.6.0, 2.5.0, 2.4.0, 2.3.0, 2.2.0
Reporter: Jochen Franz
Attachments: image-1.png
Links to NIFI-14254 from about a year ago.
As we are facing exactly the same as already described, I'm skipping the
behavior description but want to bring this bug back on the table.
Following NIFI-14254's description I agree that the event time should be
handled internal using unixtime and on-the-fly conversion for better reading.
A nifi.property could allow to define the date/time format for the installation.
Attached a screenshot, which shows the behavior in 2.7.2. The records are
sorted by Event Time, but the node has an impact on it.
The current behavior can be handled with some workaround, by defining the
timerange in the filter. Still, this does change the sorting behavior. It just
limits the amount of records in the provenance which makes it a bit difficult
to analyze certain event behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
