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 2017/08/22 12:57:00 UTC
[jira] [Commented] (KYLIN-2766) Kylin uses default FS to put the
coprocessor jar, instead of the working dir
[ https://issues.apache.org/jira/browse/KYLIN-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136750#comment-16136750 ]
Shaofeng SHI commented on KYLIN-2766:
-------------------------------------
Initial fix passed integration test, pushed to master, commit id: 4316cfdbe21cbab5764c2bcb6a45010bef434bf3
> Kylin uses default FS to put the coprocessor jar, instead of the working dir
> ----------------------------------------------------------------------------
>
> Key: KYLIN-2766
> URL: https://issues.apache.org/jira/browse/KYLIN-2766
> Project: Kylin
> Issue Type: Bug
> Reporter: Shaofeng SHI
> Assignee: Shaofeng SHI
>
> Problem:
> Deploy Kylin in EMR, and specify to use S3 as the working dir in kylin.properties, after build finished, noticed the HBase table is using jar on HDFS; If the EMR is re-created, although data in S3, HBase wasn't able to startup because the HDFS location doesn't exist anymore.
> Expected behavior: Kylin should use the working dir as the location for coprocessor, instead of using default FS.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)