> On 2012-05-22 18:23:05, Alejandro Abdelnur wrote:
> > Han Xiao,
> >
> > I've tried your latests patch on derby, running 'bin/ooziedb.sh create
> > -sqlfile derby.sql' and the following is missing from the generated sql:
> >
> >
> > 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.3.0-SNAPSHOT')
> >
> >
> > Also, have you verified that the connection health check set in the
> > JPAService is working on the custom schema.
> >
> > thx
1.In the new version, these sql are added:
insert into OOZIE_SYS (name, data) values ('db.version', '1')
insert into OOZIE_SYS (name, data) values ('oozie.version', '3.3.0-SNAPSHOT')
with "create table OOZIE_SYS (name varchar(100), data varchar(100))" now under
"CREATE TABLE COORD_JOBS (id VARCHAR(255)..."
2.Also, have you verified that the connection health check set in the
JPAService is working on the custom schema.
--thanks for your reminder, i've fixed the missing in the new version.
- Han
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4755/#review8038
-----------------------------------------------------------
On 2012-05-28 07:52:09, Han Xiao wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/4755/
> -----------------------------------------------------------
>
> (Updated 2012-05-28 07:52:09)
>
>
> Review request for oozie.
>
>
> Summary
> -------
>
> 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 addresses bug OOZIE-814.
> https://issues.apache.org/jira/browse/OOZIE-814
>
>
> Diffs
> -----
>
>
> http://svn.apache.org/repos/asf/incubator/oozie/trunk/utils/dbutils/updatescripts/readme.txt
> 1339440
>
> http://svn.apache.org/repos/asf/incubator/oozie/trunk/core/src/main/java/org/apache/oozie/SystemInfoBean.java
> PRE-CREATION
>
> http://svn.apache.org/repos/asf/incubator/oozie/trunk/core/src/main/java/org/apache/oozie/service/JPAService.java
> 1339440
>
> http://svn.apache.org/repos/asf/incubator/oozie/trunk/core/src/main/resources/META-INF/persistence.xml
> 1339440
>
> http://svn.apache.org/repos/asf/incubator/oozie/trunk/core/src/main/resources/oozie-default.xml
> 1339440
>
> http://svn.apache.org/repos/asf/incubator/oozie/trunk/docs/src/site/twiki/AG_Install.twiki
> 1339440
>
> http://svn.apache.org/repos/asf/incubator/oozie/trunk/tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java
> 1343152
>
> http://svn.apache.org/repos/asf/incubator/oozie/trunk/core/src/main/conf/oozie-site.xml
> 1339440
>
> Diff: https://reviews.apache.org/r/4755/diff
>
>
> Testing
> -------
>
> * Deployed Oozie, added oozie.db.schema.name configs values, succeed to run
> the examples on Derby and Postgres databases.
>
>
> Thanks,
>
> Han
>
>
