[SERVER-67306] Allow single and multi-level traverse under EvalPath and EvalFilter respectively Created: 15/Jun/22  Updated: 01/Jun/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Svilen Mihaylov (Inactive) Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-67436 Add parameter to Traverse path elemen... Closed
Assigned Teams:
Query Optimization
Participants:

 Description   
  • Extend traverseF and traverseP to handle multi-level and single-level traversals respectively.
  • Allow for optimizer rewrites which introduce Traverses which are not constrained by the enclosing EvalPath/EvalFilter


 Comments   
Comment by Drew Paroski [ 30/Aug/22 ]

SERVER-67436 updated SBE's implementation of traverseP() to support both single- and multi-level traversals. The ABT->SBE lowering code has not yet been updated to take advantage of this.

At present, SBE's implementation of traverseF() supports single-level traversals, but it doesn't support multi-level traversals.

Generated at Thu Feb 08 06:07:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.