fix: added deprecation warning for kafka header migration #1311
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
aryamohanan
force-pushed
the
kafka-deprecation-warning
branch
from
d5d1cb6 to
cf78e12
Compare
Merged
7 tasks
aryamohanan
force-pushed
the
kafka-deprecation-warning
branch
from
db5ccfe to
b2c5d20
Compare
kirrg001
requested changes
Sep 5, 2024
abhilash-sivan
approved these changes
Sep 6, 2024
aryamohanan
force-pushed
the
kafka-deprecation-warning
branch
from
aae5965 to
85d0535
Compare
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.
Added deprecation warning for kafka header migration, in next major release(v4) we will remove the configuration option for kafka header and by default the header format will be 'string'. For more details about the kafka migration see official documentation
Related PR
refs INSTA-809