Thanks, ShaoFeng



------------------ ???????? ------------------
??????: "ShaoFeng Shi"<[email protected]>;
????????: 2019??7??31??(??????) ????10:12
??????: "user"<[email protected]>;
????: "240902713"<[email protected]>;
????: Re: kylin doesn't drop intermediate lookup table after job finished



Hello,

Good feedback. I think it is a legacy issue. At the very beginning, the 
intermediate table name for the lookup table in view is likely to be the same. 
So if a job dropped the table on the finish, it may cause another job failed. 
As a temporary solution, we disabled the cleanup for Hive view tables.


Now since KYLIN-3515 has solved the conflict problem, I think this cleanup can 
be uncommented. JIRA is created for this: 
https://issues.apache.org/jira/browse/KYLIN-4121 If you want to contribute, 
welcome to raise a PR. Thanks!

Best regards,

Shaofeng Shi ??????
Apache Kylin PMC
Email: [email protected]


Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
Join Kylin user mail group: [email protected]
Join Kylin dev mail group: [email protected]

















Xiaoxiang Yu <[email protected]> ??2019??7??31?????? ????1:27??????

Hi,
    I think these tables could be cleaned by StorageCleanupJob. Please refer to 
http://kylin.apache.org/docs/howto/howto_cleanup_storage.html to clean these 
intermediate table.




-----------------
-----------------
Best wishes to you ! 
From ??Xiaoxiang Yu




At 2019-07-31 15:42:27, "240902713" <[email protected]> wrote:
 Hello :


I have a  question about why kylin doesn't drop the intermediate lookup table 
after job finished.


My kylin version: 2.6.0


I have a cube with a fact table join a lookup table  in hive, and both are hive 
view. I submit a job one time per hour.


Kylin can drop the intermediate fact table , but doesn't drop the intermediate 
lookup table .


I check the source code , and find out that , at '13 step: Hive Cleanup' ,  the 
source code has been commented. as the 


following picture shows:





After several days, in hive, there are a lot of intermediate lookup tables 
which are not droped.


Why can this step result some concurrent issue ? 




Looking forward your reply.


Thanks !

Reply via email to