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

[email protected] commented on OOZIE-814:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4755/#review7807
-----------------------------------------------------------


I've run 'ooziedb.sh create -sqlfile x.sql' with the patch and i've noticed 
that the table indexes are not being created anymore and  that the OOZIE_SYS 
table is not seeded with data:


create table OOZIE_SYS (name varchar(100), data varchar(100))
insert into OOZIE_SYS (name, data) values ('db.version', '1')
insert into OOZIE_SYS (name, data) values ('oozie.version', '3.2.0-SNAPSHOT')


- Alejandro


On 2012-05-11 03:55:07, Han Xiao wrote:
bq.  
bq.  -----------------------------------------------------------
bq.  This is an automatically generated e-mail. To reply, visit:
bq.  https://reviews.apache.org/r/4755/
bq.  -----------------------------------------------------------
bq.  
bq.  (Updated 2012-05-11 03:55:07)
bq.  
bq.  
bq.  Review request for oozie.
bq.  
bq.  
bq.  Summary
bq.  -------
bq.  
bq.  Oozie's JPA service doesn't support configure different schemas for 
oozie's db.
bq.  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.
bq.  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.
bq.  
bq.  
bq.  This addresses bug OOZIE-814.
bq.      https://issues.apache.org/jira/browse/OOZIE-814
bq.  
bq.  
bq.  Diffs
bq.  -----
bq.  
bq.    
http://svn.apache.org/repos/asf/incubator/oozie/trunk/core/src/main/conf/oozie-site.xml
 1335881 
bq.    
http://svn.apache.org/repos/asf/incubator/oozie/trunk/core/src/main/java/org/apache/oozie/SystemInfoBean.java
 PRE-CREATION 
bq.    
http://svn.apache.org/repos/asf/incubator/oozie/trunk/core/src/main/java/org/apache/oozie/service/JPAService.java
 1335881 
bq.    
http://svn.apache.org/repos/asf/incubator/oozie/trunk/core/src/main/resources/META-INF/persistence.xml
 1335881 
bq.    
http://svn.apache.org/repos/asf/incubator/oozie/trunk/core/src/main/resources/oozie-default.xml
 1335881 
bq.    
http://svn.apache.org/repos/asf/incubator/oozie/trunk/docs/src/site/twiki/AG_Install.twiki
 1335881 
bq.    
http://svn.apache.org/repos/asf/incubator/oozie/trunk/tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java
 1335881 
bq.    
http://svn.apache.org/repos/asf/incubator/oozie/trunk/utils/dbutils/updatescripts/readme.txt
 1335881 
bq.  
bq.  Diff: https://reviews.apache.org/r/4755/diff
bq.  
bq.  
bq.  Testing
bq.  -------
bq.  
bq.  * Deployed Oozie, added oozie.db.schema.name configs values, succeed to 
run the examples on Derby and Postgres databases.
bq.  
bq.  
bq.  Thanks,
bq.  
bq.  Han
bq.  
bq.


                
> 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, trunk
>            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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to