liukun4515 opened a new pull request, #2088: URL: https://github.com/apache/kylin/pull/2088
## Proposed changes Dev design doc: https://docs.google.com/document/d/1wUNd8U1u-w8T-qQUReplPhDFkETj3AtFr_Shex501ls/edit?usp=sharing - add config and checker to enable or disable the cube planner1 when build a new segment or refresh a segment. - add property of `@JsonProperty("layout_cost_based_pruned_list")` which is used to indicate whether the rulebaseindex has been recommended by the cost based algorithm. - insert a new stage of `COST_BASED_PLANNER` in `CUBING` job, and the new stage is used to create task to collect the statistics and run the cost based algorithm. - use the `biginteger` instead of `long` to represent the cuboio - migrate the algorithm from kylin3.1 to kylin5.0 without major changes, and just make some adaptive changes. For example, change the cubeio from `long` to `biginteger` - migrate the IT/UT for the recommended algorithm from kylin3.1 to kylin5.0 ## Branch to commit - [ ] Branch **kylin3** for v2.x to v3.x - [ ] Branch **kylin4** for v4.x - [x] Branch **kylin5** for v5.x ## Types of changes What types of changes does your code introduce to Kylin? _Put an `x` in the boxes that apply_ - [ ] Bugfix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Documentation Update (if none of the other choices apply) ## Checklist _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._ - [x] I have created an issue on [Kylin's jira](https://issues.apache.org/jira/browse/KYLIN), and have described the bug/feature there in detail - [ ] Commit messages in my PR start with the related jira ID, like "KYLIN-0000 Make Kylin project open-source" - [ ] Compiling and unit tests pass locally with my changes - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I have added necessary documentation (if appropriate) - [ ] Any dependent changes have been merged ## Further comments If this is a relatively large or complex change, kick off the discussion at [email protected] or [email protected] by explaining why you chose the solution you did and what alternatives you considered, etc... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
