Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15868
Conceptually, it does seem nicer to resolve this with a connection pool.
There is however some complexity in implementing our own connection pool.
I think you've pointed out a key issue: pools can only be per executor
anyway, so, not sure that helps. Scratch that.
Now, this would only ever coalesce to smaller number of partitions right?
that means it doesn't have to shuffle, right? especially if we make sure to set
`shuffle = false` explicitly. In that case maybe this really is the best
solution, especially if it's documented how it works.
---
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]
