[
https://issues.apache.org/jira/browse/HIVE-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455636#comment-13455636
]
Alexander Alten-Lorenz commented on HIVE-3463:
----------------------------------------------
As hive is using atomic transactions to perform individual operations, its
causing issue during replication of the database. Hive does not have cascade on
the foreign key constraints, when the atomic transactions been performed on the
database, the bin log will be written based on the completion of the task
rather than the time of issuance. This is causing reversal of the order in bin
log, which causes the replication break.
> 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
> Priority: Minor
>
> 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
