mongo kafka
1.13.1
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
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"
The com.mongodb.kafka.connect.util.custom.credentials.CustomCredentialProvider interface can be implemented to provide an object of type com.mongodb.MongoCredential which gets wrapped in the MongoClient that is constructed for the sink and source connector.
The following properties need to be set -
mongo.custom.auth.mechanism.enable - set to true. mongo.custom.auth.mechanism.providerClass - qualified class name of the implementation class
Additional properties and can be set as required within the implementation class. The init and validate methods of the implementation class get called when the connector initializes.
When using MONGODB-AWS authentication mechanism for atlas, one can specify the following configuration -
"connection.uri": "mongodb+srv:///?authMechanism=MONGODB-AWS" "mongo.custom.auth.mechanism.enable": true, "mongo.custom.auth.mechanism.providerClass": "sample.AwsAssumeRoleCredentialProvider" "mongodbaws.auth.mechanism.roleArn": "arn:aws:iam:: :role/ "
Here the sample.AwsAssumeRoleCredentialProvider must be available on the classpath. mongodbaws.auth.mechanism.roleArn is an example of custom properties that can be read by sample.AwsAssumeRoleCredentialProvider.
Here is sample code that can work.
public class AwsAssumeRoleCredentialProvider implements CustomCredentialProvider { public AwsAssumeRoleCredentialProvider() {} @Override public MongoCredential getCustomCredential(Map map) { AWSCredentialsProvider provider = new DefaultAWSCredentialsProviderChain(); Supplier awsFreshCredentialSupplier = () -> { AWSSecurityTokenService stsClient = AWSSecurityTokenServiceAsyncClientBuilder.standard()
.withCredentials(provider)
.withRegion("us-east-1")
.build(); AssumeRoleRequest assumeRoleRequest = new AssumeRoleRequest().withDurationSeconds(3600)
.withRoleArn((String)map.get("mongodbaws.auth.mechanism.roleArn"))
.withRoleSessionName("Test_Session"); AssumeRoleResult assumeRoleResult = stsClient.assumeRole(assumeRoleRequest); Credentials creds = assumeRoleResult.getCredentials(); // Add your code to fetch new credentials return new AwsCredential(creds.getAccessKeyId(), creds.getSecretAccessKey(), creds.getSessionToken());
}; return MongoCredential.createAwsCredential(null, null)
.withMechanismProperty(MongoCredential.AWS_CREDENTIAL_PROVIDER_KEY, awsFreshCredentialSupplier);
} @Override public void validate(Map map) { String roleArn = (String) map.get("mongodbaws.auth.mechanism.roleArn"); if (StringUtils.isNullOrEmpty(roleArn)) { throw new RuntimeException("Invalid value set for customProperty");
}
} @Override public void init(Map map) {
}
} Here is the pom.xml that can build the complete jar containing the AwsAssumeRoleCredentialProvider
