wuchong opened a new issue, #2599: URL: https://github.com/apache/fluss/issues/2599
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Description To improve discoverability and align with industry terminology, I suggest renaming the **“Changelog Generation”** section (currently at [https://fluss.apache.org/docs/0.9/table-design/table-types/pk-table/#changelog-generation](https://fluss.apache.org/docs/0.9/table-design/table-types/pk-table/#changelog-generation)) to **“Change Data Feed”**. The updated section should clearly explain how users can leverage Fluss’s virtual tables—specifically `$changelog` and `$binlog`—to consume row-level changes (inserts, updates, deletes) in a structured and efficient manner. It should also include direct links to the dedicated documentation pages for `$changelog` and `$binlog` virtual tables. This naming and framing align with established patterns in modern data systems like **Delta Lake** and **Databricks**, whose “Change Data Feed” feature serves a similar purpose: - [Delta Lake Change Data Feed](https://docs.delta.io/latest/delta-change-data-feed/) - [Databricks: Use Delta Lake change data feed](https://docs.databricks.com/aws/en/delta/delta-change-data-feed.html) Adopting the widely recognized term “Change Data Feed” will make the capability more intuitive for new users and improve consistency with ecosystem standards. ### 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]
