+1 for adding an OVERWRITE_EXISTING_FILES option to FileSystems interface to make this explicit.
I think FileSystems is the place where we should try to enforce an easy to use API that is consistent across file-system implementations of Beam. For example rename with OVERWRITE_EXISTING_FILES should work for renaming using a loop as Luke mentioned. I expect FileSystem interface to be flexible and to be somewhat file system dependent. This will make the life easy for people who want to add support for new file systems. Seems like Java File API allows similar flexibility across platforms. For example, https://docs.oracle.com/javase/7/docs/api/java/io/File.html#renameTo(java.io.File) "Many aspects of the behavior of this method are inherently platform-dependent" [ Full content available at: https://github.com/apache/beam/pull/6289 ] This message was relayed via gitbox.apache.org for [email protected]
