Hi, Hongbin Finally get it work! Thanks for the hint, here's the steps to disable access control for sandbox 2.2.4:
1. Open the "Configs" tab of HBase in Ambari 2. Inside "Advanced hbase-site" section, empty the value of "hbase.coprocessor.region.classes" and "hbase.coprocessor.master.classes" 3. Restart Hbase Hope it could help anyone who run into the same problem :-) Thanks again to Hongbin, Shaofeng! Regards, Dayue > 在 2015年7月24日，上午10:47，hongbin ma <[email protected]> 写道： > > hi, Dayue, > > I tried 0.7-staging against a brand new hdp 2.2.4 sandbox, it worked out > well > (I skipped BuildCubeWithEngineTest and directly ran DebugTomcat. > BuildCubeWithEngineTest > will populate some sample cubes in the system, i.e metadata store, by > skipping it we'll get a clean&empty metdata store ) > > My guess is that you enabled any access control on HBase? Can you stop it ? > It is my believe that Kylin always assume current user have permissions to > create tables and read tables from HBase, The following configuration you > made are related to hive query executing, it has nothing to do with HBase > > kylin.job.run.as.remote.cmd=true > > # Only necessary when kylin.job.run.as.remote.cmd=true > kylin.job.remote.cli.hostname=sandbox > > # Only necessary when kylin.job.run.as.remote.cmd=true > kylin.job.remote.cli.username=root > > # Only necessary when kylin.job.run.as.remote.cmd=true > kylin.job.remote.cli.password=hadoop > > -- > Regards, > > *Bin Mahone | 马洪宾* > Apache Kylin: http://kylin.io > Github: https://github.com/binmahone
