[
https://issues.apache.org/jira/browse/CAMEL-21833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932939#comment-17932939
]
Claus Ibsen commented on CAMEL-21833:
-------------------------------------
Okay so we should move the kamelet util code away from camel-kamelet and into
their correct components such as camel-kafka / camel-jackson and so on. And
avoid this provided classpath scope stuff that is causing pain.
> Kafka Batch Manual commit doesn't work if used in Kamelets
> ----------------------------------------------------------
>
> Key: CAMEL-21833
> URL: https://issues.apache.org/jira/browse/CAMEL-21833
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
> Reporter: Andrea Cosentino
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.11.0
>
>
> if you try this example:
> https://github.com/apache/camel-kamelets-examples/tree/main/jbang/kafka-batch-s3
> you'll notice the manual commit never happens. If you try to log the content
> of the header in the batch-manual-commit-action using
> https://github.com/apache/camel/blob/main/components/camel-kamelet/src/main/java/o[…]/component/kamelet/utils/transform/kafka/BatchManualCommit.java
> it seems on line 34
> the processor is not able to access the KafkaManualCommit instance
> If you run the integration test in the kafka component, everything seems to
> work, but with Kamelets it's not
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
