Github user juanmirocks commented on the issue:
https://github.com/apache/flink/pull/4997
No. I don't think this is going to be a suitable solution, as if = is
allowed in the comparison, the very same file will be triggered multiple times.
Note that the older and deprecated `FileMonitoringFunction` solves this
situation by having a map of filenames to modification times. More robust but
also more expensive memory-wise. A limit to a possible map could be given in
`LinkedHashMap` with `removeEldestEntry`.
---
