-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Querying
-
Query
-
ALL
Currently, when doing a sharded lookup pipeline with a $text stage in the subpipeline, we will hit the following error:
{{"errmsg" : "Should never call getNext on a $match stage with $text clause", "code" : 17309, "codeName" : "Location17309", "operationTime" : Timestamp(1547497994, 58), "$clusterTime" : \{ "clusterTime" : Timestamp(1547497994, 58), "signature" : { "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="), "keyId" : NumberLong(0) } }}}
This comes from DocumentSourceMatch::getNext.
Part of this ticket will be reenabling jstests/aggregation/sources/match/text_search_requires_index.js and jstests/aggregation/sources/lookup/lookup_contains_text.js
- depends on
-
SERVER-38716 fix $geoNear and $text within $lookup sub-pipeline
- Closed
-
SERVER-38728 Allow pipeline with $lookup into a sharded collection to run on mongod
- Closed
- related to
-
SERVER-43498 Complete TODO listed in SERVER-38996
- Closed
-
SERVER-44219 Complete TODO listed in SERVER-38996
- Closed