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

ASF GitHub Bot commented on KYLIN-4384:
---------------------------------------

hit-lacus commented on pull request #1118: KYLIN-4384 Disable create table via 
spark by default
URL: https://github.com/apache/kylin/pull/1118
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Spark build failed in EMR when KYLIN-4224 introduced
> ----------------------------------------------------
>
>                 Key: KYLIN-4384
>                 URL: https://issues.apache.org/jira/browse/KYLIN-4384
>             Project: Kylin
>          Issue Type: Bug
>          Components: Spark Engine
>         Environment: AWS EMR 5.28 with Glue support
>            Reporter: Xiaoxiang Yu
>            Priority: Major
>              Labels: aws-emr, aws-glue
>             Fix For: v3.1.0
>
>         Attachments: image-2020-02-21-20-17-36-060.png, 
> image-2020-02-21-20-18-12-440.png
>
>
> I built a package using the latest code of master branch to test the Kylin 
> Glue integration. 
>  
> I create a EMR cluster(5.28) with glue enabled. In my test, MR build engine 
> works fine.  But spark build engine failed at the first step, and I found the 
> code change is introduced in https://issues.apache.org/jira/browse/KYLIN-4224.
>  
> The *new added step* change the way that how {color:#de350b}*intermediate 
> table*{color} was created. And it is mandatory, so nobody can disable or 
> change it without rebuild the binary. It is not good in my side. Currently, I 
> can not find the root cause and I am not good at spark indeed. But I suggest 
> we should add a config to make it easy to disable that feature.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to