rkhachatryan commented on code in PR #20708:
URL: https://github.com/apache/flink/pull/20708#discussion_r957727218
##########
docs/layouts/shortcodes/generated/checkpointing_configuration.html:
##########
@@ -18,7 +18,7 @@
<td><h5>state.backend.local-recovery</h5></td>
<td style="word-wrap: break-word;">false</td>
<td>Boolean</td>
- <td>This option configures local recovery for this state backend.
By default, local recovery is deactivated. Local recovery currently only covers
keyed state backends. Currently, the MemoryStateBackend does not support local
recovery and ignores this option.</td>
+ <td>This option configures local recovery for this state backend.
By default, local recovery is deactivated. Local recovery currently only covers
keyed state backends. Currently, the OperatorStateBackend does not support
local recovery and ignores this option.</td>
Review Comment:
I think these two lines mean the same:
```
Local recovery currently only covers keyed state backends.
```
```
Currently, the OperatorStateBackend does not support local recovery and
ignores this option.
```
We DO have operator state backend in the code, but it's not exposed to the
user (it's not possible to set state.backend to operator for example). So I'd
just remove the 2nd sentence.
##########
flink-core/src/main/java/org/apache/flink/configuration/CheckpointingOptions.java:
##########
@@ -142,8 +142,8 @@ public class CheckpointingOptions {
* This option configures local recovery for this state backend. By
default, local recovery is
* deactivated.
*
- * <p>Local recovery currently only covers keyed state backends.
Currently, MemoryStateBackend
- * and HashMapStateBackend do not support local recovery and ignore this
option.
+ * <p>Local recovery currently only covers keyed state backends.
Currently, the
+ * OperatorStateBackend does not support local recovery and ignore this
option.
Review Comment:
ignore**s**
--
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]
