[fix](regression) Enable Paimon GCS regression#63554
Open
xylaaaaa wants to merge 1 commit into
Open
Conversation
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds explicit GCS filesystem support configuration to the Paimon GCS external table regression suite to ensure catalogs are created with the required GCS settings.
Changes:
- Add
'fs.gcs.support' = 'true'to Paimon catalog creation properties (with and without region variants). - Remove trailing whitespace at EOF.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| CREATE CATALOG ${catalog_name} PROPERTIES ( | ||
| 'type' = 'paimon', | ||
| 'warehouse' = '${gcs_warehouse}', | ||
| 'fs.gcs.support' = 'true', |
| CREATE CATALOG ${catalog_name}_with_region PROPERTIES ( | ||
| 'type' = 'paimon', | ||
| 'warehouse' = '${gcs_warehouse}', | ||
| 'fs.gcs.support' = 'true', |
### What problem does this PR solve?
Issue Number: None
Related PR: None
Problem Summary: Re-enable test_paimon_gcs in the external regression pipeline, configure Paimon to use the GCS filesystem provider, and avoid generating invalid catalog properties such as gs.endpoint='null'. The external pipeline now supplies the standard GCS endpoint and region while credentials remain provided by CI secret configuration.
### Release note
None
### Check List (For Author)
- Test: Manual test
- Not run in this branch worktree. The same change was verified on master PR apache#63521 with real, non-dry-run regression executions: one without local GCS credentials failed with NoAuthWithAWSException after removing 'null' catalog properties, and one with dummy credentials failed with GCS 403 Forbidden, confirming the case reaches storage.googleapis.com.
- Behavior changed: No
- Does this need documentation: No
xylaaaaa
force-pushed
the
fix/paimon-gcs-regression-branch-4.1
branch
from
2232776 to
9c6e703
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Issue Number: None
Related PR: #63521
Problem Summary: Configure the Paimon GCS regression case to explicitly enable GCS filesystem support so Paimon can access the existing GCS warehouse through the S3-compatible path on branch-4.1.
Release note
None
Check List (For Author)