You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Webster Homer <we...@sial.com> on 2018/06/07 15:26:56 UTC

Camel Kafka Documentation seems wrong

I am in the process of upgrading an application that uses Camel and Kafka
from Camel 2.18.2 to 21.1 and Kafka from 0.10.0.2 to 1.1.0

The Kafka upgrade just worked, however URL used by camel to specify the
kafka consumers and producers changed.

Old format:
kakfa:server.port?topic=mytopic&...

New format
kafka:mytopic?brokers=server.port&...

The old url with the new Camel throws
java.lang.IllegalArgumentException: Brokers must be configured

The documentation for Camel's Kafka component still shows the old format.
http://camel.apache.org/kafka.html

It's easy to fix, but strange that it needed to be, and that the online
documentation was not updated to reflect the change

Thanks

-- 


This message and any attachment are confidential and may be
privileged or 
otherwise protected from disclosure. If you are not the intended
recipient, 
you must not copy this message or attachment or disclose the
contents to 
any other person. If you have received this transmission in error,
please 
notify the sender immediately and delete the message and any attachment

from your system. Merck KGaA, Darmstadt, Germany and any of its 
subsidiaries do
not accept liability for any omissions or errors in this 
message which may
arise as a result of E-Mail-transmission or for damages 
resulting from any
unauthorized changes of the content of this message and 
any attachment thereto.
Merck KGaA, Darmstadt, Germany and any of its 
subsidiaries do not guarantee
that this message is free of viruses and does 
not accept liability for any
damages caused by any virus transmitted 
therewith.



Click http://www.emdgroup.com/disclaimer 
<http://www.emdgroup.com/disclaimer> to access the
German, French, Spanish 
and Portuguese versions of this disclaimer.

R: Camel Kafka Documentation seems wrong

Posted by Andrea Cosentino <an...@yahoo.com.INVALID>.
You'll find the new documentation directly in the git repository. In the old site there is a news on top of all pages about the migration. We are working on a new site with docs generated directly from repository. 
 
  Il gio, 7 giu, 2018 alle 17:27, Webster Homer<we...@sial.com> ha scritto:   I am in the process of upgrading an application that uses Camel and Kafka
from Camel 2.18.2 to 21.1 and Kafka from 0.10.0.2 to 1.1.0

The Kafka upgrade just worked, however URL used by camel to specify the
kafka consumers and producers changed.

Old format:
kakfa:server.port?topic=mytopic&...

New format
kafka:mytopic?brokers=server.port&...

The old url with the new Camel throws
java.lang.IllegalArgumentException: Brokers must be configured

The documentation for Camel's Kafka component still shows the old format.
http://camel.apache.org/kafka.html

It's easy to fix, but strange that it needed to be, and that the online
documentation was not updated to reflect the change

Thanks

-- 


This message and any attachment are confidential and may be
privileged or 
otherwise protected from disclosure. If you are not the intended
recipient, 
you must not copy this message or attachment or disclose the
contents to 
any other person. If you have received this transmission in error,
please 
notify the sender immediately and delete the message and any attachment

from your system. Merck KGaA, Darmstadt, Germany and any of its 
subsidiaries do
not accept liability for any omissions or errors in this 
message which may
arise as a result of E-Mail-transmission or for damages 
resulting from any
unauthorized changes of the content of this message and 
any attachment thereto.
Merck KGaA, Darmstadt, Germany and any of its 
subsidiaries do not guarantee
that this message is free of viruses and does 
not accept liability for any
damages caused by any virus transmitted 
therewith.



Click http://www.emdgroup.com/disclaimer 
<http://www.emdgroup.com/disclaimer> to access the
German, French, Spanish 
and Portuguese versions of this disclaimer.