How to disable EnumerableThetaJoin?

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?

Re: How to disable EnumerableThetaJoin?

But I want filter node over the join node.

'Because of the outer it’s difficult to push down or pull up the condition.' Does this mean condition splitter as of now , not able to do so?

On 2018/05/07 16:39:18, Julian Hyde <jh...@apache.org> wrote: 
> 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, aishwaryaanns@gmail.com 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?
> 
> 

Re: How to disable EnumerableThetaJoin?

[Julian Hyde <jh...@apache.org>]

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, aishwaryaanns@gmail.com 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?