[SERVER-20278] filemd5 command hides execution error in some cases Created: 03/Sep/15 Updated: 06/Dec/22 Resolved: 18/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | GridFS |
| Affects Version/s: | 3.1.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Steps To Reproduce: | 1. Import a large file with mongofiles. index. index. This will make the planner select this and not fail because table scan is not allowed in filemd5. |
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
When filemd5 command exceeds the sort memory limit, it does not report the error but instead return a result as if the file was empty. A modified version of the existing gridfs.js is attached. |