It sounds like EnumerableThetaJoin is necessary for that query. I don’t believe that an equi-join would give the right answer. Because of the outer it’s difficult to push down or pull up the condition.
> On May 7, 2018, at 2:42 AM, [email protected] wrote: > > In case of queries having outer joins with one condition on equality between > two columns and another condition on one particular column, then in > optimization, LogicalJoin has been converted to EnumerableThetaJoin instead > of EnumerableJoin. How to make changes such that LogicalJoin will not be > converted to EnumerableThetaJoin, but to EnumerableJoin?
