[ https://issues.apache.org/jira/browse/SPARK-36191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-36191. --------------------------------- Fix Version/s: 4.0.0 Resolution: Fixed Issue resolved by pull request 42705 [https://github.com/apache/spark/pull/42705] > Support ORDER BY and LIMIT to be on the correlation path > -------------------------------------------------------- > > Key: SPARK-36191 > URL: https://issues.apache.org/jira/browse/SPARK-36191 > Project: Spark > Issue Type: Sub-task > Components: SQL > Affects Versions: 3.2.0 > Reporter: Allison Wang > Assignee: Allison Wang > Priority: Major > Labels: pull-request-available > Fix For: 4.0.0 > > > A correlation path is defined as the sub-tree of all the operators that are > on the path from the operator hosting the correlated expressions up to the > operator producing the correlated values. > We want to support ORDER BY (Sort) and LIMT operators to be on the > correlation path to achieve better feature parity with Postgres. Here is an > example query in `postgreSQL/join.sql`: > {code:SQL} > select * from > text_tbl t1 > left join int8_tbl i8 > on i8.q2 = 123, > lateral (select i8.q1, t2.f1 from text_tbl t2 limit 1) as ss > where t1.f1 = ss.f1; > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org