[test](regression) drop unsupported use_path_style=true in test_s3_tvf

[0AyanamiRei]

What problem does this PR solve?

Issue Number: None

Related PR: None

Problem Summary:

regression-test/suites/load_p2/tvf/test_s3_tvf.groovy configured several S3 TVF attributes with both a virtual-host style URI and use_path_style=true:

uri = "s3://${bucket}.${endpoint}/..."
use_path_style = "true"

These two settings conflict. Aliyun OSS rejects path-style access for this bucket with HTTP 403 SecondLevelDomainForbidden and the message Please use virtual hosted style to access. The regression case could pass on the previous endpoint, but failed after the P2 environment switched to the Aliyun internal Beijing endpoint where OSS enforces virtual-host style access.

This PR fixes the regression case by removing the six active addProperty("use_path_style", "true") settings whose URI is already in virtual-host form, so the SDK sends requests in the addressing style required by OSS. The remaining S3 TVF attributes in this file do not set use_path_style and keep their previous behavior.

This PR also improves the failure path in the test. Previously, assertTrue(attribute.expectFiled) threw immediately and the later logger.info("error: ", ex) line was skipped, so the failure only showed a bare assertion line. The exception is now logged before the assertion, and the assertion message includes the loop index, table name, property map, and original error message.

Manual verification used the same OSS bucket, key prefix, and endpoint while only changing the addressing style:

Path-style request:
https://oss-cn-beijing.aliyuncs.com/doris-regression-bj/?prefix=regression/load/data/kd16=abcdefg/&max-keys=2
Result: HTTP 403 SecondLevelDomainForbidden

Virtual-host request:
https://doris-regression-bj.oss-cn-beijing.aliyuncs.com/?prefix=regression/load/data/kd16=abcdefg/&max-keys=2
Result: HTTP 200 OK

The same behavior was reproduced through Doris S3 TVF: the query fails with use_path_style=true and succeeds after the property is removed.

Release note

None

Check List (For Author)

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
    • Verified Aliyun OSS rejects the path-style URL with HTTP 403 SecondLevelDomainForbidden and accepts the virtual-host URL with HTTP 200 OK.
    • Verified Doris S3 TVF fails with use_path_style=true and succeeds after removing the property.
  • No need to test or manual test. Explain why:
    • This is a refactor/code format and no logic has been changed.
    • Previous test can cover this change.
    • No code files have been changed.
    • Other reason

• Behavior changed:

  • No.
  • Yes. The regression test now uses virtual-host style access for Aliyun OSS cases whose URI is already virtual-host style. Doris product behavior is unchanged.

• Does this need documentation?

  • No.
  • Yes.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label

[hello-stephen]

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:

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

[0AyanamiRei]

run buildall

[0AyanamiRei]

run buildall

[sollhui]

/review

[github-actions]

Automated review completed. I am requesting changes for one regression-test correctness issue: the touched catch block improves the message for unexpected exceptions, but still does not fail when an expected-error TVF insert unexpectedly succeeds.

Critical checkpoint conclusions: the PR scope is narrow and test-only; no product concurrency, lifecycle, transaction, persistence, or FE/BE protocol compatibility change is involved. The S3/OSS addressing change follows the existing OSS property path: Aliyun endpoints select OSSProperties and the bucket.endpoint URI form is normalized before listing/scanning. The remaining issue is test coverage semantics for negative cases, covered inline. No additional user focus was provided.

Subagent conclusions: optimizer-rewrite reported no candidates. tests-session-config proposed TSC-001, accepted as MAIN-001 and submitted inline. The suspected bucket-authority issue and assertion-overload issue were dismissed with code evidence in the ledger. Convergence round 1 ended with both live subagents replying NO_NEW_VALUABLE_FINDINGS for the same ledger/comment set.

[sollhui]

LGTM

skip

[github-actions]

PR approved by at least one committer and no changes requested.

[github-actions]

PR approved by anyone and no changes requested.