DanielCarter-stack commented on issue #10410: URL: https://github.com/apache/seatunnel/issues/10410#issuecomment-3815785782
<!-- code-pr-reviewer --> Thanks for reporting this issue. This is a valid bug affecting table schema discovery. The problem is that `DatabaseMetaData#getColumns()` treats the `tableNamePattern` parameter as a SQL LIKE pattern, where underscores (`_`) are wildcards matching any single character. When a table name contains underscores (e.g., `user_info`), it can incorrectly match other tables (e.g., `userAinfo`, `user1info`). This issue affects multiple components: - JDBC Connectors: `JdbcColumnConverter.convert()` in connector-jdbc - CDC Connectors: `SqlServerConnection.getTableSchemaFromTable()` in connector-cdc-sqlserver To help us reproduce and fix this, please provide: 1. Example table names that trigger the issue 2. Database type and version (MySQL/PostgreSQL/SQL Server?) 3. Full SeaTunnel job configuration 4. Error logs or observed incorrect behavior (wrong column mappings? task failure?) 5. Do you have tables with names differing only at the underscore position (e.g., `user_info` and `userAinfo`) in the same database? As a temporary workaround, you could rename tables to avoid underscores or ensure no conflicting table names exist in your database. -- 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]
