andyhuangdev opened a new pull request, #11924:
URL: https://github.com/apache/ozone/pull/11924

   ## What changes were proposed in this pull request?
   
   Recon’s heatmap API omits color when its value is zero, which occurs when a 
key’s read count is less than 0.1% of the highest read count in its bucket. 
Both Recon UIs use color to identify leaves, causing these keys to receive no 
normalized size and disappear from the heatmap.
   
   This patch identifies groups by non-empty children instead. It updates size 
normalization, legacy size-bound calculation, and click handling so 
low-read-count keys remain visible and clicking a leaf does not trigger a 
drill-down request.
   
   ## What is the link to the Apache JIRA
   
   [HDDS-17693](https://issues.apache.org/jira/browse/HDDS-17693)
   
   ## How was this patch tested?
   
   - Added regression tests first: 6 of the initial 12 cases failed before the 
fix.
   - All 14 heatmap regression tests pass, covering omitted, zero, and positive 
color values, group drill-down, and zero-size leaves.
   - Full Recon UI test suite: 118 passed, 1 skipped.
   - Production UI build and Checkstyle passed.
   - Recon RAT check passed. The full repository RAT check failed on existing 
generated and third-party files.
   
   Screenshot: Recon heatmap using mock API data: both keys are visible when 
cold-key has 1 read and hot-key has 5,000 reads. The cold-key response omits 
the color field.
   <img width="1442" height="853" alt="image" 
src="https://github.com/user-attachments/assets/8007306f-0f86-498b-b8e1-92058674d064";
 />
   


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