Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8321561

(fs) Clarify non-atomic behavior of Files.move

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Fixed
    • P4
    • 23
    • 21, 22
    • core-libs
    • b06

    Description

      Although the existence and description of the ATOMIC_MOVE option imply the possibility of the Files.move operation not being performed as a atomic operation, this is not explicitly stated. For example, if REPLACE_EXISTING is specified, a file having the same path as the move target might be deleted and then another file created in the same location before the actual move occurs. This will result in a potentially confusing FileAlreadyExistsException as described in JDK-8150700.

      Attachments

        Issue Links

          csr for

          CSR - null JDK-8323194 (fs) Clarify non-atomic behavior of Files.move

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JDK-8150700 (fs) FileAlreadyExistsException with Files.move with REPLACE_EXISTING

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-8325302 Files.move(REPLACE_EXISTING) throws NoSuchFileException on deleted target

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          links to

          Commit Commit openjdk/jdk/19287eee

          Review Review openjdk/jdk/17061

          Activity

            People

              bpb Brian Burkhalter
              bpb Brian Burkhalter
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: