Feature/tibero connector

[thehkkim]

Description

This PR adds a new JDBC connector for Tibero database. Tibero is an enterprise-grade relational database management system that is Oracle-compatible and widely used in enterprise environments.

The connector extends BaseJdbcClient and provides:

• Support for common SQL data types (numeric, character, timestamp, binary)
• Tibero-specific type mappings for DATE and TIMESTAMP types with precision up to 9
• Proper handling of B.C. dates (year adjustment)
• Type conversion handling for CLOB, NCLOB, BLOB, and RAW types

Additional context and related issues

The implementation follows the same pattern as other JDBC connectors in Trino (e.g., Oracle, PostgreSQL). The connector handles Tibero's type system including:

• Numeric types: SMALLINT, INTEGER, BIGINT, REAL, DOUBLE, DECIMAL/NUMERIC
• Character types: CHAR, VARCHAR, NVARCHAR, CLOB, NCLOB
• Binary types: VARBINARY (RAW), BLOB
• Temporal types: DATE, TIMESTAMP with nanosecond precision

Note: The connector uses a system-scoped JDBC driver dependency which needs to be configured with the actual Tibero JDBC driver location.

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

## JDBC
* Add support for Tibero database connector.

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: hmc7491871.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[chenjian2664]

Could you add the connector tests?

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[thehkkim]

@chenjian2664
Thank you for the detailed review and feedback. I've made the following updates:

• Enhanced documentation
• Added type mapping tests

Please review and let me know if any further adjustments are needed.

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[chenjian2664]

@thehkkim Have you signed cla yet - suggested by the cla-bot?

[thehkkim]

@chenjian2664
Yes, I have already signed the CLA and sent it to cla@trino.io on Jan 9.
I re-sent the signed CLA because the previous email had an incorrect subject. Thanks!

Additionally, this PR was originally labeled only as docs.
It seems that some additional labels were added after an intermediate commit.
Would it be possible to keep only the docs label?

[github-actions]

This pull request has gone a while without any activity. Ask for help on #core-dev on Trino slack.

[thehkkim]

Hi @martint,

I submitted my CLA to cla@trino.io on January 9th with the subject "Signed CLA for Trino - GitHub user thehkkim". My email address is thehkkim@gmail.com.

Could you help me verify the status of my CLA submission?

Thank you!

[github-actions]

This pull request has gone a while without any activity. Ask for help on #core-dev on Trino slack.

[thehkkim]

@martint
Thank you for your email!
I've resubmitted the CLA with a proper handwritten signature as you suggested.

• the subject : Signed CLA for Trino - GitHub user thehkkim
• My email address : thehkkim@gmail.com

Could you please verify the status of my CLA submission?

[chenjian2664]

@cla-bot check

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[thehkkim]

Hi @chenjian2664,

It seems that some extra labels were added unintentionally due to a previous incorrect merge. Only the cla-signed and docs labels should remain — could you help remove the other labels?

Also, is there anything else I need to do on my end? Please let me know if any further action is required.
Thank you! 🙏

[chenjian2664]

@thehkkim Could you add a connector test, you can refer TestOracleConnectorTest.
Once tests are added, my main question is, do you have a plan for how they'll be executed, and who will cover the ci testing costs(bill)?