8494496dc9
[fix](p2) fix assertion in test_broker_load_p2 ( #41116 ) ( #41117 )
...
cherry-pick #41116
2024-09-24 09:46:07 +08:00
e7d41eb143
[test](p2) print error message when assert fails ( #40699 ) ( #40977 )
...
cherry-pick #40699
2024-09-19 22:01:40 +08:00
fb17f204d7
[fix](http) fix http url with incorrect character notation ( #38420 ) ( #39535 )
...
## Proposed changes
pick from master #38420
2024-08-19 15:03:19 +08:00
8f39143c14
[test](fix) replace hardcode s3BucketName ( #37750 )
...
## Proposed changes
pick from master #37739
<!--Describe your changes.-->
---------
Co-authored-by: stephen <hello-stephen@qq.com >
2024-07-14 18:38:52 +08:00
d7cae940d2
[fix](test) fix case conflict between test_tvf_based_broker_load and test_broker_load #37622 ( #37631 )
...
cherry pick from #37622
2024-07-11 17:52:21 +08:00
0a95757a4d
[opt](test) Optimize execution time of test_s3_load case #37562 ( #37612 )
...
cherry pick from #37562
2024-07-10 19:09:46 +08:00
d1eb917076
[fix](rpc) fix transfer large data and enable transfer_large_data_by_brpc by default #35770 ( #36169 )
...
cherry pick from #35770
2024-06-12 19:39:07 +08:00
0e2b7480b7
[fix](regression-test) line_delimiter parse error in regression_test test_tvf_based_broker_load ( #35001 )
2024-05-24 16:23:58 +08:00
b11f2ad9f0
[fix](cases) fix broker_load & schema_change & table_property cases ( #35061 )
...
1. log more info to investigate problem.
2. use def in groovy to avoid gloabl namespace
2024-05-22 00:46:11 +08:00
3f2a794c2e
[refactor](insert) remove unused insert code in FE #29924
2024-01-18 09:00:32 +08:00
de03c152ce
[fix](thrift)cancel thrift msg max size limit ( #25194 )
...
On Thrift 0.14.0+, need use TConfiguration to raise the max message size.
see https://github.com/apache/arrow/pull/11123/files
2023-10-13 20:21:36 +08:00
c9dc715c5d
[fix](broker-load) fix error when using multi data description for same table in load stmt ( #22666 )
...
For load request, there are 2 tuples on scan node, input tuple and output tuple.
The input tuple is for reading file, and it will be converted to output tuple based on user specified column mappings.
And the broker load support different column mapping in different data description to same table(or partition).
So for each scanner, the output tuples are same but the input tuple can be different.
The previous implements save the input tuple in scan node level, causing different scanner using same input tuple,
which is incorrect.
This PR remove the input tuple from scan node and save them in each scanners.
2023-08-07 20:03:03 +08:00
e489b60ea3
[feature](load) support line delimiter for old broker load ( #22030 )
2023-07-21 19:31:19 +08:00
e18465eac7
[feature](TVF) support path partition keys for external file TVF ( #21648 )
2023-07-13 10:15:55 +08:00
46f0295b78
[feature](load-refactor-with-tvf) S3 load with S3 tvf and native insert ( #19937 )
2023-06-25 17:45:31 +08:00
c80c4477cf
[Enhancement](broker-load) broker load show stmt support display cluster name if specified ( #19392 )
2023-05-18 00:10:15 +08:00
894801f5ce
[feature](load-refactor) Step1: InsertStmt as facade layer and run S3/Broker Load ( #19142 )
2023-05-10 17:48:50 +08:00
425101bf53
[fix](test)Move broker test to p2. Move test data to cos in Beijing region ( #18893 )
...
Fix broker load p2 test case error.
1. Move test data from cos Hong kong region to Beijing region.
2. Move broker load test to p2 group.
3. Fix error message mismatch error.
2023-04-21 22:15:52 +08:00
