Table of Contents

Search

  1. Abstract
  2. PowerExchange for Amazon Redshift
  3. PowerExchange for Amazon S3
  4. PowerExchange for Cassandra
  5. PowerExchange for Cassandra JDBC
  6. PowerExchange for DataSift
  7. PowerExchange for Facebook
  8. PowerExchange for Google Analytics
  9. PowerExchange for Google BigQuery
  10. PowerExchange for Google Cloud Spanner
  11. PowerExchange for Google Cloud Storage
  12. PowerExchange for Greenplum
  13. PowerExchange for HBase
  14. PowerExchange for HDFS
  15. PowerExchange for Hive
  16. PowerExchange for JD Edwards EnterpriseOne
  17. PowerExchange for JDBC V2
  18. PowerExchange for LDAP
  19. PowerExchange for LinkedIn
  20. PowerExchange for MapR-DB
  21. PowerExchange for Microsoft Azure Blob Storage
  22. PowerExchange for Microsoft Azure Cosmos DB SQL API
  23. PowerExchange for Microsoft Azure Data Lake Storage Gen1
  24. PowerExchange for Microsoft Azure Data Lake Storage Gen2
  25. PowerExchange for Microsoft Azure SQL Data Warehouse
  26. PowerExchange for Microsoft Dynamics CRM
  27. PowerExchange for MongoDB
  28. PowerExchange for Netezza
  29. PowerExchange for OData
  30. PowerExchange for Salesforce
  31. PowerExchange for Salesforce Marketing Cloud
  32. PowerExchange for SAP NetWeaver
  33. PowerExchange for Snowflake
  34. PowerExchange for Tableau
  35. PowerExchange for Tableau V3
  36. PowerExchange for Teradata Parallel Transporter API
  37. PowerExchange for Twitter
  38. PowerExchange for Web Content-Kapow Katalyst
  39. Informatica Global Customer Support

PowerExchange Adapters for Informatica Release Notes (10.4.1.2)

PowerExchange Adapters for Informatica Release Notes (10.4.1.2)

PowerExchange for Google Cloud Storage Known Issues (10.4.0)

PowerExchange for Google Cloud Storage Known Issues (10.4.0)

The following table describes known issues:
Bug
Description
OCON-23109
If you select the
Is Directory
option in the data object read operation advanced properties to read files in a Google Cloud Storage folder in JSON or Binary format and run a mapping in the native environment, the mapping fails.
OCON-17932
When you specify the
Google Cloud Storage Path
in the
gs://<bucket name>
format and run a mapping on the Spark engine to write data to a Google Cloud Storage target, the mapping fails.
Workaround: Specify the
Google Cloud Storage Path
in the following format:
gs://<bucket name>/<folder_name>