[
https://issues.apache.org/jira/browse/CAMEL-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-9467:
-------------------------------
Attachment: camel-kafka-claus.zip
Attached a .zip with the code updated and fixed in some places.
Removed using scala by mistake in the main source, and in the unit tests. The
scala is only used to run the embedded kafka server. All the test and client
code should be using the java client.
What is outstanding is likely to cleanup the configuration parameters in the
KafkaConfiguration to match what the karaf java client exposes of options. The
java client has constant fields to refer to the option keys.
And in the consumer we should remove that complicated code with the cyclic
barriers, and just leave it as a subscriber as-is.
The producer can be improved to be async with the callback, but that is
something we can look at after cleaning up the other bits first.
Then it would be good if anyone could try this camel-kafka component against a
real kafka server and see how it runs.
> Camel-Kafka: Upgrade Producer/Consumer and their configuration properties
> -------------------------------------------------------------------------
>
> Key: CAMEL-9467
> URL: https://issues.apache.org/jira/browse/CAMEL-9467
> Project: Camel
> Issue Type: Task
> Components: camel-kafka
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Fix For: 2.17.0
>
> Attachments: camel-kafka-claus.zip, camel-kafka.zip, camel-kafka.zip
>
>
> From release 0.9.0.0 the Kafka Consumer/Producer configuration properties
> seems to be changed a little.
> Also we have to use the new Java implementation of Kafka Producer/Consumer,
> actually we are using the Scala version
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
