OIiveirra commented on code in PR #69591:
URL: https://github.com/apache/doris/pull/69591#discussion_r4374770916


##########
regression-test/suites/datatype_p0/uuid/test_uuid_export.groovy:
##########
@@ -19,25 +19,12 @@
 // UUID annotations survive nested file export and direct reload into native 
UUID columns.
 suite("test_uuid_export", "p0,external") {
 
-    String localPath = context.config.otherConfigs.get("uuidLocalExportPath")
-    boolean localMode = localPath != null
     String token = UUID.randomUUID().toString()
-    String outputPath
-    String sinkProperties
-    String sourceProperties
-    if (localMode) {
-        outputPath = "file://${localPath}_${token}_"
-        sinkProperties = ""
-        def backends = sql "SHOW BACKENDS"
-        sourceProperties = "\"backend_id\"=\"${backends[0][0]}\""
-    } else {
-        outputPath = 
"s3://${context.config.otherConfigs.get('s3BucketName')}/uuid_file_export/${token}_"
-        sinkProperties = """
+    String outputPath = 
"s3://${context.config.otherConfigs.get('s3BucketName')}/uuid_file_export/${token}_"
+    String sinkProperties = """

Review Comment:
   Fixed in d197857e663ea16cac712e6b2081b2650d8d5c6b, with the same change in 
#69592 (0f6e0e07e8d84329151a2b07a93b670f317b249c). The existing shared 
sinkProperties now contains provider and the resolved Azure endpoint, so both 
WITH S3 export and S3 TVF readback receive identical routing parameters. 
Default Azure placeholders resolve to the account endpoint; explicit endpoints 
are preserved. One Groovy file changed per branch (+11/-1); fixture data, 
export completion/cancellation handling and ordered result assertions are 
unchanged. Both scripts compiled and eight intercepted-SQL scenarios checked 
export/readback parameter equality for default/explicit Azure and OSS. No Doris 
SQL execution or live storage validation was performed.



-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to