Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15868
Yeah, although we change the operator from `repartition` to `coalesce`, but
yeah still costly.
When users use JDBC source to connect RDBMS, the max number of concurrent
connections is always a concern. This is a common issue in the design of most
RDBMS applications. We definitely can ask users to do it manually. I do not
have a strong opinion on this.
However, if we decide to not add such a property, we still need to document
it. The current behavior is unclear to the external users. cc @rxin @cloud-fan
@yhuai
---
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]
