Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange for Amazon S3
  3. PowerExchange for Amazon S3 Configuration Overview
  4. Amazon S3 Connections
  5. PowerExchange for Amazon S3 Data Objects
  6. PowerExchange for Amazon S3 Mappings
  7. Appendix A: Amazon S3 Data Type Reference
  8. Appendix B: Troubleshooting

PowerExchange for Amazon S3 User Guide

PowerExchange for Amazon S3 User Guide

Troubleshooting for PowerExchange for Amazon S3

Troubleshooting for PowerExchange for Amazon S3

How to solve the following error that occurs while running an Amazon S3 mapping on the Spark engine to write a Parquet file and then run another Amazon S3 mapping or preview data in the native environment to read that Parquet file: "The requested schema is not compatible with the file schema."
What are the performance tuning guidelines to read data from or write data to Amazon S3?
How to solve the out of disk space error that occurs when you use PoweExchange for Amazon S3 to read and preview data?
How to solve the following error that occurs when you enable server-side encryption with KMS and run an Amazon S3 mapping on the Spark engine with EMR 5.16 distribution: " [java.lang.RuntimeException: java.lang.ClassNotFoundException: Class com.amazon.ws.emr.hadoop.fs.EmrFileSystem not found]"
How to solve the following error that occurs when you run an Amazon S3 mapping on the Spark engine and then run another mapping in the native environment with Server-side Encryption with KMS enabled: "The encryption method specified is not supported"
Can I run a mapping successfully on the Spark engine with the following configurations:
  • Use server-side encryption with KMS enabled EMR 5.20 or later distributions.
  • Use Amazon S3 bucket without enabling the KMS policy.
No. If you run a mapping on the Spark engine with such configurations, the mapping fails with following error message:
com.amazon.ws.emr.hadoop.fs.shaded.com.amazonaws.services.s3.model.AmazonS3Exception:Invalid arn us-west-1 (Service: Amazon S3; Status Code: 400; ErrorCode: KMS.NotFoundException;
If you use server-side encryption with KMS enabled EMR 5.20 or later distributions, you must enable the KMS policy for the Amazon S3 bucket to run the mapping successfully.

0 COMMENTS

We’d like to hear from you!