[feature](maxcompute)support maxcompte catalog read project-schema-table. #57012
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-DS: Total hot run time: 190491 ms |
ClickBench: Total hot run time: 29.95 s |
Contributor
FE UT Coverage ReportIncrement line coverage |
Contributor
FE Regression Coverage ReportIncrement line coverage |
morningman
reviewed
Oct 20, 2025
| if (getClient().schemas().exists(dbName)) { | ||
| List<Partition> parts; | ||
| if (limit < 0) { | ||
| parts = getClient().tables().get(defaultProject, dbName, tbl).getPartitions(); |
Contributor
There was a problem hiding this comment.
There are 9 places to call different version of getClient().tables().get().
I suggest to extract to a method in MCUtils.java
Contributor
Author
There was a problem hiding this comment.
i add a McStructureHelper interface to simple the logical of getclient().xxx
| // a variable is introduced: | ||
| // - When the property is true, the new architecture is used. | ||
| // - When the property is false, the old architecture is used. | ||
| public static final String PROJECT_SCHEMA_TABLE = "mc.project.schema.table"; |
Contributor
There was a problem hiding this comment.
I suggest: mc.enable.namespace.schema
Contributor
Author
|
run buildall |
TPC-DS: Total hot run time: 190526 ms |
ClickBench: Total hot run time: 28.98 s |
Contributor
FE UT Coverage ReportIncrement line coverage |
Contributor
FE Regression Coverage ReportIncrement line coverage |
morningman
approved these changes
Oct 24, 2025
zy-kkk
approved these changes
Oct 24, 2025
CalvinKirs
approved these changes
Oct 24, 2025
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. |
github-actions bot
pushed a commit
that referenced
this pull request
Oct 24, 2025
…ble. (#57012) ### What problem does this PR solve? Problem Summary: In the previous MaxCompute architecture, and its mapping in Doris, the hierarchy was: `project / database -> table / table`. When creating a catalog, users needed to specify the property `mc.default.project`, which indicated the default project to access. In this structure, executing `SHOW DATABASES` would list other projects. After MaxCompute introduced the concept of schemas, the hierarchy changed to: `project / catalog -> schema / database -> table / table`. Here, the project is at a higher level, and `SHOW DATABASES` should now list all schemas under the current project. As a result, users need to create a separate catalog for each project, specifying a different `mc.default.project` property. doc: https://help.aliyun.com/zh/maxcompute/user-guide/schema-related-operations?spm=a2c4g.11186623.help-menu-search-27797.d_0#9d8326491bagj To maintain compatibility with the old version, a catalog property `mc.project.schema.table` is introduced: - When the property is true, the new architecture is used. - When the property is false, the old architecture is used.
github-actions bot
pushed a commit
that referenced
this pull request
Oct 24, 2025
…ble. (#57012) ### What problem does this PR solve? Problem Summary: In the previous MaxCompute architecture, and its mapping in Doris, the hierarchy was: `project / database -> table / table`. When creating a catalog, users needed to specify the property `mc.default.project`, which indicated the default project to access. In this structure, executing `SHOW DATABASES` would list other projects. After MaxCompute introduced the concept of schemas, the hierarchy changed to: `project / catalog -> schema / database -> table / table`. Here, the project is at a higher level, and `SHOW DATABASES` should now list all schemas under the current project. As a result, users need to create a separate catalog for each project, specifying a different `mc.default.project` property. doc: https://help.aliyun.com/zh/maxcompute/user-guide/schema-related-operations?spm=a2c4g.11186623.help-menu-search-27797.d_0#9d8326491bagj To maintain compatibility with the old version, a catalog property `mc.project.schema.table` is introduced: - When the property is true, the new architecture is used. - When the property is false, the old architecture is used.
Hastyshell
pushed a commit
to Hastyshell/doris
that referenced
this pull request
Nov 12, 2025
…alog read project-schema-table. apache#57012 (apache#5620) cherry-picks from apache#57012 Related to apache#5289 Co-authored-by: daidai <changyuwei@selectdb.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 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:
In the previous MaxCompute architecture, and its mapping in Doris, the hierarchy was:
project / database -> table / table. When creating a catalog, users needed to specify the propertymc.default.project, which indicated the default project to access. In this structure, executingSHOW DATABASESwould list other projects.After MaxCompute introduced the concept of schemas, the hierarchy changed to:
project / catalog -> schema / database -> table / table. Here, the project is at a higher level, andSHOW DATABASESshould now list all schemas under the current project. As a result, users need to create a separate catalog for each project, specifying a differentmc.default.projectproperty.doc: https://help.aliyun.com/zh/maxcompute/user-guide/schema-related-operations?spm=a2c4g.11186623.help-menu-search-27797.d_0#9d8326491bagj
To maintain compatibility with the old version, a catalog property
mc.project.schema.tableis introduced:- When the property is true, the new architecture is used.
- When the property is false, the old architecture is used.
Release note
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)