Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14235
I can understand the advantage of comparing SQL statement strings, but the
cost is higher than the benefit especially for a small group of key developers
who are maintaining the Spark code everyday.
In some commercial RDBMS, they have a whole team for developing and
maintaining SQL generation. However, I am not sure if the Spark community can
afford it. You know, SQL generation is only used for native view support so far.
---
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
