Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
As most of the development works are on Kylin 4, we need to switch it as main branch. Apache Kylin community changes the branch settings on Github since 2021-08-04 :
Please check Intro to Kylin 4 architecture and INFRA-22166 if you are interested.
What types of changes does your code introduce to Kylin? Put an x
in the boxes that apply
Put an x
in the boxes that apply. You can also fill these out after creating the PR. If you‘re unsure about any of them, don’t hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
If this is a relatively large or complex change, kick off the discussion at user@kylin.apache.org or dev@kylin.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...