[
https://issues.apache.org/jira/browse/KYLIN-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694461#comment-17694461
]
ASF GitHub Bot commented on KYLIN-5447:
---------------------------------------
DorrisRuixuanZhang opened a new pull request, #2098:
URL: https://github.com/apache/kylin/pull/2098
## 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.
## 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)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [x] 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...
> Support creating logical views to improve the data reprocessing ability of
> data developers
> ------------------------------------------------------------------------------------------
>
> Key: KYLIN-5447
> URL: https://issues.apache.org/jira/browse/KYLIN-5447
> Project: Kylin
> Issue Type: Improvement
> Components: RDBMS Source
> Affects Versions: 5.0-alpha
> Reporter: Ruixuan Zhang
> Assignee: Ruixuan Zhang
> Priority: Major
> Fix For: 5.0-alpha
>
> Attachments: Dev Design - KYLIN supporting Logical View-1.pdf
>
>
> Add some preprocessing process such as filtering for dimension tables,
> dimension tables' aggregation to a certain extent to adapt to the granularity
> of the fact table (avoid many-to-many), deduplication of dimension tables,
> etc. Logical views are hoped to be capable of being created, maintained in
> metadata, referenced by models and queryable, as normal views.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
