[fix](connector) fix no suitable driver found issue when getting fe jdbc connection #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently, Spark Load is integrated into the Doris core, which brings the following problems: Due to the reliance on Spark-related dependencies, the security issues of Spark itself will cause security issues in Doris When modifying the content of Spark ETL, it also depends on the version release of Doris, which is not conducive to rapid expansion and problem repair The reliance on Hadoop ecosystem also increases the complexity of the Doris system Therefore, separating the task submission, management, and Spark DPP processing of Spark Load from the Doris core will help reduce the complexity of the Doris core and also help unify Doris's Spark ecosystem tools.
* fix unstable ut * fix unstable ut * fix doris catalog init config table check failed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Issue Number: close #xxx
Problem Summary:
Sometimes, even though the MySQL driver jar is included in the classpath, a "No suitable driver found" exception is thrown when calling the
DriverManager.getConnectionmethod.So it is still necessary to call the
Class.forNamemethod to load the driver before getting the connection.Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...