You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Mona Chitnis (JIRA)" <ji...@apache.org> on 2013/07/13 01:13:48 UTC
[jira] [Commented] (OOZIE-1369) OozieDBCLI code should not hardcode
the Oozie table filenames
[ https://issues.apache.org/jira/browse/OOZIE-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707522#comment-13707522 ]
Mona Chitnis commented on OOZIE-1369:
-------------------------------------
Confirmed that patch works as expected with default Derby DB. +1 pending verification against Oracle DB etc.
Also [~jaoki] could you please rebase your patch to trunk?
> OozieDBCLI code should not hardcode the Oozie table filenames
> -------------------------------------------------------------
>
> Key: OOZIE-1369
> URL: https://issues.apache.org/jira/browse/OOZIE-1369
> Project: Oozie
> Issue Type: Improvement
> Affects Versions: trunk
> Reporter: Mona Chitnis
> Assignee: jun aoki
> Fix For: trunk
>
> Attachments: OOZIE-1369-2.patch, OOZIE-1369.patch
>
>
> The code in OozieDBCLI reads from the persistence.xml file to know the code files declaring all the tables and schemas. The method createMappingToolArguments() then should not duplicate and hardcode those filenames again. persistence.xml should be the singular place to specify openjpa tables and schema to avoid having to track 2 places
--
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