[
https://issues.apache.org/jira/browse/KYLIN-5500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712270#comment-17712270
]
ASF GitHub Bot commented on KYLIN-5500:
---------------------------------------
LauraXia123 opened a new pull request, #2111:
URL: https://github.com/apache/kylin/pull/2111
## 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
- [ ] 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)
- [ ] 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._
- [ ] 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...
> Adding dimensions does not recognize Spaces
> -------------------------------------------
>
> Key: KYLIN-5500
> URL: https://issues.apache.org/jira/browse/KYLIN-5500
> Project: Kylin
> Issue Type: Bug
> Reporter: Laura Xia
> Assignee: Laura Xia
> Priority: Major
>
> 建两张相同的表，其中某一列末尾带空格，然后构建模型，将带空格的列添加到维度中，
> 保存模型时，报的错误信息：“KE-010010001(重复的维度名)：维度名称 “LO_ORDERKEY” 已存在。请重新命名。”
> 但接口展示的维度，其中的一个是带空格的，并没有重复，所以无法识别维度末尾带空格的情况
>
> 复现步骤：
> 1、建表：
> 表1：正常构建
> create TABLE FOX.LINEORDER_kg1 (
> {{LO_ORDERKEY}} BIGINT,
> {{LO_LINENUMBER}} BIGINT,
> {{LO_PARTKEY}} INT)
> 表2：维度LO_ORDERKEY末尾带空格（”LO_ORDERKEY “）
> create TABLE FOX.LINEORDER_kg2(
> {{`LO_ORDERKEY `}} BIGINT,
> {{LO_LINENUMBER}} BIGINT,
> {{LO_PARTKEY}} INT)
>
> 2、构建模型：表1 join 表2，添加维度：表1的“LO_ORDERKEY”、表2的”LO_ORDERKEY “
> 3、报错模型：报错误的信息
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
