ArafatKhan2198 commented on PR #4245:
URL: https://github.com/apache/ozone/pull/4245#issuecomment-1842809972

   The decision to reconsider the proposed approach for creating namespace 
summaries for OBS keys with prefix-based filtering was made after discussions 
that happened in the 
[document](https://docs.google.com/document/d/1g2NCR-kgcSfLFQRBhZfYsMZmaZ6edlA_26Pq0-qfzT8/edit)
 They expressed concerns about two key aspects:
   
   1. Performance Impact: We are concerned that the introduction of synthetic 
paths as outlined in the proposal could potentially have a negative impact on 
Recon performance. The additional complexity of generating and managing these 
synthetic paths might consume more resources and potentially slow down the 
system.
   
   2. Lack of Business Use Case: There were questions the practical necessity 
of introducing this complexity for (OBS). In contrast to the Filesystem (FSO) 
layout, where directory tables exist, it was suggested that there might not be 
a strong business need to create synthetic paths and namespace summaries for 
individual OBS keys. As a result, they proposed focusing on generating 
bucket-level summaries for OBS keys as a more pragmatic approach.
   
   Following these discussions, we've chosen to proceed with generating disk 
usage statistics at the bucket level. We've decided to put the prefix-based 
filtering on hold for now. If it becomes necessary in the future, we'll seek 
input from the community. For more information, please refer to the 
[document](https://docs.google.com/document/d/1g2NCR-kgcSfLFQRBhZfYsMZmaZ6edlA_26Pq0-qfzT8/edit).


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