Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10205#issuecomment-206033335
I realize I'm super late to this party, but I just spent a bunch of time
trying to understand this new system while rebasing a PR. Overall, I think all
of the different classes make this pretty complicated.
> Because with the default arguments, you have to copy & paste the argument
list for every type-specific builder (look at the current SQLConf). Also, you
can't overload methods with default arguments, in case for some reason you want
to.
The refactored SQLConf looks pretty close to what it was before. Just now
we are copying builder methods instead of named arguments. In what case do we
need overloading?
---
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]
