davsclaus commented on issue #3183:
URL: 
https://github.com/apache/camel-kamelets/issues/3183#issuecomment-6953266036

   ## Decision: the vendor logic goes into camel-kafka, filed as 
[CAMEL-27130](https://issues.apache.org/jira/browse/CAMEL-27130)
   
   Two options, `schemaRegistryVendor` and `schemaFormat`, let camel-kafka set 
the serde classes and the vendor's registry properties itself. The Kafka 
Kamelets then pass a few optional options through.
   
   ### Vendors
   
   Maven Central and licences checked on 2026-11-17:
   
   | Vendor | Serde artifacts | On Maven Central | Licence |
   |---|---|---|---|
   | `confluent` | `io.confluent:kafka-avro-serializer`, ... | No, only 
`packages.confluent.io/maven`, which is public with no login | Avro and client: 
Apache 2.0. JSON Schema and Protobuf: Confluent Community License and Apache 
2.0 |
   | `apicurio` | `io.apicurio:apicurio-registry-avro-serde-kafka` 3.0.8, ... | 
Yes | Apache 2.0 |
   | `aws-glue` | `software.amazon.glue:schema-registry-serde` 1.1.25 | Yes | 
Apache 2.0 |
   | `azure` | `com.microsoft.azure:azure-schemaregistry-kafka-avro` 1.1.2 | 
Yes | MIT |
   | `custom` | given by the user | | |
   
   - **Confluent-compatible registries:** several registries speak the 
Confluent registry API, so `confluent` also covers, for example, Karapace, 
Redpanda and the Confluent-compatible API of Apicurio.
   - **Confluent jars:** the user is responsible for adding the Confluent Maven 
repository, or for having the jars in their `pom.xml`. The Kamelets do not ship 
them.
   - **Apicurio version:** Apicurio 3 renamed the serde artifacts of 2.x, which 
the current Apicurio Kamelets use. A new implementation should start from 3.x.
   
   _Claude Code on behalf of Claus Ibsen_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to