[
https://issues.apache.org/jira/browse/OOZIE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276849#comment-13276849
]
[email protected] commented on OOZIE-814:
-----------------------------------------------------
bq. On 2012-05-11 17:50:16, Alejandro Abdelnur wrote:
bq. > 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:
bq. >
bq. >
bq. > create table OOZIE_SYS (name varchar(100), data varchar(100))
bq. > insert into OOZIE_SYS (name, data) values ('db.version', '1')
bq. > insert into OOZIE_SYS (name, data) values ('oozie.version',
'3.2.0-SNAPSHOT')
bq. >
bq.
bq. Han Xiao wrote:
bq. The index is no need, the 'name' filed is assigned as primary key, so
database will create index for it when create the OOZIE_SYS table;
bq. You can see wf_actions in which id is the priamry key and there is no
index for it also.
bq. The data is insert in the createOozieSysTable() method. I use jpa to
insert the data, so there is no explict sql for it.
bq. I find no way to get the sql directly from jpa's persist() method,
which jpa uses it to insert a row of data.
bq.
bq. Thank you.
Han Xiao, I've meant the indexes of ALL tables created by Oozie are missing.
Please try the following using an Oozie build from a fresh checkout and then
applying your patch and you'll see the difference:
$ bin/ooziedb.sh create -sqlfile oozie.sql
compare the oozie.sql obtain in both runs.
thx
- Alejandro
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4755/#review7807
-----------------------------------------------------------
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
