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? That'd help
a lot (and I doubt I'm the only one confused). Thanks.

[1]
https://github.com/apache/spark/blob/branch-2.3/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/subquery.scala?utf8=%E2%9C%93#L246
[2]
https://github.com/apache/spark/blob/branch-2.3/sql/core/src/main/scala/org/apache/spark/sql/execution/subquery.scala?utf8=%E2%9C%93#L46

Pozdrawiam,
Jacek Laskowski
----
https://about.me/JacekLaskowski
Mastering Spark SQL https://bit.ly/mastering-spark-sql
Spark Structured Streaming https://bit.ly/spark-structured-streaming
Mastering Kafka Streams https://bit.ly/mastering-kafka-streams
Follow me at https://twitter.com/jaceklaskowski

Reply via email to