Closed dduong1603 closed 1 month ago
Interesting. So, basically, if the destination file/object exists, do nothing?
In your situation, is the stream incremental? is the source a database or file?
The stream is not incremental, and the source is a file (trying to do a file to file transfer), and we want to write that same file to multiple destinations, and if something fails midway, we want to retry the process but skip the destinations that already have that file. We could probably hack together something in our process to ignore the CLI call for those particular destinations, but thought it would be nice to have a flag in the CLI call or as part of the tgt-options
😄
I guess this also applies to multiple streams within a single destination/replication, and we want to skip the file/stream that has the same destination name since they are all within the same CLI call
Cool, will add a ignore_existing
key in target-options.
any update on this @flarco ?
Should be completed this week for upcoming release #289 (likely this weekend).
Done (https://github.com/slingdata-io/sling-cli/pull/289/commits/cc6b5d1a7586e9649bf036ba8245037a195d39f9). Feel free to compile binary and test.
Right now Sling deletes the file and replace it with a new file. This changes the update time of the file and potentially impacts downstream workflow. Can we get a skip/ignore-existing option instead?