-
Notifications
You must be signed in to change notification settings - Fork 517
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
Tracking issues of RFC-2133: Append API #2163
Comments
I found that there are two different kinds of
How do we deal with this problem?
WDYT? cc @Xuanwo references: |
It's not a big different.
No, we don't need it. To start an append process, we will need to head it first:
|
So we can specifically handle the not existing error in our implementation. |
Sftp services also support append API natively. Do I need to implement it? |
You can have a try if you want to do it. Have fun! |
Have implemented. |
I'm guessing |
It's ok to create seperate issues for services and leave this tracking issue closed. |
Already reopened. 🤣 I'll check them. |
I would like to implement the wasabi part. |
@Xuanwo I would take the obs part. |
RFC: #2133
Actions
Append
in theoio
module andAppender
trait forAccessor
#2258The text was updated successfully, but these errors were encountered: