Closed sp-gupta closed 6 months ago
Project ID: kafka-connect-elasticsearch
Project ID: kafka-connect-elasticsearch
Project ID: kafka-connect-elasticsearch
Project ID: kafka-connect-elasticsearch
Project ID: kafka-connect-elasticsearch
Project ID: kafka-connect-elasticsearch
Project ID: kafka-connect-elasticsearch
Project ID: kafka-connect-elasticsearch
Project ID: kafka-connect-elasticsearch
Problem
https://confluentinc.atlassian.net/browse/CC-26337
Few issues with updating
common
package:Usually in
common
repo, artifacts are created as soon as a commit is merged to a feature branch. But 6.0.x is not migrated to Semaphore. Hence, no artifacts are generated for this branch. Also, there is no provision to run connect-releases job on this repo. Hence migrated the common package to 6.1.x branch.The converters (Avro, Json etc) use
confluent.version
parameter which translates to the common package version (6.1.16-32 in this case). Upon checking the maven packages available for Kafka Avro converter, it is available till 6.1.15 So we would need to pin the converter artifacts to 6.1.15 version.Solution
We can pin the jackson version to 2.16.0 in the pom. Created a new ticket here to bump to new common version and remove jackson changes from this pom once the CP release is done at the end of the quarter.
Does this solution apply anywhere else?
If yes, where?
Test Strategy
Testing done:
Refer to the comment: https://confluentinc.atlassian.net/browse/CC-26337?focusedCommentId=2591491
Release Plan