Release Notes > Fall 2016 - November > MongoDB Connector
  

MongoDB Connector

MongoDB Connector Fixed Limitations

There are no fixed limitations in this release.

MongoDB Connector Known Limitations

The following table describes known limitations:
CR
Description
CON-2350
If you run a task with the ODBC driver enabled to read from or write to MongoDB as a JSON document, the status logs of the Data Synchronization task shows as successful even though the Secure Agent fails to load the data from or to MongoDB.
CON-2349
The virtual tables from MongoDB appear in the source or target view of a task only when you import the table metadata.
CON-2348
When you refresh a MongoDB connection in the source or target view of a task, the dropped MongoDB collections still appear in the source objects or target objects list.
CON-2347
You cannot use Mongo shell commands in preprocessing and postprocessing commands of a task to write data to MongoDB.
CON-2346
You cannot use the MongoDB ODBC driver to import a MongoDB collection that does not contain data.
CON-2345
Transformation errors appear in the mapping log for MongoDB Connector even if the mapping does not contain any transformations.
Workaround: You can ignore the transformation errors.
CON-2077
When you create a MongoDB connection and specify the schema name, the connection fails with an error stating that the schema is not supported.
Workaround: Do not specify the schema name in the connection attributes. Instead, specify the database name in the Data Source Name (DSN) entry.

MongoDB Third-Party Limitations

The following table describes third-party known limitations:
CR
Description
CON-2354
Even when you enable Show array count in virtual main table, the MongoDB driver does not create the array count column.
CON-2353
When you run a mapping with a Joiner transformation to read from a MongoDB database prior to version 2.6.3, the following error might appear in the mapping log even if the nested element is not null: LEFT_SUBFIELD only supports Object
CON-2352
When you enable reading or writing as JSON documents, JSON import might fail because the JSON import and export formats in the MongoDB driver are not symmetrical.
Workaround: To load JSON documents, use the mongoimport tool.
CON-2351
When you use MongoDB Connector to insert, update, or delete records in the MongoDB database, the performance for each of these operations is slow for a MongoDB cluster when compared to a single node.