[
https://issues.apache.org/jira/browse/OOZIE-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110171#comment-14110171
]
Hadoop QA commented on OOZIE-1636:
----------------------------------
Testing JIRA OOZIE-1636
Cleaning local git workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
132
. {color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
. Tests run: 1508
. Tests failed: 6
. Tests errors: 2
. The patch failed the following testcases:
. testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)
. testMain(org.apache.oozie.action.hadoop.TestHiveMain)
. testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
. testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
. testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
. testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/1697/
> OOZIE_SYS table engine should be innodb
> ---------------------------------------
>
> Key: OOZIE-1636
> URL: https://issues.apache.org/jira/browse/OOZIE-1636
> Project: Oozie
> Issue Type: Improvement
> Components: tools
> Affects Versions: trunk, 4.1.0
> Reporter: Jayesh
> Priority: Minor
> Fix For: trunk, 4.1.0
>
> Attachments: OOZIE-1636.patch
>
>
> All oozie table are created with engine set to innodb explicitly but
> OOZIE_SYS table does not have engine specified which defaults to whatever
> mysql default engine is, which could be myisam sometimes.
> This could be easily missed and create problem while taking database backup.
> so this ticket is for specifying engine innodb for OOZIE_SYS explicitly while
> creating oozie.sql
--
This message was sent by Atlassian JIRA
(v6.2#6252)
