Doesn't support SQLSERVER type 'UNIQUEIDENTIFIER' on column 'Id'

visiontk commented 2 months ago

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

Doesn't support SQLSERVER type 'UNIQUEIDENTIFIER' on column 'Id'

SeaTunnel Version

apache-seatunnel-2.3.7

SeaTunnel Config

env {
  execution.parallelism = 2
  job.mode = "BATCH"
}
source {
    Jdbc {
        driver = com.microsoft.sqlserver.jdbc.SQLServerDriver
        url = "jdbc:sqlserver://ip;databaseName="
        user = "sa"
        password = ""
        query = "select top 100 * from  table where CreationTime> '${maxtime}' order by CreationTime"
    }
}
sink {
  jdbc {
    url = "jdbc:mysql://ip/?"
    driver = "com.mysql.cj.jdbc.Driver"
    user = ""
    password = ""
    generate_sink_sql = true
    database = ""
    table = ""
  }
}

Running Command

null

Error Exception

08:51:05.155 [main] WARN org.apache.seatunnel.connectors.seatunnel.jdbc.source.JdbcSource - get row type info exception

    org.apache.seatunnel.connectors.seatunnel.jdbc.exception.JdbcConnectorException: ErrorCode:[COMMON-05], ErrorDescription:[Unsupported operation] - Doesn't support SQLSERVER type 'UNIQUEIDENTIFIER' on column 'Id'  yet.

        at org.apache.seatunnel.connectors.seatunnel.jdbc.internal.dialect.sqlserver.SqlserverTypeMapper.mapping(SqlserverTypeMapper.java:130)

        at org.apache.seatunnel.connectors.seatunnel.jdbc.source.JdbcSource.initTableField(JdbcSource.java:178)

        at

Zeta or Flink or Spark Version

No response

Java or Scala Version

No response

Screenshots

No response

Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

zhangshenghang commented 2 months ago

Please assign it to me

zhangshenghang commented 2 months ago

Error SqlserverTypeMapper.java:130, does not exist in the code. This issue has been resolved.

Please confirm whether your version is correct.

github-actions[bot] commented 1 month ago

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

apache / seatunnel