fix checkstyle

Author: Stephen Wu

hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3ARetryPolicy.java

@@ -215,9 +215,8 @@ protected Map<Class<? extends Exception>, RetryPolicy> createExceptionMap() {
     // policy on a 400/bad request still ambiguous.
     // Treated as an immediate failure
     RetryPolicy awsBadRequestExceptionRetryPolicy =
-      configuration.getBoolean(FAIL_ON_AWS_BAD_REQUEST, DEFAULT_FAIL_ON_AWS_BAD_REQUEST) ?
-        fail :
-        retryIdempotentCalls;
+        configuration.getBoolean(FAIL_ON_AWS_BAD_REQUEST, DEFAULT_FAIL_ON_AWS_BAD_REQUEST) ?
+            fail : retryIdempotentCalls;
     policyMap.put(AWSBadRequestException.class, awsBadRequestExceptionRetryPolicy);
 
     // Status 500 error code is also treated as a connectivity problem

hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/TestInvoker.java

@@ -326,8 +326,8 @@ public void testRetryBadRequestIdempotent() throws Throwable {
 
     IOException ex = translateException("GET", "/", BAD_REQUEST);
     assertRetryAction("Expected retry on aws bad request",
-      retryPolicy, RetryPolicy.RetryAction.RETRY,
-      ex, 1, true);
+        retryPolicy, RetryPolicy.RetryAction.RETRY,
+        ex, 1, true);
   }
 
   @Test