wuchong opened a new pull request, #2687:
URL: https://github.com/apache/fluss/pull/2687
This pull request introduces documentation updates to highlight and explain
efficient row counting features in Fluss tables, both through the Admin API and
Flink SQL. The changes clarify the use of table statistics and pushdown
`COUNT(*)` aggregation, including important notes about changelog modes
required for Primary Key Tables.
**Table statistics and aggregation features:**
* Added a section in `website/docs/apis/java-client.md` describing the
`getTableStats` Admin API method for retrieving table statistics, including row
count, with a note about changelog mode requirements for Primary Key Tables.
* Updated `website/docs/engine-flink/reads.md` to document pushdown
`COUNT(*)` aggregation support in batch mode for Log Tables and Primary Key
Tables, with usage examples and changelog mode caveats.
* Enhanced `website/docs/quickstart/flink.md` with a quickstart example
showing how to use `COUNT(*)` in Flink SQL to efficiently retrieve the total
row count, including sample output and explanation of real-time updates.
<!--
*Thank you very much for contributing to Fluss - we are happy that you want
to help us improve Fluss. To help the community review your contribution in the
best possible way, please go through the checklist below, which will get the
contribution into a shape in which it can be best reviewed.*
## Contribution Checklist
- Make sure that the pull request corresponds to a [GitHub
issue](https://github.com/apache/fluss/issues). Exceptions are made for typos
in JavaDoc or documentation files, which need no issue.
- Name the pull request in the format "[component] Title of the pull
request", where *[component]* should be replaced by the name of the component
being changed. Typically, this corresponds to the component label assigned to
the issue (e.g., [kv], [log], [client], [flink]). Skip *[component]* if you are
unsure about which is the best component.
- Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
- Make sure that the change passes the automated tests, i.e., `mvn clean
verify` passes.
- Each pull request should address only one issue, not mix up code from
multiple issues.
**(The sections below can be removed for hotfixes or typos)**
-->
--
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]
