[fix](maxcompute)fix maxcompute partition column schema order #48325
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 31923 ms |
TPC-DS: Total hot run time: 190892 ms |
ClickBench: Total hot run time: 30.69 s |
hubgeter
force-pushed
the
fix_mc_part_col
branch
from
a0d8fd4 to
edd1a19
Compare
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 32243 ms |
TPC-DS: Total hot run time: 189908 ms |
ClickBench: Total hot run time: 31.45 s |
github-actions
bot
added
the
approved
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
zy-kkk
approved these changes
Feb 26, 2025
CalvinKirs
approved these changes
Feb 26, 2025
github-actions bot
pushed a commit
that referenced
this pull request
Feb 26, 2025
### 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 | | +------------+------+------+------+---------+-------+ ```
github-actions bot
pushed a commit
that referenced
this pull request
Feb 26, 2025
### 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 | | +------------+------+------+------+---------+-------+ ```
zhiqiang-hhhh
pushed a commit
to zhiqiang-hhhh/doris
that referenced
this pull request
Feb 27, 2025
…#48325) ### 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 | | +------------+------+------+------+---------+-------+ ```
seawinde
pushed a commit
to seawinde/doris
that referenced
this pull request
Feb 28, 2025
…#48325) ### 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 | | +------------+------+------+------+---------+-------+ ```
mymeiyi
pushed a commit
to mymeiyi/doris
that referenced
this pull request
Mar 4, 2025
…#48325) ### 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 | | +------------+------+------+------+---------+-------+ ```
hubgeter
added a commit
to hubgeter/doris
that referenced
this pull request
Mar 12, 2025
…#48325) ### 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 | | +------------+------+------+------+---------+-------+ ```
hubgeter
added a commit
to hubgeter/doris
that referenced
this pull request
Mar 19, 2025
…#48325) ### 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 | | +------------+------+------+------+---------+-------+ ```
Closed
hubgeter
added a commit
to hubgeter/doris
that referenced
this pull request
Mar 27, 2025
…#48325) ### 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 | | +------------+------+------+------+---------+-------+ ```
csun5285
pushed a commit
to csun5285/doris
that referenced
this pull request
Mar 28, 2025
…n prune && timstamp type(apache#44508, apache#48768, apache#48325) (apache#3805) pick apache#44508 apache#48768 apache#48325 --------- Co-authored-by: zhangdong <zhangdong@selectdb.com>
hubgeter
added a commit
to hubgeter/doris
that referenced
this pull request
Mar 28, 2025
…#48325) ### 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 | | +------------+------+------+------+---------+-------+ ```
koarz
pushed a commit
to koarz/doris
that referenced
this pull request
Jun 4, 2025
…#48325) ### 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 | | +------------+------+------+------+---------+-------+ ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)