You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by "DanielLeens (via GitHub)" <gi...@apache.org> on 2026/07/02 06:02:06 UTC
[I] Clarify JDBC database version and type edge cases in docs [seatunnel]
DanielLeens opened a new issue, #11278:
URL: https://github.com/apache/seatunnel/issues/11278
## Background
The JDBC and database connector docs already cover many common options, but several edge cases still lead to unclear answers for users:
- `fetch_size = 0` means using the JDBC driver default, but users ask what the actual default is for MySQL, PostgreSQL, Oracle, and other drivers.
- Users ask whether old database versions such as Oracle 10g are supported by JDBC source or CDC source.
- Users ask how database-specific types such as PostgreSQL `enum` map into sinks such as Iceberg.
- Users ask about options such as `column_type_mapping`, but this option does not appear in the current Apache SeaTunnel docs.
These should be documented clearly so users do not rely on guessed behavior.
## Goal
Add a JDBC/database edge-case FAQ that documents support boundaries, type mapping caveats, and non-existent or unsupported options.
## Suggested scope
Please update English and Chinese docs in the most suitable locations, such as:
- `docs/en/connectors/source/Jdbc.md`
- `docs/zh/connectors/source/Jdbc.md`
- `docs/en/connectors/sink/Jdbc.md`
- `docs/zh/connectors/sink/Jdbc.md`
- connector-specific pages such as Oracle, Oracle-CDC, PostgreSQL, PostgreSQL-CDC, and Iceberg if needed
- `docs/en/connectors/connector-faq.md`
- `docs/zh/connectors/connector-faq.md`
The update should explain:
1. What `fetch_size = 0` means and why driver defaults are not controlled by SeaTunnel.
2. Whether docs should list driver-specific fetch-size defaults or link users to driver documentation.
3. How to verify database version compatibility, especially for old versions such as Oracle 10g.
4. How PostgreSQL enum-like types are represented in SeaTunnel and what to check before writing to Iceberg.
5. Whether `column_type_mapping` is an Apache SeaTunnel option. If it is not, say so explicitly and point to supported alternatives.
## Acceptance criteria
- The docs give direct answers for the edge cases above.
- Unsupported or non-existent options are clearly marked instead of silently omitted.
- English and Chinese docs are consistent.
- The content is verified against current connector options and type mapping tables.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@seatunnel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Clarify JDBC database version and type edge cases in docs [seatunnel]
Posted by "DanielLeens (via GitHub)" <gi...@apache.org>.
DanielLeens commented on issue #11278:
URL: https://github.com/apache/seatunnel/issues/11278#issuecomment-4862677398
Closing this based on maintainer/user clarification: database version and type boundary documentation should not be tracked as an issue here.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Clarify JDBC database version and type edge cases in docs [seatunnel]
Posted by "DanielLeens (via GitHub)" <gi...@apache.org>.
DanielLeens closed issue #11278: Clarify JDBC database version and type edge cases in docs
URL: https://github.com/apache/seatunnel/issues/11278
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org