You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2019/07/01 01:19:00 UTC
[jira] [Assigned] (KYLIN-4020) Fix_length rowkey encode without
sepecified length can be saved but cause CreateHTable step failed
[ https://issues.apache.org/jira/browse/KYLIN-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shaofeng SHI reassigned KYLIN-4020:
-----------------------------------
Assignee: Yuzhang QIU
Priority: Minor (was: Major)
Summary: Fix_length rowkey encode without sepecified length can be saved but cause CreateHTable step failed (was: fix_length rowkey encode without sepecified length can be saved but cause CreateHTable step failed)
> Fix_length rowkey encode without sepecified length can be saved but cause CreateHTable step failed
> --------------------------------------------------------------------------------------------------
>
> Key: KYLIN-4020
> URL: https://issues.apache.org/jira/browse/KYLIN-4020
> Project: Kylin
> Issue Type: Improvement
> Components: Metadata
> Affects Versions: v2.5.2
> Reporter: Yuzhang QIU
> Assignee: Yuzhang QIU
> Priority: Minor
> Fix For: v2.6.3
>
>
> Hi dear team:
> Just as title said.
> Maybe there should have more strict check for advanced settings, I think.
> How do you think about this?
> If there already have same JIRAļ¼please inform me and close this one.
> Best regards
> yuzhang
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)