Fix interchanged formats of total_indexing_buffer_in_bytes and total_indexing_buffer #17070
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.
Description
Fix format interchange between
total_indexing_buffer_in_bytes
andtotal_indexing_buffer
fields in nodes API response.total_indexing_buffer_in_bytes
should display raw bytes (e.g. 53687091)total_indexing_buffer
should display human readable format (e.g. 51.1mb)Related Issues
Resolves #16910
Comments
I considered this change to be a breaking change and implemented it to take effect starting from version 3.0.0.
Would it be appropriate to apply this change to the 2.x versions as well?
If so, I would consider implementing it as follows:
Thank you for your time and consideration!
Check List
(Based on the feedback I previously received, it was mentioned that for breaking changes, the companion PR should be created after the current PR is merged. I will make sure to create the PR after this change is merged. Thank you!)
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.