[SERVER-69502] Add an index parameter to traverseF lambda Created: 07/Sep/22 Updated: 28/Nov/22 Resolved: 28/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Zixuan Zhuang | Assignee: | Zixuan Zhuang |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | pm2697-m4 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | QE 2022-09-19, QE 2022-10-03, QE 2022-10-17, QE 2022-10-31, QE 2022-11-14, QE 2022-12-12 | ||||||||
| Participants: | |||||||||
| Story Points: | 5 | ||||||||
| Description |
|
Add an index of array element as the second parameter to traverseF lambda It will be Null if the first argument of traverseF is not an array. |
| Comments |
| Comment by Pawel Terlecki [ 28/Nov/22 ] |
|
Sounds good. Thanks for the update, zixuan.zhuang@mongodb.com |
| Comment by Zixuan Zhuang [ 28/Nov/22 ] |
|
pawel.terlecki@mongodb.com kyle.suarez@mongodb.com sorry for replying late, the latest performance test results (perf sys-perf) show regressions, so we decide to defer the work until there's concrete use case for this. |
| Comment by Kyle Suarez [ 23/Nov/22 ] |
|
There was a question in standup whether we should continue to pursue this code change if it will be used for something specific, or if we should defer or unschedule it entirely. Zixuan is out this week for Thanksgiving, so we've punted on the question until next week when he returns. |
| Comment by Pawel Terlecki [ 22/Nov/22 ] |
|
Are we still pursuing this change? I heard we decided to code it up differently in the meantime. |
| Comment by Kyle Suarez [ 21/Sep/22 ] |
|
This is related to the NLJ work so moving this from M2 to M4. |