552091f21f
[performance](pipelineX) optimize pipelineX ( #25713 )
2023-10-25 10:13:17 +08:00
22684dedff
[pipelineX](pick) pick PRs from pipeline ( #25340 )
2023-10-12 14:35:32 +08:00
642e5cdb69
[Fix](Status) Make Status [[nodiscard]] and handle returned Status correctly ( #23395 )
2023-09-29 22:38:52 +08:00
b9997d69fa
[refactor](pipelineX) return error when local_state can not find id ( #24360 )
2023-09-21 16:04:08 +08:00
8ce109bda7
[pipelineX](profile) phase 2: refine profile ( #24467 )
2023-09-16 14:28:20 +08:00
d24f3efd4a
[pipelineX](profile) Phase 1: refactor pipelineX detailed profile ( #24322 )
2023-09-15 16:14:05 +08:00
65f41f71c1
[pipelineX](refactor) refine codes ( #23726 )
2023-09-01 07:57:35 +08:00
d22290e548
[pipelineX](join) support hash join ( #23689 )
2023-08-31 13:01:26 +08:00
5c37be16fe
[pipelineX](correctness) Fix close problem for local state ( #23479 )
2023-08-25 14:19:27 +08:00
55e572df82
[pipelineX](analytic operator) Support analytic operator ( #23444 )
2023-08-24 23:05:29 +08:00
e412dd12e8
[chore](build) Use include-what-you-use to optimize includes (PART II) ( #18761 )
...
Currently, there are some useless includes in the codebase. We can use a tool named include-what-you-use to optimize these includes. By using a strict include-what-you-use policy, we can get lots of benefits from it.
2023-04-19 23:11:48 +08:00
7fb695b51d
[Pipeline](select node) Support select node on pipeline engine ( #14928 )
2022-12-11 21:31:32 +08:00
ef46b580d0
[Vectorized](operator) support analytic eval operator ( #14774 )
2022-12-10 19:32:11 +08:00
