Table of Contents

Search

  1. Abstract
  2. 2020 - August
  3. 2020 - July
  4. 2020 - April
  5. 2020 - February
  6. 2020 - January
  7. 2019 - November
  8. 2019 - September
  9. 2019 - August
  10. 2019 - July
  11. 2019 - June
  12. 2019 - May
  13. 2019 - April
  14. 2019 - March
  15. Informatica Global Customer Support

Connector Release Notes

Connector Release Notes

Microsoft Azure Cosmos DB SQL API Connector Known Limitations

Microsoft Azure Cosmos DB SQL API Connector Known Limitations

The following table describes known limitations:
CR
Description
CCON-18390
When you run a mapping to perform an insert, update, or delete operation on a Cosmos DB target and the target collection is empty, the mapping fails.
CCON-17439
When you read data from a Cosmos DB source, the mapping fails if you set the Tracing Level option to Verbose Data.
CCON-12139
When you run a task to fetch the data and the collection name or column consists of UTF characters, the task fails with an error.
CCON-12075
If you run a task and the database has many objects, the object selection and object search processes take a long time.
CCON-12052
When you run a mapping to read data from or write data to Microsoft Azure Cosmos DB, by default the scale of a double data type is set to 0 in the target file. This might result in data loss.
CCON-11996
When you run a task to fetch the data and the Cosmos DB source contains special characters, the task fails with an error.
CCON-11984
When you run a mapping to read data from a Cosmos DB source and write data to a Cosmos DB target, even if the mapping runs successfully the following error appears in the session log:
[Error] log4j:WARN No appenders could be found for logger(com.microsoft.azure.documentdb.DocumentClient)
CCON-11983
When you create a task, select
Formatting Options
, and import the schema source, the columns are not projected in the schema file.


Updated August 02, 2020