You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2014/09/03 05:35:51 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=14119266#comment-14119266 ]
Hadoop QA commented on OOZIE-1369:
----------------------------------
Testing JIRA OOZIE-1369
Cleaning local git workspace
----------------------------
{color:red}-1{color} Patch failed to apply to head of branch
----------------------------
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)