Copilot commented on code in PR #11204:
URL: https://github.com/apache/ozone/pull/11204#discussion_r3939297852


##########
hadoop-hdds/docs/content/interface/ReconApi.md:
##########
@@ -1397,12 +1397,15 @@ Returns the status of all the Recon tasks.
    
 * fileSize (optional)
 
-   Filters the results based on the given fileSize.
+   Filters the results by the exact upper bound of a file-size histogram bin, 
in bytes. It is not an arbitrary file
+   size or a cumulative less-than-or-equal threshold. A positive value that is 
not a bin upper bound returns an empty
+   result. This filter can be used independently or together with volume 
and/or bucket.

Review Comment:
   The docs now state that `fileSize` can be used independently of 
`volume`/`bucket`, but the current implementation only applies the `fileSize > 
0` lookup path when *both* `volume` and `bucket` are provided; otherwise 
`fileSize` is ignored during the scan. If this PR is merged without the 
implementation change from #11203, the published API docs will be incorrect.



##########
hadoop-hdds/docs/content/interface/ReconApi.zh.md:
##########
@@ -964,11 +964,13 @@ Recon跟踪所有大小从`1 KB`到`1 PB`的键。对于小于`1 KB`的键,映
     根据给定的桶名过滤结果。
     
 * fileSize (可选)
-    根据给定的文件大小筛选结果。
+    根据文件大小直方图分桶的上界精确筛选结果,单位为字节。该值不是任意文件大小,也不是小于或等于该值的
+    累计阈值。正数值如果不等于分桶上界,将回传空结果。该筛选条件可以单独使用,也可以与卷和/或桶一起使用。

Review Comment:
   The `fileSize` parameter bullet is missing the blank line used by the 
surrounding parameter list items (e.g., `volume`, `bucket`). Adding the blank 
line keeps the Markdown list formatting consistent and avoids rendering 
differences.



-- 
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]

Reply via email to