XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • fs/s3
    • None

    Description

      if you have the endpoint or signing algorithm wrong, your first sign of trouble on an s3a FS operation is a 400 bad request during init.

      Proposed: include those properties on failure.

      Attachments

        Activity

          People

            Unassigned Unassigned
            stevel@apache.org Steve Loughran
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: