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 Connector Known Limitations

Snowflake Connector Known Limitations

The following table describes known limitations:
CR
Description
IF-28002
IF-18047
When you run a mapping that contains a filter query for a Snowflake source table with special characters, the expression string in the filter condition is not considered valid and the mapping fails.
CCON-18272
The warehouse field name does not reflect as a mandatory parameter in the Snowflake connection properties.
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-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-8363
If you select a single target and write to multiple tables, the task fails.
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