myfjdthink opened a new issue, #19275: URL: https://github.com/apache/doris/issues/19275
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no similar issues. ### Version 1.2.1 and 1.2.4 both ### What's Wrong? I tried to import data to Doris using S3 LOAD, which failed when the file path“DATA INFILE” contained special characters like "tag_bucket=6" Load Command ```SQL LOAD LABEL address_tag_test_1683192596_3 ( DATA INFILE("s3://xxxpath/01.orc") INTO TABLE `dest_table` FORMAT AS "ORC" ) WITH S3 ( "AWS_ACCESS_KEY" = "xxx", "AWS_SECRET_KEY" = "xxx", "AWS_ENDPOINT" = "https://storage.googleapis.com";, "AWS_REGION" = "us-east4" ) PROPERTIES ( "send_batch_parallelism" = "1" ); ``` An example of a failed import Note: Iceberg will generates a table with a partition with *tag_bucket=6* in the file path ```SQL DATA INFILE("s3://warehouse/test.db/table_name/data/tag_bucket=6/01.orc") ``` Failure Information: > type:LOAD_RUN_FAIL; msg:errCode = 2, detailMessage = failed to init reader for file s3://warehouse/test.db/table_name/data/tag_bucket=6/01.orc, err: Error: [:No response body.] at 10.2.0.2 Example of successful import ```SQL DATA INFILE("s3://warehouse/test.db/table_name/data/01.orc") ``` ### What You Expected? Doris S3 Load can correctly recognize special s3 file paths ### How to Reproduce? Just use the practices mentioned above ### Anything Else? _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
