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
Support for table field call by "." symbol during $project execution #218
Call for field by operator "." it seems to be not working using mongo-java-server.
ex.
"
{
$project: {
user: "$user._id",
},
}
"
where is "user" is a table in this example
Simiar case to mongo function "$toString"
ex. '$toString: "$_id" '
I think I'm seeing the same issue with $graphFollow. I have documents with the following format and I'm trying to graph follow based on the directReports.employeeId
In mongoplayground.net this is working as expected, with the "allReports" field in the output being populated with all child employees. But using it here I'm seeing that the allReports array is empty like so: "allReports": []
The $graphLookup issue reported in the comments is fixed in #271, now merged.
The original $project: {user: "$user._id"} example works with an array of embedded documents; I added a regression test for it. $toString is also supported. If you still encounter the original problem, please share sample documents and the complete aggregation pipeline.
Activity
Jofishy commentedon Jun 25, 2023
I think I'm seeing the same issue with $graphFollow. I have documents with the following format and I'm trying to graph follow based on the directReports.employeeId
Here is my query
In mongoplayground.net this is working as expected, with the "allReports" field in the output being populated with all child employees. But using it here I'm seeing that the allReports array is empty like so:
"allReports": []Test projection of user IDs from an embedded array
Fix graph lookup traversal through nested array fields
bwaldvogel commentedon Nov 16, 2026
The
$graphLookupissue reported in the comments is fixed in #271, now merged.The original
$project: {user: "$user._id"}example works with an array of embedded documents; I added a regression test for it.$toStringis also supported. If you still encounter the original problem, please share sample documents and the complete aggregation pipeline.