Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.1.0
-
None
Description
The ContinuousFileReaderOperator does not correctly deal with watermarks, i.e. they are just passed through. This means that when the ContinuousFileMonitoringFunction closes and emits a Long.MAX_VALUE that watermark can "overtake" the records that are to be emitted in the ContinuousFileReaderOperator. Together with the new "allowed lateness" setting in window operator this can lead to elements being dropped as late.
Also, ContinuousFileReaderOperator does not correctly assign ingestion timestamps since it is not technically a source but looks like one to the user.