You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by "zhengxiang378928908-code (via GitHub)" <gi...@apache.org> on 2026/08/07 07:12:13 UTC

Re: [I] [Bug] [connector-jdbc] DM compatible data type NVARCHAR2 [seatunnel]

zhengxiang378928908-code commented on issue #10635:
URL: https://github.com/apache/seatunnel/issues/10635#issuecomment-5213749917

   I'd like to work on this one. I've looked into it and opened #11684.
   
   Root cause: `DmdbTypeConverter` has a case for `NVARCHAR` but not for `NVARCHAR2`, which Dameng also accepts as the Oracle-compatible synonym. So an `NVARCHAR2` column falls through to the `default` branch and throws `COMMON-17`; in a multi-table job the catalog aggregates those into the `COMMON-21` error reported here.
   
   The PR maps `NVARCHAR2` to `STRING` alongside the existing `NVARCHAR` case and keeps the declared type name in `sourceType`, so `NVARCHAR` behaviour is unchanged. I verified the added unit test reproduces the failure when the fix is reverted.
   
   Happy to adjust the approach if a maintainer would prefer something different.
   


-- 
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