KYLIN-5027 Fix query for the cube dose not build basecuboid#1731
KYLIN-5027 Fix query for the cube dose not build basecuboid#1731hit-lacus merged 1 commit intoapache:mainfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1731 +/- ##
=======================================
Coverage ? 24.62%
Complexity ? 4449
=======================================
Files ? 1092
Lines ? 61899
Branches ? 8894
=======================================
Hits ? 15242
Misses ? 45049
Partials ? 1608 Continue to review full report at Codecov.
|
2244e8b to
ab0a99d
Compare
|
This pull request introduces 1 alert and fixes 1 when merging ab0a99d into 9797e4c - view on LGTM.com new alerts:
fixed alerts:
|
114c6d5 to
35179a4
Compare
|
This pull request introduces 1 alert and fixes 1 when merging 35179a4 into 9797e4c - view on LGTM.com new alerts:
fixed alerts:
|
35179a4 to
3c06333
Compare
|
This pull request fixes 1 alert when merging 3c06333 into 9797e4c - view on LGTM.com fixed alerts:
|
3c06333 to
55a436a
Compare
|
This pull request fixes 1 alert when merging 55a436a into 9797e4c - view on LGTM.com fixed alerts:
|
Proposed changes
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.
Github Branch
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.
Types of changes
What types of changes does your code introduce to Kylin?
Put an
xin the boxes that applyChecklist
Put an
xin 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.Further comments
If this is a relatively large or complex change, kick off the discussion at user@kylin or dev@kylin by explaining why you chose the solution you did and what alternatives you considered, etc...