-
Notifications
You must be signed in to change notification settings - Fork 420
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
Support writes to mounted local path with blobfuse #1765
Comments
Hi @scsmithr , I tried to solve the rename issue, but got another issue when write to mounted path. Could you please help to check?
|
For what it's worth, I was testing with this change to object store: https://github.com/GlareDB/arrow-rs/pull/2/files The first diff chunk explicitly drops the file so that the metadata gets flushed to blobstore before the rename. The second chunk I'm not sure is necessary. I was just trying out explicitly syncing the file, but I don't recall it actually fixing the issue. |
Thanks @scsmithr, I tried to mitigate the issue from blobfuse side. for #1 rename issue can be mitigated. I upload the tmp file before renaming. for #2 you said blobfuse doesn't support hard linking, I saw the same error when writing to DBFS, perhaps it's one of the reasons? |
…rd link (#1868) compatible to write to local file systems that do not support hard link. # Description When we write to the local file system, sometimes hard link is not supported, such as blobfuse, goofys, s3fs, so deal with it with compatibility. It is important to note that: There is another problem with blobfuse, that is, when it comes to rename, it will report errors. Because rename did not release the file handle before. See here for details: #1765 Arrow-rs is required to cooperate with the modification, for example: https://github.com/GlareDB/arrow-rs/pull/2/files Because object_store has been upgraded to 0.8, there are a lot of breaking change, so I haven't changed this one for the time being. Will fix it after upgrading to 0.8 #1858 # Related Issue(s) #1765 #1376 # Documentation
Description
Use Case
Re-open an issue for tracking #1418 (comment). Thank you.
Related Issue(s)
#1418 (comment)
GlareDB/glaredb#1809
The text was updated successfully, but these errors were encountered: