Table of Contents

Search

  1. Abstract
  2. PowerExchange for Amazon Redshift
  3. PowerExchange for Amazon S3
  4. PowerExchange for Cassandra
  5. PowerExchange for DataSift
  6. PowerExchange for Facebook
  7. PowerExchange for Greenplum
  8. PowerExchange for HBase
  9. PowerExchange for HDFS
  10. PowerExchange for Hive
  11. PowerExchange for JD Edwards EnterpriseOne
  12. PowerExchange for LDAP
  13. PowerExchange for LinkedIn
  14. PowerExchange for MapR-DB
  15. PowerExchange for Microsoft Azure Blob Storage
  16. PowerExchange for Microsoft Azure Data Lake Store
  17. PowerExchange for Microsoft Azure SQL Data Warehouse
  18. PowerExchange for Microsoft Dynamics CRM
  19. PowerExchange for MongoDB
  20. PowerExchange for Netezza
  21. PowerExchange for OData
  22. PowerExchange for Salesforce
  23. PowerExchange for SAP NetWeaver
  24. PowerExchange for Snowflake
  25. PowerExchange for Tableau
  26. PowerExchange for Teradata Parallel Transporter API
  27. PowerExchange for Twitter
  28. PowerExchange for Web Content-Kapow Katalyst
  29. Informatica Global Customer Support

PowerExchange Adapters for Informatica Release Notes

PowerExchange Adapters for Informatica Release Notes

PowerExchange for HDFS Known Limitations (10.2.1)

PowerExchange for HDFS Known Limitations (10.2.1)

The following table describes known limitations:
Bug
Description
OCON-12579
If you set the Hive warehouse directory in a Hadoop connection to an encrypted HDFS directory and the impersonation user does not have the DECRYPT_EEK permission, complex file mappings run indefinitely on the Hive engine.
OCON-11753
If you use a non-Kerberos Cloudera cluster and try to import a complex file data object with the Avro format concurrently on 10 Developer tool client machines, the metadata fetch fails with a
Filesystem closed
error.
OCON-1108
When you configure pushdown optimization, a complex file mapping fails to write to the target if the file has the .seq extension.
Workaround: Change the file extension to something other than .seq.
BDM-14811
Validating a mapping shows the incorrect name of the parameter when you select a type that is not valid for the connection parameter.
This error occurs when you import a flat file from the Hadoop environment, parameterize the connection name, and change the parameter type to a type that is not valid.