-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Append write operation ends in AttributeError
#249
Comments
The package default behavior is to follow Azure's default, which creates a BlockBlob, as described here. BlockBlobs do not accept an append operation. There's limited ability to create an append blob, but it hasn't been tried with this use case. From a roadmap perspective, and thinking about how the package gets used by Dask, I'd really like to understand your use case. Currently, the approach I generally see is to incrementally add new files, rather than appending to an existing file. However, the ability to append to an existing file, or collection of files when incrementally updating files, is definitely needed. @martindurant -- can you comment on how s3fs and gcsfs handle this? |
gcsfs does not support append In s3fs, append means: "make a new file, where the first block(s) is the contents of the file which previously had the same name". This is possible if the original file is >5MB. If not, append works by downloading the contents of the previous file and starting a new file from scratch. |
What happened:
Running the script for the first time (i.e. when the file does not already exist), it completes without problem. On next run when the file is to be appended:
What you expected to happen:
One of two options:
append
withfastparquet
inadlfs
fundamentally challenging due to e.g. the options of appending/modifying blobs being limited, or is it more a prioritization/not yet implemented question?)NotImplementedError
, but for some reason "Exception ignored" and instead it ends with anAttributeError
. 🤔As far as I can see, in the append mode, the mode that is tried behind the scenes is
rb+
when theAttributeError
occurs.Environment:
The text was updated successfully, but these errors were encountered: