[
https://issues.apache.org/jira/browse/KYLIN-5633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756698#comment-17756698
]
ASF GitHub Bot commented on KYLIN-5633:
---------------------------------------
ygjia opened a new pull request, #2148:
URL: https://github.com/apache/kylin/pull/2148
## Proposed changes
issue list
https://issues.apache.org/jira/browse/KYLIN-5633
https://issues.apache.org/jira/browse/KYLIN-5687
https://issues.apache.org/jira/browse/KYLIN-5690
https://issues.apache.org/jira/browse/KYLIN-5691
https://issues.apache.org/jira/browse/KYLIN-5692
https://issues.apache.org/jira/browse/KYLIN-5693
https://issues.apache.org/jira/browse/KYLIN-5694
https://issues.apache.org/jira/browse/KYLIN-5695
https://issues.apache.org/jira/browse/KYLIN-5696
https://issues.apache.org/jira/browse/KYLIN-5697
https://issues.apache.org/jira/browse/KYLIN-5698
https://issues.apache.org/jira/browse/KYLIN-5699
https://issues.apache.org/jira/browse/KYLIN-5700
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.
## 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_
- [x] 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
- [x] Commit messages in my PR start with the related jira ID, like
"KYLIN-0000 Make Kylin project open-source"
- [x] Compiling and unit tests pass locally with my changes
- [x] I have added tests that prove my fix is effective or that my feature
works
- [x] I have added necessary documentation (if appropriate)
- [x] Any dependent changes have been merged
## Further comments
If this is a relatively large or complex change, kick off the discussion at
u...@kylin.apache.org or d...@kylin.apache.org by explaining why you chose the
solution you did and what alternatives you considered, etc...
> The query can answered with the existing data of the current model (accepting
> index or segment data is not uniform), and there should be no query failure
> or push-down
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: KYLIN-5633
> URL: https://issues.apache.org/jira/browse/KYLIN-5633
> Project: Kylin
> Issue Type: Improvement
> Components: Query Engine
> Affects Versions: 5.0-alpha
> Reporter: Zhiting Guo
> Assignee: Zhiting Guo
> Priority: Major
> Fix For: 5.0-beta
>
> Attachments: Segment heterogeneous query behavior (1).pdf
>
>
> Details are included in the attachment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
