branch-2.1: [fix](maxcompute)fix maxcompute partition column schema order #48325#48373

Merged

morningman merged 1 commit intobranch-2.1from

auto-pick-48325-branch-2.1

Feb 26, 2025

Contributor

github-actions bot commented Feb 26, 2025

Cherry-picked from #48325


          [fix](maxcompute)fix maxcompute partition column schema order (#48325)

19e19d9

### What problem does this PR solve?
Problem Summary:
```sql
create table in  MaxCompute :
CREATE TABLE `mc_parts` (`id` STRING COMMENT 'Id')
PARTITIONED BY (
	`ds` STRING ,
	`audit_flag` STRING );

query in doris :
before:
mysql> desc mc_parts;
+------------+------+------+------+---------+-------+
| Field      | Type | Null | Key  | Default | Extra |
+------------+------+------+------+---------+-------+
| id         | text | Yes  | true | NULL    |       |
| audit_flag | text | Yes  | true | NULL    |       |
| ds         | text | Yes  | true | NULL    |       |
+------------+------+------+------+---------+-------+

mysql> select * from mc_parts;
ERROR 1105 (HY000): errCode = 2, detailMessage = java.io.IOException: ODPS-0420061: Invalid parameter in HTTP request - The requested columns should be in order with table schema

The reason is because this ds column needs to be before audit_flag, and this order is also required when doing partition pruning ( eg: ds=2024-01-01/audit_flag=Y  ).

after:
mysql> desc mc_parts;
+------------+------+------+------+---------+-------+
| Field      | Type | Null | Key  | Default | Extra |
+------------+------+------+------+---------+-------+
| id         | text | Yes  | true | NULL    |       |
| ds         | text | Yes  | true | NULL    |       |
| audit_flag | text | Yes  | true | NULL    |       |
+------------+------+------+------+---------+-------+
```

Contributor

Thearas commented Feb 26, 2025

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

What problem was fixed (it's best to include specific error reporting information). How it was fixed.
Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
What features were added. Why was this function added?
Which code was refactored and why was this part of the code refactored?
Which functions were optimized and what is the difference before and after the optimization?

dataroaring closed this

dataroaring reopened this

Contributor

Thearas commented Feb 26, 2025

run buildall

morningman merged commit d6a5cbb into branch-2.1

18 of 19 checks passed

github-actions bot deleted the auto-pick-48325-branch-2.1 branch

February 26, 2025 12:34

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet