[jira] [Updated] (KYLIN-1904) WebUI for GlobalDictionary
[ https://issues.apache.org/jira/browse/KYLIN-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1904: - Attachment: 0001-KYLIN-1904-WBE-DICTIONARY-UPDATE.patch > WebUI for GlobalDictionary > -- > > Key: KYLIN-1904 > URL: https://issues.apache.org/jira/browse/KYLIN-1904 > Project: Kylin > Issue Type: Improvement > Components: Metadata >Affects Versions: v1.5.3 >Reporter: Yerui Sun >Assignee: Zhong,Jason > Fix For: v1.5.4 > > Attachments: 0001-KYLIN-1904-WBE-DICTIONARY-UPDATE.patch, > 0001-KYLIN-1904-WEB-Global-Dictionary.patch > > > Global Dictionary is introduced since v1.5.3. However, there's no Web UI to > config with Global Dict, it's not convenience for users. > The use case can be found in > examples/test_case_data/localmeta/cube_desc/test_kylin_cube_without_slr_left_join_desc.json, > the "dictionaries" arrays. > One Global Dict config may contains three elements, "column", the column to > generate dict, "builder", the builder to build dict, and "reuse", the column > to be reused. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1702) The Key of the Snapshot to the related lookup table may be not informative
[ https://issues.apache.org/jira/browse/KYLIN-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15444393#comment-15444393 ] Zhong Yanghong commented on KYLIN-1702: --- Hi [~mahongbin], thanks for your suggestion. As you mentioned, it's better to use org.apache.kylin.metadata.model.TableDesc#getIdentity. For the MetadataCleanupJob, maybe there's no need to make any changes, since for old segments with old path of snapshot, they can still be extracted. > The Key of the Snapshot to the related lookup table may be not informative > -- > > Key: KYLIN-1702 > URL: https://issues.apache.org/jira/browse/KYLIN-1702 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > Attachments: change_layout_path_of_table_snapshot_with_tableName.patch > > > Currently the key for the snapshot stored in hbase metadata file is as > follows: > ResourceStore.SNAPSHOT_RESOURCE_ROOT + "/" + new > File(signature.getPath()).getName() + "/" + uuid + ".snapshot" > However, some hive tables stored in hive may organized like > dirName/tableName/00, dirName/tableName/01. > Based on current setting, the key will be > ResourceStore.SNAPSHOT_RESOURCE_ROOT + "/" + 00 + "/" + uuid + ".snapshot", > which is lack of the table name information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KYLIN-1702) The Key of the Snapshot to the related lookup table may be not informative
[ https://issues.apache.org/jira/browse/KYLIN-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15444352#comment-15444352 ] Zhong Yanghong edited comment on KYLIN-1702 at 8/29/16 12:24 AM: - Hi [~Shaofengshi], to make it compatible with old version, there are two ways: 1. upgrade the old path of snapshot to the new ones; 2. keep the old path, and let new snapshot go to the new path, and make the old path and new path compatible. For the first solution, it may be trivial and We have to prepare an upgrade tool. For the second one, it's simple, but some duplication between the old path and the new path will occur. We have employed the second one and tested in eBay. It works well until now. was (Author: yaho): Hi [~Shaofengshi], as [~mahongbin] mentioned, the table name contains the db information. To make it compatible with old version, there are two ways: 1. upgrade the old path of snapshot to the new ones; 2. keep the old path, and let new snapshot go to the new path, and make the old path and new path compatible. For the first solution, it may be trivial and We have to prepare an upgrade tool. For the second one, it's simple, but some duplication between the old path and the new path will occur. We have employed the second one and tested in eBay. It works well until now. > The Key of the Snapshot to the related lookup table may be not informative > -- > > Key: KYLIN-1702 > URL: https://issues.apache.org/jira/browse/KYLIN-1702 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > Attachments: change_layout_path_of_table_snapshot_with_tableName.patch > > > Currently the key for the snapshot stored in hbase metadata file is as > follows: > ResourceStore.SNAPSHOT_RESOURCE_ROOT + "/" + new > File(signature.getPath()).getName() + "/" + uuid + ".snapshot" > However, some hive tables stored in hive may organized like > dirName/tableName/00, dirName/tableName/01. > Based on current setting, the key will be > ResourceStore.SNAPSHOT_RESOURCE_ROOT + "/" + 00 + "/" + uuid + ".snapshot", > which is lack of the table name information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1319) Find a better way to check hadoop job status
[
https://issues.apache.org/jira/browse/KYLIN-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15443369#comment-15443369
]
hongbin ma commented on KYLIN-1319:
---
KYLIN-1319 makes KYLIN-1014 deprecated
> Find a better way to check hadoop job status
>
>
> Key: KYLIN-1319
> URL: https://issues.apache.org/jira/browse/KYLIN-1319
> Project: Kylin
> Issue Type: Improvement
> Components: Job Engine
>Reporter: liyang
>Assignee: Zhong Yanghong
> Labels: newbie
> Fix For: v1.5.3
>
> Attachments:
> Find_better_way_of_checking_hadoop_job_status_by_YarnClient_master.patch,
> Find_better_way_of_checking_hadoop_job_status_via_job_API_master.patch
>
>
> Currently Kylin retrieves jobs status via a resource manager web service like
> {code}https://:/ws/v1/cluster/apps/${job_id}?anonymous=true{code}
> It is not most robust. Some user does not have
> "yarn.resourcemanager.webapp.address" set in yarm-site.xml, then get status
> will fail out-of-box. They have to set a Kylin property
> "kylin.job.yarn.app.rest.check.status.url" to overcome, which is not user
> friendly.
> Kerberos authentication might cause problem too if security is enabled.
> Is there a more robust way to check job status? Via Job API?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KYLIN-1965) Check duplicated measure name
[ https://issues.apache.org/jira/browse/KYLIN-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hongbin ma resolved KYLIN-1965. --- Resolution: Fixed Fix Version/s: v1.5.4 > Check duplicated measure name > - > > Key: KYLIN-1965 > URL: https://issues.apache.org/jira/browse/KYLIN-1965 > Project: Kylin > Issue Type: Improvement > Components: Metadata >Affects Versions: v1.5.2, v1.5.3 >Reporter: kangkaisen >Assignee: kangkaisen > Fix For: v1.5.4 > > Attachments: KYLIN-1965.patch > > > The duplicated measure's name will lead to query failed, so we should check > duplicated measure name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1965) Check duplicated measure name
[ https://issues.apache.org/jira/browse/KYLIN-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15442890#comment-15442890 ] hongbin ma commented on KYLIN-1965: --- patch merged. thanks [~kangkaisen] > Check duplicated measure name > - > > Key: KYLIN-1965 > URL: https://issues.apache.org/jira/browse/KYLIN-1965 > Project: Kylin > Issue Type: Improvement > Components: Metadata >Affects Versions: v1.5.2, v1.5.3 >Reporter: kangkaisen >Assignee: kangkaisen > Fix For: v1.5.4 > > Attachments: KYLIN-1965.patch > > > The duplicated measure's name will lead to query failed, so we should check > duplicated measure name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
