Hey team - any reason Daft doesn't emit a failure ...
# general
j
Hey team - any reason Daft doesn't emit a failure message when attempting to write a csv to a location that doens't exist?
j
It should give an error… What are you currently observing?
j
It was outputting the target location in stdout even if the target location didn’t exist
E.g if i write it in User/jake/documents/ it wouldn’t error but the location doesn’t exist - the correct one is /User/jake/Documents/ (Not sure if it doesn’t error due to case sensitive)
j
I’m guessing it will create the necessary folders and then write the CSVs — Would you expect different behavior?
We optimized the experience for S3 and cloud storage, which does differ from the experience with local filesystems a little bit because object stores don’t have the concept of folders
c
I believe it is case insensitive, e.g. i just tried writing to "/Users/colinho/documents" and the write succeeds in "/Users/colinho/Documents"
j
Hmm - weirdly the behaviour didn’t work for me, nothing was written to the correctly cased location. I’ll double check again in a few hours. Behaviour id expect is if the target write location doesn’t exist locally it would throw an error saying location doesn’t exist essentially, similiar to pandas
My Bad - looks like it is behaving as expected and was creating the folder without me realising