[SERVER-51121] $graphqLookup with dynamic value evaluation in restrictSearchWithMatch expression Created: 24/Sep/20 Updated: 15/Jul/21 Resolved: 15/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Hitesh Baldaniya | Assignee: | Edwin Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Here is the example
In the above example, when we search for the "c12" and "d13" id and all of it's parents using aggregation.
As per the results you can see both documents contain the same document ids. If we allow dynamic search on the value "Tree.id" where the condition
will stop the repeated documents from getting again into the results set and instead of the different documents from the result set can we get output something like a single document as result set. |
| Comments |
| Comment by Edwin Zhou [ 15/Jul/21 ] | |||
|
Hi hitesh.baldaniya@contentstack.com, We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket. Best, | |||
| Comment by Edwin Zhou [ 22/Jun/21 ] | |||
|
Hi hitesh.baldaniya@contentstack.com, We still need additional information to diagnose the problem. If this is still an issue for you, would you please further specify what was unexpected in your given result set, as well as example documents that you expect to see when running the aggregation? Best, | |||
| Comment by Edwin Zhou [ 02/Jun/21 ] | |||
|
Hi hitesh.baldaniya@contentstack.com, I apologize for the delay in our response; we're extremely grateful for your patience. I'd first like to stress that the server currently supports checking objects to see if they have already been evaluated. We would otherwise end up in an infinite loop. In the example you provided, could you further specify what was unexpected in your given result set, as well as example documents that you expect to see when running the aggregation? Best, | |||
| Comment by Hitesh Baldaniya [ 29/Sep/20 ] | |||
|
Hi @Jonathan, I am actually making a kind of feature request, "$graphLookup" is working perfectly fine . What I am looking for is kind of like when we iterate through the objects we can check if they are already evaluated or not. Actual graph like evaluation where we do not visit the already visited node in the Graph. While in GraphLookup what happens is something like for each node we identify the all of it's parents nodes but in my case I am looking for global graph where how each node is connected with other and in that if node is already visited we do not have to identify the their linked nodes again. Let me know if you still have any questions. | |||
| Comment by Jonathan Streets (Inactive) [ 28/Sep/20 ] | |||
|
hi hitesh.baldaniya@contentstack.com,
Can you tell me more about what you would like to see ?
|