[ https://issues.apache.org/jira/browse/HADOOP-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742334#comment-16742334 ]
Steve Loughran commented on HADOOP-15843: ----------------------------------------- bq. Tested on ireland. Got timeout on org.apache.hadoop.fs.s3a.s3guard.ITestDynamoDBMetadataStore:testProvisionTable (unrelated?). I'd missed that test: looks like its doomed once it's been invoked enough times that day for changing capacity to fail. See HADOOP-15426's change to testDynamoDBInitDestroyCycle for similar. How about you file a JIRA to cut that test, because we've moved beyond it and it can only cause trouble. > s3guard bucket-info command to not print a stack trace on bucket-not-found > -------------------------------------------------------------------------- > > Key: HADOOP-15843 > URL: https://issues.apache.org/jira/browse/HADOOP-15843 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Affects Versions: 3.3.0 > Reporter: Steve Loughran > Assignee: Adam Antal > Priority: Minor > Attachments: HADOOP-15843-001.patch, HADOOP-15843.002.patch > > > when you go {{hadoop s3guard bucket-info s3a://bucket-which-doesnt-exist}} > you get a full stack trace on the failure. This is overkill: all the caller > needs to know is the bucket isn't there. > Proposed: catch FNFE and treat as special, have return code of "44", "not > found". -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org