You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
$graphLookup fails with "Unrecognized BSON data type code 0" when the collection has a wildcard index #805
$graphLookup over a collection that has a wildcard index fails with CommandNotSupported: Unrecognized BSON data type code 0. The same query succeeds once the wildcard index is dropped. The wildcard index is on an unrelated path, not on connectFromField or connectToField.
Environment
Operating system and version: documentdb-local Docker image, Debian GNU/Linux 13 (trixie), image ghcr.io/documentdb/documentdb/documentdb-local:latest (sha256:4a341daca29b…, DocumentDB 1.0.0), host macOS 26.6.2 with OrbStack (Docker 29.8.2)
The query returns the same result with or without the wildcard index ([ { _id: 19999, n: 3 } ]), as on MongoDB 9.0.4.
Actual behavior
With the wildcard index present:
MongoServerError[CommandNotSupported]: Unrecognized BSON data type code 0
Without it, or with only a regular index on manager_id, the result is correct.
Additional context
#769 item 1 reports the same error on $lookup and infers that a wildcard index on the foreign collection triggers it, without isolating it. In our testing, a plain $lookup and a let/pipeline $lookup into a collection with a wildcard index both worked on 1.0.0, while $graphLookup fails every time. This repro isolates the trigger.
Activity