This document contains important information about known limitations for Data Integration Connectors.

Transcription

1 Cloud Data Integration Winter 2017 Connector Release Notes Copyright Informatica LLC 2018 Contents February... 1 New Connectors Amazon S3 V2 Connector Microsoft Azure SQL Data Warehouse V2 Connector Qlik Connector REST V2 Connector SAP BW Connector Informatica Global Customer Support... 5 This document contains important information about known limitations for Data Integration Connectors February New Connectors This section describes the new connector in the February 2018 release: Qlik Connector You can use Qlik Connector to connect to Qlik from Data Integration and write data to Qlik. You can use a Qlik object as a target in synchronization tasks, mappings, and mapping tasks. Amazon S3 V2 Connector New Features This section describes new features in Amazon S3 V2 Connector for the February 2018 release: Support for Mappings and Mapping Tasks You can create and run mappings or mapping tasks to read data from and write data to Amazon S3 objects. AWS Identity and Access Management (IAM) You can use AWS Identity and Access Management (IAM) authentication to securely control access to Amazon S3 resources. For more information, see the Data Integration Amazon S3 V2 Connector User Guide

2 Amazon S3 V2 Connector Known Limitations CCON CCON CCON CCON CCON CCON CCON CCON CCON You cannot use Amazon S3 V2 Connector to read or write files with Avro and Parquet file formats on Windows. When you run a mapping to read data from a Parquet file that contain null values, the data preview fails with the following error message: java.lang.runtimeexception: java.lang.runtimeexception: When you run a mapping to write data to a Parquet target and if you do not connect all the ports in the target, the mapping fails. If the delimiter in the source and target is a multibyte character, the mapping fails. When you run a task to write data to an Amazon S3 target and select the Import From Schema File option, the Secure Agent creates a duplicate header row in the target file. Workaround: You must select the importcolumnfromfirstline option in the Formatting Options tab. When you select an encryption type and run a mapping to read or write Avro and Parquet files, the mapping runs successfully. However, the encryption type is not honoured. When you run a mapping to write data to an Amazon S3 target and select Gzip as the compression format, the task runs successfully. However, the Amazon S3 target file does not contain the.gz extension. When you run a task to read data from or write data to a file that contains no header, the task fails. When you run a task to read or write an Avro or Parquet file, error messages appear in the session log. However, the task runs successfully. Microsoft Azure SQL Data Warehouse V2 Connector New Features This section describes new features in Microsoft Azure SQL Data Warehouse V2 Connector for the February 2018 release: IDENTITY Column You can use the IDENTITY column in synchronization and mapping tasks. For more details, see the Data Integration Microsoft Azure SQL Data Warehouse V2 Connector Help

3 Microsoft Azure SQL Data Warehouse V2 Connector Known Limitations CCON-8571 CCON-8395 CCON-8264 CCON-8263 CCON-7730 CCON-7595 CCON-7213 When you use pre-sql, post-sql or SQL Override query to read data from or write data to Microsoft Azure SQL Data Warehouse and the query length is more than 256 characters, the Secure Agent truncates the query. When you upsert or update data to Microsoft Azure SQL Data Warehouse and more than one column in the source table contains the same value as the target column on which the primary key is defined, the Secure Agent updates data incorrectly. When you use a lookup condition on a Microsoft Azure SQL Data Warehouse object and enable return all to get the values of all the multiple matched fields, the Secure Agent fails to return values. When you use a lookup condition on a Microsoft Azure SQL Data Warehouse object and enable report error on multiple matched fields, the Secure Agent returns the value for any random field. When you use a lookup condition on a Microsoft Azure SQL Data Warehouse object and schedule the task to run later, the task fails to respond. The Secure Agent does not write and dates to the Datetime2 column in a Microsoft Azure SQL Data Warehouse table. When you write data to Microsoft Azure SQL Data Warehouse, the Secure Agents incorrectly writes the :00: Datetime data type as :07: Qlik Connector Qlik Connector Known Limitations CCON-4566 When you run a task to write binary data to a.qvx file, the task fails with the following error message: CMN_1081 ERROR: Invalid Data Type Conversion Workaround: On the Field Mapping tab, do not map the fields that contain binary data and run the task

4 REST V2 Connector REST V2 Connector Known Limitations IF-9352 IF-8919 ICS-9579 CCON CCON CCON CCON CCON-9933 CCON-9744 CCON-9329 CCON-7687 CCON-4389 The namespace attribute is not supported in the request message. Request message validation is not supported when the Informatica JSON parser is enabled. After you upgrade to Spring 2017 release, if you edit a business service that is used in a REST V2 midstream transformation, the respective mapping fails with the following error: Internal error. An error occurred while loading the business service. Contact Informatica Global Customer Support. Solution: To avoid this issue, do not edit the business service. If you edit the business service, recreate the Web Services transformation and map all the required fields. When the swagger specification file contains the namespace attribute for request, the Secure Agent uses INFA namespace prefix, tns0, in place of the namespace defined in the swagger specification file. REST V2 Connector does not support extended ascii characters and I18N characters in a field name. Request message validation is not supported when the request message has XML attributes. Request message validation is not supported when the Wrapper element is set to true in the swagger specification file. REST V2 Connector parses NULL as a value if the response data has single element. When you use the hosted URL of the swagger file and the test connection fails, the validation error message shows the HTML content. When the request input field is used as a page parameter, mapping fails with the following error: [ERROR] Page parameter [ProductID] not found When you use the REST V2 connection to read JSON data with an array of response, the session log contains only the first instance of the array. Mappings that read data of Long data type fail with the following error: Hierarchial input precision set is : [102400] Workaround: In the swagger specification file, set type as normal and format as int64 for fields that contain values of Long data type

5 SAP BW Connector SAP BW Connector Fixed Limitations The following table describes fixed limitations: CCON CCON CCON SAP BW Connector does not support filters for columns of the Datetime data type. When you read data from an SAP BW source, the task fails with an error message after 10 minutes without reading any records. This issue occurs because SAP BW Connector closes the session after 10 minutes. When you create and run a task or mapping to read data from the SAP BW DSO object, SAP Connector does not list all the fields. SAP BW Connector Known Limitations There are no known limitations. Informatica Global Customer Support You can contact a Customer Support Center by telephone or online. For online support, click Submit Support Request in Informatica Intelligent Cloud Services. You can also use Online Support to log a case. Online Support requires a login. You can request a login at The telephone numbers for Informatica Global Customer Support are available from the Informatica web site at