Compatible the HTTP header properties with PIP-279 #1299
Merged
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.
Motivation
After pip-279, all properties keys and values use json string save to header:
X-Pulsar-Property
This PR to compatible with this change when using subscription admin API.
Also, Using
pip-279
also avoids the issue where the Go HTTP client automatically formats HTTP headers: golang/go#37834, This will impact the peek command, the previous method might retrieveproperties
with inconsistent casing compared to the user-defined.Modifications
Verifying this change
Does this pull request potentially affect one of the following parts:
If
yes
was chosen, please highlight the changesDocumentation