[BugFix] fix partial update failure due to column name case (backport #53656)

[mergify]

Why I'm doing:

Partial update fail in this case: #53655
This is because in UpdatePlaner.java:

for (Column column : targetTable.getFullSchema()) {
                if (updateStmt.usePartialUpdate() && !column.isGeneratedColumn() &&
                        !updateStmt.isAssignmentColumn(column.getName()) && !column.isKey()) {
                    // When using partial update, skip columns which aren't key column and not be assign, except for
                    // generated column
                    continue;
                }

!updateStmt.isAssignmentColumn(column.getName()) is case-sensitively, so if the update column name are not same as which it was defined when create table, it will generate wrong plan. E.g.

CREATE TABLE employees (
    EmployeeID INT,
    Name VARCHAR(50),
    Salary DECIMAL(10, 2)
)

If you update salary instead of Salary, it will fail with number of exprs is not same with slots backend.

What I'm doing:

Update planner treats column names case-sensitively, which can lead to incorrect execution plans.

This pull request introduces improvements to the handling of column updates in SQL statements and adds corresponding test cases. The most important changes include modifying how assignment columns are stored, adding a new test method for partial updates, and creating new test scripts for upper-case partial updates.

Enhancements to column updates:

• fe/fe-core/src/main/java/com/starrocks/sql/ast/UpdateStmt.java: Changed the assignmentColumns from a HashSet to a TreeSet with case-insensitive ordering to ensure consistent handling of column names.

New test cases for partial updates:

• fe/fe-core/src/test/java/com/starrocks/sql/plan/UpdatePlanTest.java: Added a new test method testColumnPartialUpdate to verify the behavior of partial updates in different scenarios.

New test scripts for upper-case partial updates:

• test/sql/test_partial_update_column_mode/R/test_upper_case_partial_update: Added a new test script to validate partial updates with upper-case column names. This script includes table creation, data insertion, and update operations.
• test/sql/test_partial_update_column_mode/T/test_upper_case_partial_update: Added another test script with the same purpose as the previous one, ensuring thorough testing of partial updates with upper-case column names.

Fixes #53655

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 3.4
  • 3.3
  • 3.2
  • 3.1
  • 3.0

    ---

    This is an automatic backport of pull request [BugFix] fix partial update failure due to column name case #53656 done by Mergify.

Why I'm doing:

Partial update fail in this case: #53655
This is because in UpdatePlaner.java:

for (Column column : targetTable.getFullSchema()) {
                if (updateStmt.usePartialUpdate() && !column.isGeneratedColumn() &&
                        !updateStmt.isAssignmentColumn(column.getName()) && !column.isKey()) {
                    // When using partial update, skip columns which aren't key column and not be assign, except for
                    // generated column
                    continue;
                }

!updateStmt.isAssignmentColumn(column.getName()) is case-sensitively, so if the update column name are not same as which it was defined when create table, it will generate wrong plan. E.g.

CREATE TABLE employees (
    EmployeeID INT,
    Name VARCHAR(50),
    Salary DECIMAL(10, 2)
)

If you update salary instead of Salary, it will fail with number of exprs is not same with slots backend.

What I'm doing:

Update planner treats column names case-sensitively, which can lead to incorrect execution plans.

This pull request introduces improvements to the handling of column updates in SQL statements and adds corresponding test cases. The most important changes include modifying how assignment columns are stored, adding a new test method for partial updates, and creating new test scripts for upper-case partial updates.

Enhancements to column updates:

• fe/fe-core/src/main/java/com/starrocks/sql/ast/UpdateStmt.java: Changed the assignmentColumns from a HashSet to a TreeSet with case-insensitive ordering to ensure consistent handling of column names.

New test cases for partial updates:

• fe/fe-core/src/test/java/com/starrocks/sql/plan/UpdatePlanTest.java: Added a new test method testColumnPartialUpdate to verify the behavior of partial updates in different scenarios.

New test scripts for upper-case partial updates:

• test/sql/test_partial_update_column_mode/R/test_upper_case_partial_update: Added a new test script to validate partial updates with upper-case column names. This script includes table creation, data insertion, and update operations.
• test/sql/test_partial_update_column_mode/T/test_upper_case_partial_update: Added another test script with the same purpose as the previous one, ensuring thorough testing of partial updates with upper-case column names.

Fixes #53655

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud