Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-8176

Disambiguate the destination of FsShell copies

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 0.23.2, 0.24.0
    • 0.23.2
    • fs
    • None

    Description

      The copy commands currently do not provide a way to disambiguate the expected destination of a copy. Ex.
      fs -put myfile path/mydir

      If "mydir" is an existing directory, then the copy produces path/mydir/file. If "mydir" does not exist at all, the copy produces path/mydir. The file has unexpectedly been renamed to what was expected to be a directory! It's standard unix shell behavior, but it lacks a special trait.

      Unix allows a user to disambiguate their intent by allowing path/mydir/ or path/mydir/. to mean "mydir" is always be treated as a directory. If the copy succeeds, it will always be called path/mydir/myfile.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            daryn Daryn Sharp Assign to me
            daryn Daryn Sharp
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment