Thanks. Other option is to tighten *FileSystem* spec by making all file-systems 
raise FileAlreadyExistsException for rename when destination exists. Then users 
can achieve the desired behavior through *FileSystems* abstraction using 
StandardMoveOptions.REPLACE_EXISTING. I'm fine with either. Note that the 
default behavior of FileSystems abstraction should not change since we want to 
be backwards compatible.

[ Full content available at: https://github.com/apache/beam/pull/6289 ]
This message was relayed via gitbox.apache.org for [email protected]

Reply via email to