DanielCarter-stack commented on issue #10635: URL: https://github.com/apache/seatunnel/issues/10635#issuecomment-4105068707
<!-- code-pr-reviewer --> Thanks for the report. This appears to be a real bug in the DM JDBC connector. **Root cause:** `DmdbTypeConverter` lacks support for `NVARCHAR2`. The converter defines `DM_NVARCHAR` but not `NVARCHAR2`, so encounters with this type fall through to the default case and throw `CONVERT_TO_SEATUNNEL_TYPE_ERROR_SIMPLE`. **Evidence:** - `DmdbTypeConverter.java:68-69` defines `DM_VARCHAR2` and `DM_NVARCHAR`, but no `NVARCHAR2` constant - `DmdbTypeConverter.java:200-210` switch handles `VARCHAR`/`VARCHAR2`/`NVARCHAR` but missing `NVARCHAR2` case - `DmdbTypeConverter.java:317-319` default throws `convertToSeaTunnelTypeError` for unknown types - Oracle and Kingbase converters already support `NVARCHAR2` (see `OracleTypeConverter.java:54,187-192`) Dameng supports `NVARCHAR2` as an Oracle-compatible type, so the converter should handle it similarly to Oracle's implementation (map to `BasicType.STRING_TYPE` with proper length calculation). Would you be interested in contributing a fix? The change would involve adding `NVARCHAR2` handling in `DmdbTypeConverter` similar to how Oracle's converter implements it. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
