Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14022
> Wouldn't enabling it by default break backwards compatibility?
Yes, maybe. But having a flag to disable everything would also potentially
break features that rely on it... although you could argue it's the user's
fault at that point.
I just don't like adding new options that only exist because we can't make
a decision about what their behavior should be. If variable substitution
applies to all configs, then it does apply to all configs and you can't disable
it. Since no configs that I know of have this functionality (the SQL variable
substitution would be broken), from a user's perspective it's very unlikely
doing it for all would break things.
---
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
