THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
1) Add the job-level config piplinepipeline.backlog.watermark-lag-threshold
...
Here is the specification of this config. This config will be marked Experimental.
- Name: piplinepipeline.backlog.watermark-lag-threshold
- Type: Duration
- Default value: null
- Description: If the configured value is not null, it must be greater than 0, and a source would report isProcessingBacklog=true if its watermarkLag metric is defined and the metric value exceeds the configured value. Note that this config does not support switching source's isProcessingBacklog from false to true for now.
...
The changes made in this FLIP are backward compatible. With the default value of piplinepipeline.backlog.watermark-lag-threshold, the source will not report its backlog status based on watermark lag, which is the current behavior.
...