Conversation
Every broker interaction stays with Flink's connector, so the connector release a line is built against decides what Kafka behaviour and fixes that line can ever receive. On the older line that release targets a different patch version than the engine does and is the last one its maintainers published, which is a support boundary a deployment needs stated rather than inferred from a version table. Name the admitted pairing on the connector page alongside the client it was built against, say how it is exercised on every change, and note that a newer Kafka connector now requires a newer host line. Point the compatibility page at it instead of repeating the detail.
Contributor
Author
|
@jordepic, pinging for a review just some doc updates and making sure docs are accurate |
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
1 participant
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.
Every broker interaction stays with Flink's connector, so the connector release a line is built against decides what Kafka behaviour and fixes that line can ever receive. On the older line that release targets a different patch version than the engine does and is the last one its maintainers published, which is a support boundary a deployment needs stated rather than inferred from a version table.
Name the admitted pairing on the connector page alongside the client it was built against, say how it is exercised on every change, and note that a newer Kafka connector now requires a newer host line. Point the compatibility page at it instead of repeating the detail.