Adding confluent kafka instance type#17785
Merged
Croway merged 1 commit intoapache:mainfrom Apr 17, 2025
Merged
Conversation
oscerd
approved these changes
Apr 17, 2025
Croway
approved these changes
Apr 17, 2025
mcarlett
approved these changes
Apr 17, 2025
smongiar
force-pushed
the
camel-infra-confluent-kafka
branch
from
1b5d3d5 to
2a8f1da
Compare
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
4 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.
Description
Since parameters between apache-kafka server (the default one) and cp-kafka (confluent) differ a bit, need to create a separate instance that would be activated by:
-Dkafka.instance.type=local-confluent-container