Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15868
I see, because a user can specify this option through SQL only? Ok, then
that logic makes sense to me.
It's still kinda a coarse way to achieve a limit on concurrent connections.
Some drivers let you configuring pooling in the driver string. That would cap
connections globally, which is even better. Is that not an option? if it's
readily available that's a much more direct solution.
At least, we ought to document that this is a potentially expensive
operation; it doesn't actually just limit connections.
---
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]
