You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "fengYu (JIRA)" <ji...@apache.org> on 2016/11/01 09:17:59 UTC

[jira] [Issue Comment Deleted] (KYLIN-1826) kylin support more than one hive based on different hadoop claster

     [ https://issues.apache.org/jira/browse/KYLIN-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

fengYu updated KYLIN-1826:
--------------------------
    Comment: was deleted

(was: Thanks for review and reply.  

1、I will modify the job name and unify the name.
2、In early version, I do not pay attention to ID_STREAMING source, I will learn this and try to make it incompatible.
3、I have pass 'mvn test' in my cluster, I have to check the test code and rerun it.
4、"hive" in TableDesc is comes from ProjectInstance, it make something easy to store it in TableDesc, to keep inconsistency, we can take "hive" in ProjectInstance unchangeable, which it is meaningless. because we can just modify hive name in local filesystem rather than modify metadata.
5、currently, we still use cli for all hive source which is stable, We will consider and modify it to beeline if necessary.
)

> kylin support more than one hive based on different hadoop claster
> ------------------------------------------------------------------
>
>                 Key: KYLIN-1826
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1826
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Environment 
>    Affects Versions: v1.5.2
>            Reporter: fengYu
>            Assignee: fengYu
>         Attachments: 0001-KYLIN-1826-add-external-hive-interface-project-table.patch, 0002-KYLIN-1826-add-and-modify-cube-source-job-for-extern.patch
>
>
> Currently, kylin only support one hive which should run by 'hive' command, However, when source data located in more than one hive we should deploy more kylin instance and more than one metastore. which is difficult to manager and may cause some conflict.
> I has been working on it Recently, In our cluster, there are some hive client(different metastore) which based on different hadoop cluster, I add a new hive source type which called 'external hive' in kylin 1.5.x
> Thanks to kylin Plug-in architecture in 2.x, which make this work easiler. the main modification are:
> 1. add hive root directory in hive config file, external hive client exist in this directory. hive named by directory name.
> 2. add hive-site.xml file while loading hive tables.
> 3. store hive name into project, one project can only take one hive as source.
> 4. change and add some job to support job building.
> I will upload my patch if I finish all my tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)