Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/17220
@guoxiaolongzte , I think here though "tungsten-sort" is the same as "sort"
now, for the configuration back-compatibility we still need to keep it. If
somehow user still configured with "tungsten-sort", with your change the
application will be failed. I think that's what @rxin mentioned about.
Looking at some other configurations, we typically keep backward
compatibility unless major release (Spark 1.6 to Spark 2.0).
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
