Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-15619 Über-JIRA: S3Guard Phase IV: Hadoop 3.3 features
  3. HADOOP-15843

s3guard bucket-info command to not print a stack trace on bucket-not-found

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.3.0
    • Fix Version/s: 3.3.0
    • Component/s: fs/s3
    • Labels:
      None

      Description

      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".

        Attachments

        1. HADOOP-15843-001.patch
          12 kB
          Steve Loughran
        2. HADOOP-15843.002.patch
          9 kB
          Adam Antal
        3. HADOOP-15843-03.patch
          9 kB
          Steve Loughran

          Issue Links

            Activity

              People

              • Assignee:
                adam.antal Adam Antal
                Reporter:
                stevel@apache.org Steve Loughran
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: