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 2018/11/06 02:22:07 UTC
[jira] [Closed] (KYLIN-3649) segment region count and size are not
correct when using mysql as Kylin metadata storage
[ https://issues.apache.org/jira/browse/KYLIN-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shaofeng SHI closed KYLIN-3649.
-------------------------------
“Resolved in release 2.5.1 (2018-11-06)"
> segment region count and size are not correct when using mysql as Kylin metadata storage
> -----------------------------------------------------------------------------------------
>
> Key: KYLIN-3649
> URL: https://issues.apache.org/jira/browse/KYLIN-3649
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
> Affects Versions: v2.5.0
> Reporter: Lingang Deng
> Assignee: Lingang Deng
> Priority: Major
> Fix For: v2.5.1
>
> Attachments: 0001-KYLIN-3649.patch
>
>
> As titles, segment region count and size are not correct.
> {code:java}
> if ("hbase".equals(getConfig().getMetadataUrl().getScheme())) {
> try {
> logger.debug("Loading HTable info " + cubeName + ", " + tableName);
> // use reflection to isolate NoClassDef errors when HBase is not available
> hr = (HBaseResponse) Class.forName("org.apache.kylin.rest.service.HBaseInfoUtil")//
> .getMethod("getHBaseInfo", new Class[] { String.class, KylinConfig.class })//
> .invoke(null, tableName, this.getConfig());
> } catch (Throwable e) {
> throw new IOException(e);
> }
> }
> {code}
> Judgement is not valid when using mysql as Kylin metadata storage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)