[jira] [Resolved] (KYLIN-2743) Potential corrupt TableDesc when loading an existing Hive table
[ https://issues.apache.org/jira/browse/KYLIN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang resolved KYLIN-2743. --- Resolution: Fixed Assignee: liyang Fix Version/s: v2.1.0 > Potential corrupt TableDesc when loading an existing Hive table > --- > > Key: KYLIN-2743 > URL: https://issues.apache.org/jira/browse/KYLIN-2743 > Project: Kylin > Issue Type: Bug >Reporter: liyang >Assignee: liyang > Fix For: v2.1.0 > > > The root cause is directly modifying an TableDesc in memory without making a > copy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2743) Potential corrupt TableDesc when loading an existing Hive table
[ https://issues.apache.org/jira/browse/KYLIN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang updated KYLIN-2743: -- Summary: Potential corrupt TableDesc when loading an existing Hive table (was: Potential correupt TableDesc when loading an existing Hive table) > Potential corrupt TableDesc when loading an existing Hive table > --- > > Key: KYLIN-2743 > URL: https://issues.apache.org/jira/browse/KYLIN-2743 > Project: Kylin > Issue Type: Bug >Reporter: liyang > > The root cause is directly modifying an TableDesc in memory without making a > copy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2743) Potential correupt TableDesc when loading an existing Hive table
liyang created KYLIN-2743: - Summary: Potential correupt TableDesc when loading an existing Hive table Key: KYLIN-2743 URL: https://issues.apache.org/jira/browse/KYLIN-2743 Project: Kylin Issue Type: Bug Reporter: liyang The root cause is directly modifying an TableDesc in memory without making a copy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2720: --- Summary: Should not allow user to access to all tables' metadata of a project (was: Should not allow user to access to all table metadata of a project) > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2720) Should not allow user to access to all table metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qiumingming updated KYLIN-2720: --- Summary: Should not allow user to access to all table metadata of a project (was: Should not allow user to access to all tables of a project) > Should not allow user to access to all table metadata of a project > -- > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming > Fix For: v2.0.0, v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2715) StorageCleanupJob removes intermediate hive tables of jobs in progress
[ https://issues.apache.org/jira/browse/KYLIN-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088508#comment-16088508 ] Alexander Sterligov commented on KYLIN-2715: I've just double checked - it really deletes intermediate table, not working directory. > StorageCleanupJob removes intermediate hive tables of jobs in progress > -- > > Key: KYLIN-2715 > URL: https://issues.apache.org/jira/browse/KYLIN-2715 > Project: Kylin > Issue Type: Bug >Affects Versions: v2.0.0 >Reporter: Alexander Sterligov > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2715) StorageCleanupJob removes intermediate hive tables of jobs in progress
[ https://issues.apache.org/jira/browse/KYLIN-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088498#comment-16088498 ] Alexander Sterligov edited comment on KYLIN-2715 at 7/15/17 7:13 AM: - Yes, code looks good, but it is reproduced every time. I can investigate it further, but it seems to me, that the problem is that for segments which build is in progress getLastBuildJobID returns null and StorageCleanupJob removes the whole working dir. Is null last build job id for segments being built expected? It looks strange for me. was (Author: sterligovak): Yes, code looks good, but it reproduces every time. I can investigate it further, but it seems to me, that the problem is that for segments which build is in progress getLastBuildJobID returns null and StorageCleanupJob removes the whole working dir. Is null last build job id for segments being built expected? It looks strange for me. > StorageCleanupJob removes intermediate hive tables of jobs in progress > -- > > Key: KYLIN-2715 > URL: https://issues.apache.org/jira/browse/KYLIN-2715 > Project: Kylin > Issue Type: Bug >Affects Versions: v2.0.0 >Reporter: Alexander Sterligov > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2715) StorageCleanupJob removes intermediate hive tables of jobs in progress
[ https://issues.apache.org/jira/browse/KYLIN-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088498#comment-16088498 ] Alexander Sterligov commented on KYLIN-2715: Yes, code looks good, but it reproduces every time. I can investigate it further, but it seems to me, that the problem is that for segments which build is in progress getLastBuildJobID returns null and StorageCleanupJob removes the whole working dir. Is null last build job id for segments being built expected? It looks strange for me. > StorageCleanupJob removes intermediate hive tables of jobs in progress > -- > > Key: KYLIN-2715 > URL: https://issues.apache.org/jira/browse/KYLIN-2715 > Project: Kylin > Issue Type: Bug >Affects Versions: v2.0.0 >Reporter: Alexander Sterligov > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
