HDDS-13335. Implement and adopt lightweight proto for Recon listKeys API #8699
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 etcIn 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:
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.
API response before the PR change:
API response after the PR change: