Details

    • Sub-task
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • 2.7.3
    • 2.8.0, 3.0.0-alpha2
    • fs/s3
    • None
    • Reviewed

    Description

      HIVE-15199 shows that s3a allows rename onto an existing file, which is something HDFS, azure and s3n do not permit (though file:// does). This is breaking bits of Hive, is an inconsistency with HDFS and a regression compared to s3n semantics.

      I propose: rejecting the rename on a file -> file rename if the destination exists (easy) and changing the s3a.xml contract file to declare the behavior change; this is needed for AbstractContractRenameTest.testRenameFileOverExistingFile to handle the changed semantics.

      Attachments

        1. HADOOP-13813-branch-2-001.patch
          10 kB
          Steve Loughran
        2. HADOOP-13823-branch-2-002.patch
          10 kB
          Steve Loughran

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: