kylin
kylin copied to clipboard
KYLIN-5371 fix segment prune
Proposed changes
创建model时在partition部分指定了天分区和时分区,格式分别为:yyyy-MM-dd、HH,在根据天分区值查询时结果非预期。原因是这种场景下segment裁剪有bug。
--不加天分区过滤得到的结果(18号3条数据,19号5条数据)
--加天分区在修复前查询结果
--18号实际有3条数据
--19号实际有5条数据
--18号19号共有8条数据
--加天分区在修复后查询结果
Branch to commit
- [ ] Branch kylin3 for v2.x to v3.x
- [x] Branch kylin4 for v4.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)
- [ ] 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, 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"
- [ ] 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
- [ ] 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...