chihsuan opened a new pull request, #11204: URL: https://github.com/apache/ozone/pull/11204
## What changes were proposed in this pull request? This pull request documents the exact semantics of the optional `fileSize` filter on the Recon `GET /api/v1/utilization/fileCount` endpoint. The API documentation, Swagger specification, chatbot semantics guide, and LLM tool description now clarify that: * `fileSize` is matched against the exact upper bound of a file-size histogram bin. * It is not an arbitrary raw file size or a cumulative less-than-or-equal threshold. * A positive value that is not a bin upper bound returns an empty result. * The filter can be used independently or together with `volume` and/or `bucket`. The misleading chatbot example "how many files are under 1MB" is replaced with an example that asks for the single bin ending at 1 MiB. This is a documentation follow-up to #11203, which fixes the endpoint scan path to apply `fileSize` independently of the other filters. #11203 should be merged before this pull request so that the implementation and documented behavior remain consistent. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-16384 ## How was this patch tested? * `mvn -pl :ozone-recon -am install -DskipTests -DskipShade -DskipRecon -DskipDocs` * `mvn -pl :ozone-recon test -Dtest=TestReconToolCatalogConsistency -DskipShade -DskipRecon -DskipDocs` * `./hadoop-ozone/dev-support/checks/checkstyle.sh` * Parsed `recon-api.yaml` with Ruby's YAML parser. * `git diff --check` Generated-by: Codex (GPT-5) -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
