Github user ericl commented on the issue:
https://github.com/apache/spark/pull/14022
Instead of selectively enabling this for certain confs / config builders,
how about a global flag for enabling config expansion? I think that would be
less likely to be confusing. Also, perhaps a warning should be logged if there
is a config value that looks expandable but the flag is off.
---
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
