[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:
Duplicate
duplicates SERVER-13123 All callers of PlanExecutor::getNext ... Closed
Related
related to SERVER-13123 All callers of PlanExecutor::getNext ... Closed
Assigned Teams:
Query
Operating System: ALL
Steps To Reproduce:

1. Import a large file with mongofiles.
2. Drop the

{ files_id: 1, n: 1 }

index.
3. Create a

{ files_id: 1 }

index. This will make the planner select this and not fail because table scan is not allowed in filemd5.
4. Call filemd5 on the file.

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.


Generated at Thu Feb 08 03:53:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.