curcur commented on a change in pull request #16606:
URL: https://github.com/apache/flink/pull/16606#discussion_r684084187
##########
File path:
flink-core/src/main/java/org/apache/flink/api/common/ExecutionConfig.java
##########
@@ -127,13 +128,29 @@
private boolean forceAvro = false;
private long autoWatermarkInterval = 200;
+ // ---------- statebackend related configurations
------------------------------
/**
* Interval in milliseconds for sending latency tracking marks from the
sources to the sinks.
*/
private long latencyTrackingInterval =
MetricOptions.LATENCY_INTERVAL.defaultValue();
private boolean isLatencyTrackingConfigured = false;
+ /** Interval in milliseconds to perform periodic materialization. */
+ private long periodicMaterializeInterval =
+
StateBackendOptions.PERIODIC_MATERIALIZATION_INTERVAL.defaultValue();
+
+ /** Interval in milliseconds for initial delay of periodic
materialization. */
+ private long periodicMaterializeInitDelay =
+
StateBackendOptions.PERIODIC_MATERIALIZATION_INIT_DELAY.defaultValue();
+
+ /** Max allowed number of failures */
+ private int materializationMaxAllowedFailures =
+
StateBackendOptions.MATERIALIZATION_MAX_ALLOWED_FAILURES.defaultValue();
+
+ /** Flag to enable periodic materialization */
+ private boolean isPeriodicMaterializationEnabled = false;
Review comment:
Not to randomize materialization. It provides a way that only uses
changelog
OR changelog + materialization.
For testing purposes (at least for now), I think it is quite important.
Using very big intervals could also be a solution, but it depends on the
implementation of how materialization is implemented, which as you commented
(very practical).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
