Open Charantl opened 2 months ago
I think Beam supports S3 natively; we should probably just add a dependency and maybe set some filesystem options to fix this. I will take a look at this soon.
@bashir2, We are still facing the same issue while applying the S3 location in dwhRootPrefix of docker/config/application.yaml file.
Thanks @Charantl for the note; when I fixed this last month I only tested it in the base pipeline and made sure S3 output locations work. This error is coming from the controller which I missed. I am going to fix it next week.