database/doris
2
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

branch-2.1: [improvement](jdbc catalog) Optimize the acquisition of indentity type in SQLServer (#51659)

Browse Source 
pick #51285
This commit is contained in:
zy-kkk
2025-06-16 16:50:37 +08:00
committed by GitHub
parent eaa6556721
commit 3a1e95c6c2
5 changed files with 20 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
fe/fe-core/src/main/java/org/apache/doris/datasource/jdbc/client/JdbcSQLServerClient.java
View File

@ -32,7 +32,14 @@ public class JdbcSQLServerClient extends JdbcClient {
String originSqlserverType = fieldSchema.getDataTypeName().orElse("unknown");
// For sqlserver IDENTITY type, such as 'INT IDENTITY'
// originSqlserverType is "int identity", so we only get "int".
// For types with parameters like 'decimal(18,0) IDENTITY(1,1)', we need to extract the base type
String sqlserverType = originSqlserverType.split(" ")[0];
// Handle types with parentheses like decimal(18,0), varchar(50), etc.
if (sqlserverType.contains("(")) {
sqlserverType = sqlserverType.substring(0, sqlserverType.indexOf("("));
}
switch (sqlserverType) {
case "bit":
return Type.BOOLEAN;
@ -55,7 +62,7 @@ public class JdbcSQLServerClient extends JdbcClient {
case "numeric": {
int precision = fieldSchema.getColumnSize().orElse(0);
int scale = fieldSchema.getDecimalDigits().orElse(0);
return ScalarType.createDecimalV3Type(precision, scale);
return createDecimalOrStringType(precision, scale);
}
case "date":
return ScalarType.createDateV2Type();