You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all, I'd like a see a new cache type where the presence of a file is the only criteria for the checksum calculation (ignoring the file size, the file timestamp, etc...). I understand such cache must be used carefully .
Usage scenario
This kind of cache would be used in a linear (many steps, without branching) workflow where a file needs to be updated.
Example 1
For example a pipeline creates a SQLite3 database and the database is updated for each process (without making a copy of the DB itself).
It could be a way to implement a workflow requiring to delete the files before #452 is in production.
For example, a VCF is annotated, each time a new annotation is added, the previous file in the workflow is deleted an re-created with a zero-size using touch, avoiding a growing space required for the storage of each annotation step.
It seems to me that both examples would make resuming the workflow impossible, right? If a task failed and the pipeline had to be re-run, there would be no way of skipping the first n steps because the intermediate files would have been removed or overwritten. Is that correct?
New feature
Hi all, I'd like a see a new cache type where the presence of a file is the only criteria for the checksum calculation (ignoring the file size, the file timestamp, etc...). I understand such cache must be used carefully .
Usage scenario
This kind of cache would be used in a linear (many steps, without branching) workflow where a file needs to be updated.
Example 1
For example a pipeline creates a SQLite3 database and the database is updated for each process (without making a copy of the DB itself).
Example 2
It could be a way to implement a workflow requiring to delete the files before #452 is in production.
For example, a VCF is annotated, each time a new annotation is added, the previous file in the workflow is deleted an re-created with a zero-size using
touch
, avoiding a growing space required for the storage of each annotation step.with something like:
Suggest implementation
well it must be somewhere in modules/nf-commons/src/main/nextflow/util/CacheHelper.java :-P
The text was updated successfully, but these errors were encountered: