JIRA https://issues.apache.org/jira/browse/CAMEL-19172 has been created -- Ramesh
On Sun, Mar 19, 2023 at 7:03 PM Jeremy Ross <jeremy.g.r...@gmail.com> wrote: > > https://issues.apache.org/jira/projects/CAMEL/issues > > On Fri, Mar 17, 2023 at 1:17 PM Ramesh Venkitaswaran < > venkitaswa...@gmail.com> wrote: > > > Sure. Where would I make this ticket at? Is there a JIRA board link > > that I can get? > > -- > > Ramesh > > > > On Fri, Mar 17, 2023 at 11:02 AM Claus Ibsen <claus.ib...@gmail.com> > > wrote: > > > > > > Hi > > > > > > Yeah that is a good question. Dont have super much time to help / > > > investigate this. > > > > > > Would you create a ticket to add an example at > > > https://github.com/apache/camel-kamelets-examples > > > > > > We should surely make this easier with both camel-kafka component, and > > > especially with the kafka based kamelets. > > > And jbang can help make this easier as you should ideally just configure > > a > > > few bits. > > > > > > > > > > > > > > > On Thu, Mar 16, 2023 at 1:32 PM Ramesh Venkitaswaran < > > > venkitaswa...@gmail.com> wrote: > > > > > > > Hello > > > > I am testing out camel integration with the confluent schema registry > > > > and trying to consume a message that is avro encoded using a schema > > > > from the schema registry. However, when I run the integration, camel > > > > is issuing a WARN level log message that these properties are not > > > > known configurations. > > > > > > > > Camel version: Apache Camel 3.20.2 > > > > Jbang version: 0.104.0 > > > > > > > > Here is my sample yaml: > > > > > > > > # camel-k: language=yaml > > > > > > > > - from: > > > > uri: "kafka:TOPIC_NAME" > > > > parameters: > > > > brokers: "XXXXXX:9092" > > > > clientId: "laptop" > > > > schemaRegistryURL: "https://url-to-schema-registry" > > > > additionalProperties.auto.credentials.source: USER_INFO > > > > additionalProperties.basic.auth.user.info: "XXXXXX:XXXXXX" > > > > securityProtocol: SASL_SSL > > > > saslMechanism: PLAIN > > > > saslJaasConfig: > > > > "org.apache.kafka.common.security.plain.PlainLoginModule required > > > > username=XXXXXX password=XXXXXX;" > > > > autoCommitEnable: true > > > > groupId: "example-1" > > > > specificAvroReader: true > > > > steps: > > > > - log: "${body}" > > > > > > > > And here is the relevant log lines > > > > > > > > 2023-03-16 07:14:39.500 INFO 2098 --- [ main] > > > > el.impl.engine.AbstractCamelContext : Routes startup (started:1) > > > > 2023-03-16 07:14:39.500 INFO 2098 --- [ main] > > > > el.impl.engine.AbstractCamelContext : Started route1 > > > > (kafka://IT.SMS.Platform-Events_dev) > > > > 2023-03-16 07:14:39.501 INFO 2098 --- [ main] > > > > el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (demo) > > > > started in 200ms (build:51ms init:82ms start:67ms JVM-uptime:1s) > > > > > > > > 2023-03-16 07:14:39.661 WARN 2098 --- [XXXXXX]] > > > > fka.clients.consumer.ConsumerConfig : The configuration > > > > 'specific.avro.reader' was supplied but isn't a known config. > > > > > > > > and > > > > 2023-03-16 07:14:39.661 WARN 2098 --- [XXXXX]] > > > > fka.clients.consumer.ConsumerConfig : The configuration > > > > 'basic.auth.user.info' was supplied but isn't a known config. > > > > > > > > Is there something else I need to configure to be able to deserialize > > > > avro messages? > > > > > > > > Thanks > > > > > > > > > > > > > -- > > > Claus Ibsen > > > ----------------- > > > @davsclaus > > > Camel in Action 2: https://www.manning.com/ibsen2 > >