[jira] [Commented] (OOZIE-814) Add support of configuring db's schema in JPAService for oozie

["David Villegas (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037604#comment-14037604 ] 

David Villegas commented on OOZIE-814:
--------------------------------------

Hi Han Xiao and Alejandro,

was there any progress with this JIRA? We actually hit the same issue when using a DB schema, so I'd be happy to re-take this. I have an initial patch, plus I submitted another one to remove the last remaining NativeQuery in OOZIE-1889 so that the schema can be specified as a property through JPA.

I don't see any patch attached to this issue, if any of you still have it I can compare and merge it to mine, else I can submit my take on the issue.

Thanks!

> Add support of configuring db's schema in JPAService for oozie
> --------------------------------------------------------------
>
>                 Key: OOZIE-814
>                 URL: https://issues.apache.org/jira/browse/OOZIE-814
>             Project: Oozie
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.2.0, 3.3.0
>            Reporter: Han Xiao
>             Fix For: trunk
>
>
> Oozie's JPA service doesn't support configure different schemas for oozie's db.
> Our company wants to use one db for multi oozie clusters, and then we want each oozie cluster can use different schema of the db. Therefore JPAService in oozie should support to configure the schema of the db, not just the database.
> The oozie.db.schema.name is use to configure oozie's db name, however, it is a little confusing for it is not used to configure the actually schema of db.



--
This message was sent by Atlassian JIRA
(v6.2#6252)