English
Cloud Data Integration Connectors All Products

Table of Contents

Search

  1. Abstract
  2. Connectors Released for 2021 February
  3. Amazon Athena Connector
  4. Amazon Redshift V2 Connector
  5. Amazon S3 V2 Connector
  6. Ariba V2 Connector
  7. Business 360 Connector
  8. Databricks Delta Connector
  9. Db2 for i CDC Connector
  10. Db2 for LUW CDC Connector
  11. Db2 for z/OS CDC Connector
  12. Google BigQuery V2 Connector
  13. Google Cloud Spanner Connector
  14. Google Cloud Storage V2 Connector
  15. JDBC V2 Connector
  16. Kafka Connector
  17. Microsoft Azure Data Lake Storage Gen2 Connector
  18. Microsoft Azure Synapse SQL Connector
  19. Microsoft SQL Server CDC Connector
  20. MongoDB Connector
  21. MySQL CDC Connector
  22. OData V2 Applications Connector
  23. Oracle Business Intelligence Publisher V1 Connector
  24. Oracle CDC Connector
  25. Oracle CDC V2 Connector
  26. Oracle Connector
  27. Oracle HCM Cloud V1 Connector
  28. PostgreSQL CDC Connector
  29. Salesforce Connector
  30. SAP BAPI Connector
  31. SAP HANA Connector
  32. SAP Table Connector
  33. ServiceNow Connector
  34. Snowflake Cloud Data Warehouse V2 Connector
  35. VSAM CDC Connector
  36. Informatica Global Customer Support

Connector Release Notes

Connector Release Notes

Back Next

Databricks Delta Connector

Databricks Delta Connector

Known Issues

The following table describes known issues:
CR
Description
CCON-30977
When you create a Databricks Delta connection and configure properties for AWS cluster environment,
S3 Service Regional Endpoint
 is ignored in elastic mappings. (February 2021)
CCON-30757
A transaction commit conflict error might occur and certain mappings might fail when you run multiple concurrent mappings to write data to Databricks Delta targets. (February 2021)
CCON-30482
When you run an elastic mapping to read data from or write data to Databricks Delta and the source or target object contains 5000 or more columns, the mapping fails. (February 2021)
CCON-29229
When you run a mapping to write data to a Databricks Delta target and use create target at runtime, if the target table already exists and contains different schema, the mapping fails. (February 2021)

Third-party known issues

The following table describes third-party known issues:
CR
Description
CCON-30746
When you create a Databricks Delta connection with an invalid org ID and test the connection, the connection prompts successful even with an invalid org ID. (February 2021)
Azure ticket number: 120122226002275
CCON-28606
View objects are displayed in the Table panel instead of the View panel while importing a Databricks Delta object. This issue occurs when the Databricks cluster is deployed on AWS cloud service. (February 2021)
CCON-27893
When you import a Databricks Delta object as target and non-Delta tables exist in the database, non-Delta tables are also displayed along with the Delta tables during the import process. (February 2021)
Azure ticket number: 142002729
CCON-28505
When you make changes to the Spark library jars on an existing Databricks cluster, the changes do not reflect. (October 2020)
Workaround:
When a new Spark driver jar is released, you must manually perform the following tasks to uninstall the Spark libraries from the existing cluster:
  1. Log in to Databricks.
  2. Click the cluster name.
  3. Click the
    Libraries
     tab.
  4. Select the databricksDeltaSparkDriver.jar you want to uninstall the library from, and then click
    Uninstall
    .
  5. Restart the cluster.
Ticket Number: 120100626001896

Updated February 11, 2021

Download Guide
Send Feedback
Explore Informatica Network
Communities
Knowledge Base
Success Portal