You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Cheng Lian (JIRA)" <ji...@apache.org> on 2016/01/08 23:33:40 UTC
[jira] [Created] (SPARK-12725) SQL generation suffers from name
conficts introduced by some analysis rules
Cheng Lian created SPARK-12725:
----------------------------------
Summary: SQL generation suffers from name conficts introduced by some analysis rules
Key: SPARK-12725
URL: https://issues.apache.org/jira/browse/SPARK-12725
Project: Spark
Issue Type: Sub-task
Reporter: Cheng Lian
Some analysis rules generate auxiliary attribute references with the same name but different expression IDs. For example, {{ResolveAggregateFunctions}} introduces {{havingCondition}} and {{aggOrder}}, and {{DistinctAggregationRewriter}} introduces {{gid}}.
This is OK for normal query execution since these attribute references get expression IDs. However, it's troublesome when converting resolved query plans back to SQL query strings since expression IDs are erased.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org