Hi Hongbin, After installing a clean hdp 2.2.4, I'm able to run BuildCubeWithEngineTest and DebugTomcat without any hbase permission error. I'm using the lastest master code this time (commit: f96d6e9)
So I think my previous sandbox may be affected by abnormal actions. Here's the reminiscence of what I've done before: 1. I checked out the 0.7 branch and run BuildCubeWithEngineTest successfully with the sandbox 2. Then I want to evaluate the resent 0.7.2-Incubating release. So I checked out the master branch and recompile it 3. I failed to run DebugTomcat and came to ask here 4. Throughout the process, I didn't modify any configs of the sandbox Hope you'll get a clue from the above description. Anyway, here's some undocumented steps to get it right: 1. For IDEA users, replace all "PROVIDED" with "COMPILE" in server/kylin-server.iml 2. Copy "server/src/main/webapp/WEB-INF" to "webapp/app/" 3. In debug configurations, setup "Working directory" to server, and what I find useful is to add the "-Dcatalina.home" VM options, otherwise the log will go to /logs/kylin.log which can cause file permission problem Thanks, Dayue > 在 2015年7月24日，下午3:20，hongbin ma <[email protected]> 写道： > > hi, dayue > > It's interesting that I started with a clean hdp 2.2.4 without modifying > the ambari hbase config. > Till now I can still see > "com.xasecure.authorization.hbase.XaSecureAuthorizationCoprocessor" in my > config. > > Did you make any changes to sandbox prior to installing Kylin? > > Besides, if you encounter any other issues/questions when trying to debug > Kylin, kindly let us know. We'll make it develop-friendly as much as > possible. > > > On Fri, Jul 24, 2015 at 2:32 PM, Dayue Gao <[email protected]> wrote: > >> 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 >> >> >> > > > -- > Regards, > > *Bin Mahone | 马洪宾* > Apache Kylin: http://kylin.io > Github: https://github.com/binmahone
