davsclaus opened a new issue, #3182:
URL: https://github.com/apache/camel-kamelets/issues/3182

   Consolidating the Kafka Kamelets (#3144) raised a wider question. Do we want 
Kamelets for the Apicurio Registry at all, or should the catalog instead (or 
also) support the Confluent Schema Registry, which many people use with Kafka?
   
   ### Today
   
   There are seven Apicurio Kamelets, all with a Kafka connection that has no 
security:
   
   - `kafka-apicurio-registry-not-secured-sink`
   - `kafka-apicurio-registry-not-secured-source`
   - `kafka-batch-apicurio-registry-not-secured-source`
   - `kafka-batch-apicurio-registry-source`
   - `kafka-not-secured-apicurio-registry-json-source`
   - `kafka-not-secured-apicurio-registry-sink`
   - `kafka-not-secured-apicurio-registry-source`
   
   Between them:
   
   - They mix Avro and JSON Schema, and three different serde versions.
   - Four of them depend on Quarkus-only jars and fail on Camel JBang.
   
   Nothing supports the Confluent Schema Registry.
   
   The camel-kafka component already has options for a Confluent-style registry:
   
   - `schemaRegistryURL`, known as `schema.registry.url` in the registry 
documentation;
   - `specificAvroReader`;
   - `valueSerializer` and `valueDeserializer`, for the serde classes.
   
   ### Options
   
   1. **Deprecate all the Apicurio Kamelets,** and remove them in a later 
release, as #3180 does for other variants.
   2. **Keep Apicurio,** consolidated into three Kamelets, as proposed in 
#3144: one sink, one source and one batch source, with Kafka security options 
and an optional registry login.
   3. **Add Confluent Schema Registry support.** It could be options on 
`kafka-source` and `kafka-sink` (registry URL, format, serde), or separate 
Kamelets, so that the plain Kafka Kamelets do not carry registry jars for 
everyone.
   4. **A generic approach:** registry options on the Kafka Kamelets that work 
for any registry with a Kafka serde, Apicurio or Confluent, with the registry 
chosen by the serde classes.
   
   ### To check
   
   - **The license of the Confluent serde jars.** Kamelet dependencies must 
have an Apache-compatible license. The Confluent serializers have shipped under 
the Apache License and under the Confluent Community License over time, so 
check the exact artifacts and versions.
   - **Usage:** whether anyone uses the Apicurio Kamelets today.
   
   _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