[receiver/googlecloudpubsub] Add support for encoding extensions (#37109) #37137
+415
−200
Conversation
This file contains 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
alexvanboxel
force-pushed
the
pubsubreceiver-encodingextensions
branch
2 times, most recently
from
8952521 to
fa9e362
Compare
…n-telemetry#37109) Added support for encoding extensions. Setting the encoding field in the config now references the extension. If it didn't find the extension it will fall back to searching the internal encoders. To make the build in encoders consistent with the extensions they now have the same interface. The README is adapted accordingly.
alexvanboxel
force-pushed
the
pubsubreceiver-encodingextensions
branch
from
fa9e362 to
29ffa42
Compare
atoulme
approved these changes
Jan 10, 2025
I am the codeowner (sorry, should have stated that in the PR) |
spiderman meme here |
atoulme
added
the
ready to merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Added support for encoding extensions. Setting the encoding field in the config now references the extension. If it didn't find the extension, it will fall back to searching the internal encoders.
To make the build in encoders consistent with the extensions, they now have the same interface.
Link to tracking issue
Fixes #37109
Testing
Documentation
Reworked the encoding section of the README, with an example of a text_encoding extension