DanielLeens commented on issue #9835: URL: https://github.com/apache/seatunnel/issues/9835#issuecomment-4849338651
I checked the PostgreSQL table-discovery path more closely. This looks like a real connector issue, not a usage problem. The top-level `Unable to create a source for identifier 'Jdbc'` message is only the outer wrapper. The more specific path is that PostgreSQL custom ENUM columns are currently treated as unsupported during schema conversion, so source initialization fails before the table can be loaded normally. As a temporary workaround on released versions, you can use a `query` and cast the enum column to text explicitly, for example `status::text as status`, so the source side sees a regular string column. There is active follow-up for this now in PR #11232. So this issue is worth keeping open until that fix is merged into `dev`. Once that happens, it should be much easier to verify directly on the PostgreSQL source path without SQL casting. -- 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]
