[SERVER-5609] Option to choose different hash algorithms when storing GridFS files Created: 15/Apr/12 Updated: 15/Aug/12 Resolved: 15/Apr/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | GridFS |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Alex Yam | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
We've just begun the process of storing 500millions+ files into a GridFS server farm, and we're not comfortable with the default md5 hashing method due to the birthday paradox, currently we have to calculate a stronger hash ourself and then save the file with it, after that we run another command to remove the default md5 hash to save some space. It'd be much quicker and simpler if mongodb can let us choose different hashing algorithms when saving files, md5 is for the 90s |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 15/Apr/12 ] |
|
The MD5 for gridfs isn't used for fetching, its only used to verify the upload was succesful, and so you can use it as an etag or other verification purposes. If there is a collision, it should not have any impact on correctness. |