Phillip, That can happen if you have few Provenance events generated, because the timestamp is stored as a 32-bit offset from a known timestamp. So after some period of time (I think about a month, if I’m not mistaken), if the Provenance Event File doesn’t roll over, it can overflow that 32-bit integer. This was fixed in 1.12.0 (NIFI-7339 [1]).
Thanks -Mark [1] https://issues.apache.org/jira/browse/NIFI-7339 On Sep 23, 2020, at 10:10 AM, Phillip Grenier <[email protected]<mailto:[email protected]>> wrote: I am running a 1.11.4 instance with adoptopenjdk 1.11. The timestamps on the data provenance events are off by ~2 months and the date on the system is correct. Thanks for any help, Phillip
