[PR] [fix](regression) Seed OSS-HDFS Paimon data per run [doris]

["hello-stephen (via GitHub)" <gi...@apache.org>]

hello-stephen opened a new pull request, #69207:
URL: https://github.com/apache/doris/pull/69207

   ### What problem does this PR solve?
   
   Branch-4.1 External #330 fails `oss_hdfs_catalog_test` when the fixed OSS-HDFS Paimon filesystem warehouse has no `paimon_hms_on_oss_hdfs_db.external_test_table`. The suite reads a table that it never creates, so all six catalog-parameter read variants depend on shared data being present.
   
   Create a unique OSS-HDFS Paimon warehouse, database, and two-row table for each run using the same writable test bucket already used by this suite. Read that table through the existing old, explicit OSS-HDFS, and new property combinations with both scanner modes. Remove the table, database, and seed catalog afterward. This keeps the six parameter checks while removing the missing fixed-data prerequisite.
   
   ### Validation
   
   - `git diff --check` passed.
   - Exact head `d0524035710eb94e374b67c60d900ca4336e4a22` is awaiting a targeted TeamCity Compile and External run of `oss_hdfs_catalog_test`. Keep this PR as draft until the case finishes.
   
   ### Release note
   
   None. Regression case only.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org

Re: [PR] [fix](regression) Seed OSS-HDFS Paimon data per run [doris]

["hello-stephen (via GitHub)" <gi...@apache.org>]

hello-stephen commented on PR #69207:
URL: https://github.com/apache/doris/pull/69207#issuecomment-6217480310

   
   Thank you for your contribution to Apache Doris.
   Don't know what should be done next? See [How to process your PR](https://doris.apache.org/community/how-to-contribute/review-and-ci).
   
   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?
       


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org