[fix](regression) Enable Paimon GCS regression#63521
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.
Updates the Paimon GCS regression test to use the correct GCS warehouse scheme and enables the suite to run in the external regression pipeline.
Changes:
- Switch warehouse URI from
s3://togs://in the Paimon GCS test suite. - Add
fs.gcs.support = trueto the relevantCREATE CATALOGdefinitions. - Remove
test_paimon_gcsfrom the external regressionexcludeSuiteslist.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| regression-test/suites/external_table_p0/paimon/test_paimon_gcs.groovy | Uses gs:// warehouse and enables GCS filesystem support in catalog properties. |
| regression-test/pipeline/external/conf/regression-conf.groovy | Allows test_paimon_gcs to run by removing it from exclusions. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Contributor
Author
|
run buildall |
xylaaaaa
force-pushed
the
fix/paimon-gcs-regression
branch
from
bb6a10e to
afb861c
Compare
Contributor
Author
|
run buildall |
This was referenced May 23, 2026
### 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: Regression test / Manual test
- Regression test: ./run-regression-test.sh --run --conf regression-test/conf/regression-conf.groovy -d external_table_p0/paimon -s test_paimon_gcs -c "jdbc:mysql://127.0.0.1:9030/?useLocalSessionState=true&allowLoadLocalInfile=true&zeroDateTimeBehavior=round" -conf enablePaimonTest=true. This is a real run, not dry-run; it failed at show databases with NoAuthWithAWSException because local GCSAk/GCSSk are not available, and verified the generated catalog no longer contains 'null' endpoint/credential values.
- Regression test: ./run-regression-test.sh --run --conf regression-test/pipeline/external/conf/regression-conf.groovy -d external_table_p0/paimon -s test_paimon_gcs -c "jdbc:mysql://127.0.0.1:9030/?useLocalSessionState=true&allowLoadLocalInfile=true&zeroDateTimeBehavior=round" -ha 127.0.0.1:8030 -conf GCSAk=dummy -conf GCSSk=dummy. This is a real run, not dry-run; it failed with GCS 403 Forbidden, confirming the case reaches storage.googleapis.com with credentials.
- Behavior changed: No
- Does this need documentation: No
xylaaaaa
force-pushed
the
fix/paimon-gcs-regression
branch
from
afb861c to
0539251
Compare
xylaaaaa
added a commit
to xylaaaaa/doris
that referenced
this pull request
May 23, 2026
### 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
added a commit
to xylaaaaa/doris
that referenced
this pull request
May 23, 2026
### 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
added a commit
to xylaaaaa/doris
that referenced
this pull request
May 23, 2026
### 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
Contributor
Author
|
run buildall |
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: None
Problem Summary: Re-enable
test_paimon_gcsin the external regression pipeline and explicitly mark the Paimon catalog storage as GCS so Doris does not infer it as another S3-compatible provider. The case continues to use the existing S3-compatible warehouse path for GCS because the FE pipeline classpath does not provide nativegs://Paimon FileIO support.Release note
None
Check List (For Author)
./run-regression-test.sh --run --conf regression-test/pipeline/external/conf/regression-conf.groovy -d external_table_p0/paimon -s test_paimon_gcs -dryRun./run-fe-ut.sh --run org.apache.doris.datasource.property.storage.GCSPropertiesTest