starrocks
starrocks copied to clipboard
[WIP][Enhancement] support file sink in pipeline engine
What type of PR is this:
- [ ] BugFix
- [x] Feature
- [x] Enhancement
- [ ] Refactor
- [ ] UT
- [ ] Doc
- [ ] Tool
Which issues of this PR fixes :
Fixes #
Problem Summary(Required) :
Checklist:
- [ ] I have added test cases for my bug fix or my new feature
- [ ] I have added user document for my new feature or new function
run starrocks_admit_test
run starrocks_admit_test
run starrocks_admit_test
run starrocks_fe_unittest
run starrocks_admit_test
run starrocks_admit_test
run starrocks_admit_test
run starrocks_admit_test
run starrocks_fe_unittest
run starrocks_admit_test
run starrocks_admit_test
run starrocks_admit_test
run starrocks_fe_unittest
run starrocks_admit_test
run starrocks_admit_test
- write some tests for the core functions?
- any performance comparsion to the non-pipeline way?
run starrocks_admit_test
- write some tests for the core functions?
- any performance comparsion to the non-pipeline way? @fzhedu
- daily test has some cases can cover it.
- whether it's in pipeline or non-pipeline engine, the main bottleneck is the sync io of serially writing files. I do a simple test in my env,
SELECT * FROM tpch.lineitem limit 1000000 INTO OUTFILE "hdfs://xx" PROPERTIES ("broker.username" = "broker1", "column_separator" = ",","line_delimiter" = "\n","max_file_size" = "5MB");and it takes about the same time in pipeline and non-pipeline engine.
run starrocks_admit_test
run starrocks_admit_test
run starrocks_admit_test
run starrocks_admit_test
[FE PR Coverage Check]
:heart_eyes: pass : 1 / 1 (100.00%)
file detail
| path | covered_line | new_line | coverage | not_covered_line_detail | |
|---|---|---|---|---|---|
| :large_blue_circle: | com/starrocks/planner/ResultSink.java | 1 | 1 | 100.00% | [] |







