davsclaus opened a new issue, #3254: URL: https://github.com/apache/camel-kamelets/issues/3254
#3184 deprecated the seven Apicurio Registry Kafka Kamelets (#3182), and #3203 gave `kafka-source` and `kafka-sink` the `schemaRegistryVendor`, `schemaRegistryUrl` and `schemaFormat` options (#3183). Remove the deprecated Kamelets for 4.24, as part of reducing the Kafka Kamelets to a few (#3144): | Kamelet | Records | Use instead | |---|---|---| | `kafka-not-secured-apicurio-registry-source` | Avro | `kafka-source` with `schemaRegistryVendor: apicurio`, `schemaFormat: avro` | | `kafka-apicurio-registry-not-secured-sink`, `kafka-not-secured-apicurio-registry-sink` | Avro | `kafka-sink` with `schemaRegistryVendor: apicurio`, `schemaFormat: avro` | | `kafka-apicurio-registry-not-secured-source`, `kafka-not-secured-apicurio-registry-json-source` | JSON Schema | None yet, see below | | `kafka-batch-apicurio-registry-source`, `kafka-batch-apicurio-registry-not-secured-source` | Avro, many per message | None yet, see below | Also remove what only these Kamelets use: the `kafka_apicurio` entry of `KameletPrefixSchemeEnum`, the `quarkus-apicurio-registry-avro` version property of the root `pom.xml`, their names in the option check of `ValidateKameletsMojo`, and their rows in the catalog tests. ## Known gaps The replacement does not cover everything the removed Kamelets did. Removing them is still the plan; these are the consequences to state in the upgrade notes: - **Apicurio Registry 3.x.** The removed Kamelets used the Apicurio 2.x serde and the `/apis/registry/v2` API. `schemaRegistryVendor: apicurio` uses the 3.x serde, for Apicurio Registry 3.x. - **Apicurio with JSON Schema.** `kafka-apicurio-registry-not-secured-source` and `kafka-not-secured-apicurio-registry-json-source` read records with a JSON Schema. `kafka-source` with `schemaRegistryVendor: apicurio` and `schemaFormat: json` fails on Camel JBang because of a json-schema-validator version conflict (#3183), and its description says to use `avro` with `apicurio`. Until that is fixed, there is no Kamelet for it: use the `kafka` component with the Apicurio serde. - **Batch.** `kafka-batch-source` has no schema registry options yet (#3183), so the two `kafka-batch-apicurio-*` Kamelets have no Kamelet replacement either: use the `kafka` component with the Apicurio serde, or `kafka-source` with one record per message. - **Keycloak login to the registry.** `kafka-batch-apicurio-registry-source` and the `kafka-not-secured-apicurio-registry-*` Kamelets logged in to the registry with Keycloak. camel-kafka has no options for a registry login yet (#3183). _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]
