Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
2.8.0
-
None
Description
Current Situation
- When Profile/.../TargetFileOptions/AppendFiles=true
- If Profile/.../TargetFileOptions/DisableOverwriteFiles=true:
- AppendFiles documentation excerpt:
If AppendFiles is specified with the value true, then the parameter DisableOverwriteFiles will be ignored.
- Behavior in YADE 1.x branches:
- As described in the documentation, DisableOverwriteFiles=true is ignored.
- This means that if the target file already exists, the source file is appended to the target file.
- Behavior in YADE 2.x branches:
- If the target file already exists, the transfer is logged with a "not_overwritten" state, and no source file is appended.
- AppendFiles documentation excerpt:
- When Profile/.../TransferOptions/Transactional=true or Profile/.../TargetFileOptions/Atomicity/AtomicSuffix | AtomicPrefix are set:
- Behavior in YADE 1.x branches:
- The transfer fails with an error message, e.g.:
SOSVfs_E_0050: usage of option 'SOSBaseOptionsSuperClass.append_files' is in conflict with option(s) 'SOSBaseOptionsSuperClass.atomic_prefix=, SOSBaseOptionsSuperClass.atomic_suffix=~'.
- The transfer fails with an error message, e.g.:
- Behavior in YADE 1.x branches:
- If Profile/.../TargetFileOptions/DisableOverwriteFiles=true:
-
-
- Behavior in YADE 2.x branches:
- The transfer does not fail. If the target file already exists, it is overwritten by the current transfer.
- Behavior in YADE 2.x branches:
-
Desired Behaviour
- The behaviour in YADE branches 2.x should be aligned with the behaviour of YADE branches 1.x.