Gargi-jais11 opened a new pull request, #7908:
URL: https://github.com/apache/ozone/pull/7908

   ## What changes were proposed in this pull request?
   
   Ozone Recon - admin namespace summary CLI command is not giving complete 
output:
   `ozone admin namespace summary /volume1/obs-bucket`
   
   output:
   `Connecting to Recon: 
http://recon:9888/api/v1/namespace/summary?path=/volume1/obs-bucket ...`
    `[Warning] Namespace CLI is not designed for OBS bucket layout.`
    `Bucket being accessed must be of type FILE_SYSTEM_OPTIMIZED bucket layout 
or 
      LEGACY bucket layout with 'ozone.om.enable.filesystem.paths' set to true.`
     `Entity Type : "BUCKET"`
     
     The above output is incomplete it should also print information like
   1. "numVolume"
   2. "numBucket"
   3. "numDir"
   4. "numKey"
   which is present in the **SummarySubCommand class** which the current code 
is not reading correct from correct json node.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-12335
   
   ## How was this patch tested?
   
   Ran the CLI command locally on docker cluster and tested the patch:
   
   1.)
   `bash-5.1$ ozone admin namespace summary /vol2/buck1`
   
   `Connecting to Recon: 
http://recon:9888/api/v1/namespace/summary?path=/vol2/buck1 ...`
   `Entity Type : "BUCKET"`
   `Directories : 3`
   `Keys : 4`
   
   2.)
   `bash-5.1$ ozone admin namespace summary /`
   
   `Connecting to Recon: http://recon:9888/api/v1/namespace/summary?path=/...`
   `Entity Type : "ROOT"`
   `Volumes : 4`
   `Buckets : 3`
   `Directories : 7`
   `Keys : 9`
   


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