[jira] [Commented] (CAMEL-14931) camel-kafka additionalProperties not set

["Omar Al-Safi (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-14931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17087490#comment-17087490 ] 

Omar Al-Safi commented on CAMEL-14931:
--------------------------------------

Hey [~Gurpal2000], 

This is actually _not_ a bug, indeed it should accept {{Map}} since you have used the EndpointDSL as well as ComponentDSL which they will enforce typesafe parameters, thus enforcing the `Map` type which is intended here. However, in case of string prefixed with {{additionalProperties}}, this is only valid if you use the plain String URI, e.g: 
{{kafka:mytopic?brokers=broker1:12345,broker2:12566&partitioner=com.class.Party&additionalProperties.extra.1=123&additionalProperties.extra.2=test}}. 

Hope is clear! 

Regards, 
Omar

> camel-kafka additionalProperties not set
> ----------------------------------------
>
>                 Key: CAMEL-14931
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14931
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-kafka
>    Affects Versions: 3.2.0
>            Reporter: Gurpal2000
>            Assignee: Omar Al-Safi
>            Priority: Minor
>         Attachments: log.txt
>
>
> Camel: 3.2.0
> SB: 2.2.6
> Java: 1.8
> For a kafka producer, it seems the additionalProperties method does not seem to take effect. Specifically, the goal is to set "transactional.id" and I thought additionalProperties is the way to do it.
> I have attached a log where the kafka properties shows "transactional.id = null" on startup. I assume it should be set on startup. Other values are set as expected.
> Test code here: [https://github.com/gurpal2000/camelproblemdemo3|https://github.com/gurpal2000/camelproblemdemo3]
> You will need to have a sample broker running. I used a docker one.
> The documentation mentions prefixing the value with "additionalProperties" also. That does not work either.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)