Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
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.