[ 
https://issues.apache.org/jira/browse/KYLIN-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16423412#comment-16423412
 ] 

ASF subversion and git services commented on KYLIN-3277:
--------------------------------------------------------

Commit 25b4b3bc06b30a4030f4949d97a05566bcbddca4 in kylin's branch 
refs/heads/sync from [~yuchuqian]
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=25b4b3b ]

KYLIN-3277 Kylin should override hiveconf settings when connecting to hive 
using jdbc

Signed-off-by: nichunen <[email protected]>


> Kylin should override hiveconf settings when connecting to hive using jdbc
> --------------------------------------------------------------------------
>
>                 Key: KYLIN-3277
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3277
>             Project: Kylin
>          Issue Type: Bug
>            Reporter: Chuqian Yu
>            Assignee: Chuqian Yu
>            Priority: Major
>              Labels: patch
>             Fix For: v2.4.0
>
>         Attachments: 0001-KYLIN-3277.patch
>
>
> Hi, kylin developers. My cube building procedure failing at Step 2 
> "Redistribute Flat Hive Table" because Kylin always trying to submit a mr job 
> to the default yarn queue.
>  
> I have overrided the mapred.job.queue.name property in both 
> kylin_hive_conf.xml and kylin.properties but it doesn't work. 
>  
> kylin.properties
> ```
> kylin.source.hive.beeline-params=-n hive -p hive --hiveconf 
> mapred.job.queue.name=myQueue  -u 
> "jdbc:hive2://myZk:2181/;serviceDiscoveryMode=zooKeeper;" 
> ```
>  
> kylin_hive_conf.xml
> ```
>    <property>
>        <name>mapred.job.queue.name</name>
>        <value>myQueue</value>
>    </property>
> ```
>  
> After digging into the source code ,I found that kylin try to get the row 
> count of hive table before redistributing it. But it dose not override the 
> hive configuration when using jdbc to connect to hive server.
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to