The official MongoDB Kafka Connector.

Documentation for the connector is available on https://docs.mongodb.com/kafka-connector/current/

The connector will be published on maven central.

For issues with, questions about, or feedback for the MongoDB Kafka Connector, please look into our support channels. Please do not email any of the Kafka connector developers directly with issues or questions - you're more likely to get an answer on the MongoDB Community Forums.

At a minimum, please include in your description the exact version of the driver that you are using. If you are having connectivity issues, it's often also useful to paste in the Kafka connector configuration. You should also check your application logs for any connectivity-related exceptions and post those as well.

Think you’ve found a bug? Want to see a new feature in the Kafka driver? Please open a case in our issue management tool, JIRA:

• Create an account and login.
• Navigate to the KAFKA project.
• Click Create Issue - Please provide as much information as possible about the issue type and how to reproduce it.

Bug reports in JIRA for the connector are public.

If you’ve identified a security vulnerability in a connector or any other MongoDB project, please report it according to the instructions here.

The MongoDB Kafka Connector follows semantic versioning. See the changelog for information about changes between releases.

Java 8+ is required to build and compile the source. To build and test the driver:

$ git clone https://github.com/mongodb/mongo-kafka.git
$ cd mongo-kafka
$ ./gradlew check -Dorg.mongodb.test.uri=mongodb://localhost:27017

The test suite requires mongod to be running. Note, the source connector requires a replicaSet.

• Ross Lawley [email protected]

Original Sink connector work by: Hans-Peter Grahsl : https://github.com/hpgrahsl/kafka-connect-mongodb

Additional contributors can be found here.

• ./gradlew publishArchives - publishes to Maven
• ./gradlew createConfluentArchive - creates the confluent archive / github release zip file

We use the Release Job to release the CCloud connectors to the staging bucket. In case the Release Job is broken, we need to do it locally with the following steps:

1. Commit the code changes and merge to the release branch
2. After the changes are merged, update the version in build.gradle.kts file (this will be an rc version followed by initials of the last commit hash e.g. 1.7.0-rc-b5f3b89. Commit and merge this change as well.)
3. Generate a tag with version on the release branch and push it (example as follows)

• git tag v1.7.0-rc-b5f3b89
• git push origin --tag v1.7.0-rc-b5f3b89

4. Run ./gradlew createConfluentArchive
5. Upload the zip file from ./build/confluent/ to staging bucket in AWS and replicate the permissions for the zip file from previous version

A couple of manual configuration steps are required to run the code in IntelliJ:

• Error: java: cannot find symbol. symbol: variable Versions
  Fixes: Any of the following:
  
  • Run the compileBuildConfig task: eg: ./gradlew compileBuildConfig or via Gradle > mongo-kafka > Tasks > other > compileBuildConfig
  • Set compileBuildConfig to execute Before Build. via Gradle > Tasks > other > right click compileBuildConfig - click on "Execute Before Build"
  • Delegate all build actions to Gradle: Settings > Build, Execution, Deployment > Build Tools > Gradle > Runner - tick "Delegate IDE build/run actions to gradle"