+1 It's enough to keep non-vectorization code just in 1.1-lts It's time to remove non-vectorization code now in master
On Tue, Dec 6, 2022 at 12:23 PM GuoLei Yi <yiguo...@gmail.com> wrote: > Hi All Developers, > > Vectorization is introduced into Doris in 1.0 which is released > earlier this year. Many companies is using 1.1.x and it is very very > Fast and Stable. I think it's time to remove non-vectorization code > now. Following is my considerations: > > - Lots of company is using doris 1.1.x and it is stable. > - 1.1-lts is a LTS branch, we will maintain it and fix bugs for it, If > you need non-vectorization code, I think 1.1 will solve your problem. > - 1.2 is now released, many features like array, JsonB, nest loop > join, decimalv3, datev2 and etc. are not implemented on > non-vectorization engine. So if a user is using 1.2 and using some new > features then it could not rollback to non-vectorization engine any > more. > - We need to refactor some code but we need to maintain these > non-vectorization code, it is very hard and it is very likely to > import BUGs and there are not many developers could add feature or fix > bugs for non-vectorization code. > > So that, I think it's time to remove non-vectorization code now to > move Fast and Stable!!! > > -- > Best Regards, > Yi Guo Lei > SelectDB > The Best Cloud Native Platform for Apache Doris > Tel:134-3991-0228 > Email:yiguo...@gmail.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@doris.apache.org > For additional commands, e-mail: dev-h...@doris.apache.org > >
