davidradl commented on code in PR #27509:
URL: https://github.com/apache/flink/pull/27509#discussion_r2758346140
##########
docs/layouts/shortcodes/generated/web_configuration.html:
##########
@@ -26,6 +26,12 @@
<td>Integer</td>
<td>Number of checkpoints to remember for recent history.</td>
</tr>
+ <tr>
+ <td><h5>web.execution-graph.cache-ttl</h5></td>
+ <td style="word-wrap: break-word;">(none)</td>
+ <td>Duration</td>
+ <td>Time-to-live for cached ExecutionGraph. If not set, defaults
to the value of '<code class="highlighter-rouge">web.refresh-interval</code>'.
Setting this to 0 means the cache will always fetch fresh data, which is useful
for real-time state synchronization scenarios.</td>
Review Comment:
The only reference to web.refresh-interval is see in the docs is
[web.refresh-interval](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#historyserver-web-refresh-interval).
The config parameter starts with web. implies it is for the Web UI. There
are no other parameters starting with `web.execution-graph` - this is a Flink
internal concept. How should I understand the context of where this config
option implies?
--
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]
