[
https://issues.apache.org/jira/browse/SPARK-13720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenchen Fan updated SPARK-13720:
--------------------------------
Description:
parse this SQL "SELECT COUNT(value) FROM parquet_t1 GROUP BY key HAVING
MAX(key) > 0 SORT BY key" to logical plan and generate SQL string again, the
generated SQL string can't be parsed.
This is because, we will add extra `SubqueryAlias` while converting logical
plan to SQL string(the `RecoverScopingInfo` rule in SQLBuilder). However, we
only update qualifiers in the `Project` operator that just above the added
`SubqueryAlias`, logically we also need to update qualifiers in all ancestor
plans. For example, if there is a Project under a Sort, if we add
`SubqueryAlias` under Project, we need update qualifiers for Sort too.
was:parse this SQL "SELECT COUNT(value) FROM parquet_t1 GROUP BY key HAVING
MAX(key) > 0 SORT BY key" to logical plan and generate SQL string again, the
generated SQL string can't be parsed.
> SQLBuilder.toSQL is broken when there is a sort by after having
> ---------------------------------------------------------------
>
> Key: SPARK-13720
> URL: https://issues.apache.org/jira/browse/SPARK-13720
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Reporter: Wenchen Fan
>
> parse this SQL "SELECT COUNT(value) FROM parquet_t1 GROUP BY key HAVING
> MAX(key) > 0 SORT BY key" to logical plan and generate SQL string again, the
> generated SQL string can't be parsed.
> This is because, we will add extra `SubqueryAlias` while converting logical
> plan to SQL string(the `RecoverScopingInfo` rule in SQLBuilder). However, we
> only update qualifiers in the `Project` operator that just above the added
> `SubqueryAlias`, logically we also need to update qualifiers in all ancestor
> plans. For example, if there is a Project under a Sort, if we add
> `SubqueryAlias` under Project, we need update qualifiers for Sort too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
