Allow single and multi-level traverse under EvalPath and EvalFilter respectively

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      • 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

            Assignee:
            [DO NOT USE] Backlog - Query Optimization
            Reporter:
            Svilen Mihaylov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: