Description of problem: The S3A filesystem client from Hadoop common switched from the v1 list objects API to to v2 with Hadoop 3.0. This change has been backported to downstream Hortonworks, and since Cloudera 6 is based on Hadoop 3.0, it's present there as well. We do not currently support the v2 list objects API call, and given that it's now the default behavior for S3A, we probably should. Currently, there is a workaround detailed in HADOOP-13421, which is setting a S3A property: fs.s3a.list.version="1" Additional info: https://docs.aws.amazon.com/AmazonS3/latest/API/v2-RESTBucketGET.html https://issues.apache.org/jira/browse/HADOOP-13421
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri
*** Bug 1784197 has been marked as a duplicate of this bug. ***
Hi Ranjini, This looks fine. Thanks
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:2231