unsubscribe
Le ven. 25 mai 2018 à 23:11, Felix Cheung a
écrit :
> This is the fix
>
> https://github.com/apache/spark/commit/f27a035daf705766d3445e5c6a99867c11c552b0#diff-e1e1d3d40573127e9ee0480caf1283d6
>
> I don’t have the email though.
>
> --
> *From:* Hossein
> *
Hi,
Just been bitten by finding out that there are two ScalarSubquery
expressions, one is a SubqueryExpression [1] and another is a
ExecSubqueryExpression
[2].
Could we have the ExecSubqueryExpression subclass called ScalarSubqueryExec
to follow the naming convention in logical and physical plans
Hi,
I'm trying to understand RewriteCorrelatedScalarSubquery optimization and
how extractCorrelatedScalarSubqueries [1] works. I don't understand how
"The expression is rewritten and returned." is done. How is the expression
rewritten?
Since it's private it's not even possible to write tests and
