Details

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

      Description

      HADOOP-14035 hasn't yet been merged with HADOOP-13345, but it adds tests that will break when run with S3Guard enabled. It expects that certain filesystem actions will throw exceptions when the client-provided encryption key is not configured properly, but those actions may sometimes bypass S3 entirely thanks to S3Guard (for example, getFileStatus may not actually need to invoke s3GetFileStatus). If the exception is never thrown, the test fails.

      At a minimum we should tweak the tests so they definitely invoke S3 directly, or just skip the offending tests when anything but the Null implementation is in use. This also opens the larger question of whether or not S3Guard should be serving up metadata that is otherwise only accessible when an encryption key is provided.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                mackrorysd Sean Mackrory
                Reporter:
                mackrorysd Sean Mackrory
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: