You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2021/11/22 15:18:44 UTC
[GitHub] [spark] tdg5 edited a comment on pull request #31622: [SPARK-34497][SQL] Fix built-in JDBC connection providers to restore JVM security context changes
tdg5 edited a comment on pull request #31622:
URL: https://github.com/apache/spark/pull/31622#issuecomment-974350953
Help!
It seems like no one considered the reality that some apps may rely on being able to establish many connections simultaneously for performance reasons. This change forces concurrency to 1 when establishing database connections and that strikes me as a **significant** user impacting change.
Can anyone propose a workaround for this? I have an app that makes connections to thousands of databases and I can't upgrade to any version >3.1.x because of this **significant** bottleneck.
https://issues.apache.org/jira/browse/SPARK-37391
ðŸ˜
EDIT: oops, I got confused the problem is actually introduced here: https://github.com/apache/spark/pull/29024/files#diff-345beef18081272d77d91eeca2d9b5534ff6e642245352f40f4e9c9b8922b085R58
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org