[ https://issues.apache.org/jira/browse/HIVE-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459680#comment-13459680 ]
Ashutosh Chauhan commented on HIVE-3463: ---------------------------------------- Alexander, Good findings! Couple of comments: * I wonder what about same issues for other backend dbs we support (postgres/derby/oracle). I assume you didn't look into those, but was wondering if you have any insight for that. * Wherever possible we should dictate the schema definitions from datanucleus ORM mapping (which lives in package.jdo) and try to avoid directly playing with schemas of individual db(in scripts/ dir). Obviously, if datanucleus doesn't expose feature of underlying db which we need, we won't have a choice. > Add CASCADING to MySQL's InnoDB schema > -------------------------------------- > > Key: HIVE-3463 > URL: https://issues.apache.org/jira/browse/HIVE-3463 > Project: Hive > Issue Type: Improvement > Components: Metastore > Affects Versions: 0.9.0 > Reporter: Alexander Alten-Lorenz > > Cascading could help to cleanup the tables when a FK is deleted. > http://dev.mysql.com/doc/refman/5.5/en/innodb-foreign-key-constraints.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira