Hi, it looks like in cases where two schema entries share the same downloaded_name, any operation that touches both will show md5 mismatches and rerun the download step.
You could put a download_as field in the schema, or form a different filename out of a combination of fields guaranteed to be unique. Then rename the file after download.
Hi, it looks like in cases where two schema entries share the same
downloaded_name, any operation that touches both will show md5 mismatches and rerun the download step.You could put a
download_asfield in the schema, or form a different filename out of a combination of fields guaranteed to be unique. Then rename the file after download.