You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

[Progress record]: Dlimeng has claimed
Proposed time: 2022/06/17
Discussion time: 2022/06/25
Acceptance time: 2022/06/17
Complete time:
[issues]: https://github.com/apache/incubator-linkis/issues/2443
[email]： 
[release]:
[Proposer]: Dlimeng

Motivation & Background

Extend the data sources supported by Linkis DataSource, extend dm, greenplum, kingbase, oracle, postgres, sqlserver

Basic concept

Expect to achieve goals

Dameng, greenplum, kingbase, oracle, postgres, sqlserver


Implementation plan

metadataManager Service implementation
Based on mysql module integration of Dameng, greenplum, kingbase, oracle, postgres, sqlserver, protocol and sql are separated, metadatamanager reflects multiple data sources, based on mysql module extension, integrated into one module.


Changes


Modification Detail
1
Modification of maven module

  • linkis-metadata-manager-server
  • linkis-metadata-manager-service-mysql
  • linkis-metadata-manager-common
2Modification of HTTP interface
3Modification of the client interface
4Modification of database table structure
5Modification of configuration item
6Modification Error code 
7Modifications for Third Party Dependencies
  • dm driver: Dm7JdbcDriver16-7.6.0.165.jar
  • greenplum driver:greenplum-jdbc-5.1.4
  • kingbase driver: kingbase8-8.2.0.jar
  • oracle driver:ojdbc6-11.2.0.3.jar
  • postgres driver:postgresql-42.3.1.jar
  • sqlserver driver:
  • msbase-1.0.jar
  • mssqlserver-1.0.jar
  • msutil-1.0.jar
  • db2 driver: db2jcc4.jar

Compatibility, Deprecation, and Migration Plan

  • What impact (if any) will there be on existing users?
  • If we are changing behavior, how will we phase out the older behavior?
  • If we require special migration tools, describe them here.
  • When will we remove the existing behavior?


  • No labels