mxm commented on code in PR #27489:
URL: https://github.com/apache/flink/pull/27489#discussion_r2741500398
##########
docs/content/docs/ops/state/disaggregated_state.md:
##########
@@ -204,4 +204,25 @@ Default is true. Setting this to false will raise the CPU
usage.
- `state.backend.forst.executor.inline-coordinator`: Whether to let task
thread be the coordinator thread.
Default is true. Setting this to false will raise the CPU usage.
+{{< hint info >}}
+`ForStStateBackend` utilizes [ForSt](https://github.com/ververica/ForSt/) as
its underlying database core.
+The current iteration of ForSt is forked from
[frocksdb](https://github.com/ververica/frocksdb),
+architected as an embedded database core specifically for Flink local state
management.
+
+While transitioning the db toward a disaggregated architecture, we encountered
significant
+architectural and engineering constraints within the existing framework.
+To address these challenges, we are now actively developing a next-generation,
+cloud-native ForSt DB written in Rust.
+
+#### Key Advantages of the New ForSt DB:
+- Architectural Simplicity: A streamlined codebase designed for high
extensibility.
+- Stream-Native Design: Optimized specifically for the unique demands of
large-scale stream processing.
+- Cloud-Native: Built from the ground up to support disaggregation.
+
+#### Roadmap & Maintenance:
+- Release Schedule: The first stable open-source version is projected for
August 2026.
Review Comment:
We don't have to be that precise in terms of a delivery date. We can also
say "end of 2026" or "soon". Up to you.
##########
docs/content/docs/ops/state/disaggregated_state.md:
##########
@@ -204,4 +204,25 @@ Default is true. Setting this to false will raise the CPU
usage.
- `state.backend.forst.executor.inline-coordinator`: Whether to let task
thread be the coordinator thread.
Default is true. Setting this to false will raise the CPU usage.
+{{< hint info >}}
+`ForStStateBackend` utilizes [ForSt](https://github.com/ververica/ForSt/) as
its underlying database core.
+The current iteration of ForSt is forked from
[frocksdb](https://github.com/ververica/frocksdb),
+architected as an embedded database core specifically for Flink local state
management.
+
+While transitioning the db toward a disaggregated architecture, we encountered
significant
+architectural and engineering constraints within the existing framework.
+To address these challenges, we are now actively developing a next-generation,
+cloud-native ForSt DB written in Rust.
+
+#### Key Advantages of the New ForSt DB:
+- Architectural Simplicity: A streamlined codebase designed for high
extensibility.
+- Stream-Native Design: Optimized specifically for the unique demands of
large-scale stream processing.
+- Cloud-Native: Built from the ground up to support disaggregation.
+
+#### Roadmap & Maintenance:
+- Release Schedule: The first stable open-source version is projected for
August 2026.
+- Deprecation Notice:As we shift our focus to the new Rust-based
implementation, the frocksdb-based version of ForSt is no longer under active
development and will be phased out (deprecated) following the new release.
Review Comment:
NIT
```suggestion
- Deprecation Notice: As we shift our focus to the new Rust-based
implementation, the frocksdb-based version of ForSt is no longer under active
development and will be phased out (deprecated) following the new release.
```
##########
docs/content/docs/ops/state/disaggregated_state.md:
##########
@@ -204,4 +204,25 @@ Default is true. Setting this to false will raise the CPU
usage.
- `state.backend.forst.executor.inline-coordinator`: Whether to let task
thread be the coordinator thread.
Default is true. Setting this to false will raise the CPU usage.
+{{< hint info >}}
+`ForStStateBackend` utilizes [ForSt](https://github.com/ververica/ForSt/) as
its underlying database core.
+The current iteration of ForSt is forked from
[frocksdb](https://github.com/ververica/frocksdb),
Review Comment:
```suggestion
The current version of ForSt is forked from
[frocksdb](https://github.com/ververica/frocksdb),
```
Maybe this is clearer?
##########
docs/content/docs/ops/state/disaggregated_state.md:
##########
@@ -204,4 +204,25 @@ Default is true. Setting this to false will raise the CPU
usage.
- `state.backend.forst.executor.inline-coordinator`: Whether to let task
thread be the coordinator thread.
Default is true. Setting this to false will raise the CPU usage.
+{{< hint info >}}
+`ForStStateBackend` utilizes [ForSt](https://github.com/ververica/ForSt/) as
its underlying database core.
+The current iteration of ForSt is forked from
[frocksdb](https://github.com/ververica/frocksdb),
+architected as an embedded database core specifically for Flink local state
management.
+
+While transitioning the db toward a disaggregated architecture, we encountered
significant
+architectural and engineering constraints within the existing framework.
+To address these challenges, we are now actively developing a next-generation,
Review Comment:
Maybe we should say:
```suggestion
To address these challenges, community members are now working on a
next-generation,
```
I don't think the initial development itself necessarily has to be done in
the open, even if it's preferable from a community point of view.
--
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]
