Hi Yu feng,
In 0.7.2 and before, Kylin will not drop the old HTable after merge be
finished; Since 1.0, a "Garbage collection" step is introduced as the final
step, which will drop the old HTable;
We usually do offline cleanup to release the HDFS and HBase storages; You
can run:
hbase org.apache.hadoop.util.RunJar
${KYLIN_HOME}/lib/kylin-job-(version).jar
org.apache.kylin.job.hadoop.cube.StorageCleanupJob
This will list all the resources that can be dropped, then you can add
"--delete true" option to let it do the cleanup:
hbase org.apache.hadoop.util.RunJar
${KYLIN_HOME}/lib/kylin-job-(version).jar
org.apache.kylin.job.hadoop.cube.StorageCleanupJob --delete true
In the future versions, these will be automated; But you still can run
this offline cleanup at any point of time.
2015-09-06 11:17 GMT+08:00 yu feng <[email protected]>:
> we have tried cube building and merging in kylin-0.7.2, However , we find
> old cubes still exist after we merge them and a new cube created ,
> meanwhile , We find the metadata of this cube(in /cube/xxx) has
> been modified (only one segment exist !).
>
> I want to ask you guys can I remove those old tables from hbase and what
> the significance of their existing.
>
> Thanks a lot ...
>
