[improvement](sqlserver catalog) Configurable whether to use encrypt when connecting to SQL Server using the catalog #36659
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
…ion when connecting to SQL Server using the catalog
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
|
run buildall |
TPC-H: Total hot run time: 39487 ms |
TPC-DS: Total hot run time: 174138 ms |
ClickBench: Total hot run time: 31.52 s |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
|
run external |
|
run buildall |
TPC-H: Total hot run time: 39409 ms |
TPC-DS: Total hot run time: 174004 ms |
ClickBench: Total hot run time: 31.05 s |
zy-kkk
added a commit
to zy-kkk/doris
that referenced
this pull request
Jun 28, 2024
…when connecting to SQL Server using the catalog (apache#36659) In previous versions, we used druid as the default JDBC connection pool, which can use custom decryption to parse the certificate when SQL Server encryption is turned on. However, in the new version, after changing HikariCP as the default connection pool, the SQLServer certificate cannot be parsed, so encryption needs to be turned off for normal use. Therefore, a parameter is added to decide whether to disable SQLServer encryption. It is not disabled by default.
dataroaring
pushed a commit
that referenced
this pull request
Jun 28, 2024
…when connecting to SQL Server using the catalog (#36659) In previous versions, we used druid as the default JDBC connection pool, which can use custom decryption to parse the certificate when SQL Server encryption is turned on. However, in the new version, after changing HikariCP as the default connection pool, the SQLServer certificate cannot be parsed, so encryption needs to be turned off for normal use. Therefore, a parameter is added to decide whether to disable SQLServer encryption. It is not disabled by default.
zy-kkk
added a commit
that referenced
this pull request
Jul 1, 2024
…_encrypt` to `force_sqlserver_jdbc_encrypt_false` (#37015) Front #36659 Renamed the configuration parameter `disable_jdbc_sqlserver_encrypt` to `force_sqlserver_jdbc_encrypt_false` to make its purpose clearer and more explicit. This new name better indicates that the parameter forces the JDBC URL to set `encrypt=false` when enabled.
zy-kkk
added a commit
that referenced
this pull request
Jul 2, 2024
…use encrypt when connecting to SQL Server using the catalog (#36971) pick (#36659) pick #37015 In previous versions, we used druid as the default JDBC connection pool, which can use custom decryption to parse the certificate when SQL Server encryption is turned on. However, in the new version, after changing HikariCP as the default connection pool, the SQLServer certificate cannot be parsed, so encryption needs to be turned off for normal use. Therefore, a parameter is added to decide whether to disable SQLServer encryption. It is not disabled by default.
dataroaring
pushed a commit
that referenced
this pull request
Jul 2, 2024
…_encrypt` to `force_sqlserver_jdbc_encrypt_false` (#37015) Front #36659 Renamed the configuration parameter `disable_jdbc_sqlserver_encrypt` to `force_sqlserver_jdbc_encrypt_false` to make its purpose clearer and more explicit. This new name better indicates that the parameter forces the JDBC URL to set `encrypt=false` when enabled.
mongo360
pushed a commit
to mongo360/doris
that referenced
this pull request
Aug 16, 2024
… use encryption when connecting to SQL Server using the catalog (apache#36940) pick apache#36659 pick apache#37015
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.
In previous versions, we used druid as the default JDBC connection pool, which can use custom decryption to parse the certificate when SQL Server encryption is turned on. However, in the new version, after changing HikariCP as the default connection pool, the SQLServer certificate cannot be parsed, so encryption needs to be turned off for normal use. Therefore, a parameter is added to decide whether to disable SQLServer encryption. It is not disabled by default.