[
https://issues.apache.org/jira/browse/CAMEL-21046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871263#comment-17871263
]
Claus Ibsen commented on CAMEL-21046:
-------------------------------------
No you just create a kafka2 component that you use for that other broker, that
is how you always do that, like with JMS as well.
Or use kamelets that work in isolation
> camel-support - Camel component must support unknown properties by a
> configuration
> ----------------------------------------------------------------------------------
>
> Key: CAMEL-21046
> URL: https://issues.apache.org/jira/browse/CAMEL-21046
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 3.22.2
> Reporter: Kartik
> Priority: Minor
>
> Currently, the camel component if it is non lenient will throw an exception
> when unknown properties are passed when creating an endpoint.
> Considering multi-tenant cloud environments, there can be cases with the same
> endpoints. For example, take a Kafka endpoint, 2 tenants can create a camel
> route having the same localhost broker with the same topic and group id which
> results in an error.
> To overcome this the component should expose certain APIs to filter & ignore
> unknown properties.
> I do see that in DefaultComponent#validateParameters function takes"
> optionPrefix" which ignores the properties starting with the provided prefix,
> This should be exposed to users.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
