-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
ALL
Similar to SERVER-88949, query settings make it so that the cursor hint is ignored, and therefore queries with PQS index hints applied will make queries containing '$_requestResumeToken' fail without engaging the fallback mechanism.
[js_test:find_with_resume_after_param] uncaught exception: Error: command failed: { [js_test:find_with_resume_after_param] "ok" : 0, [js_test:find_with_resume_after_param] "errmsg" : "Executor error during find command: test.normalColl :: caused by :: Failed to resume collection scan: the recordId from which we are attempting to resume no longer exists in the collection: RecordId(8)", [js_test:find_with_resume_after_param] "code" : 211, [js_test:find_with_resume_after_param] "codeName" : "KeyNotFound", [js_test:find_with_resume_after_param] "$clusterTime" : { [js_test:find_with_resume_after_param] "clusterTime" : Timestamp(1712768079, 4), [js_test:find_with_resume_after_param] "signature" : { [js_test:find_with_resume_after_param] "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="), [js_test:find_with_resume_after_param] "keyId" : NumberLong(0) [js_test:find_with_resume_after_param] } [js_test:find_with_resume_after_param] }, [js_test:find_with_resume_after_param] "operationTime" : Timestamp(1712768079, 4) [js_test:find_with_resume_after_param] } with original command request: { [js_test:find_with_resume_after_param] "find" : "normalColl", [js_test:find_with_resume_after_param] "filter" : { [js_test:find_with_resume_after_param] [js_test:find_with_resume_after_param] }, [js_test:find_with_resume_after_param] "$_requestResumeToken" : true, [js_test:find_with_resume_after_param] "$_resumeAfter" : { [js_test:find_with_resume_after_param] "$recordId" : NumberLong(8) [js_test:find_with_resume_after_param] }, [js_test:find_with_resume_after_param] "hint" : { [js_test:find_with_resume_after_param] "$natural" : 1 [js_test:find_with_resume_after_param] }, [js_test:find_with_resume_after_param] "lsid" : { [js_test:find_with_resume_after_param] "id" : UUID("b72bde45-ad57-4cbc-86c1-d3ea6f754215") [js_test:find_with_resume_after_param] }, [js_test:find_with_resume_after_param] "$clusterTime" : { [js_test:find_with_resume_after_param] "clusterTime" : Timestamp(1712768079, 4), [js_test:find_with_resume_after_param] "signature" : { [js_test:find_with_resume_after_param] "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="), [js_test:find_with_resume_after_param] "keyId" : NumberLong(0) [js_test:find_with_resume_after_param] } [js_test:find_with_resume_after_param] } [js_test:find_with_resume_after_param] } on connection: connection to localhost:20000 :
- related to
-
SERVER-88949 Explain for classic multi planner displays incorrect skip amount
- Closed