dcache rest api: do not filter out fields with default and null values#7843
Merged
mksahakyan merged 1 commit into11.0from Jul 14, 2025
Merged
dcache rest api: do not filter out fields with default and null values#7843mksahakyan merged 1 commit into11.0from
mksahakyan merged 1 commit into11.0from
Conversation
when building json reply object. Enable get/set of OUTPUT quota Motivation: ----------- dCache rest api response filters out fields that have null or default (for that type) values. As the result, for instance, integer filed with 0 value is skipped (so is any filed with null value). This is not desirable Modification: ------------- Change custom Json ObjectMapper to retain fields with null and default values Result: ------- Request results returned by dCache rest api contain fields having null or default values Ticket: #7836 Patch: https://rb.dcache.org/r/14479/ Target: trunk Request: 11.0, 10.2, 10.1, 10.0, 9.2 Acked-by: Tigran Require-book: no Require-notes: yes
Contributor
|
retest this please |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
when building json reply object. Enable get/set of OUTPUT quota
Motivation:
dCache rest api response filters out fields that have null or default (for that type) values. As the result, for instance, integer filed with 0 value is skipped (so is any filed with null value). This is not desirable
Modification:
Change custom Json ObjectMapper to retain fields with null and default values
Result:
Request results returned by dCache rest api contain fields having null or default values
Ticket: #7836
Patch: https://rb.dcache.org/r/14479/
Target: trunk
Request: 11.0, 10.2, 10.1, 10.0, 9.2
Acked-by: Tigran
Require-book: no
Require-notes: yes