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 (10.4.1)
  15. PowerExchange for HDFS (10.4.0)
  16. PowerExchange for Hive
  17. PowerExchange for JD Edwards EnterpriseOne
  18. PowerExchange for JDBC V2
  19. PowerExchange for LDAP
  20. PowerExchange for LinkedIn
  21. PowerExchange for MapR-DB
  22. PowerExchange for Microsoft Azure Blob Storage
  23. PowerExchange for Microsoft Azure Cosmos DB SQL API
  24. PowerExchange for Microsoft Azure Data Lake Storage Gen1
  25. PowerExchange for Microsoft Azure Data Lake Storage Gen2
  26. PowerExchange for Microsoft Azure SQL Data Warehouse
  27. PowerExchange for Microsoft Dynamics CRM
  28. PowerExchange for MongoDB
  29. PowerExchange for Netezza
  30. PowerExchange for OData
  31. PowerExchange for Salesforce
  32. PowerExchange for Salesforce Marketing Cloud
  33. PowerExchange for SAP NetWeaver
  34. PowerExchange for Snowflake
  35. PowerExchange for Tableau
  36. PowerExchange for Tableau V3
  37. PowerExchange for Teradata Parallel Transporter API
  38. PowerExchange for Twitter
  39. PowerExchange for Web Content-Kapow Katalyst
  40. Informatica Global Customer Support

PowerExchange Adapters for Informatica Release Notes

PowerExchange Adapters for Informatica Release Notes

PowerExchange for Google Cloud Storage Known Limitations (10.4.0)

PowerExchange for Google Cloud Storage Known Limitations (10.4.0)

The following table describes known limitations:
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>

0 COMMENTS

We’d like to hear from you!