Release Notes > Fall 2016 - November > REST V2 Connector
  

REST V2 Connector

REST V2 Connector Known Limitations

The following table describes known limitations:
CR
Description
CON-4389
When you run a mapping to read data from fields that contain values of Long data type, the mapping fails 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.
CON-4387
When you run a mapping that contains a midstream transformation and if the source contains some rows that are not valid, the mapping runs successfully and does not write rows that are not valid to the target. The log file also does not display the number of rejected rows.
CON-4153
You cannot send OAuth authorization key and secret as query parameters in a request message.
Workaround: Specify the OAuth authorization credentials when you configure the REST connection.
CON-3930
When you run a Mapping Configuration task to read data from fields that contains special characters in the field name, the task fails with the following error:
Cannot create an Unstructured Data transformation.
Workaround: On the Field Mapping tab, do not map fields that contain special characters in the field name.
CON-3763
When you provide incorrect values for the REST connection attributes, the Secure Agent does not throw an error while running the Mapping Configuration task.