[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (95 issues) Subscriber: ooziedaily Key Summary OOZIE-3415 oozie.libpath cannot be used together with oozie.coord.application.path and oozie.bundle.application.path https://issues.apache.org/jira/browse/OOZIE-3415 OOZIE-3409 Oozie Server : Possible memory leak in EL evaluation https://issues.apache.org/jira/browse/OOZIE-3409 OOZIE-3407 Cleanup TestPurgeXCommand https://issues.apache.org/jira/browse/OOZIE-3407 OOZIE-3404 The env variable of SPARK_HOME needs to be set when running pySpark https://issues.apache.org/jira/browse/OOZIE-3404 OOZIE-3401 TestPySpark failure https://issues.apache.org/jira/browse/OOZIE-3401 OOZIE-3375 Can't use empty in coordinator https://issues.apache.org/jira/browse/OOZIE-3375 OOZIE-3367 Using && in EL expressions in oozie bundle.xml files generates parse errors https://issues.apache.org/jira/browse/OOZIE-3367 OOZIE-3366 Update workflow status and subworkflow status on suspend command https://issues.apache.org/jira/browse/OOZIE-3366 OOZIE-3364 Rerunning Oozie bundle jobs starts the coordinators in indeterminate order https://issues.apache.org/jira/browse/OOZIE-3364 OOZIE-3362 When killed, SSH action should kill the spawned processes on target host https://issues.apache.org/jira/browse/OOZIE-3362 OOZIE-3326 Sqoop Action should support tez delegation tokens for hive-import https://issues.apache.org/jira/browse/OOZIE-3326 OOZIE-3320 Oozie ShellAction should support absolute bash file path https://issues.apache.org/jira/browse/OOZIE-3320 OOZIE-3319 Log SSH action callback error output https://issues.apache.org/jira/browse/OOZIE-3319 OOZIE-3301 Update NOTICE file https://issues.apache.org/jira/browse/OOZIE-3301 OOZIE-3274 Remove slf4j https://issues.apache.org/jira/browse/OOZIE-3274 OOZIE-3266 Coord action rerun support RERUN_SKIP_NODES option https://issues.apache.org/jira/browse/OOZIE-3266 OOZIE-3265 properties RERUN_FAIL_NODES and RERUN_SKIP_NODES should be able to appear together https://issues.apache.org/jira/browse/OOZIE-3265 OOZIE-3256 refactor OozieCLI class https://issues.apache.org/jira/browse/OOZIE-3256 OOZIE-3249 [tools] Instrumentation log parser https://issues.apache.org/jira/browse/OOZIE-3249 OOZIE-3199 Let system property restriction configurable https://issues.apache.org/jira/browse/OOZIE-3199 OOZIE-3196 Authorization: restrict world readability by user https://issues.apache.org/jira/browse/OOZIE-3196 OOZIE-3179 Adding a configurable config-default.xml location to a workflow https://issues.apache.org/jira/browse/OOZIE-3179 OOZIE-3170 Oozie Diagnostic Bundle tool fails with NPE due to missing service class https://issues.apache.org/jira/browse/OOZIE-3170 OOZIE-3137 Add support for log4j2 in HiveMain https://issues.apache.org/jira/browse/OOZIE-3137 OOZIE-3135 Configure log4j2 in SqoopMain https://issues.apache.org/jira/browse/OOZIE-3135 OOZIE-3091 Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: org/apache/avro/mapred/AvroWrapper" https://issues.apache.org/jira/browse/OOZIE-3091 OOZIE-3071 Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than Spark 2.2.0 https://issues.apache.org/jira/browse/OOZIE-3071 OOZIE-3063 Sanitizing variables that are part of openjpa.ConnectionProperties https://issues.apache.org/jira/browse/OOZIE-3063 OOZIE-3062 Set HADOOP_CONF_DIR for spark action https://issues.apache.org/jira/browse/OOZIE-3062 OOZIE-2952 Fix Findbugs warnings in oozie-sharelib-oozie https://issues.apache.org/jira/browse/OOZIE-2952 OOZIE-2949 Escape quotes whitespaces in Sqoop field https://issues.apache.org/jira/browse/OOZIE-2949 OOZIE-2927 Append new line character for Hive2 query using query tag https://issues.apache.org/jira/browse/OOZIE-2927 OOZIE-2834 ParameterVerifier logging non-useful warning for workflow definition https://issues.apache.org/jira/browse/OOZIE-2834 OOZIE-2833 when using uber mode the regex pattern used in the extractHeapSizeMB method does not allow heap sizes specified in bytes. https://issues.apache.org/jira/browse/OOZIE-2833 OOZIE-2812 SparkConfigurationService should support loading configurations from multiple Spark versions https://issues.apache.org/jira/browse/OOZIE-2812 OOZIE-2795 Create lib directory or symlink for Oozie CLI during packaging https://issues.apache.org/jira/browse/OOZIE-2795 OOZIE-2784 Include WEEK as a parameter in the Coordinator Expression Language Evaulator https://issues.apache.org/jira/browse/OOZIE-2784 OOZIE-2779 Mask Hive2 action Beeline
[jira] [Commented] (OOZIE-3415) oozie.libpath cannot be used together with oozie.coord.application.path and oozie.bundle.application.path
[
https://issues.apache.org/jira/browse/OOZIE-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737251#comment-16737251
]
Hadoop QA commented on OOZIE-3415:
--
Testing JIRA OOZIE-3415
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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 star imports
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch adds/modifies 1 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} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
.{color:orange}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{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{color} There are no new bugs found in total.
. {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/git].
. {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
[fluent-job/fluent-job-api].
. {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 [webapp].
. {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: 1634
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}*+1 Overall result, good!, no -1s*{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/963/
> oozie.libpath cannot be used together with oozie.coord.application.path and
> oozie.bundle.application.path
> -
>
> Key: OOZIE-3415
> URL: https://issues.apache.org/jira/browse/OOZIE-3415
> Project: Oozie
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-3415-01.patch
>
>
> If {{oozie.libpath}} is specified then
> [V1JobsServlet.checkAndWriteApplicationXMLToHDFS|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/servlet/V1JobsServlet.java#L139-L185]
> will ignore the {{oozie.coord.application.path}} and
> {{oozie.bundle.application.path}} settings. So it's not possible to specify
> {{oozie.libpath}} and {{oozie.coord.application.path}} /
> {{oozie.bundle.application.path}} at the same time in the {{job.properties}}
> file.
> I don't really see the reason for checking the {{oozie.libpath}} directory
> when we search for {{workflow.xml}} we should delete this check. If this
> check is important then we should still check
> {{oozie.coord.application.path}} and {{oozie.bundle.application.path}} if we
> found nothing in {{oozie.libpath}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Failed: OOZIE-3415 PreCommit Build #963
Jira: https://issues.apache.org/jira/browse/OOZIE-3415 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/963/ ### ## LAST 100 LINES OF THE CONSOLE ### [...truncated 1.86 MB...] [TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts [DEBUG] There are no new bugs found in [fluent-job/fluent-job-api]. [TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts [DEBUG] There are no new bugs found in [docs]. [TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts [DEBUG] There are no new bugs found in [server]. [TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts [DEBUG] There are no new bugs found in [core]. [TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts [DEBUG] There are no new bugs found in [examples]. [TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts [DEBUG] There are no new bugs found in [webapp]. [TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts [DEBUG] There are no new bugs found in [tools]. [INFO] There are no new bugs found totally]. [TRACE] FindBugs diffs checked and reports created [TRACE] Summary file size is 2560 bytes [TRACE] Full summary file size is 1471 bytes [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar] removed [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum] removed Running test-patch task BACKWARDS_COMPATIBILITY Running test-patch task TESTS Running test-patch task DISTRO Testing JIRA OOZIE-3415 Cleaning local git workspace +1 PATCH_APPLIES +1 CLEAN +1 RAW_PATCH_ANALYSIS +1 the patch does not introduce any @author tags +1 the patch does not introduce any tabs +1 the patch does not introduce any trailing spaces +1 the patch does not introduce any star imports +1 the patch does not introduce any line longer than 132 +1 the patch adds/modifies 1 testcase(s) +1 RAT +1 the patch does not seem to introduce new RAT warnings +1 JAVADOC +1 Javadoc generation succeeded with the patch +1 the patch does not seem to introduce new Javadoc warning(s) WARNING: the current HEAD has 100 Javadoc warning(s) +1 COMPILE +1 HEAD compiles +1 patch compiles +1 the patch does not seem to introduce new javac warnings +1 There are no new bugs found in total. +1 There are no new bugs found in [client]. +1 There are no new bugs found in [sharelib/hive]. +1 There are no new bugs found in [sharelib/sqoop]. +1 There are no new bugs found in [sharelib/spark]. +1 There are no new bugs found in [sharelib/streaming]. +1 There are no new bugs found in [sharelib/hive2]. +1 There are no new bugs found in [sharelib/oozie]. +1 There are no new bugs found in [sharelib/hcatalog]. +1 There are no new bugs found in [sharelib/git]. +1 There are no new bugs found in [sharelib/pig]. +1 There are no new bugs found in [sharelib/distcp]. +1 There are no new bugs found in [fluent-job/fluent-job-api]. +1 There are no new bugs found in [docs]. +1 There are no new bugs found in [server]. +1 There are no new bugs found in [core]. +1 There are no new bugs found in [examples]. +1 There are no new bugs found in [webapp]. +1 There are no new bugs found in [tools]. +1 BACKWARDS_COMPATIBILITY +1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations +1 the patch does not modify JPA files +1 TESTS Tests run: 1634 +1 DISTRO +1 distro tarball builds with the patch +1 Overall result, good!, no -1s There is at least one warning, please check The full output of the test-patch run is available at https://builds.apache.org/job/PreCommit-OOZIE-Build/963/ Adding comment to JIRA % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0100 32640 0 100 3264 0 4956 --:--:-- --:--:-- --:--:--
[jira] [Commented] (OOZIE-2949) Escape quotes whitespaces in Sqoop field
[
https://issues.apache.org/jira/browse/OOZIE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737200#comment-16737200
]
Andras Salamon commented on OOZIE-2949:
---
Thanks for the code review [~dionusos]
* This class tries to mimic bash, so there is nothing sqoop specific it. It
would be good to put into a separate class.
* Sure thing, I'll create constants.
* Dead code was just a mistake, [~kmarton] already pointed this out, I'll
remove it.
> Escape quotes whitespaces in Sqoop field
> --
>
> Key: OOZIE-2949
> URL: https://issues.apache.org/jira/browse/OOZIE-2949
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Peter Cseh
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-2949-0.patch, OOZIE-2949-01.patch,
> OOZIE-2949-02.patch
>
>
> The current behavior of the Sqoop action is:
> {noformat}
> The Sqoop command can be specified either using the command element or
> multiple arg elements.
> When using the command element, Oozie will split the command on every space
> into multiple arguments.
> When using the arg elements, Oozie will pass each argument value as an
> argument to Sqoop.
> {noformat}
> This prevents the user to simply copy-paste the command worked in the shell
> into the workflow.xml.
> We should split the field by taking quotes into account, similar to
> what OOZIE-2391
> did for the Spark action's field.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-2949) Escape quotes whitespaces in Sqoop field
[
https://issues.apache.org/jira/browse/OOZIE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737179#comment-16737179
]
Denes Bodo commented on OOZIE-2949:
---
Code review:
* Does ShellSplitter need to be a static inner class? Isn't a normal class in
a separate file means cleaner code?
* Can you please extract characters into ShellSplitter constants which are
used in the state machine?
* In TestSqoopActionExecutor.java:242 you commented out Java code. Was that
intentional and can be deleted?
> Escape quotes whitespaces in Sqoop field
> --
>
> Key: OOZIE-2949
> URL: https://issues.apache.org/jira/browse/OOZIE-2949
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Peter Cseh
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-2949-0.patch, OOZIE-2949-01.patch,
> OOZIE-2949-02.patch
>
>
> The current behavior of the Sqoop action is:
> {noformat}
> The Sqoop command can be specified either using the command element or
> multiple arg elements.
> When using the command element, Oozie will split the command on every space
> into multiple arguments.
> When using the arg elements, Oozie will pass each argument value as an
> argument to Sqoop.
> {noformat}
> This prevents the user to simply copy-paste the command worked in the shell
> into the workflow.xml.
> We should split the field by taking quotes into account, similar to
> what OOZIE-2391
> did for the Spark action's field.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3415) oozie.libpath cannot be used together with oozie.coord.application.path and oozie.bundle.application.path
[
https://issues.apache.org/jira/browse/OOZIE-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737173#comment-16737173
]
Hadoop QA commented on OOZIE-3415:
--
PreCommit-OOZIE-Build started
> oozie.libpath cannot be used together with oozie.coord.application.path and
> oozie.bundle.application.path
> -
>
> Key: OOZIE-3415
> URL: https://issues.apache.org/jira/browse/OOZIE-3415
> Project: Oozie
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-3415-01.patch
>
>
> If {{oozie.libpath}} is specified then
> [V1JobsServlet.checkAndWriteApplicationXMLToHDFS|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/servlet/V1JobsServlet.java#L139-L185]
> will ignore the {{oozie.coord.application.path}} and
> {{oozie.bundle.application.path}} settings. So it's not possible to specify
> {{oozie.libpath}} and {{oozie.coord.application.path}} /
> {{oozie.bundle.application.path}} at the same time in the {{job.properties}}
> file.
> I don't really see the reason for checking the {{oozie.libpath}} directory
> when we search for {{workflow.xml}} we should delete this check. If this
> check is important then we should still check
> {{oozie.coord.application.path}} and {{oozie.bundle.application.path}} if we
> found nothing in {{oozie.libpath}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-2949) Escape quotes whitespaces in Sqoop field
[
https://issues.apache.org/jira/browse/OOZIE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737161#comment-16737161
]
Denes Bodo commented on OOZIE-2949:
---
In case of changing default behaviour: can we just put a switch into
oozie-default.xml where we can declare which mode we want to use? I think
current users will be afraid of an upgrade due to many possible changes in
their workflow. However, new users shall be forced to use the new way. Does it
sound crazy?
> Escape quotes whitespaces in Sqoop field
> --
>
> Key: OOZIE-2949
> URL: https://issues.apache.org/jira/browse/OOZIE-2949
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Peter Cseh
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-2949-0.patch, OOZIE-2949-01.patch,
> OOZIE-2949-02.patch
>
>
> The current behavior of the Sqoop action is:
> {noformat}
> The Sqoop command can be specified either using the command element or
> multiple arg elements.
> When using the command element, Oozie will split the command on every space
> into multiple arguments.
> When using the arg elements, Oozie will pass each argument value as an
> argument to Sqoop.
> {noformat}
> This prevents the user to simply copy-paste the command worked in the shell
> into the workflow.xml.
> We should split the field by taking quotes into account, similar to
> what OOZIE-2391
> did for the Spark action's field.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-2949) Escape quotes whitespaces in Sqoop field
[
https://issues.apache.org/jira/browse/OOZIE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737146#comment-16737146
]
Andras Salamon commented on OOZIE-2949:
---
Thanks [~gezapeti] for checking the patch. I'll address your comments in my
next patch.
Yes, it changes the default behaviour which is not too good. I think it might
cause problems if someone really wanted to use the {{command}} options. For
instance this is a sample from Sqoop documentation (escaped by backspace
enclosed by double quote):
{noformat}
sqoop import --fields-terminated-by , --escaped-by \\ --enclosed-by '\"' ...
{noformat}
In the old verson if you really wanted to use a single command you could
specify as the following:
{noformat}
sqoop import --fields-terminated-by , --escaped-by \ --enclosed-by "
{noformat}
This will no longer work in the new version.
> Escape quotes whitespaces in Sqoop field
> --
>
> Key: OOZIE-2949
> URL: https://issues.apache.org/jira/browse/OOZIE-2949
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Peter Cseh
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-2949-0.patch, OOZIE-2949-01.patch,
> OOZIE-2949-02.patch
>
>
> The current behavior of the Sqoop action is:
> {noformat}
> The Sqoop command can be specified either using the command element or
> multiple arg elements.
> When using the command element, Oozie will split the command on every space
> into multiple arguments.
> When using the arg elements, Oozie will pass each argument value as an
> argument to Sqoop.
> {noformat}
> This prevents the user to simply copy-paste the command worked in the shell
> into the workflow.xml.
> We should split the field by taking quotes into account, similar to
> what OOZIE-2391
> did for the Spark action's field.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-2949) Escape quotes whitespaces in Sqoop field
[
https://issues.apache.org/jira/browse/OOZIE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737106#comment-16737106
]
Peter Cseh commented on OOZIE-2949:
---
Thanks for the patch [~asalamon74]!
I have a few review comments:
# please use org.junit instead of junit.framework when importing assertEquals
# don't forget to update the [Sqoop action
documentation|https://github.com/apache/oozie/blob/master/docs/src/site/markdown/DG_SqoopActionExtension.md]
with the new behavior
I'm a bit worried about changing default behavior, but I can't think of a
scenario when this would break things. Can you?
> Escape quotes whitespaces in Sqoop field
> --
>
> Key: OOZIE-2949
> URL: https://issues.apache.org/jira/browse/OOZIE-2949
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Peter Cseh
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-2949-0.patch, OOZIE-2949-01.patch,
> OOZIE-2949-02.patch
>
>
> The current behavior of the Sqoop action is:
> {noformat}
> The Sqoop command can be specified either using the command element or
> multiple arg elements.
> When using the command element, Oozie will split the command on every space
> into multiple arguments.
> When using the arg elements, Oozie will pass each argument value as an
> argument to Sqoop.
> {noformat}
> This prevents the user to simply copy-paste the command worked in the shell
> into the workflow.xml.
> We should split the field by taking quotes into account, similar to
> what OOZIE-2391
> did for the Spark action's field.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3415) oozie.libpath cannot be used together with oozie.coord.application.path and oozie.bundle.application.path
[
https://issues.apache.org/jira/browse/OOZIE-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736996#comment-16736996
]
Andras Salamon commented on OOZIE-3415:
---
It seems to me [BaseJobsServlet. ensureJobApplicationPath
|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/servlet/BaseJobsServlet.java#L122]
also check the value of {{oozie.libpath}}.
> oozie.libpath cannot be used together with oozie.coord.application.path and
> oozie.bundle.application.path
> -
>
> Key: OOZIE-3415
> URL: https://issues.apache.org/jira/browse/OOZIE-3415
> Project: Oozie
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.2.0
>
>
> If {{oozie.libpath}} is specified then
> [V1JobsServlet.checkAndWriteApplicationXMLToHDFS|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/servlet/V1JobsServlet.java#L139-L185]
> will ignore the {{oozie.coord.application.path}} and
> {{oozie.bundle.application.path}} settings. So it's not possible to specify
> {{oozie.libpath}} and {{oozie.coord.application.path}} /
> {{oozie.bundle.application.path}} at the same time in the {{job.properties}}
> file.
> I don't really see the reason for checking the {{oozie.libpath}} directory
> when we search for {{workflow.xml}} we should delete this check. If this
> check is important then we should still check
> {{oozie.coord.application.path}} and {{oozie.bundle.application.path}} if we
> found nothing in {{oozie.libpath}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OOZIE-3415) oozie.libpath cannot be used together with oozie.coord.application.path and oozie.bundle.application.path
Andras Salamon created OOZIE-3415:
-
Summary: oozie.libpath cannot be used together with
oozie.coord.application.path and oozie.bundle.application.path
Key: OOZIE-3415
URL: https://issues.apache.org/jira/browse/OOZIE-3415
Project: Oozie
Issue Type: Bug
Affects Versions: trunk
Reporter: Andras Salamon
Assignee: Andras Salamon
Fix For: 5.2.0
If {{oozie.libpath}} is specified then
[V1JobsServlet.checkAndWriteApplicationXMLToHDFS|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/servlet/V1JobsServlet.java#L139-L185]
will ignore the {{oozie.coord.application.path}} and
{{oozie.bundle.application.path}} settings. So it's not possible to specify
{{oozie.libpath}} and {{oozie.coord.application.path}} /
{{oozie.bundle.application.path}} at the same time in the {{job.properties}}
file.
I don't really see the reason for checking the {{oozie.libpath}} directory when
we search for {{workflow.xml}} we should delete this check. If this check is
important then we should still check {{oozie.coord.application.path}} and
{{oozie.bundle.application.path}} if we found nothing in {{oozie.libpath}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
