You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Britt Cyr (JIRA)" <ji...@apache.org> on 2012/06/06 02:22:22 UTC
[jira] [Created] (OOZIE-861) allow for use of multiple
Britt Cyr created OOZIE-861:
-------------------------------
Summary: allow for use of multiple <java-opts>
Key: OOZIE-861
URL: https://issues.apache.org/jira/browse/OOZIE-861
Project: Oozie
Issue Type: Improvement
Reporter: Britt Cyr
Priority: Minor
>From the workflow schema you'll see:
<xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
However, 'arg' is:
<xs:element name="arg" type="xs:string" minOccurs="0"
maxOccurs="unbounded"/>
Notice the 'maxOccurs' difference.
Instead of having:
<java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
It would be easier to have:
<java-opt>-Dparam1=val1</java-opt>
<java-opt>-Dparam2=val2</java-opt>
<java-opt>-Dparam3=val3</java-opt>
...
Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Commented] (OOZIE-861) allow for use of multiple
Posted by "Virag Kothari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403228#comment-13403228 ]
Virag Kothari commented on OOZIE-861:
-------------------------------------
Committed to trunk..thanks Britt
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-861-DOCS.patch, OOZIE-861-v2.patch, OOZIE-861-v3.patch, OOZIE-861-v4.patch, OOZIE-861-v5.patch, OOZIE-861.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Updated] (OOZIE-861) allow for use of multiple
Posted by "Britt Cyr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Britt Cyr updated OOZIE-861:
----------------------------
Attachment: (was: multipleJavaOpts.patch)
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-861.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Updated] (OOZIE-861) allow for use of multiple
Posted by "Britt Cyr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Britt Cyr updated OOZIE-861:
----------------------------
Attachment: OOZIE-861-v4.patch
(java-opts?|java-opt*)
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-861-v2.patch, OOZIE-861-v3.patch, OOZIE-861-v4.patch, OOZIE-861.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Updated] (OOZIE-861) allow for use of multiple
Posted by "Britt Cyr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Britt Cyr updated OOZIE-861:
----------------------------
Attachment: OOZIE-861-v2.patch
Changing ooze-workflow-0.3.xsd here should not break backwards compatibility because I am just allowing multiple java-opts where it wasn't before.
Added a testcase to validate multiple java-opts.
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-861-v2.patch, OOZIE-861.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Updated] (OOZIE-861) allow for use of multiple
Posted by "Britt Cyr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Britt Cyr updated OOZIE-861:
----------------------------
Attachment: OOZIE-861-v3.patch
workflow 0.4 instead of 0.3 for compatibility
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-861-v2.patch, OOZIE-861-v3.patch, OOZIE-861.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Commented] (OOZIE-861) allow for use of multiple
Posted by "Virag Kothari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402028#comment-13402028 ]
Virag Kothari commented on OOZIE-861:
-------------------------------------
Can a testcase be added to verify that java-opt are retrieved in the conf? (can be done in TestJavaActionExe)
Can this be added to java-cookbook? Java cookbook is available at https://svn.apache.org/repos/asf/incubator/oozie/branches/ap-pages/src/site/apt/java-cookbook.apt.vm
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-861-v2.patch, OOZIE-861-v3.patch, OOZIE-861-v4.patch, OOZIE-861.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Resolved] (OOZIE-861) allow for use of multiple
Posted by "Virag Kothari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Virag Kothari resolved OOZIE-861.
---------------------------------
Resolution: Fixed
Fix Version/s: trunk
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-861-DOCS.patch, OOZIE-861-v2.patch, OOZIE-861-v3.patch, OOZIE-861-v4.patch, OOZIE-861-v5.patch, OOZIE-861.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Updated] (OOZIE-861) allow for use of multiple
Posted by "Britt Cyr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Britt Cyr updated OOZIE-861:
----------------------------
Attachment: OOZIE-861.patch
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-861.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Commented] (OOZIE-861) allow for use of multiple
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396187#comment-13396187 ]
Alejandro Abdelnur commented on OOZIE-861:
------------------------------------------
I think we should create new versions of the modified schemas, otherwise jobs would fail in earlier versions of oozie with the same schema version.
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-861.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Commented] (OOZIE-861) allow for use of multiple
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398806#comment-13398806 ]
Alejandro Abdelnur commented on OOZIE-861:
------------------------------------------
Shouldn't we have <java-opts> for multiple values and <java-opt> for a single value in the way that they are excluyent of each other? (java-opts?|java-opt*)
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-861-v2.patch, OOZIE-861-v3.patch, OOZIE-861.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Assigned] (OOZIE-861) allow for use of multiple
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur reassigned OOZIE-861:
----------------------------------------
Assignee: Britt Cyr
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-861.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Commented] (OOZIE-861) allow for use of multiple
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397714#comment-13397714 ]
Alejandro Abdelnur commented on OOZIE-861:
------------------------------------------
@Britt, regardin compat issues, the problem is somebody using Oozie 3.3.0 with the modified schema to develop and then submitting the job in an Oozie 3.2.0. That is why we need to rev up the schema version. Note that OOZIE-12 is also making changes and it is wiring schema 0.4, if you wait till OOZIE-12 is in then you'll just have to modify that one. Make sense?
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-861-v2.patch, OOZIE-861.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Commented] (OOZIE-861) allow for use of multiple
Posted by "Mona Chitnis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396175#comment-13396175 ]
Mona Chitnis commented on OOZIE-861:
------------------------------------
Add a testcase function with a sample workflow having the multiple <java-opt> and getting validated. The testcase in this patch only checks that version 0.3 is accepted.
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-861.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Commented] (OOZIE-861) allow for use of multiple
Posted by "Virag Kothari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403211#comment-13403211 ]
Virag Kothari commented on OOZIE-861:
-------------------------------------
looks good.. +1
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-861-DOCS.patch, OOZIE-861-v2.patch, OOZIE-861-v3.patch, OOZIE-861-v4.patch, OOZIE-861-v5.patch, OOZIE-861.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Updated] (OOZIE-861) allow for use of multiple
Posted by "Britt Cyr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Britt Cyr updated OOZIE-861:
----------------------------
Attachment: multipleJavaOpts.patch
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Priority: Minor
> Attachments: multipleJavaOpts.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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
[jira] [Updated] (OOZIE-861) allow for use of multiple
Posted by "Britt Cyr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Britt Cyr updated OOZIE-861:
----------------------------
Attachment: OOZIE-861-DOCS.patch
OOZIE-861-v5.patch
Added test case to test that it is in the conf.
> allow for use of multiple <java-opts>
> -------------------------------------
>
> Key: OOZIE-861
> URL: https://issues.apache.org/jira/browse/OOZIE-861
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-861-DOCS.patch, OOZIE-861-v2.patch, OOZIE-861-v3.patch, OOZIE-861-v4.patch, OOZIE-861-v5.patch, OOZIE-861.patch
>
>
> From the workflow schema you'll see:
> <xs:element name="java-opts" type="xs:string" minOccurs="0" maxOccurs="1"/>
> However, 'arg' is:
> <xs:element name="arg" type="xs:string" minOccurs="0"
> maxOccurs="unbounded"/>
> Notice the 'maxOccurs' difference.
> Instead of having:
> <java-opts>-Dparam1=val1 -Dparam2=val2 -Dparam3=val3 ...</java-opts>
> It would be easier to have:
> <java-opt>-Dparam1=val1</java-opt>
> <java-opt>-Dparam2=val2</java-opt>
> <java-opt>-Dparam3=val3</java-opt>
> ...
> Just like we can do with <arg>. Hence, the inconsistency.
--
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