Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/11121#issuecomment-183737298
IMO, in the future, if we need to convert the optimized plans to SQL, we
need to add a few rules in SQLBuilder to revert back the changes of some
optimization rules. Otherwise, the Parser is unable to parse the generated SQL.
I already hit a couple of issues caused by Analyzer rules.
Also cc @liancheng
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
