wuchong opened a new issue, #2298: URL: https://github.com/apache/fluss/issues/2298
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Description Currently, the **"Merge Engine"** documentation is buried deep in the hierarchy: `Table Design` → `Table Types` → `Primary Key Tables` → `Merge Engine`. Given that Merge Engines, especially the newly introduced *Aggregation Merge Engine*, are a key differentiator for Fluss in real-time feature engineering, this critical feature deserves **greater visibility and easier discoverability**. To improve the user experience and highlight Fluss’s capabilities, I propose **restructuring the documentation hierarchy** as follows: ``` Table Design ├── Overview ├── Table Types ├── Merge Engines │ ├── Default (LastRow) │ ├── FirstRow │ ├── Versioned │ └── Aggregation ├── Data Distribution └── ... ``` This change would: - Elevate **Merge Engines** to a top-level concept under *Table Design*, - Make it immediately visible to users exploring Fluss’s streaming-table capabilities, - Better reflect the strategic importance of merge logic in Fluss’s architecture. <img width="858" height="1428" alt="Image" src="https://github.com/user-attachments/assets/a2f1e583-3e74-4234-abc4-08fe4e719264"; /> ### Willingness to contribute - [ ] I'm willing to submit a PR! -- 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]
