S3FileSystem.checksum() returns different values if file is moved to a new bucket
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 305
- Avg merge
- 22h 37m
- Merged PRs (30d)
- 4
Description
The value of S3FileSystem.checksum() changes when a file is moved to a new location even if the file is not modified.
I have a file at s3://path/file
I copy that file to s3://path/a/file
The values of S3FileSystem.checksum('s3://path/file) and S3FileSystem.checksum('s3://path/a/file') are different when they should be the same.
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 at the S3FileSystem.checksum() entry point and reproduce the report using the two S3 paths in the issue, checking whether the checksum inputs differ because of the object location. The issue is done when an unchanged file returns the same checksum after being copied to a new bucket or path, with tests covering that move.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100