[
https://issues.apache.org/jira/browse/OOZIE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568752#comment-15568752
]
Andras Piros edited comment on OOZIE-2662 at 10/12/16 1:43 PM:
---------------------------------------------------------------
Following error handling is implemented:
# check if all necessary tables are present and empty
# rows are imported till the end
# if at least one row is skipped in the meanwhile for some
{{ConstraintViolationException}}, we delete all rows of all necessary tables.
That enables the user to have the log messages of all the erroneous rows in one
run, and Oozie database is never in an inconsistent state of some rows present,
some not present of an import
was (Author: andras.piros):
Following error handling is implemented:
# check if all necessary tables are present and empty
# rows are imported till the end
# if at least one row is skipped in the meanwhile for some
{{ConstraintViolationException}}, we delete all necessary tables. That enables
the user to have the log messages of all the erroneous rows in one run, and
Oozie database is never in an inconsistent state of some rows present, some not
present of an import
> DB migration fails if DB is too big
> -----------------------------------
>
> Key: OOZIE-2662
> URL: https://issues.apache.org/jira/browse/OOZIE-2662
> Project: Oozie
> Issue Type: Bug
> Reporter: Peter Cseh
> Assignee: Andras Piros
> Attachments: OOZIE-2662.001.patch, OOZIE-2662.002.patch,
> OOZIE-2662.002.wip.patch
>
>
> The initial version of the DB import tool commits all the workflows, actions
> etc. in one huge commit. If it does not fits into the memory, AOOME is thrown.
> We should commit every 1k or 10k elements to prevent this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
