dosubot[bot] commented on issue #7821: URL: https://github.com/apache/opendal/issues/7821#issuecomment-4796839951
<!-- Answer --> Thanks for the report. Here's what I found for each issue: **AZDLS — "Unsupported (permanent) => copy"** The `azdls` backend does **not** declare `copy` as a native capability [[1]](https://github.com/apache/opendal/blob/27d5677d4526519313cbce00cd28f8fbcc099642/core/src/services/azdls/backend.rs#L302-L320). It supports `stat`, `read`, `write`, `delete`, `rename`, `create_dir`, and `list`, but copy is not among them. If it was working for you before, you may have been using a version/configuration that fell back to a read-then-write pattern, or you might be thinking of `rename` (which *is* supported natively). For now, the workaround you're already using (read → write → delete) is effectively what you'd need to do. **S3 (NetApp) — "Missing content_length http header"** The S3 copy operation uses AWS's server-side `CopyObject` API [[2]](https://github.com/apache/opendal/blob/27d5677d4526519313cbce00cd28f8fbcc099642/core/src/services/s3/core.rs#L656-L701). NetApp's S3-compatible endpoint may not fully implement this API the same way AWS does. There have been significant changes to the S3 copy implementation in recent releases — including multipart copy support [[3]](https://github.com/apache/opendal/pull/7541) and content-length hint handling [[4]](https://github.com/apache/opendal/pull/7543) — which may interact poorly with non-standard S3 implementations. A few questions that would help narrow this down: - What version of OpenDAL are you using? - How large are the files you're trying to copy on NetApp S3? - Can you share the full error/traceback for the NetApp S3 case? If the NetApp endpoint doesn't return a `Content-Length` header in its `CopyObject` response, that would be a compatibility issue with how OpenDAL parses the response. Filing with the full traceback and version info would help the maintainers pinpoint the exact code path. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fopendal).* --- Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fopendal). [](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fopendal&message_id=20537af9-da5f-4019-b821-4d7c68c69c97) [](https://github.dosu.com/apache/opendal?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fopendal) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fopendal) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
