cannot copy file from s3 bucket #2740
Replies: 3 comments 1 reply
-
I have determined the issue. As the s3 path is passed through to the process from a channel using splitCsv it is not seen as a true 's3' path and therefore internally nextflow does not invoke the aws cli to access the file. If I add a column containing the fastq file name into
However, it would be nice to be able to source fastq files from multiple different s3 buckets defined by the sample.csv file rather than being restricted to the s3 bucket set by |
Beta Was this translation helpful? Give feedback.
-
I am seeing the same behaviour
Can we change this to a bug? |
Beta Was this translation helpful? Give feedback.
-
I am observing the same behavior on 22.10.4 build 5836. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am receiving the following error when running my nextflow pipeline on aws.
cp: cannot stat 's3://bucket-name/*_sample-1_*fastq.gz': No such file or directory
relevant section in the .nf file:
This process works locally when ${ReadPath} is a local dir. My assumption was that nextflow had built in capability for s3 paths and I wouldn't need to change anything in the process code.
Any suggestions would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions