Feature request: Hasher, copy hashes on server-side copy (maybe simple copy too)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 59.9k
- Forks
- 5.4k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 48
Description
i see that if i use the --hasher-auto-size and copying files in same remote, so rclone uses server-side copy, then the hashes aren't just copied to the new files, but re-hashing all.
I think copying the hashes is enough for server-side copy, as its very likely that the server verifies the copy. I don't know how rclone verifies the copies it not server-side, but maybe for those its enough too, or perhaps it should be chooseable with a command line flag to copy the hash, or re-hash on non server side copy
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the --hasher-auto-size handling and the server-side copy path, then compare how hashes are currently handled for server-side and non-server-side copies. The issue is done when the intended hash-copy versus re-hash behavior is defined and implemented consistently, including whether a command-line choice is needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100