[FLINK-38244][hotfix] Fix the full snapshot phase, the field case is adjusted based on isTableIdCaseInsensitive

[sd4324530]

During the full snapshot phase, the field case is adjusted based on isTableIdCaseInsensitive.

[sd4324530]

@leonardBang @loserwang1024 Please take a look when you have time.

[ThorneANN]

looks good but no test

[sd4324530]

looks good but no test

@ThorneANN I've tested it in a real environment and I'm already using it. Because the test module has not been working properly in my local environment

[ThorneANN]

looks good but no test

@ThorneANN I've tested it in a real environment and I'm already using it. Because the test module has not been working properly in my local environment

test it class without your local env ,just write some test code and use maven and docker to run test applition

[sd4324530]

looks good but no test

@ThorneANN I've tested it in a real environment and I'm already using it. Because the test module has not been working properly in my local environment

test it class without your local env ,just write some test code and use maven and docker to run test applition

#4275
After this pr, I found that my local Docker environment is now ready for testing. I will add test cases as soon as possible.

[lvyanquan]

MySQL field name case sensitivity should be independent of table name case sensitivity and should not be affected by
the lower_case_table_names configuration parameter.

[sd4324530]

MySQL field name case sensitivity should be independent of table name case sensitivity and should not be affected by the lower_case_table_names configuration parameter.

@lvyanquan You're right. This issue was discussed in the DingTalk group before. The lower_case_table_names configuration option is used to control the case of table names, not fields. But the previous pr-4095 modified the incremental phase, causing inconsistencies between the full and incremental phases when fields are uppercase. After communication with @loserwang1024 , the conclusion was to first handle the full phase with the same rules, and then consider a unified solution later, such as converting all fields to lowercase. What do you think?

[loserwang1024]

the conclusion was to first handle the full phase with the same rules, and then consider a unified solution later, such as converting all fields to lowercase.

@lvyanquan , yes, we first make the behavior of #4095 same, and then can move forward in another pr.

[Copilot]

Pull request overview

Fixes MySQL pipeline connector snapshot/schema handling so that column (and PK) name casing is normalized consistently during full snapshot/schema emission when isTableIdCaseInsensitive is enabled.

Changes:

• Add an uppercase_products fixture table (uppercase column names) to the MySQL inventory test DDL.
• Expand IT coverage to run the existing alter-statement parsing test against both products and uppercase_products.
• Normalize emitted schema column/PK names to lower-case in MySqlPipelineRecordEmitter when table IDs are case-insensitive, and plumb the flag from MySqlDataSource.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
.../src/test/resources/ddl/inventory.sql	Adds uppercase_products table + data to exercise uppercase column-name scenarios.
.../MySqlTableIdCaseInsensitveITCase.java	Parameterizes the existing IT to validate schema-change parsing for both normal and uppercase-column tables.
.../MySqlPipelineITCase.java	Excludes uppercase_products from an exclusion test to keep expected outputs stable.
.../MySqlDataSourceFactoryTest.java	Updates expected discovered tables list to include uppercase_products.
.../MySqlPipelineRecordEmitter.java	Lowercases column names and primary key column names when isTableIdCaseInsensitive is true.
.../MySqlDataSource.java	Computes isTableIdCaseInsensitive once and passes it to both deserializer and record emitter.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Typo in inserted test data: "water resistent" is misspelled and should be "water resistant" (even if this is only test DDL, keeping strings correct avoids propagating typos across fixtures).

[Copilot]

The new case-normalization logic for column names/primary keys is gated by isTableIdCaseInsensitive, but there doesn't appear to be test coverage for the bounded snapshot (StartupOptions.snapshot()) path where schemas are fetched via SHOW CREATE TABLE/DESC. Consider adding an IT that runs with StartupOptions.snapshot() against a table with uppercase column names (and PK) to exercise this end-to-end.