New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting some error logs for camel.connector 3.1.0 with strimzi 0.20.0 update #766
Comments
Are you using the camel component version 3.1.0? Or are you using the camel connector from camel-kafka-connector? It's not clear, there is no connectors with version 3.1.0 or 3.6.0, btw the suggestion is to upgrade to the latest version |
Sorry, For the confusion. I am using connector version |
You don't need the camel component if you use the new release |
The connector are now packaged as zip |
By the way use a released version not a snapshot |
Yeah, I am trying to upgrade, but we need to upgrade strimzi 0.20 sooner, so is there any way I can fix these errors? |
Yeah, By the time I decided to use the camel-Kafka-connector, there was not stable version, I know repo was saying its not production-ready (It was WIP). So its my mistake to use that code. But I want to check with you if you know about this issue. I can try fixing by my own. |
The release 0.6.0/0.6.1 has been tested against strimzi 0.20. So the only way I see is upgrading |
Thanks for the information. |
Closing the issue, it had to do with the strimzi image. Thanks for help. |
Hello,
We have updated the kafka cluster to strimzi 0.20.0 version and I am seeing that all my connectors (s3 connectors) started printing this error.
I am running camel connector version 3.1.0 I have updated the connector to add few more headers for my specific purpose.
It has been working with 0.16, 0.19 strimzi release. The connector is working as expected (processing data and pushing to kafka) but just posting these error logs.
Do I need to upgrade camel-connector version to latest (3.6.0)? or is there any settings I can use in current camel (3.1.0) to diable this api calls.
The text was updated successfully, but these errors were encountered: