Connectors (BI, Kafka, Spark)
35 results found
-
Enable custom DRDL upload for Atlas BI Connector
We cannot upload custom DRDL to Atlas BI connector. This forces us to roll our own BI connector
25 votes -
Bi connector - store schema information
We have the BI connector installed/configured via OPS manager on one of our deployments.
When we have to restart the node, the BI connector takes a long time to start as it has to rebuild the schema.
Hence we would like to file an enhancement request to be able to store the schema information and then retrieve it again after a restart.10 votes -
Enable CSFLE decryption in BI Connector
Enable CSFLE decryption in BI Connector, in order to provide encrypted fields in MongoDB decrypted for ODBC exposition.
CSFLE is described here: https://www.mongodb.com/docs/manual/core/security-client-side-encryption/.
For exemple, CSFLE would then be an option triggerable at BI Connector Launch, that should come with KMS link or keyring if enabled.9 votes -
Allow separate whitelist for Atlas BI Connector
Currently, whitelisting is only possible at the Project level. We would like to allow whitelisting of the BI connector instance separately from the project.
The Users/IPs that connect to mongo are completely different for BI connector vs the actual DB
8 votes -
Support Prepared Statements in BI Connector
The Power Query Editor in Microsoft leverages a prepared statement for query/filtering.
Error message:
This command is not supported in the prepared statement protocol yetThis is a feature request to support prepared statements in the mongosqld BI Connector service.
7 votes -
BI Connector username and password in yaml file
Currently BI Connector has username and password in clear. this presents problem in terms of security. BI connector has to have a way to encrypt the password and then we store the encrypted password which BI connector can decrypt and use it. it can be any standard encrypt decrypt algorithm but the secret key can be generated by the person using this.
6 votes -
BI Connector Atlas - View current schema creation/update status
In Atlas the is no way to see the BI connector logs, so, the request is to be able to see the Current schema creation/update status or even better, be able to see the log.
6 votes -
Enable Write Permission In BI
Hope BI enable write permission because a lot of system especially Windows base using ODBC
6 votes -
Notification and alerts when BI Connector fails
When a BI Connector fails, no alerts are sent to admins, only the notification on the page is available indicating that it will "restart in 5 minutes".
6 votes -
Add X509 as a Authentication Method
The current authentication methods lack in their ability to control password complexity requirements (SCRAM-SHA-*) or require exposing on-premise LDAP servers to the public internet. The addition of X509 is worthwhile given that MongoDB Atlas already supports X509 as a user authentication mechanism.
5 votes -
CFLE support for Kafka connector
Using MongoDB CFLE, The data need to be passed to downstream using Kafka connector which is consumed by downstream datalake for further processing. When data is pushed into Kafka it will remain encrypted and same encrypted data will land into the datalake, as encryption and decryption is happening at the driver level.
If Kafka connector supports CFLE encryption/decryption this would work seamlessly
4 votes -
Ignore heartbeats-mongodb topic by default
As per KAFKA-208, SMTs can't be applied to the heartbeats-mongodb topic. Users should not have to configure each connector to ignore this topic. Please either ignore this topic by default or provide a command-line switch so it can be ignored.
4 votes -
Kafka source connector once only semantics
Added as a suppport case here : https://support.mongodb.com/case/00634630
When using the connector as a Source, i.e we capture change streams from the Source Mongo DB and stream that to a Kafka endpoint.
Imagine these are updates on financial transactions in mongodb and they are NOT tolerant to
1) missed data and
2) duplicated data
in that order.So, we need to make sure that the Change Streams that we are observing(matching) on, are delivered once and exactly once to the Kafka pipeline. (Blog on the same : https://www.confluent.io/blog/exactly-once-semantics-are-possible-heres-how-apache-kafka-does-it/). If exactly-once semantics are enabled, it makes commits transactional by default.
…
4 votes -
Multiple clusters in a single mongosqld configuration.
The limitation of supporting multiple clusters in a single mongosqld configuration is now supported or not.
3 votes -
Get schema validation "feedback" in Kafka Mongo Sink Connector
Objective :
We want to be able to validate that data matches some requirements. We would like to to perform this data validation by adding a JSON schema in Mongo (such as it is described here : https://docs.mongodb.com/manual/core/schema-validation/).
Problem is that current implementation of the current Mongo DB Kafka Sink connector does not implement the required elements to benefit from features brought by this KIP : https://cwiki.apache.org/confluence/display/KAFKA/KIP-610%3A+Error+Reporting+in+Sink+Connectors
So if we define such a validation on Mongo, if a message has a value that does not match the definition, it would not go in the dead letter queue, and the…
3 votes -
MongoDB Sink Connector CDC default handler
I would like to have a default CDC handler that can process data produced from MongoDB Source Connector without Debezium https://docs.mongodb.com/kafka-connector/master/kafka-sink-cdc#cdc-handler-configuration
3 votes -
Kafka connector to support Kafka Schema Registry
One of the issues that our team has been talking about is when getting data from MongoDB, via a Kafka connector, and sending it through to Kafka we try to enforce schemas in Kafka but that schema is not enforced on the MongoDB data. This leads to developers needing to make sure they let the Data Engineering team know when their schema evolves so we can accommodate that change in the Avro schema. Our thought is to potentially have the developers use the Confluent Schema Registry to serialize their data to Avro prior to writing it to MongoDB. This would…
2 votes -
Provide an alternative sampling technique for views in MongoBI Connector
As stated in the docs (https://docs.mongodb.com/manual/reference/operator/aggregation/sample/#behavior), the
$samplestage will perform a fullCOLLSCANif some criteria won't be met. The problem is that no view (https://docs.mongodb.com/manual/core/views/) will ever meet these, as the$samplewon't be the first aggregation stage.My proposal is to implement additional,
$skip+$limitbased sampling.2 votes -
Re-sample only part of the MongoBI Connector schema
It'd be great if we could run "FLUSH SAMPLE collectionName". It's rarely the case that a lot of collections have changed at once and such a "light re-sample" might be a good alternative.
2 votes -
Implement error handling in MongoBI Connector
Right now, if the
$samplequery (used to create the DRDL schema) fails, it'll re-run the query once again, forever. The only place when the error is accessible is in the "Profiler" tab of a given node. In our case - and I believe it's common - that it was a secondary node, which "Profiler" is far less accessible than the one for the primary node.We learned it the hard way, as our cluster was silently maxing out one CPU core for over a week. After a lot of debugging, it turned out that one of our views has…
2 votes
- Don't see your idea?