Ban PathIdentity in Filter context

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • Fully Compatible
    • QO 2023-02-06
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We should ban the use of PathIdentity under EvalFilter. This will require asserting here, but it may also require changes in the optimization code to ensure PathId cannot be generated under EvalFilter by some rewrite

            Assignee:
            Ted Tuckman
            Reporter:
            Hana Pearlman
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: