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

   ## What changes were proposed in this pull request?
   Recon's listKeys API (/api/v1/keys/listKeys) uses full KeyInfo proto where 
lot of other key proto fields are not desired and needed. Some of them are like 
   
   `KeyLocationList,  FileEncryptionInfoProto,  OzoneAclInfo,  
FileChecksumProto etc  `
   
   In case of large keys or Multi part upload keys, key locations list can be 
huge and can create performance impact for some clients calling the listKeys 
API. So suggested and proposed light weight proto is:
   
   ```
   message KeyInfoProtoLight {
   required string volumeName = 1;
   required string bucketName = 2;
   required string keyName = 3;
   required uint64 dataSize = 4;
   required hadoop.hdds.ReplicationType type = 5;
   optional hadoop.hdds.ReplicationFactor factor = 6;
   required uint64 creationTime = 8;
   required uint64 modificationTime = 9;
   optional uint64 objectID = 14;
   optional uint64 updateID = 15;
   optional uint64 parentID = 16;
   optional hadoop.hdds.ECReplicationConfig ecReplicationConfig = 17;
   optional bool isFile = 19;
   }
   ```
   
   Above proto is light weight compared to keyinfo proto and skipped not needed 
fields.
   
   ## What is the link to the Apache JIRA
   https://issues.apache.org/jira/browse/HDDS-13335
   
   ## How was this patch tested?
   This patch is tested with existing junit and integration test cases. And 
tested using docker cluster locally.
   


-- 
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: issues-unsubscr...@ozone.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org
For additional commands, e-mail: issues-h...@ozone.apache.org

Reply via email to