[jira] [Commented] (OOZIE-2339) Provide an API for writing jobs based on the XSD schemas
[ https://issues.apache.org/jira/browse/OOZIE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16414862#comment-16414862 ] Artem Ervits commented on OOZIE-2339: - how about "workflow as code"? > Provide an API for writing jobs based on the XSD schemas > > > Key: OOZIE-2339 > URL: https://issues.apache.org/jira/browse/OOZIE-2339 > Project: Oozie > Issue Type: New Feature > Components: client >Affects Versions: 4.3.0 >Reporter: Robert Kanter >Assignee: Andras Piros >Priority: Major > Fix For: 5.1.0 > > Attachments: OOZIE-2339.001.patch, OOZIE-2339.002.patch, > OOZIE-2339.003.patch, OOZIE-2339.004.patch, OOZIE-2339.005.patch, > OOZIE-2339.006.patch, OOZIE-2339.008.patch, OOZIE-2339.010.patch, > OOZIE-2339.011.patch > > > Users often complain about the XML they have to write for Oozie jobs. It > would be nice if they could write them in something like Java, but we don't > want to have to maintain a separate Java API for this. I was looking around > and saw that JAXB might be the right thing here. From what I can tell, it > lets you create Java classes from XSD schemas. So, we should be able to > auto-generate a Java API for writing Oozie jobs, without having to really > maintain it. > We should investigate if this is feasible and, if so, implement it. > Some useful looking links: > * [JAXB > overview|https://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding] > * [JAXB description|https://jaxb.java.net/2.2.11/docs/ch03.html] > * [Maven JAXB plugin|https://java.net/projects/maven-jaxb2-plugin/pages/Home] > * [Apache Falcon|https://falcon.apache.org] > Key features: > * must have: > ** inside an {{oozie-jobs-api}} artifact > ** able to create workflow / coordinator / bundle definitions programmatically > ** synchronizing each and every XSD change on rebuild > ** can write {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and > {{jobs.properties}} artifacts of every XSD version > ** cloneability of workflow etc. {{Object}} s > ** perform cross checks, e.g. that the workflow graph is a DAG > ** only latest XSD versions should be supported as must have > * nice to have: > ** XSD version(s) can be provided. When not provided, latest ones are > considered as valid > ** implement a [*fluent API*|https://en.wikipedia.org/wiki/Fluent_interface] > ** have a Python / Jython REPL to make it easy to experiment > ** create documentation about usage > ** can read {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and > {{jobs.properties}} artifacts of every XSD version > ** can convert between XSD versions > ** support XSD change on the fly (within REPL) > ** support HDFS reads / writes > ** support dry run on an Oozie server to perform checks -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2339) Provide an API for writing jobs based on the XSD schemas
[ https://issues.apache.org/jira/browse/OOZIE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16414845#comment-16414845 ] Robert Kanter commented on OOZIE-2339: -- I just left some more comments on ReviewBoard. Though in the interest of time, I didn't look too carefully at some of the generating code like the {{DozerConverter}} classes and a lot of the unit tests. One high-level thing I wanted to bring up is what are we calling this feature? It looks like it's currently "Jobs API", but I have a few concerns about that name: # It's pretty generic-sounding and non-specific. # "Jobs" is a pretty overloaded term already. It refers to Oozie Jobs (i.e. Workflows, Coordinators, and Bundles), Hadoop/Pig/Sqoop/etc Jobs, the Launcher Job, etc. I'd like to avoid "Jobs" if possible, or at least qualify it with something else like "Programatic Jobs API" or something. I don't have a great alternative for a name, other than "Programatic Jobs API", which isn't super great either. Any ideas? > Provide an API for writing jobs based on the XSD schemas > > > Key: OOZIE-2339 > URL: https://issues.apache.org/jira/browse/OOZIE-2339 > Project: Oozie > Issue Type: New Feature > Components: client >Affects Versions: 4.3.0 >Reporter: Robert Kanter >Assignee: Andras Piros >Priority: Major > Fix For: 5.1.0 > > Attachments: OOZIE-2339.001.patch, OOZIE-2339.002.patch, > OOZIE-2339.003.patch, OOZIE-2339.004.patch, OOZIE-2339.005.patch, > OOZIE-2339.006.patch, OOZIE-2339.008.patch, OOZIE-2339.010.patch, > OOZIE-2339.011.patch > > > Users often complain about the XML they have to write for Oozie jobs. It > would be nice if they could write them in something like Java, but we don't > want to have to maintain a separate Java API for this. I was looking around > and saw that JAXB might be the right thing here. From what I can tell, it > lets you create Java classes from XSD schemas. So, we should be able to > auto-generate a Java API for writing Oozie jobs, without having to really > maintain it. > We should investigate if this is feasible and, if so, implement it. > Some useful looking links: > * [JAXB > overview|https://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding] > * [JAXB description|https://jaxb.java.net/2.2.11/docs/ch03.html] > * [Maven JAXB plugin|https://java.net/projects/maven-jaxb2-plugin/pages/Home] > * [Apache Falcon|https://falcon.apache.org] > Key features: > * must have: > ** inside an {{oozie-jobs-api}} artifact > ** able to create workflow / coordinator / bundle definitions programmatically > ** synchronizing each and every XSD change on rebuild > ** can write {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and > {{jobs.properties}} artifacts of every XSD version > ** cloneability of workflow etc. {{Object}} s > ** perform cross checks, e.g. that the workflow graph is a DAG > ** only latest XSD versions should be supported as must have > * nice to have: > ** XSD version(s) can be provided. When not provided, latest ones are > considered as valid > ** implement a [*fluent API*|https://en.wikipedia.org/wiki/Fluent_interface] > ** have a Python / Jython REPL to make it easy to experiment > ** create documentation about usage > ** can read {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and > {{jobs.properties}} artifacts of every XSD version > ** can convert between XSD versions > ** support XSD change on the fly (within REPL) > ** support HDFS reads / writes > ** support dry run on an Oozie server to perform checks -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2339) Provide an API for writing jobs based on the XSD schemas
[ https://issues.apache.org/jira/browse/OOZIE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407429#comment-16407429 ] Hadoop QA commented on OOZIE-2339: -- Testing JIRA OOZIE-2339 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:red}-1{color} the patch contains 12 line(s) with tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:red}-1{color} the patch contains 37 line(s) longer than 132 characters .{color:green}+1{color} the patch adds/modifies 97 testcase(s) {color:red}-1 RAT{color} .{color:red}-1{color} the patch seems to introduce 1 new RAT warning(s) {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings .{color:red}WARNING{color}: the current HEAD has 100 Javadoc warning(s) {color:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:red}-1{color} the patch seems to introduce 11 new javac warning(s) {color:red}-1{color} There are [120] new bugs found below threshold in total that must be fixed. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:red}-1{color} There are [114] new bugs found below threshold in [jobs/jobs-api] that must be fixed, listing only the first [5] ones. . You can find the FindBugs diff here (look for the red and orange ones): jobs/jobs-api/findbugs-new.html . The top [5] most important FindBugs errors are: . At GraphVisualization.java:[line 102]: java/io/File.init(Ljava/lang/String;Ljava/lang/String;)V reads a file whose location might be specified by user input . At GraphVisualization.java:[line 108]: java/io/File.init(Ljava/lang/String;Ljava/lang/String;)V reads a file whose location might be specified by user input . At NodeBuilderBaseImpl.java:[line 247]: The use of java.lang.Math.random() is predictable . At SimpleWorkflowFactory.java:[line 54]: Dead store to happyPath in org.apache.oozie.jobs.api.factory.SimpleWorkflowFactory.create() . At SimpleWorkflowFactory.java:[line 60]: Dead store to sadPath in org.apache.oozie.jobs.api.factory.SimpleWorkflowFactory.create() . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [webapp]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:red}-1{color} There are [5] new bugs found below threshold in [client] that must be fixed. . You can find the FindBugs diff here (look for the red and orange ones): client/findbugs-new.html . The most important FindBugs errors are: . Dereferenced at ApiJarFactory.java:[line 86]: Possible null pointer dereference in org.apache.oozie.cli.ApiJarFactory.addWorkflowJarEntry(File, JarOutputStream) due to return value of called method . java/io/FileOutputStream.init(Ljava/lang/String;)V writes to a file whose location might be specified by user input: Known null at ApiJarFactory.java:[line 86] . At ApiJarFactory.java:[line 67]: At ApiJarFactory.java:[line 67] . At ApiJarLoader.java:[line 52]: org.apache.oozie.cli.ApiJarLoader.loadAndGenerate() may fail to close stream . At OozieCLI.java:[line 1396]: Found reliance on default encoding in org.apache.oozie.cli.OozieCLI.checkApiJar(XOozieClient, CommandLine, boolean): String.getBytes() . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [server]. . {color:red}-1{color} There are [1] new bugs found below threshold in [core] that must be fixed. . You can find the FindBugs diff here (look for the red and orange ones): core/findbugs-new.html . The most important FindBugs errors are: . At V1JobsServlet.java:[line 163]: Found reliance on default encoding in org.apache.oozie.servlet.V1JobsServlet.checkAndWriteApplicationXMLToHDFS(String, Configuration): new java.io.OutputStreamWriter(OutputStream) {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
[jira] [Commented] (OOZIE-2339) Provide an API for writing jobs based on the XSD schemas
[ https://issues.apache.org/jira/browse/OOZIE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407353#comment-16407353 ] Hadoop QA commented on OOZIE-2339: -- PreCommit-OOZIE-Build started > Provide an API for writing jobs based on the XSD schemas > > > Key: OOZIE-2339 > URL: https://issues.apache.org/jira/browse/OOZIE-2339 > Project: Oozie > Issue Type: New Feature > Components: client >Affects Versions: 4.3.0 >Reporter: Robert Kanter >Assignee: Andras Piros >Priority: Major > Fix For: 5.1.0 > > Attachments: OOZIE-2339.001.patch, OOZIE-2339.002.patch, > OOZIE-2339.003.patch, OOZIE-2339.004.patch, OOZIE-2339.005.patch, > OOZIE-2339.006.patch, OOZIE-2339.008.patch, OOZIE-2339.010.patch, > OOZIE-2339.011.patch > > > Users often complain about the XML they have to write for Oozie jobs. It > would be nice if they could write them in something like Java, but we don't > want to have to maintain a separate Java API for this. I was looking around > and saw that JAXB might be the right thing here. From what I can tell, it > lets you create Java classes from XSD schemas. So, we should be able to > auto-generate a Java API for writing Oozie jobs, without having to really > maintain it. > We should investigate if this is feasible and, if so, implement it. > Some useful looking links: > * [JAXB > overview|https://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding] > * [JAXB description|https://jaxb.java.net/2.2.11/docs/ch03.html] > * [Maven JAXB plugin|https://java.net/projects/maven-jaxb2-plugin/pages/Home] > * [Apache Falcon|https://falcon.apache.org] > Key features: > * must have: > ** inside an {{oozie-jobs-api}} artifact > ** able to create workflow / coordinator / bundle definitions programmatically > ** synchronizing each and every XSD change on rebuild > ** can write {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and > {{jobs.properties}} artifacts of every XSD version > ** cloneability of workflow etc. {{Object}} s > ** perform cross checks, e.g. that the workflow graph is a DAG > ** only latest XSD versions should be supported as must have > * nice to have: > ** XSD version(s) can be provided. When not provided, latest ones are > considered as valid > ** implement a [*fluent API*|https://en.wikipedia.org/wiki/Fluent_interface] > ** have a Python / Jython REPL to make it easy to experiment > ** create documentation about usage > ** can read {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and > {{jobs.properties}} artifacts of every XSD version > ** can convert between XSD versions > ** support XSD change on the fly (within REPL) > ** support HDFS reads / writes > ** support dry run on an Oozie server to perform checks -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2339) Provide an API for writing jobs based on the XSD schemas
[ https://issues.apache.org/jira/browse/OOZIE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317271#comment-16317271 ] Hadoop QA commented on OOZIE-2339: -- Testing JIRA OOZIE-2339 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:red}-1{color} the patch contains 12 line(s) with tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:red}-1{color} the patch contains 17 line(s) longer than 132 characters .{color:green}+1{color} the patch adds/modifies 97 testcase(s) {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:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:red}-1{color} patch does not compile .{color:red}-1{color} the patch seems to introduce 1 new javac warning(s) {color:green}+1{color} There are no new bugs found in total. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [client]. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [server]. {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} - patch does not compile, cannot run testcases {color:red}-1 DISTRO{color} .{color:red}-1{color} distro tarball fails 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/PreCommit-OOZIE-Build/316/ > Provide an API for writing jobs based on the XSD schemas > > > Key: OOZIE-2339 > URL: https://issues.apache.org/jira/browse/OOZIE-2339 > Project: Oozie > Issue Type: New Feature > Components: client >Affects Versions: 4.3.0 >Reporter: Robert Kanter >Assignee: Andras Piros > Fix For: 5.0.0 > > Attachments: OOZIE-2339.001.patch, OOZIE-2339.002.patch, > OOZIE-2339.003.patch, OOZIE-2339.004.patch, OOZIE-2339.005.patch, > OOZIE-2339.006.patch, OOZIE-2339.008.patch, OOZIE-2339.010.patch > > > Users often complain about the XML they have to write for Oozie jobs. It > would be nice if they could write them in something like Java, but we don't > want to have to maintain a separate Java API for this. I was looking around > and saw that JAXB might be the right thing here. From what I can tell, it > lets you create Java classes from XSD schemas. So, we should be able to > auto-generate a Java API for writing Oozie jobs, without having to really > maintain it. > We should investigate if this is feasible and, if so, implement it. > Some useful looking links: > * [JAXB > overview|https://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding] > * [JAXB description|https://jaxb.java.net/2.2.11/docs/ch03.html] > * [Maven JAXB plugin|https://java.net/projects/maven-jaxb2-plugin/pages/Home] > * [Apache Falcon|https://falcon.apache.org] > Key features: > * must have: > ** inside an {{oozie-jobs-api}} artifact > ** able to create workflow / coordinator / bundle definitions programmatically > ** synchronizing each and every XSD change on rebuild > ** can write {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and > {{jobs.properties}} artifacts of every XSD version > ** cloneability of workflow etc. {{Object}} s > ** perform cross checks, e.g. that the workflow graph is a DAG > ** only latest XSD versions should be supported as must have > * nice to have: >
[jira] [Commented] (OOZIE-2339) Provide an API for writing jobs based on the XSD schemas
[ https://issues.apache.org/jira/browse/OOZIE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317252#comment-16317252 ] Hadoop QA commented on OOZIE-2339: -- Testing JIRA OOZIE-2339 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:red}-1{color} the patch contains 12 line(s) with tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:red}-1{color} the patch contains 17 line(s) longer than 132 characters .{color:green}+1{color} the patch adds/modifies 97 testcase(s) {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:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:red}-1{color} patch does not compile .{color:red}-1{color} the patch seems to introduce 1 new javac warning(s) {color:green}+1{color} There are no new bugs found in total. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [client]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [server]. {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} - patch does not compile, cannot run testcases {color:red}-1 DISTRO{color} .{color:red}-1{color} distro tarball fails 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/PreCommit-OOZIE-Build/315/ > Provide an API for writing jobs based on the XSD schemas > > > Key: OOZIE-2339 > URL: https://issues.apache.org/jira/browse/OOZIE-2339 > Project: Oozie > Issue Type: New Feature > Components: client >Affects Versions: 4.3.0 >Reporter: Robert Kanter >Assignee: Andras Piros > Fix For: 5.0.0 > > Attachments: OOZIE-2339.001.patch, OOZIE-2339.002.patch, > OOZIE-2339.003.patch, OOZIE-2339.004.patch, OOZIE-2339.005.patch, > OOZIE-2339.006.patch, OOZIE-2339.008.patch, OOZIE-2339.010.patch > > > Users often complain about the XML they have to write for Oozie jobs. It > would be nice if they could write them in something like Java, but we don't > want to have to maintain a separate Java API for this. I was looking around > and saw that JAXB might be the right thing here. From what I can tell, it > lets you create Java classes from XSD schemas. So, we should be able to > auto-generate a Java API for writing Oozie jobs, without having to really > maintain it. > We should investigate if this is feasible and, if so, implement it. > Some useful looking links: > * [JAXB > overview|https://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding] > * [JAXB description|https://jaxb.java.net/2.2.11/docs/ch03.html] > * [Maven JAXB plugin|https://java.net/projects/maven-jaxb2-plugin/pages/Home] > * [Apache Falcon|https://falcon.apache.org] > Key features: > * must have: > ** inside an {{oozie-jobs-api}} artifact > ** able to create workflow / coordinator / bundle definitions programmatically > ** synchronizing each and every XSD change on rebuild > ** can write {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and > {{jobs.properties}} artifacts of every XSD version > ** cloneability of workflow etc. {{Object}} s > ** perform cross checks, e.g. that the workflow graph is a DAG > ** only latest XSD versions should be supported as must have > * nice to have: >
[jira] [Commented] (OOZIE-2339) Provide an API for writing jobs based on the XSD schemas
[ https://issues.apache.org/jira/browse/OOZIE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266553#comment-16266553 ] Hadoop QA commented on OOZIE-2339: -- Testing JIRA OOZIE-2339 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:red}-1{color} the patch contains 12 line(s) with tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:red}-1{color} the patch contains 6 line(s) longer than 132 characters .{color:green}+1{color} the patch does adds/modifies 87 testcase(s) {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:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:red}-1{color} patch does not compile .{color:red}-1{color} the patch seems to introduce 1 new javac warning(s) {color:green}+1{color} There are no new bugs found in total. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [client]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [server]. {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} - patch does not compile, cannot run testcases {color:red}-1 DISTRO{color} .{color:red}-1{color} distro tarball fails 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/PreCommit-OOZIE-Build/255/ > Provide an API for writing jobs based on the XSD schemas > > > Key: OOZIE-2339 > URL: https://issues.apache.org/jira/browse/OOZIE-2339 > Project: Oozie > Issue Type: New Feature > Components: client >Affects Versions: 4.3.0 >Reporter: Robert Kanter >Assignee: Andras Piros > Fix For: 5.0.0 > > Attachments: OOZIE-2339.001.patch, OOZIE-2339.002.patch, > OOZIE-2339.003.patch, OOZIE-2339.004.patch, OOZIE-2339.005.patch, > OOZIE-2339.006.patch, OOZIE-2339.008.patch > > > Users often complain about the XML they have to write for Oozie jobs. It > would be nice if they could write them in something like Java, but we don't > want to have to maintain a separate Java API for this. I was looking around > and saw that JAXB might be the right thing here. From what I can tell, it > lets you create Java classes from XSD schemas. So, we should be able to > auto-generate a Java API for writing Oozie jobs, without having to really > maintain it. > We should investigate if this is feasible and, if so, implement it. > Some useful looking links: > * [JAXB > overview|https://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding] > * [JAXB description|https://jaxb.java.net/2.2.11/docs/ch03.html] > * [Maven JAXB plugin|https://java.net/projects/maven-jaxb2-plugin/pages/Home] > * [Apache Falcon|https://falcon.apache.org] > Key features: > * must have: > ** inside an {{oozie-jobs-api}} artifact > ** able to create workflow / coordinator / bundle definitions programmatically > ** synchronizing each and every XSD change on rebuild > ** can write {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and > {{jobs.properties}} artifacts of every XSD version > ** cloneability of workflow etc. {{Object}} s > ** perform cross checks, e.g. that the workflow graph is a DAG > ** only latest XSD versions should be supported as must have > * nice to have: > ** XSD version(s)
[jira] [Commented] (OOZIE-2339) Provide an API for writing jobs based on the XSD schemas
[ https://issues.apache.org/jira/browse/OOZIE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264585#comment-16264585 ] Hadoop QA commented on OOZIE-2339: -- Testing JIRA OOZIE-2339 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:red}-1{color} the patch contains 12 line(s) with tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:red}-1{color} the patch contains 6 line(s) longer than 132 characters .{color:green}+1{color} the patch does adds/modifies 70 testcase(s) {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:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:red}-1{color} patch does not compile .{color:red}-1{color} the patch seems to introduce 1 new javac warning(s) {color:green}+1{color} There are no new bugs found in total. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [client]. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [server]. {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} - patch does not compile, cannot run testcases {color:red}-1 DISTRO{color} .{color:red}-1{color} distro tarball fails 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/PreCommit-OOZIE-Build/253/ > Provide an API for writing jobs based on the XSD schemas > > > Key: OOZIE-2339 > URL: https://issues.apache.org/jira/browse/OOZIE-2339 > Project: Oozie > Issue Type: New Feature > Components: client >Affects Versions: 4.3.0 >Reporter: Robert Kanter >Assignee: Andras Piros > Fix For: 5.0.0 > > Attachments: OOZIE-2339.001.patch, OOZIE-2339.002.patch, > OOZIE-2339.003.patch, OOZIE-2339.004.patch, OOZIE-2339.005.patch, > OOZIE-2339.006.patch > > > Users often complain about the XML they have to write for Oozie jobs. It > would be nice if they could write them in something like Java, but we don't > want to have to maintain a separate Java API for this. I was looking around > and saw that JAXB might be the right thing here. From what I can tell, it > lets you create Java classes from XSD schemas. So, we should be able to > auto-generate a Java API for writing Oozie jobs, without having to really > maintain it. > We should investigate if this is feasible and, if so, implement it. > Some useful looking links: > * [JAXB > overview|https://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding] > * [JAXB description|https://jaxb.java.net/2.2.11/docs/ch03.html] > * [Maven JAXB plugin|https://java.net/projects/maven-jaxb2-plugin/pages/Home] > * [Apache Falcon|https://falcon.apache.org] > Key features: > * must have: > ** inside an {{oozie-jobs-api}} artifact > ** able to create workflow / coordinator / bundle definitions programmatically > ** synchronizing each and every XSD change on rebuild > ** can write {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and > {{jobs.properties}} artifacts of every XSD version > ** cloneability of workflow etc. {{Object}} s > ** perform cross checks, e.g. that the workflow graph is a DAG > ** only latest XSD versions should be supported as must have > * nice to have: > ** XSD version(s) can be provided. When
[jira] [Commented] (OOZIE-2339) Provide an API for writing jobs based on the XSD schemas
[ https://issues.apache.org/jira/browse/OOZIE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262543#comment-16262543 ] Hadoop QA commented on OOZIE-2339: -- Testing JIRA OOZIE-2339 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:red}-1{color} the patch contains 12 line(s) with tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:red}-1{color} the patch contains 6 line(s) longer than 132 characters .{color:green}+1{color} the patch does adds/modifies 64 testcase(s) {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:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:red}-1{color} patch does not compile .{color:red}-1{color} the patch seems to introduce 1 new javac warning(s) {color:green}+1{color} There are no new bugs found in total. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [client]. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [server]. {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} - patch does not compile, cannot run testcases {color:red}-1 DISTRO{color} .{color:red}-1{color} distro tarball fails 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/PreCommit-OOZIE-Build/251/ > Provide an API for writing jobs based on the XSD schemas > > > Key: OOZIE-2339 > URL: https://issues.apache.org/jira/browse/OOZIE-2339 > Project: Oozie > Issue Type: New Feature > Components: client >Affects Versions: 4.3.0 >Reporter: Robert Kanter >Assignee: Andras Piros > Fix For: 5.0.0 > > Attachments: OOZIE-2339.001.patch, OOZIE-2339.002.patch, > OOZIE-2339.003.patch, OOZIE-2339.004.patch, OOZIE-2339.005.patch > > > Users often complain about the XML they have to write for Oozie jobs. It > would be nice if they could write them in something like Java, but we don't > want to have to maintain a separate Java API for this. I was looking around > and saw that JAXB might be the right thing here. From what I can tell, it > lets you create Java classes from XSD schemas. So, we should be able to > auto-generate a Java API for writing Oozie jobs, without having to really > maintain it. > We should investigate if this is feasible and, if so, implement it. > Some useful looking links: > * [JAXB > overview|https://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding] > * [JAXB description|https://jaxb.java.net/2.2.11/docs/ch03.html] > * [Maven JAXB plugin|https://java.net/projects/maven-jaxb2-plugin/pages/Home] > * [Apache Falcon|https://falcon.apache.org] > Key features: > * must have: > ** inside an {{oozie-jobs-api}} artifact > ** able to create workflow / coordinator / bundle definitions programmatically > ** synchronizing each and every XSD change on rebuild > ** can write {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and > {{jobs.properties}} artifacts of every XSD version > ** cloneability of workflow etc. {{Object}} s > ** perform cross checks, e.g. that the workflow graph is a DAG > ** only latest XSD versions should be supported as must have > * nice to have: > ** XSD version(s) can be provided. When not provided, latest ones
[jira] [Commented] (OOZIE-2339) Provide an API for writing jobs based on the XSD schemas
[ https://issues.apache.org/jira/browse/OOZIE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262162#comment-16262162 ] Attila Sasvari commented on OOZIE-2339: --- [~andras.piros] thanks for working on it, can you file a reviewboard request, and add a link here? > Provide an API for writing jobs based on the XSD schemas > > > Key: OOZIE-2339 > URL: https://issues.apache.org/jira/browse/OOZIE-2339 > Project: Oozie > Issue Type: New Feature > Components: client >Affects Versions: 4.3.0 >Reporter: Robert Kanter >Assignee: Andras Piros > Fix For: 5.0.0 > > Attachments: OOZIE-2339.001.patch, OOZIE-2339.002.patch, > OOZIE-2339.003.patch > > > Users often complain about the XML they have to write for Oozie jobs. It > would be nice if they could write them in something like Java, but we don't > want to have to maintain a separate Java API for this. I was looking around > and saw that JAXB might be the right thing here. From what I can tell, it > lets you create Java classes from XSD schemas. So, we should be able to > auto-generate a Java API for writing Oozie jobs, without having to really > maintain it. > We should investigate if this is feasible and, if so, implement it. > Some useful looking links: > * [JAXB > overview|https://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding] > * [JAXB description|https://jaxb.java.net/2.2.11/docs/ch03.html] > * [Maven JAXB plugin|https://java.net/projects/maven-jaxb2-plugin/pages/Home] > * [Apache Falcon|https://falcon.apache.org] > Key features: > * must have: > ** inside an {{oozie-jobs-api}} artifact > ** able to create workflow / coordinator / bundle definitions programmatically > ** synchronizing each and every XSD change on rebuild > ** can write {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and > {{jobs.properties}} artifacts of every XSD version > ** cloneability of workflow etc. {{Object}} s > ** perform cross checks, e.g. that the workflow graph is a DAG > ** only latest XSD versions should be supported as must have > * nice to have: > ** XSD version(s) can be provided. When not provided, latest ones are > considered as valid > ** implement a [*fluent API*|https://en.wikipedia.org/wiki/Fluent_interface] > ** have a Python / Jython REPL to make it easy to experiment > ** create documentation about usage > ** can read {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and > {{jobs.properties}} artifacts of every XSD version > ** can convert between XSD versions > ** support XSD change on the fly (within REPL) > ** support HDFS reads / writes > ** support dry run on an Oozie server to perform checks -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OOZIE-2339) Provide an API for writing jobs based on the XSD schemas
[ https://issues.apache.org/jira/browse/OOZIE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259751#comment-16259751 ] Hadoop QA commented on OOZIE-2339: -- Testing JIRA OOZIE-2339 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:red}-1{color} the patch contains 12 line(s) with tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:red}-1{color} the patch contains 6 line(s) longer than 132 characters .{color:green}+1{color} the patch does adds/modifies 57 testcase(s) {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:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s) {color:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:red}-1{color} patch does not compile .{color:red}-1{color} the patch seems to introduce 1 new javac warning(s) {color:green}+1{color} There are no new bugs found in total. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [client]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [server]. {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} - patch does not compile, cannot run testcases {color:red}-1 DISTRO{color} .{color:red}-1{color} distro tarball fails with the patch {color:red}*-1 Overall result, please check the reported -1(s)*{color} {color:red}. There is at least one warning, please check{color} The full output of the test-patch run is available at . https://builds.apache.org/job/PreCommit-OOZIE-Build/246/ > Provide an API for writing jobs based on the XSD schemas > > > Key: OOZIE-2339 > URL: https://issues.apache.org/jira/browse/OOZIE-2339 > Project: Oozie > Issue Type: New Feature > Components: client >Affects Versions: 4.3.0 >Reporter: Robert Kanter >Assignee: Andras Piros > Fix For: 5.0.0 > > Attachments: OOZIE-2339.001.patch, OOZIE-2339.002.patch, > OOZIE-2339.003.patch > > > Users often complain about the XML they have to write for Oozie jobs. It > would be nice if they could write them in something like Java, but we don't > want to have to maintain a separate Java API for this. I was looking around > and saw that JAXB might be the right thing here. From what I can tell, it > lets you create Java classes from XSD schemas. So, we should be able to > auto-generate a Java API for writing Oozie jobs, without having to really > maintain it. > We should investigate if this is feasible and, if so, implement it. > Some useful looking links: > * [JAXB > overview|https://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding] > * [JAXB description|https://jaxb.java.net/2.2.11/docs/ch03.html] > * [Maven JAXB plugin|https://java.net/projects/maven-jaxb2-plugin/pages/Home] > * [Apache Falcon|https://falcon.apache.org] > Key features: > * must have: > ** inside an {{oozie-jobs-api}} artifact > ** able to create workflow / coordinator / bundle definitions programmatically > ** synchronizing each and every XSD change on rebuild > ** can write {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and > {{jobs.properties}} artifacts of every XSD version > ** cloneability of workflow etc. {{Object}} s > ** perform cross checks, e.g. that the workflow graph is a DAG > ** only latest XSD versions should be supported as
[jira] [Commented] (OOZIE-2339) Provide an API for writing jobs based on the XSD schemas
[ https://issues.apache.org/jira/browse/OOZIE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143639#comment-16143639 ] Hadoop QA commented on OOZIE-2339: -- Testing JIRA OOZIE-2339 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:red}-1{color} the patch contains 5 line(s) longer than 132 characters .{color:green}+1{color} the patch does adds/modifies 53 testcase(s) {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:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s) {color:red}-1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:red}-1{color} the patch seems to introduce 1 new javac warning(s) {color:red}-1{color} There are [85] new bugs found below threshold in total that must be fixed. . {color:red}-1{color} There are [85] new bugs found below threshold in [jobs-api] that must be fixed, listing only the first [5] ones. . You can find the FindBugs diff here (look for the red and orange ones): jobs-api/findbugs-new.html . The top [5] most important FindBugs errors are: . At GraphVisualization.java:[line 96]: File(...) reads a file whose location might be specified by user input . At SimpleEmailExample.java:[line 46]: Dead store to b in org.apache.oozie.jobs.api.examples.SimpleEmailExample.main(String[]) . At SimpleEmailExample.java:[line 52]: Dead store to c in org.apache.oozie.jobs.api.examples.SimpleEmailExample.main(String[]) . At SimpleMapReduceExample.java:[line 59]: Dead store to mrAction3 in org.apache.oozie.jobs.api.examples.SimpleMapReduceExample.main(String[]) . At ACTION.java:[lines 328-329]: org.apache.oozie.jobs.api.generated.action.distcp.ACTION.equals(Object) is unusual . {color:green}+1{color} There are no new bugs found in [client]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [server]. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [tools]. {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:green}+1 TESTS{color} .Tests run: 2416 {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} {color:red}. There is at least one warning, please check{color} The full output of the test-patch run is available at . https://builds.apache.org/job/oozie-trunk-precommit-build/4046/ > Provide an API for writing jobs based on the XSD schemas > > > Key: OOZIE-2339 > URL: https://issues.apache.org/jira/browse/OOZIE-2339 > Project: Oozie > Issue Type: New Feature > Components: client >Affects Versions: 4.3.0 >Reporter: Robert Kanter >Assignee: Andras Piros > Fix For: 5.0.0 > > Attachments: OOZIE-2339.001.patch > > > Users often complain about the XML they have to write for Oozie jobs. It > would be nice if they could write them in something like Java, but we don't > want to have to maintain a separate Java API for this. I was looking around > and saw that JAXB might be the right thing here. From what I can tell, it > lets you create Java classes from XSD schemas. So, we should be able to > auto-generate a Java API for writing Oozie jobs, without having to really >