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

Snowflake Cloud Data Warehouse V2 Connector Known Limitations

Snowflake Cloud Data Warehouse V2 Connector Known Limitations

The following table describes known limitations:
CR
Description
CCON-25127
When you specify a custom SQL query to read from columns that have special characters, the mapping fails with the following error:
com.informatica.powercenter.sdk.SDKException: Invalid operation field name
CCON-22379
When you use the Snowflake ODBC connection to run a mapping with the
Create New at Runtime
option, but later delete the created target table and re-run the mapping task, the Secure Agent fails to create the target table.
CCON-22201
If you configure both a sort and a platform filter in a mapping and the table name has special characters, the sort query is not appended to the final query.
CCON-22031
If some records are rejected while writing large amounts of data to Snowflake, the specified rejected file might not display some of the rejected records even though the statistics of rejected records appear correctly in the session logs.
CCON-21214
When you configure cross-database pushdown optimization for a Snowflake ODBC mapping that includes a Sequence Generator transformation, pushdown optimization fails.
CCON-20090
When you use the Snowflake Cloud Data Warehouse V2 connection in a mapping and configure the
Create Target
option to create a table in Snowflake, special characters in the column name are replaced by the _ character.
CCON-19151
When you configure an unconnected lookup in a mapping configured for pushdown optimization using a Snowflake ODBC connection, and if there are multiple matches in the data, the Secure Agent processes the records, but does not log an error when it finds multiple matches.
CCON-17006
When you use a Snowflake ODBC connection in a mapping enabled with pushdown optimization to read data from two Snowflake sources that have fields with the same name and you define a filter condition for one of the common fields, the mapping fails.
CCON-17002
When you add an advanced filter condition for the source object, the condition contains the "/" separator to separate the database name, schema name, and table name, and the mapping fails with an SQL compilation error.
Workaround: Change the slash
"/"
separator to a dot
"."
in the SQL query and run the mapping.
CCON-16999
When you define a relationship for multiple source objects in a Source transformation, the condition uses the "/" separator to separate the database name, schema name, and table name, and the mapping fails with an SQL compilation error.
Workaround: Update the forward slash
"/"
separator with a dot
"."
in the SQL query and run the mapping.
CCON-15712
When you configure key range partitioning for a mapping to read data from Snowflake, the throughput does not scale linearly beyond two partitions.
Workaround: To improve the throughput, specify
CLIENT_MEMORY_LIMIT=8192
in the
Additional JDBC URL Parameters
field in the Snowflake connection properties.
CCON-11123
When you import a Snowflake object, you cannot differentiate between tables or views from the Snowflake metadata.
CCON-8548
If the lookup condition fetches multiple matches and if the multiplicity option is set to Report error, the task does not fail.
CCON-8310
You cannot read from or write to a table that has special or i18n characters in column names or the table name.


Updated August 02, 2020