[jira] [Updated] (OOZIE-2678) Oozie job -kill doesn't work with tez jobs
[ https://issues.apache.org/jira/browse/OOZIE-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna updated OOZIE-2678: -- Attachment: OOZIE-2678-01.patch Added the tez application tags for Shell and Java action as well. Previously, Shell action did not have even yarn tags added, included them as well. > Oozie job -kill doesn't work with tez jobs > -- > > Key: OOZIE-2678 > URL: https://issues.apache.org/jira/browse/OOZIE-2678 > Project: Oozie > Issue Type: Bug >Reporter: Rohini Palaniswamy >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2678-00.patch, OOZIE-2678-01.patch > > > OOZIE-2243 added support for mapreduce jobs. We need to do that for Tez jobs > as well. TEZ-909 added tez.application.tags similar to mapreduce.job.tags, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2678) Oozie job -kill doesn't work with tez jobs
[ https://issues.apache.org/jira/browse/OOZIE-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15507528#comment-15507528 ] Abhishek Bafna commented on OOZIE-2678: --- [~rohini] Attached a patch. Please review it. Thanks. > Oozie job -kill doesn't work with tez jobs > -- > > Key: OOZIE-2678 > URL: https://issues.apache.org/jira/browse/OOZIE-2678 > Project: Oozie > Issue Type: Bug >Reporter: Rohini Palaniswamy >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2678-00.patch > > > OOZIE-2243 added support for mapreduce jobs. We need to do that for Tez jobs > as well. TEZ-909 added tez.application.tags similar to mapreduce.job.tags, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15507526#comment-15507526 ] Abhishek Bafna commented on OOZIE-2613: --- Ping: [~rohini] and [~rkanter] > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2582) Populating external child Ids for action failures
[ https://issues.apache.org/jira/browse/OOZIE-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15507523#comment-15507523 ] Abhishek Bafna commented on OOZIE-2582: --- Thanks for the feedback [~rohini]. Attached the updated patch here and RB as well. > Populating external child Ids for action failures > - > > Key: OOZIE-2582 > URL: https://issues.apache.org/jira/browse/OOZIE-2582 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2582-00.patch, OOZIE-2582-01.patch, > OOZIE-2582-02.patch, OOZIE-2582-03.patch, OOZIE-2582-04.patch, > OOZIE-2582-05.patch, OOZIE-2582-06.patch > > > Currently Oozie external child ids are populated into workflow bean, when the > job/action completes successfully. It should populate external child ids in > case of job failures as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2678) Oozie job -kill doesn't work with tez jobs
[ https://issues.apache.org/jira/browse/OOZIE-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506932#comment-15506932 ] Abhishek Bafna commented on OOZIE-2678: --- Testcases passes locally. > Oozie job -kill doesn't work with tez jobs > -- > > Key: OOZIE-2678 > URL: https://issues.apache.org/jira/browse/OOZIE-2678 > Project: Oozie > Issue Type: Bug >Reporter: Rohini Palaniswamy >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2678-00.patch > > > OOZIE-2243 added support for mapreduce jobs. We need to do that for Tez jobs > as well. TEZ-909 added tez.application.tags similar to mapreduce.job.tags, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2678) Oozie job -kill doesn't work with tez jobs
[
https://issues.apache.org/jira/browse/OOZIE-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506920#comment-15506920
]
Abhishek Bafna commented on OOZIE-2678:
---
Jenkins failed to add comment into Jira.
{noformat}
The full output of the test-patch run is available at
https://builds.apache.org/job/oozie-trunk-precommit-build/3303/
mv: cannot stat 'jira-cli-2.6.0': No such file or directory
chmod: cannot access
'/home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/test-patch/tools/jira-cli/jira.sh':
No such file or directory
Adding comment to JIRA
bin/test-patch: line 124:
/home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/test-patch/tools/jira-cli/jira.sh:
No such file or directory
{noformat}
Copy-Pasting Jenkins Report:
{noformat}
Testing JIRA OOZIE-2678
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 line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+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: 1807
Tests failed: 1
Tests errors: 0
The patch failed the following testcases:
testSingleRecord(org.apache.oozie.servlet.TestBulkMonitorWebServiceAPI)
+1 DISTRO
+1 distro tarball builds with the patch
-1 Overall result, please check the reported -1(s)
{noformat}
> Oozie job -kill doesn't work with tez jobs
> --
>
> Key: OOZIE-2678
> URL: https://issues.apache.org/jira/browse/OOZIE-2678
> Project: Oozie
> Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2678-00.patch
>
>
> OOZIE-2243 added support for mapreduce jobs. We need to do that for Tez jobs
> as well. TEZ-909 added tez.application.tags similar to mapreduce.job.tags,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2582) Populating external child Ids for action failures
[ https://issues.apache.org/jira/browse/OOZIE-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506915#comment-15506915 ] Abhishek Bafna commented on OOZIE-2582: --- Testcase passes locally. > Populating external child Ids for action failures > - > > Key: OOZIE-2582 > URL: https://issues.apache.org/jira/browse/OOZIE-2582 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2582-00.patch, OOZIE-2582-01.patch, > OOZIE-2582-02.patch, OOZIE-2582-03.patch, OOZIE-2582-04.patch, > OOZIE-2582-05.patch, OOZIE-2582-06.patch > > > Currently Oozie external child ids are populated into workflow bean, when the > job/action completes successfully. It should populate external child ids in > case of job failures as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-2679) Decrease HttpClient library versions
[ https://issues.apache.org/jira/browse/OOZIE-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna updated OOZIE-2679: -- Attachment: OOZIE-2679.patch > Decrease HttpClient library versions > > > Key: OOZIE-2679 > URL: https://issues.apache.org/jira/browse/OOZIE-2679 > Project: Oozie > Issue Type: Bug >Reporter: Peter Cseh >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2679.patch > > > Version 4.4 of HttpClient has issued with Hadoop: HADOOP-11859 > It will be fixed in Hadoop 2.8.0, until we use that we should use 4.3 of > HttpClient. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile
[
https://issues.apache.org/jira/browse/OOZIE-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506626#comment-15506626
]
Abhishek Bafna commented on OOZIE-2676:
---
Thanks [~gezapeti]. Will be uploading the patch with:
{code}
4.3.3
4.3.6
{code}
I have tested for these tests manually.
mvn clean test -Dtest=org.apache.oozie.client.* -Phadoop-2
mvn clean test -Dtest=org.apache.oozie.servlet.* -Phadoop-2
mvn clean test -Dtest=org.apache.oozie.action.hadoop.TestJavaActionExecutor
-Phadoop-2 -pl core
mvn clean test -Dtest=org.apache.oozie.client.*
mvn clean test -Dtest=org.apache.oozie.servlet.* -pl core
mvn clean test -Dtest=org.apache.oozie.action.hadoop.TestJavaActionExecutor -pl
core
> Make hadoop-2 as the default profile
>
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the
> project. It would be good to make the {{hadoop-2}} profile as default for
> building Oozie and running the unit testcase.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2679) Decrease HttpClient library versions
[ https://issues.apache.org/jira/browse/OOZIE-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna updated OOZIE-2679: -- Priority: Blocker (was: Major) > Decrease HttpClient library versions > > > Key: OOZIE-2679 > URL: https://issues.apache.org/jira/browse/OOZIE-2679 > Project: Oozie > Issue Type: Bug >Reporter: Peter Cseh >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > > Version 4.4 of HttpClient causes HADOOP- -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OOZIE-2679) Decrease HttpClient library versions
[ https://issues.apache.org/jira/browse/OOZIE-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna reassigned OOZIE-2679: - Assignee: Abhishek Bafna > Decrease HttpClient library versions > > > Key: OOZIE-2679 > URL: https://issues.apache.org/jira/browse/OOZIE-2679 > Project: Oozie > Issue Type: Bug >Reporter: Peter Cseh >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > > Version 4.4 of HttpClient causes HADOOP- -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile
[
https://issues.apache.org/jira/browse/OOZIE-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506578#comment-15506578
]
Abhishek Bafna commented on OOZIE-2676:
---
I think we can go with
{code}
4.3.3
4.3.6
{code}
> Make hadoop-2 as the default profile
>
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the
> project. It would be good to make the {{hadoop-2}} profile as default for
> building Oozie and running the unit testcase.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile
[
https://issues.apache.org/jira/browse/OOZIE-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506559#comment-15506559
]
Abhishek Bafna commented on OOZIE-2676:
---
I am running the testcases with {{4.3.}} version. I was able to execute the
{{TestWorkflowXClient}} for both the profiles. I will update the same soon.
Thanks [~gezapeti].
{code}
4.3
4.3
{code}
> Make hadoop-2 as the default profile
>
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the
> project. It would be good to make the {{hadoop-2}} profile as default for
> building Oozie and running the unit testcase.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile
[
https://issues.apache.org/jira/browse/OOZIE-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506480#comment-15506480
]
Abhishek Bafna commented on OOZIE-2676:
---
[~gezapeti] Are you using the attached patch or made some more changes? I
wanted to try it out. If there is any more information, please do provide.
Thanks.
> Make hadoop-2 as the default profile
>
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the
> project. It would be good to make the {{hadoop-2}} profile as default for
> building Oozie and running the unit testcase.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2582) Populating external child Ids for action failures
[ https://issues.apache.org/jira/browse/OOZIE-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna updated OOZIE-2582: -- Attachment: OOZIE-2582-06.patch > Populating external child Ids for action failures > - > > Key: OOZIE-2582 > URL: https://issues.apache.org/jira/browse/OOZIE-2582 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2582-00.patch, OOZIE-2582-01.patch, > OOZIE-2582-02.patch, OOZIE-2582-03.patch, OOZIE-2582-04.patch, > OOZIE-2582-05.patch, OOZIE-2582-06.patch > > > Currently Oozie external child ids are populated into workflow bean, when the > job/action completes successfully. It should populate external child ids in > case of job failures as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-2678) Oozie job -kill doesn't work with tez jobs
[ https://issues.apache.org/jira/browse/OOZIE-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna updated OOZIE-2678: -- Attachment: OOZIE-2678-00.patch > Oozie job -kill doesn't work with tez jobs > -- > > Key: OOZIE-2678 > URL: https://issues.apache.org/jira/browse/OOZIE-2678 > Project: Oozie > Issue Type: Bug >Reporter: Rohini Palaniswamy >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2678-00.patch > > > OOZIE-2243 added support for mapreduce jobs. We need to do that for Tez jobs > as well. TEZ-909 added tez.application.tags similar to mapreduce.job.tags, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OOZIE-2678) Oozie job -kill doesn't work with tez jobs
[ https://issues.apache.org/jira/browse/OOZIE-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna reassigned OOZIE-2678: - Assignee: Abhishek Bafna > Oozie job -kill doesn't work with tez jobs > -- > > Key: OOZIE-2678 > URL: https://issues.apache.org/jira/browse/OOZIE-2678 > Project: Oozie > Issue Type: Bug >Reporter: Rohini Palaniswamy >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > > OOZIE-2243 added support for mapreduce jobs. We need to do that for Tez jobs > as well. TEZ-909 added tez.application.tags similar to mapreduce.job.tags, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2491) oozie acl cannot specify group,it does`t work
[ https://issues.apache.org/jira/browse/OOZIE-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504068#comment-15504068 ] Abhishek Bafna commented on OOZIE-2491: --- [~rohini] Thanks for review and committing it. I will take care of your suggestion. Thanks. > oozie acl cannot specify group,it does`t work > - > > Key: OOZIE-2491 > URL: https://issues.apache.org/jira/browse/OOZIE-2491 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 4.1.0 >Reporter: Lingang Deng >Assignee: Abhishek Bafna >Priority: Minor > Fix For: 4.3.0 > > Attachments: OOZIE-2491-01.patch > > > when I do oozie acl, specify oozie.job.acl=aclGroup, it doesn`t work when > modify the job with user which belong to the aclGroup.By debugging source > code, " groupsService.getGroups(user).equals(aclItem) ", a List object > compare to a String object ,it`s false forever. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile
[
https://issues.apache.org/jira/browse/OOZIE-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504061#comment-15504061
]
Abhishek Bafna commented on OOZIE-2676:
---
I think, it would be better to change the default profile, so when the user
compile and build the Oozie, It will be done using Hadoop 2, without passing
any specific parameter. Also many of us pointed, most of the consumers use
Hadoop 2.
> Make hadoop-2 as the default profile
>
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the
> project. It would be good to make the {{hadoop-2}} profile as default for
> building Oozie and running the unit testcase.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OOZIE-2677) Multiple jline version jars in spark sharelib
Abhishek Bafna created OOZIE-2677:
-
Summary: Multiple jline version jars in spark sharelib
Key: OOZIE-2677
URL: https://issues.apache.org/jira/browse/OOZIE-2677
Project: Oozie
Issue Type: Bug
Components: core
Reporter: Abhishek Bafna
Oozie Spark sharelib is packing multiple version of the {{jilne}} jar. I have
not produce/re-produced any specific issue because of the different versions of
the {{jline}}, but in general, It is not a good thing.
{noformat}
ab:share abafna$ pwd
/Users/abafna/workspace/apache/oozie/distro/target/oozie-4.3.0-SNAPSHOT/share
ab:share abafna$ find . -name jline*
./lib/hive/jline-0.9.94.jar
./lib/hive2/jline-0.9.94.jar
./lib/pig/jline-0.9.94.jar
./lib/spark/jline-0.9.94.jar
./lib/spark/jline-2.10.5.jar
{noformat}
Here is the dependency tree from spark module for {{jline}}. Full output is
attached in the bug.
{noformat}
[INFO] +- org.apache.spark:spark-repl_2.10:jar:1.6.1:compile
[INFO] | +- org.scala-lang:scala-compiler:jar:2.10.5:compile
[INFO] | +- org.scala-lang:scala-reflect:jar:2.10.5:compile
[INFO] | \- org.scala-lang:jline:jar:2.10.5:compile
[INFO] | \- org.fusesource.jansi:jansi:jar:1.4:compile
[INFO] +- org.apache.spark:spark-hive_2.10:jar:1.6.1:compile
[INFO] | +- com.twitter:parquet-hadoop-bundle:jar:1.6.0:compile
[INFO] | +- org.spark-project.hive:hive-cli:jar:1.2.1.spark:compile
[INFO] | | +- commons-cli:commons-cli:jar:1.2:compile
[INFO] | | \- jline:jline:jar:0.9.94:compile
[INFO] | +- org.apache.avro:avro:jar:1.7.7:compile
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2677) Multiple jline version jars in spark sharelib
[
https://issues.apache.org/jira/browse/OOZIE-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-2677:
--
Attachment: tree_spark.txt
> Multiple jline version jars in spark sharelib
> -
>
> Key: OOZIE-2677
> URL: https://issues.apache.org/jira/browse/OOZIE-2677
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
> Attachments: tree_spark.txt
>
>
> Oozie Spark sharelib is packing multiple version of the {{jilne}} jar. I have
> not produce/re-produced any specific issue because of the different versions
> of the {{jline}}, but in general, It is not a good thing.
> {noformat}
> ab:share abafna$ pwd
> /Users/abafna/workspace/apache/oozie/distro/target/oozie-4.3.0-SNAPSHOT/share
> ab:share abafna$ find . -name jline*
> ./lib/hive/jline-0.9.94.jar
> ./lib/hive2/jline-0.9.94.jar
> ./lib/pig/jline-0.9.94.jar
> ./lib/spark/jline-0.9.94.jar
> ./lib/spark/jline-2.10.5.jar
> {noformat}
> Here is the dependency tree from spark module for {{jline}}. Full output is
> attached in the bug.
> {noformat}
> [INFO] +- org.apache.spark:spark-repl_2.10:jar:1.6.1:compile
> [INFO] | +- org.scala-lang:scala-compiler:jar:2.10.5:compile
> [INFO] | +- org.scala-lang:scala-reflect:jar:2.10.5:compile
> [INFO] | \- org.scala-lang:jline:jar:2.10.5:compile
> [INFO] | \- org.fusesource.jansi:jansi:jar:1.4:compile
> [INFO] +- org.apache.spark:spark-hive_2.10:jar:1.6.1:compile
> [INFO] | +- com.twitter:parquet-hadoop-bundle:jar:1.6.0:compile
> [INFO] | +- org.spark-project.hive:hive-cli:jar:1.2.1.spark:compile
> [INFO] | | +- commons-cli:commons-cli:jar:1.2:compile
> [INFO] | | \- jline:jline:jar:0.9.94:compile
> [INFO] | +- org.apache.avro:avro:jar:1.7.7:compile
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OOZIE-2676) Make hadoop-2 as the default profile
Abhishek Bafna created OOZIE-2676:
-
Summary: Make hadoop-2 as the default profile
Key: OOZIE-2676
URL: https://issues.apache.org/jira/browse/OOZIE-2676
Project: Oozie
Issue Type: Bug
Components: core
Reporter: Abhishek Bafna
Currently, {{hadoop-1}} is the default profile in Oozie for build the project.
It would be good to make the {{hadoop-2}} profile as default for building Oozie
and running the unit testcase.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2457) Oozie log parsing regex consume more than 90% cpu
[
https://issues.apache.org/jira/browse/OOZIE-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-2457:
--
Priority: Blocker (was: Minor)
> Oozie log parsing regex consume more than 90% cpu
> -
>
> Key: OOZIE-2457
> URL: https://issues.apache.org/jira/browse/OOZIE-2457
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: OOZIE-2457-1.patch, OOZIE-2457-2.patch,
> OOZIE-2457-3.patch
>
>
> http-0.0.0.0-4080-26 TID=62215 STATE=RUNNABLE CPU_TIME=1992 (92.59%)
> USER_TIME=1990 (92.46%) Allocted: 269156584
> java.util.regex.Pattern$Curly.match0(Pattern.java:4170)
> java.util.regex.Pattern$Curly.match(Pattern.java:4132)
> java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)
> java.util.regex.Matcher.match(Matcher.java:1221)
> java.util.regex.Matcher.matches(Matcher.java:559)
> org.apache.oozie.util.XLogFilter.matches(XLogFilter.java:136)
>
> org.apache.oozie.util.TimestampedMessageParser.parseNextLine(TimestampedMessageParser.java:145)
>
> org.apache.oozie.util.TimestampedMessageParser.increment(TimestampedMessageParser.java:92)
> Regex
> {code}
> (.* USER\[[^\]]*\] GROUP\[[^\]]*\] TOKEN\[[^\]]*\] APP\[[^\]]*\]
> JOB\[000-150625114739728-oozie-puru-W\] ACTION\[[^\]]*\] .*)
> {code}
> For single line parsing we use two regex.
> 1.
> {code}
> public ArrayList splitLogMessage(String logLine) {
> Matcher splitter = SPLITTER_PATTERN.matcher(logLine);
> if (splitter.matches()) {
> ArrayList logParts = new ArrayList();
> logParts.add(splitter.group(1));// timestamp
> logParts.add(splitter.group(2));// log level
> logParts.add(splitter.group(3));// Log Message
> return logParts;
> }
> else {
> return null;
> }
> }
> {code}
> 2.
> {code}
> public boolean matches(ArrayList logParts) {
> if (getStartDate() != null) {
> if (logParts.get(0).substring(0,
> 19).compareTo(getFormattedStartDate()) < 0) {
> return false;
> }
> }
> String logLevel = logParts.get(1);
> String logMessage = logParts.get(2);
> if (this.logLevels == null ||
> this.logLevels.containsKey(logLevel.toUpperCase())) {
> Matcher logMatcher = filterPattern.matcher(logMessage);
> return logMatcher.matches();
> }
> else {
> return false;
> }
> }
> {code}
> Also there is repetitive parsing for same log message in
> {code}
> private String parseTimestamp(String line) {
> String timestamp = null;
> ArrayList logParts = filter.splitLogMessage(line);
> if (logParts != null) {
> timestamp = logParts.get(0);
> }
> return timestamp;
> }
> {code}
> where the {{line}} has already parsed using regex and we already know the
> {{logParts}} if any.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2501) ZK reentrant lock doesn't work for few cases
[
https://issues.apache.org/jira/browse/OOZIE-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-2501:
--
Priority: Blocker (was: Major)
> ZK reentrant lock doesn't work for few cases
>
>
> Key: OOZIE-2501
> URL: https://issues.apache.org/jira/browse/OOZIE-2501
> Project: Oozie
> Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2501-V2.patch, OOZIE-2501-V4.patch
>
>
> We will have an issue when oozie trying to acquire a lock and at the same
> time, some other thread is releasing the same lock .
> acquireLock will wait for 5 sec to acquire the lock. It will bypass the
> synchronized block and get lockEntry from the hashmap.
> While it waiting for 5 sec to acquire the lock, other thread releases the
> lock and may execute the release code which will remove lockEntry from the
> map.
> If some other command from same thread tries to acquire the lock, it will
> create a new InterProcessReadWriteLock object and use that for acquiring the
> lock.
> Logic for lock acquiring.
> {code}
> public LockToken getWriteLock(String resource, long wait) throws
> InterruptedException {
> InterProcessReadWriteLock lockEntry;
> synchronized (zkLocks) {
> if (zkLocks.containsKey(resource)) {
> lockEntry = zkLocks.get(resource);
> }
> else {
> lockEntry = new InterProcessReadWriteLock(zk.getClient(),
> LOCKS_NODE + "/" + resource);
> zkLocks.put(resource, lockEntry);
> }
> }
> InterProcessMutex writeLock = lockEntry.writeLock();
> return acquireLock(wait, writeLock, resource);
> }
> {code}
> Logic for lock releasing
> {code}
> public void release() {
> try {
> lock.release();
> if (zkLocks.get(resource) == null) {
> return;
> }
> if (!isLockHeld()) {
> synchronized (zkLocks) {
> if (zkLocks.get(resource) != null) {
> if (!isLockHeld()) {
> zkLocks.remove(resource);
> }
> }
> }
> }
> }
> catch (Exception ex) {
> LOG.warn("Could not release lock: " + ex.getMessage(), ex);
> }
> }
> {code}
> Curator code to acquire lock.
> {code}
> private boolean internalLock(long time, TimeUnit unit) throws Exception
> {
> /*
>Note on concurrency: a given lockData instance
>can be only acted on by a single thread so locking isn't necessary
> */
> Thread currentThread = Thread.currentThread();
> LockDatalockData = threadData.get(currentThread);
> if ( lockData != null )
> {
> // re-entering
> lockData.lockCount.incrementAndGet();
> return true;
> }
> String lockPath = internals.attemptLock(time, unit,
> getLockNodeBytes());
> if ( lockPath != null )
> {
> LockDatanewLockData = new LockData(currentThread,
> lockPath);
> threadData.put(currentThread, newLockData);
> return true;
> }
> return false;
> }
> {code}
> The approach we have followed is to use map with weakvalue. Once the lock is
> unreachable. GC will remove it from the map. We don't have to explicitly
> remove it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2231) Upgrade curator to latest version 2.11.0
[ https://issues.apache.org/jira/browse/OOZIE-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna updated OOZIE-2231: -- Priority: Blocker (was: Major) > Upgrade curator to latest version 2.11.0 > > > Key: OOZIE-2231 > URL: https://issues.apache.org/jira/browse/OOZIE-2231 > Project: Oozie > Issue Type: Bug > Components: HA >Reporter: Purshotam Shah >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2231-00.patch, OOZIE-2231-01.patch, > OOZIE-2231-02.patch, OOZIE-2231-02.patch, OOZIE-2231-03.patch > > > It have some fix related to InterProcessReadWriteLock, ChildReaper, > LeaderSelector which we use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-1793) Improve find bugs reporting for Oozie
[
https://issues.apache.org/jira/browse/OOZIE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-1793:
--
Priority: Blocker (was: Major)
> Improve find bugs reporting for Oozie
> -
>
> Key: OOZIE-1793
> URL: https://issues.apache.org/jira/browse/OOZIE-1793
> Project: Oozie
> Issue Type: Sub-task
> Components: build
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-1793-01.patch, OOZIE-1793.patch, OOZIE-1793.patch
>
>
> I couldn't figure out how to run findbugs against Oozie. And even if it does
> work, it looks like it's just going to create an XML file.
> Based on some minor refactoring to this
> [tutorial|http://www.petrikainulainen.net/programming/maven/findbugs-maven-plugin-tutorial/]
> and this [stack overflow
> message|http://stackoverflow.com/questions/7035112/any-easy-way-to-generate-a-findbug-html-report-from-maven-without-sitesite/10365954#10365954],
> I was able to improve our findbugs reporting. Now, when you run {{mvn
> verify}} (which we use to generate a checkstyle report), it will also run
> findbugs and transform the resulting XML files into html files that are human
> readable.
> The hard part here will be actually going through the reports and fixing
> these bugs; but that's for other JIRAs :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-1978) Forkjoin validation code is ridiculously slow in some cases
[
https://issues.apache.org/jira/browse/OOZIE-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-1978:
--
Priority: Blocker (was: Major)
> Forkjoin validation code is ridiculously slow in some cases
> ---
>
> Key: OOZIE-1978
> URL: https://issues.apache.org/jira/browse/OOZIE-1978
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: trunk, 4.0.1
>Reporter: Robert Kanter
>Assignee: Peter Bacsko
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-1978-001.patch, OOZIE-1978-002.patch,
> OOZIE-1978-002.patch, OOZIE-1978-003.patch, OOZIE-1978-004.patch,
> OOZIE-1978-005.patch, OOZIE-1978-006.patch, OOZIE-1978_wip.001.patch,
> workflow.xml
>
>
> We've had a few users who have run into problems where submitting a workflow
> appears to hang (in the case of a subworkflow, it's similar but stuck in
> PREP). It turns out that if you wait long enough, it will actually go
> through and the workflow will run normally. The problem is that the forkjoin
> validation code is taking a really long time.
> The attached example has a series of 20 forks where each fork has 6 actions
> (it's based on an actual workflow, but all of the names were changed and the
> actions were all replaced by simple shell actions). One of our support guys
> said it took 1-2 hours , but on my computer it was taking {color:red}*15+
> hours*{color} (I had to cancel it)
> While this example doesn't have any nested forks, those can also take a long
> time too.
> It's easy to verify that it's the forkjoin validation code that's taking so
> long by looking at a jstack of the Oozie server and seeing deep recursive
> calls to
> {{org.apache.oozie.workflow.lite.LiteWorkflowAppParser.validateForkJoin}}. I
> also noticed a lot of sitting around in calls LinkedList.contains.
> I think we have 3 options:
> # See if we can make the existing code faster somehow. Perhaps there's a way
> to parallelize it? Maybe there's some redundant checking that we can
> identify and skip? Change some data structures? etc
> # See if we can write a new way to do this validation. I had originally
> completely rewritten this code a while ago, and we've since made a few fixes
> to catch edge cases and things. Perhaps it needs another rewrite?
> # Try to identify when it's taking a long time and at least let the user know
> what's happening or something. Right now, it just appears that the Oozie CLI
> has hung and the job doesn't show up in the Oozie server. Most users aren't
> going to wait more than a minute or two.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna updated OOZIE-2613: -- Priority: Blocker (was: Major) > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-2675) Drop support for hadoop 0.23
[ https://issues.apache.org/jira/browse/OOZIE-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna updated OOZIE-2675: -- Priority: Blocker (was: Major) > Drop support for hadoop 0.23 > > > Key: OOZIE-2675 > URL: https://issues.apache.org/jira/browse/OOZIE-2675 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2675-00.patch, OOZIE-2675-01.patch > > > Drop support for Hadoop 0.23. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (OOZIE-2675) Drop support for hadoop 0.23
[
https://issues.apache.org/jira/browse/OOZIE-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-2675:
--
Comment: was deleted
(was: [~asasvari] I am able to execute the testcase with {{hadoop-2}} profile.
Thanks.)
> Drop support for hadoop 0.23
>
>
> Key: OOZIE-2675
> URL: https://issues.apache.org/jira/browse/OOZIE-2675
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2675-00.patch, OOZIE-2675-01.patch
>
>
> Drop support for Hadoop 0.23.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2675) Drop support for hadoop 0.23
[
https://issues.apache.org/jira/browse/OOZIE-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503488#comment-15503488
]
Abhishek Bafna commented on OOZIE-2675:
---
[~asasvari] I am able to execute the testcase with {{hadoop-2}} profile. Thanks.
> Drop support for hadoop 0.23
>
>
> Key: OOZIE-2675
> URL: https://issues.apache.org/jira/browse/OOZIE-2675
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2675-00.patch, OOZIE-2675-01.patch
>
>
> Drop support for Hadoop 0.23.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2675) Drop support for hadoop 0.23
[
https://issues.apache.org/jira/browse/OOZIE-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503487#comment-15503487
]
Abhishek Bafna commented on OOZIE-2675:
---
[~asasvari] I am able to execute the testcase with {{hadoop-2}} profile. Thanks.
> Drop support for hadoop 0.23
>
>
> Key: OOZIE-2675
> URL: https://issues.apache.org/jira/browse/OOZIE-2675
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2675-00.patch, OOZIE-2675-01.patch
>
>
> Drop support for Hadoop 0.23.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2675) Drop support for hadoop 0.23
[ https://issues.apache.org/jira/browse/OOZIE-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502324#comment-15502324 ] Abhishek Bafna commented on OOZIE-2675: --- [~asasvari] Can you please take a look, you have recently worked on a similar issue. Thanks. > Drop support for hadoop 0.23 > > > Key: OOZIE-2675 > URL: https://issues.apache.org/jira/browse/OOZIE-2675 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2675-00.patch > > > Drop support for Hadoop 0.23. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2657) Clean up redundant access modifiers from oozie interfaces
[
https://issues.apache.org/jira/browse/OOZIE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502253#comment-15502253
]
Abhishek Bafna commented on OOZIE-2657:
---
Thanks [~jaydeepvishwakarma].
> Clean up redundant access modifiers from oozie interfaces
> -
>
> Key: OOZIE-2657
> URL: https://issues.apache.org/jira/browse/OOZIE-2657
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Minor
> Labels: code-cleanup
> Fix For: 4.3.0
>
> Attachments: OOZIE-2657-00-amend.patch, OOZIE-2657-00.patch
>
>
> By default java {{interface}} fields are {{public static final}}. Some of the
> Oozie interface still explicitly declare these redundant access modifier. I
> think we can clean it.
> Similarly, methods declared in the interface are {{public}}. This redundant
> declaration can be cleaned up.
> {code}
> public interface RestConstants {
> public static final String VERSIONS = "versions";
> public static final String JOB = "job";
> ...
> }
> public interface JsonTags {
> public static final String OOZIE_SAFE_MODE = "safeMode"; //Applicable for
> V0 only
> public static final String OOZIE_SYSTEM_MODE = "systemMode";
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2657) Clean up redundant access modifiers from oozie interfaces
[
https://issues.apache.org/jira/browse/OOZIE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15501154#comment-15501154
]
Abhishek Bafna commented on OOZIE-2657:
---
Testcase failure is not relevant to the patch and passes locally. Thanks.
> Clean up redundant access modifiers from oozie interfaces
> -
>
> Key: OOZIE-2657
> URL: https://issues.apache.org/jira/browse/OOZIE-2657
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Minor
> Labels: code-cleanup
> Fix For: 4.3.0
>
> Attachments: OOZIE-2657-00-amend.patch, OOZIE-2657-00.patch
>
>
> By default java {{interface}} fields are {{public static final}}. Some of the
> Oozie interface still explicitly declare these redundant access modifier. I
> think we can clean it.
> Similarly, methods declared in the interface are {{public}}. This redundant
> declaration can be cleaned up.
> {code}
> public interface RestConstants {
> public static final String VERSIONS = "versions";
> public static final String JOB = "job";
> ...
> }
> public interface JsonTags {
> public static final String OOZIE_SAFE_MODE = "safeMode"; //Applicable for
> V0 only
> public static final String OOZIE_SYSTEM_MODE = "systemMode";
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2675) Drop support for hadoop 0.23
[ https://issues.apache.org/jira/browse/OOZIE-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna updated OOZIE-2675: -- Attachment: OOZIE-2675-00.patch > Drop support for hadoop 0.23 > > > Key: OOZIE-2675 > URL: https://issues.apache.org/jira/browse/OOZIE-2675 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2675-00.patch > > > Drop support for Hadoop 0.23. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OOZIE-2675) Drop support for hadoop 0.23
Abhishek Bafna created OOZIE-2675: - Summary: Drop support for hadoop 0.23 Key: OOZIE-2675 URL: https://issues.apache.org/jira/browse/OOZIE-2675 Project: Oozie Issue Type: Bug Components: core Reporter: Abhishek Bafna Assignee: Abhishek Bafna Fix For: 4.3.0 Drop support for Hadoop 0.23. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-2657) Clean up redundant access modifiers from oozie interfaces
[
https://issues.apache.org/jira/browse/OOZIE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-2657:
--
Attachment: OOZIE-2657-00-amend.patch
> Clean up redundant access modifiers from oozie interfaces
> -
>
> Key: OOZIE-2657
> URL: https://issues.apache.org/jira/browse/OOZIE-2657
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Minor
> Labels: code-cleanup
> Fix For: 4.3.0
>
> Attachments: OOZIE-2657-00-amend.patch, OOZIE-2657-00.patch
>
>
> By default java {{interface}} fields are {{public static final}}. Some of the
> Oozie interface still explicitly declare these redundant access modifier. I
> think we can clean it.
> Similarly, methods declared in the interface are {{public}}. This redundant
> declaration can be cleaned up.
> {code}
> public interface RestConstants {
> public static final String VERSIONS = "versions";
> public static final String JOB = "job";
> ...
> }
> public interface JsonTags {
> public static final String OOZIE_SAFE_MODE = "safeMode"; //Applicable for
> V0 only
> public static final String OOZIE_SYSTEM_MODE = "systemMode";
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2674) Improve oozie commads documentation
[ https://issues.apache.org/jira/browse/OOZIE-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15500849#comment-15500849 ] Abhishek Bafna commented on OOZIE-2674: --- Patch does not modify any code, It is doc only patch. > Improve oozie commads documentation > --- > > Key: OOZIE-2674 > URL: https://issues.apache.org/jira/browse/OOZIE-2674 > Project: Oozie > Issue Type: Bug > Components: docs >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Attachments: OOZIE-2674-00.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2041) Add an admin command to run the PurgeXCommand
[
https://issues.apache.org/jira/browse/OOZIE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15500607#comment-15500607
]
Abhishek Bafna commented on OOZIE-2041:
---
[~gezapeti] Thanks for the feedback. Updated the patch with your suggestions.
I will fix the below error.
{code}
-1 the patch contains 1 line(s) longer than 132 characters
{code}
> Add an admin command to run the PurgeXCommand
> -
>
> Key: OOZIE-2041
> URL: https://issues.apache.org/jira/browse/OOZIE-2041
> Project: Oozie
> Issue Type: New Feature
> Components: core
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Abhishek Bafna
> Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.patch,
> OOZIE-2041-02.patch
>
>
> Some users may find it useful to be able to run the PurgeXCommand on-demand.
> We can add a new admin command to run this. e.g.
> {noformat}
> oozie admin -purge
> {noformat}
> With no args, it can use the "older than" values from oozie-site, but we
> could have it take some arguments to override those for the command.
> Another thing to worry about is making sure that we don't run this if either
> it's already running (i.e. the user sent it twice) or if the scheduled
> PurgeService is already running it. On top of that, we may need extra
> consideration for HA setups where we currently only run it on the leader.
> We should probably also have a to not schedule the PurgeService in ooize-site
> for users who only want to run it manually.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2674) Improve oozie commads documentation
[ https://issues.apache.org/jira/browse/OOZIE-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna updated OOZIE-2674: -- Attachment: OOZIE-2674-00.patch > Improve oozie commads documentation > --- > > Key: OOZIE-2674 > URL: https://issues.apache.org/jira/browse/OOZIE-2674 > Project: Oozie > Issue Type: Bug > Components: docs >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Attachments: OOZIE-2674-00.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OOZIE-2674) Improve oozie commads documentation
Abhishek Bafna created OOZIE-2674: - Summary: Improve oozie commads documentation Key: OOZIE-2674 URL: https://issues.apache.org/jira/browse/OOZIE-2674 Project: Oozie Issue Type: Bug Components: docs Reporter: Abhishek Bafna Assignee: Abhishek Bafna -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-2041) Add an admin command to run the PurgeXCommand
[
https://issues.apache.org/jira/browse/OOZIE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-2041:
--
Attachment: OOZIE-2041-02.patch
> Add an admin command to run the PurgeXCommand
> -
>
> Key: OOZIE-2041
> URL: https://issues.apache.org/jira/browse/OOZIE-2041
> Project: Oozie
> Issue Type: New Feature
> Components: core
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Abhishek Bafna
> Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.patch,
> OOZIE-2041-02.patch
>
>
> Some users may find it useful to be able to run the PurgeXCommand on-demand.
> We can add a new admin command to run this. e.g.
> {noformat}
> oozie admin -purge
> {noformat}
> With no args, it can use the "older than" values from oozie-site, but we
> could have it take some arguments to override those for the command.
> Another thing to worry about is making sure that we don't run this if either
> it's already running (i.e. the user sent it twice) or if the scheduled
> PurgeService is already running it. On top of that, we may need extra
> consideration for HA setups where we currently only run it on the leader.
> We should probably also have a to not schedule the PurgeService in ooize-site
> for users who only want to run it manually.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2041) Add an admin command to run the PurgeXCommand
[
https://issues.apache.org/jira/browse/OOZIE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-2041:
--
Attachment: OOZIE-2041-01.patch
> Add an admin command to run the PurgeXCommand
> -
>
> Key: OOZIE-2041
> URL: https://issues.apache.org/jira/browse/OOZIE-2041
> Project: Oozie
> Issue Type: New Feature
> Components: core
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Abhishek Bafna
> Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.patch
>
>
> Some users may find it useful to be able to run the PurgeXCommand on-demand.
> We can add a new admin command to run this. e.g.
> {noformat}
> oozie admin -purge
> {noformat}
> With no args, it can use the "older than" values from oozie-site, but we
> could have it take some arguments to override those for the command.
> Another thing to worry about is making sure that we don't run this if either
> it's already running (i.e. the user sent it twice) or if the scheduled
> PurgeService is already running it. On top of that, we may need extra
> consideration for HA setups where we currently only run it on the leader.
> We should probably also have a to not schedule the PurgeService in ooize-site
> for users who only want to run it manually.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2538) Update HttpClient versions to close security vulnerabilities
[ https://issues.apache.org/jira/browse/OOZIE-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15499513#comment-15499513 ] Abhishek Bafna commented on OOZIE-2538: --- Thanks [~rkanter] for reviews and committing it. > Update HttpClient versions to close security vulnerabilities > > > Key: OOZIE-2538 > URL: https://issues.apache.org/jira/browse/OOZIE-2538 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2538-01.patch, OOZIE-2538-02.patch, > OOZIE-2538-03.patch, OOZIE-2538.patch > > > We learned that > https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-5262 : > http/conn/ssl/SSLConnectionSocketFactory.java in Apache HttpComponents > HttpClient before 4.3.6 ignores the http.socket.timeout configuration setting > during an SSL handshake, which allows remote attackers to cause a denial of > service (HTTPS call hang) via unspecified vectors. > Also, Commons HttpClient project is now end of life, and is no longer being > developed. It has been replaced by the Apache HttpComponents project in its > HttpClient and HttpCore modules, which offer better performance and more > flexibility. http://hc.apache.org/httpclient-3.x/ > Hence, HttpClient version should be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15499465#comment-15499465 ] Abhishek Bafna commented on OOZIE-2613: --- All the failed and error testcases passes locally. :) > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-2613:
--
Attachment: OOZIE-2613-06.patch
Yes. The testcases broke for {{hadoop-2}} profile. The problem was, If we make
changes to the {{MiniHCatServer}} class then hive testcases fails for
{{hadoop-1}} profile with following exception:
{code}
FAILED: SemanticException [Error 10072]: Database does not exist:
default2016-09-17 09:07:10,248 [pool-1-thread-1] ERROR
org.apache.hadoop.hive.ql.Driver - FAILED: SemanticException [Error 10072]:
Database does not exist: default
org.apache.hadoop.hive.ql.parse.SemanticException: Database does not exist:
default
{code}
To fix the issue and make it work for both {{hadoop-1}} and {{hadoop-2}}
profile, added the database creation statements in the testcases. e.g.
{code}
buffer.append("CREATE DATABASE IF NOT EXISTS default;").append(NEW_LINE);
{code}
Removed the {{MiniHCatServer#resetDefaultDBCreation}} method as it does not
contain any executable statement.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch,
> OOZIE-2613-06.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2538) Update HttpClient versions to close security vulnerabilities
[ https://issues.apache.org/jira/browse/OOZIE-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna updated OOZIE-2538: -- Attachment: OOZIE-2538-03.patch Thanks a lot [~rkanter] for the feedback. Updated the patch. > Update HttpClient versions to close security vulnerabilities > > > Key: OOZIE-2538 > URL: https://issues.apache.org/jira/browse/OOZIE-2538 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2538-01.patch, OOZIE-2538-02.patch, > OOZIE-2538-03.patch, OOZIE-2538.patch > > > We learned that > https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-5262 : > http/conn/ssl/SSLConnectionSocketFactory.java in Apache HttpComponents > HttpClient before 4.3.6 ignores the http.socket.timeout configuration setting > during an SSL handshake, which allows remote attackers to cause a denial of > service (HTTPS call hang) via unspecified vectors. > Also, Commons HttpClient project is now end of life, and is no longer being > developed. It has been replaced by the Apache HttpComponents project in its > HttpClient and HttpCore modules, which offer better performance and more > flexibility. http://hc.apache.org/httpclient-3.x/ > Hence, HttpClient version should be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-1978) Forkjoin validation code is ridiculously slow in some cases
[
https://issues.apache.org/jira/browse/OOZIE-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15496866#comment-15496866
]
Abhishek Bafna commented on OOZIE-1978:
---
+1 {{non-binding}}
> Forkjoin validation code is ridiculously slow in some cases
> ---
>
> Key: OOZIE-1978
> URL: https://issues.apache.org/jira/browse/OOZIE-1978
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: trunk, 4.0.1
>Reporter: Robert Kanter
>Assignee: Peter Bacsko
> Fix For: 4.3.0
>
> Attachments: OOZIE-1978-001.patch, OOZIE-1978-002.patch,
> OOZIE-1978-002.patch, OOZIE-1978-003.patch, OOZIE-1978-004.patch,
> OOZIE-1978-005.patch, OOZIE-1978-006.patch, OOZIE-1978_wip.001.patch,
> workflow.xml
>
>
> We've had a few users who have run into problems where submitting a workflow
> appears to hang (in the case of a subworkflow, it's similar but stuck in
> PREP). It turns out that if you wait long enough, it will actually go
> through and the workflow will run normally. The problem is that the forkjoin
> validation code is taking a really long time.
> The attached example has a series of 20 forks where each fork has 6 actions
> (it's based on an actual workflow, but all of the names were changed and the
> actions were all replaced by simple shell actions). One of our support guys
> said it took 1-2 hours , but on my computer it was taking {color:red}*15+
> hours*{color} (I had to cancel it)
> While this example doesn't have any nested forks, those can also take a long
> time too.
> It's easy to verify that it's the forkjoin validation code that's taking so
> long by looking at a jstack of the Oozie server and seeing deep recursive
> calls to
> {{org.apache.oozie.workflow.lite.LiteWorkflowAppParser.validateForkJoin}}. I
> also noticed a lot of sitting around in calls LinkedList.contains.
> I think we have 3 options:
> # See if we can make the existing code faster somehow. Perhaps there's a way
> to parallelize it? Maybe there's some redundant checking that we can
> identify and skip? Change some data structures? etc
> # See if we can write a new way to do this validation. I had originally
> completely rewritten this code a while ago, and we've since made a few fixes
> to catch edge cases and things. Perhaps it needs another rewrite?
> # Try to identify when it's taking a long time and at least let the user know
> what's happening or something. Right now, it just appears that the Oozie CLI
> has hung and the job doesn't show up in the Oozie server. Most users aren't
> going to wait more than a minute or two.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-2613:
--
Attachment: OOZIE-2613-05.patch
Currently we are running the UTs with {{hadoop-1}} profile, So the
{{MiniHCatServer#resetDefaultDBCreation}} is not changed.
The patch contains the {{hive-1.2.0}} and {{jline-2.12}} for hive.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15496427#comment-15496427
]
Abhishek Bafna commented on OOZIE-2613:
---
[~rkanter] For testing, I am executing hive and hive2 examples packaged with
Oozie and some custom Hive workflows. Using {{hadoop-2}} and {{uber}} profile
for preparing the tar.
{code}
bin/mkdistro.sh -DskipTests -Phadoop-2,uber
{code}
The reason for no code change is that, It is keeping the same hive version for
{{hadoop-1}} profile, which is explicitly defined in the profile along with
required {{jline}} version. So the upgrade is happening for the all the other
profiles. I have mentioned same in the last few comments while uploading the
patch earlier.
I will upload re-base and updated patch soon. Thanks.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2569) Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher
[
https://issues.apache.org/jira/browse/OOZIE-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494155#comment-15494155
]
Abhishek Bafna commented on OOZIE-2569:
---
Ping: [~rkanter], [~jaydeepvishwakarma]
> Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher
> ---
>
> Key: OOZIE-2569
> URL: https://issues.apache.org/jira/browse/OOZIE-2569
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2569-00.patch, OOZIE-2569-02.patch,
> OOZIE-2569-03.patch
>
>
> Oozie Spark action requires yarn-site, core-site, hdfs-site and mapred-site
> to be present in the classpath for launching the spark applications.
> Currently we manually copy these files into oozie spark sharelib.
> Until it is fixed through the spark, we can copy the
> {{oozie.action.conf.xml}} file as yarn-site, core-site, hdfs-site and
> mapred-site, which will avoid manual steps of copying those files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2582) Populating external child Ids for action failures
[ https://issues.apache.org/jira/browse/OOZIE-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494154#comment-15494154 ] Abhishek Bafna commented on OOZIE-2582: --- Ping: [~rkanter], [~jaydeepvishwakarma] > Populating external child Ids for action failures > - > > Key: OOZIE-2582 > URL: https://issues.apache.org/jira/browse/OOZIE-2582 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2582-00.patch, OOZIE-2582-01.patch, > OOZIE-2582-02.patch, OOZIE-2582-03.patch, OOZIE-2582-04.patch, > OOZIE-2582-05.patch > > > Currently Oozie external child ids are populated into workflow bean, when the > job/action completes successfully. It should populate external child ids in > case of job failures as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2488) Upgrade to latest OpenJPA version
[ https://issues.apache.org/jira/browse/OOZIE-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490163#comment-15490163 ] Abhishek Bafna commented on OOZIE-2488: --- Thanks [~jaydeepvishwakarma] for the review and committing it. > Upgrade to latest OpenJPA version > - > > Key: OOZIE-2488 > URL: https://issues.apache.org/jira/browse/OOZIE-2488 > Project: Oozie > Issue Type: Improvement > Components: core >Reporter: Robert Kanter >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2488-00.patch > > > Oozie is currently using OpenJPA 2.2.2, which is from April 2013. Version > 2.3.0 is from Nov 2013, but there was a recent 2.4.1 release in Feb 2016 > (that's a long gap!). Given that this is a critical dependency, it might be > a good idea to take a look at the chnagelog, do some testing, and update the > dependency. I'm sure there's lots of bug fixes that would be great to have. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2669) Oozie error : An SQL data change is not permitted for a read-only connection, user or database
[
https://issues.apache.org/jira/browse/OOZIE-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15489757#comment-15489757
]
Abhishek Bafna commented on OOZIE-2669:
---
With what user Oozie service is running, Ideally it should be oozie user, as
you have oozie user available to you.
What is the database you are using?
Are you facing the issue with only coordinators only, are you able to submit
and run workflow successfully?
Thanks.
> Oozie error : An SQL data change is not permitted for a read-only connection,
> user or database
> --
>
> Key: OOZIE-2669
> URL: https://issues.apache.org/jira/browse/OOZIE-2669
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
>Reporter: zeeshan haider naqvi
>
> While running oozie job i am getting below exception:-
> 2016-09-13 17:43:05,449 WARN CoordSubmitXCommand:523 -
> SERVER[ip-10-47-143-47.us-west-2.compute.internal] USER[-] GROUP[-] TOKEN[-]
> APP[-] JOB[-] ACTION[-] ERROR: org.apache.oozie.command.CommandException:
> E0603: SQL error in operation,
> org.apache.openjpa.persistence.RollbackException: The transaction has been
> rolled back. See the nested exceptions for details on the errors that
> occurred. FailedObject: org.apache.oozie.CoordinatorJobBean@550f4b27
> Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: An SQL data
> change is not permitted for a read-only connection, user or database.
> {prepstmnt 1670056758 INSERT INTO COORD_JOBS (id, app_name, app_namespace,
> app_path, bundle_id, concurrency, conf, created_time, done_materialization,
> end_time, execution, external_id, frequency, group_name, job_xml,
> last_action_number, last_action, last_modified_time, mat_throttling,
> next_matd_time, orig_job_xml, pause_time, pending, sla_xml, start_time,
> status, suspended_time, time_out, time_unit, time_zone, user_name) VALUES (?,
> ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
> ?, ?, ?, ?)} [code=2, state=25502]
> I have also tried to run command :
> sudo -u oozie /usr/lib/oozie/bin/ooziedb.sh create -sqlfile
> /usr/lib/oozie/oozie.sql -run
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2648) Child jobs shouldn't send callbacks to Oozie
[
https://issues.apache.org/jira/browse/OOZIE-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488732#comment-15488732
]
Abhishek Bafna commented on OOZIE-2648:
---
Thanks [~rkanter] for the review and committing it.
> Child jobs shouldn't send callbacks to Oozie
>
>
> Key: OOZIE-2648
> URL: https://issues.apache.org/jira/browse/OOZIE-2648
> Project: Oozie
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2648-00.patch
>
>
> I noticed that all action.xml files end up having
> {{job.end.notification.url}} set to send the callback to the Oozie Server
> when they finish. This makes it so that all child MR jobs have this, and
> send notifications to the Oozie Server. This isn't the end of the world, but
> it's unnecessary, especially if you end up with multiple child jobs (e.g. a
> Hive Action that spawns multiple MR jobs). We should consider only adding it
> to the Launcher Job. The exception to this is the MapReduce Action, where
> the Launcher Job exits early and Oozie directly monitors the MR child; in
> this case, the child should have it and the Launcher should not.
> The call in {{JavaActionExecutor}} to {{injectActionCallback(context,
> actionConf);}} is where this happens.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2231) Upgrade curator to latest version 2.11.0
[ https://issues.apache.org/jira/browse/OOZIE-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488710#comment-15488710 ] Abhishek Bafna commented on OOZIE-2231: --- [~rkanter] would you like to take look into OOZIE-2613 patch, Hive upgrade seems a bit tricky. Thanks. > Upgrade curator to latest version 2.11.0 > > > Key: OOZIE-2231 > URL: https://issues.apache.org/jira/browse/OOZIE-2231 > Project: Oozie > Issue Type: Bug > Components: HA >Reporter: Purshotam Shah >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2231-00.patch, OOZIE-2231-01.patch, > OOZIE-2231-02.patch, OOZIE-2231-02.patch, OOZIE-2231-03.patch > > > It have some fix related to InterProcessReadWriteLock, ChildReaper, > LeaderSelector which we use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2583) oozie throws EL Exception when reference variable name containing dot
[
https://issues.apache.org/jira/browse/OOZIE-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487284#comment-15487284
]
Abhishek Bafna commented on OOZIE-2583:
---
Thanks Jaydeep.
> oozie throws EL Exception when reference variable name containing dot
> -
>
> Key: OOZIE-2583
> URL: https://issues.apache.org/jira/browse/OOZIE-2583
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 4.3.0
>Reporter: zhixun he
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2583-00.patch, OOZIE-2583-01.patch,
> OOZIE-2583-02.patch, OOZIE-2583-03.patch, OOZIE-2583-04.patch,
> OOZIE-2583-04.patch
>
>
> TestOozieRegression.test_BundleApppath test case failed due to following
> error:
> {noformat}
> 2016-06-21 06:34:02,116 WARN ActionStartXCommand:523 - SERVER[l]
> USER[hrt_qa] GROUP[-] TOKEN[] APP[test_4591177_1]
> JOB[075-160621052006550-oozie-oozi-W]
> ACTION[075-160621052006550-oozie-oozi-W@subwf] EL Exception in
> ActionStartXCommand
> . javax.servlet.jsp.el.EL Exception : variable [oozie] cannot be resolved
> . at
> org.apache.oozie.util.ELEvaluator$Context.resolveVariable(ELEvaluator.java:107)
> . at org.apache.commons.el.NamedValue.evaluate(NamedValue.java:124)
> . at org.apache.commons.el.ComplexValue.evaluate(ComplexValue.java:140)
> . at
> org.apache.commons.el.ExpressionString.evaluate(ExpressionString.java:114)
> . at
> org.apache.commons.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:274)
> . at
> org.apache.commons.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:190)
> . at org.apache.oozie.util.ELEvaluator.evaluate(ELEvaluator.java:204)
> . at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:193)
> . at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:63)
> . at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> . at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> . at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
> . at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> . at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
> . at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> . at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> . at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2653) Close active connection to hcat server in fs action
[ https://issues.apache.org/jira/browse/OOZIE-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna updated OOZIE-2653: -- Fix Version/s: (was: trunk) 4.3.0 > Close active connection to hcat server in fs action > --- > > Key: OOZIE-2653 > URL: https://issues.apache.org/jira/browse/OOZIE-2653 > Project: Oozie > Issue Type: Bug >Reporter: Satish Subhashrao Saley >Assignee: Satish Subhashrao Saley > Fix For: 4.3.0 > > Attachments: OOZIE-2653-1.patch > > > In FsActionExecutor.java, after deleting the uri, Oozie does not close the > hcat connection. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2491) oozie acl cannot specify group,it does`t work
[ https://issues.apache.org/jira/browse/OOZIE-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483030#comment-15483030 ] Abhishek Bafna commented on OOZIE-2491: --- Ping [~jaydeepvishwakarma] > oozie acl cannot specify group,it does`t work > - > > Key: OOZIE-2491 > URL: https://issues.apache.org/jira/browse/OOZIE-2491 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 4.1.0 >Reporter: Lingang Deng >Assignee: Abhishek Bafna >Priority: Minor > Fix For: 4.3.0 > > Attachments: OOZIE-2491-01.patch > > > when I do oozie acl, specify oozie.job.acl=aclGroup, it doesn`t work when > modify the job with user which belong to the aclGroup.By debugging source > code, " groupsService.getGroups(user).equals(aclItem) ", a List object > compare to a String object ,it`s false forever. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2583) oozie throws EL Exception when reference variable name containing dot
[
https://issues.apache.org/jira/browse/OOZIE-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483027#comment-15483027
]
Abhishek Bafna commented on OOZIE-2583:
---
Ping [~jaydeepvishwakarma]
> oozie throws EL Exception when reference variable name containing dot
> -
>
> Key: OOZIE-2583
> URL: https://issues.apache.org/jira/browse/OOZIE-2583
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 4.3.0
>Reporter: zhixun he
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2583-00.patch, OOZIE-2583-01.patch,
> OOZIE-2583-02.patch, OOZIE-2583-03.patch, OOZIE-2583-04.patch,
> OOZIE-2583-04.patch
>
>
> TestOozieRegression.test_BundleApppath test case failed due to following
> error:
> {noformat}
> 2016-06-21 06:34:02,116 WARN ActionStartXCommand:523 - SERVER[l]
> USER[hrt_qa] GROUP[-] TOKEN[] APP[test_4591177_1]
> JOB[075-160621052006550-oozie-oozi-W]
> ACTION[075-160621052006550-oozie-oozi-W@subwf] EL Exception in
> ActionStartXCommand
> . javax.servlet.jsp.el.EL Exception : variable [oozie] cannot be resolved
> . at
> org.apache.oozie.util.ELEvaluator$Context.resolveVariable(ELEvaluator.java:107)
> . at org.apache.commons.el.NamedValue.evaluate(NamedValue.java:124)
> . at org.apache.commons.el.ComplexValue.evaluate(ComplexValue.java:140)
> . at
> org.apache.commons.el.ExpressionString.evaluate(ExpressionString.java:114)
> . at
> org.apache.commons.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:274)
> . at
> org.apache.commons.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:190)
> . at org.apache.oozie.util.ELEvaluator.evaluate(ELEvaluator.java:204)
> . at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:193)
> . at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:63)
> . at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> . at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> . at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
> . at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> . at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
> . at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> . at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> . at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15472698#comment-15472698
]
Abhishek Bafna edited comment on OOZIE-2613 at 9/8/16 4:25 AM:
---
[~rkanter] Thanks for the feedback and information. Given {{hadoop-0.23}} is
already dropped as part OOZIE-2316, which is currently in the {{oya}} branch.
Should we drop this profile in {{oozie-4.2+}} or leave it as it will taken care
in the {{Oozie-5.0}} coming release.
[~asasvari] As per the above comment, we can ignore the {{hadoop-0.23}}
profile. Thanks for your feedback and review. Please let me know, you have any
other suggestions.
was (Author: abhishekbafna):
[~rkanter] Thanks for the feedback and information. I will create a separate
Jira for the that.
[~asasvari] As per the above comment, we can ignore the {{hadoop-0.23}}
profile. Thanks for your feedback and review. Please let me know, you have any
other suggestions.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15472698#comment-15472698
]
Abhishek Bafna commented on OOZIE-2613:
---
[~rkanter] Thanks for the feedback and information. I will create a separate
Jira for the that.
[~asasvari] As per the above comment, we can ignore the {{hadoop-0.23}}
profile. Thanks for your feedback and review. Please let me know, you have any
other suggestions.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470567#comment-15470567
]
Abhishek Bafna commented on OOZIE-2613:
---
[~asasvari] I was looking into the {{hadoop-0.23}} profile. It does not
compile. There is compilation errors in the {{TestJavaActionExecutor}} class. I
am not sure, If I am missing something while compiling or nobody observed. It
might require a separate jira to fix that, in case if it is a issue.
cc: [~rkanter]
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2648) Child jobs shouldn't send callbacks to Oozie
[
https://issues.apache.org/jira/browse/OOZIE-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470524#comment-15470524
]
Abhishek Bafna commented on OOZIE-2648:
---
The test failure are not relevant to the change. Tests passes locally.
> Child jobs shouldn't send callbacks to Oozie
>
>
> Key: OOZIE-2648
> URL: https://issues.apache.org/jira/browse/OOZIE-2648
> Project: Oozie
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Abhishek Bafna
> Attachments: OOZIE-2648-00.patch
>
>
> I noticed that all action.xml files end up having
> {{job.end.notification.url}} set to send the callback to the Oozie Server
> when they finish. This makes it so that all child MR jobs have this, and
> send notifications to the Oozie Server. This isn't the end of the world, but
> it's unnecessary, especially if you end up with multiple child jobs (e.g. a
> Hive Action that spawns multiple MR jobs). We should consider only adding it
> to the Launcher Job. The exception to this is the MapReduce Action, where
> the Launcher Job exits early and Oozie directly monitors the MR child; in
> this case, the child should have it and the Launcher should not.
> The call in {{JavaActionExecutor}} to {{injectActionCallback(context,
> actionConf);}} is where this happens.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2648) Child jobs shouldn't send callbacks to Oozie
[
https://issues.apache.org/jira/browse/OOZIE-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470468#comment-15470468
]
Abhishek Bafna commented on OOZIE-2648:
---
Commenting the jenkins report manually, as jenkins failed to comment it.
--- {{Jenkins Report}} ---
Testing JIRA OOZIE-2648
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 line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+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: 1800
Tests failed: 3
Tests errors: 1
The patch failed the following testcases:
testNone(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand)
testBundleId(org.apache.oozie.servlet.TestBulkMonitorWebServiceAPI)
testNone(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommandNonUTC)
+1 DISTRO
+1 distro tarball builds with the patch
-1 Overall result, please check the reported -1(s)
The full output of the test-patch run is available at
https://builds.apache.org/job/oozie-trunk-precommit-build/3264/
--- {{Jenkins Error While Reporting}}
---
mv: cannot stat 'jira-cli-2.6.0': No such file or directory
chmod: cannot access
'/home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/test-patch/tools/jira-cli/jira.sh':
No such file or directory
Adding comment to JIRA
bin/test-patch: line 124:
/home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/test-patch/tools/jira-cli/jira.sh:
No such file or directory
test-patch exit code: 1
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
Sending e-mails to: dev@oozie.apache.org
Finished: FAILURE
> Child jobs shouldn't send callbacks to Oozie
>
>
> Key: OOZIE-2648
> URL: https://issues.apache.org/jira/browse/OOZIE-2648
> Project: Oozie
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Abhishek Bafna
> Attachments: OOZIE-2648-00.patch
>
>
> I noticed that all action.xml files end up having
> {{job.end.notification.url}} set to send the callback to the Oozie Server
> when they finish. This makes it so that all child MR jobs have this, and
> send notifications to the Oozie Server. This isn't the end of the world, but
> it's unnecessary, especially if you end up with multiple child jobs (e.g. a
> Hive Action that spawns multiple MR jobs). We should consider only adding it
> to the Launcher Job. The exception to this is the MapReduce Action, where
> the Launcher Job exits early and Oozie directly monitors the MR child; in
> this case, the child should have it and the Launcher should not.
> The call in {{JavaActionExecutor}} to {{injectActionCallback(context,
> actionConf);}} is where this happens.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2648) Child jobs shouldn't send callbacks to Oozie
[
https://issues.apache.org/jira/browse/OOZIE-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456260#comment-15456260
]
Abhishek Bafna commented on OOZIE-2648:
---
[~rkanter] I think we can add a check before calling
{{injectActionCallback(context, actionConf);}} method. In case of
{{action.getType().equals("map-reduce")}}, we should add action callback,
otherwise ignore. Thanks.
> Child jobs shouldn't send callbacks to Oozie
>
>
> Key: OOZIE-2648
> URL: https://issues.apache.org/jira/browse/OOZIE-2648
> Project: Oozie
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Robert Kanter
>
> I noticed that all action.xml files end up having
> {{job.end.notification.url}} set to send the callback to the Oozie Server
> when they finish. This makes it so that all child MR jobs have this, and
> send notifications to the Oozie Server. This isn't the end of the world, but
> it's unnecessary, especially if you end up with multiple child jobs (e.g. a
> Hive Action that spawns multiple MR jobs). We should consider only adding it
> to the Launcher Job. The exception to this is the MapReduce Action, where
> the Launcher Job exits early and Oozie directly monitors the MR child; in
> this case, the child should have it and the Launcher should not.
> The call in {{JavaActionExecutor}} to {{injectActionCallback(context,
> actionConf);}} is where this happens.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15454191#comment-15454191
]
Abhishek Bafna commented on OOZIE-2613:
---
[~asasvari] Can you please refer my last comment and patch
{{OOZIE-2613-03.patch}} for the review. I have uploaded the same into RB as
well. Previously I forgot to update the patch there. Thanks.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2243) Kill Command does not kill the child job for java action
[
https://issues.apache.org/jira/browse/OOZIE-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15451500#comment-15451500
]
Abhishek Bafna commented on OOZIE-2243:
---
Looks good to me. +1 {{non-binding}}
> Kill Command does not kill the child job for java action
>
>
> Key: OOZIE-2243
> URL: https://issues.apache.org/jira/browse/OOZIE-2243
> Project: Oozie
> Issue Type: Bug
>Reporter: Narayan Periwal
>Assignee: Jaydeep Vishwakarma
> Fix For: 4.3.0
>
> Attachments: OOZIE-2243-v1.patch, OOZIE-2243-v2.patch,
> OOZIE-2243-v3.patch, OOZIE-2243-v4.patch, OOZIE-2243-v5.patch,
> OOZIE-2243-v6.patch, OOZIE-2243-v7.patch, OOZIE-2243-v8.patch
>
>
> Lets say, there is launcher job that launches another map-reduce job through
> java-action. When we kill the launcher job, the child job launched by it does
> not get killed and only the launcher job gets killed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2615) Flaky tests TestCoordActionsKillXCommand.testActionKillCommandActionNumbers and testActionKillCommandDate
[
https://issues.apache.org/jira/browse/OOZIE-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15451156#comment-15451156
]
Abhishek Bafna commented on OOZIE-2615:
---
Just a thought, Instead of destroying the services, can we use
{{XDataTestCase#setClassesToBeExcluded}} method for excluding the service in
first. An example can be found in the {{TestStatusTransitService}} class.
Thanks.
> Flaky tests TestCoordActionsKillXCommand.testActionKillCommandActionNumbers
> and testActionKillCommandDate
> --
>
> Key: OOZIE-2615
> URL: https://issues.apache.org/jira/browse/OOZIE-2615
> Project: Oozie
> Issue Type: Bug
> Components: tests
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2615-001.patch
>
>
> Two test cases are unstable because StatusTransitService might change the
> coord job status.
> {code:title=testActionKillCommandDate|borderStyle=solid}
> 08:15:16,122 [pool-3063-thread-2] TRACE CoordStatusTransitXCommand:529 -
> USER[test] GROUP[testg] TOKEN[] APP[COORD-TEST]
> JOB[000-160708081515125-oozie-root-C] ACTION[-] Precondition check for
> command [coord_status_transit] key [000-160708081515125-oozie-root-C]
> 08:15:16,122 [pool-3063-thread-2] DEBUG CoordStatusTransitXCommand:526 -
> USER[test] GROUP[testg] TOKEN[] APP[COORD-TEST]
> JOB[000-160708081515125-oozie-root-C] ACTION[-] Execute command
> [coord_status_transit] key [000-160708081515125-oozie-root-C]
> 08:15:16,122 [pool-3063-thread-2] INFO CoordStatusTransitXCommand:520 -
> USER[test] GROUP[testg] TOKEN[] APP[COORD-TEST]
> JOB[000-160708081515125-oozie-root-C] ACTION[-] Set coordinator job
> [000-160708081515125-oozie-root-C] status to 'KILLED' from 'RUNNING'
> {code}
> {code:title=testActionKillCommandActionNumbers|borderStyle=solid}
> 08:15:13,886 [pool-3059-thread-2] TRACE CoordStatusTransitXCommand:529 -
> USER[test] GROUP[testg] TOKEN[] APP[COORD-TEST]
> JOB[000-160708081512561-oozie-root-C] ACTION[-] Precondition check for
> command [coord_status_transit] key [000-160708081512561-oozie-root-C]
> 08:15:13,886 [pool-3059-thread-2] DEBUG CoordStatusTransitXCommand:526 -
> USER[test] GROUP[testg] TOKEN[] APP[COORD-TEST]
> JOB[000-160708081512561-oozie-root-C] ACTION[-] Execute command
> [coord_status_transit] key [000-160708081512561-oozie-root-C]
> 08:15:13,886 [pool-3059-thread-2] INFO CoordStatusTransitXCommand:520 -
> USER[test] GROUP[testg] TOKEN[] APP[COORD-TEST]
> JOB[000-160708081512561-oozie-root-C] ACTION[-] Set coordinator job
> [000-160708081512561-oozie-root-C] status to 'RUNNINGWITHERROR' from
> 'RUNNING'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15445614#comment-15445614 ] Abhishek Bafna commented on OOZIE-2613: --- Testcase failure is intermittent. Test passes locally. > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna updated OOZIE-2613: -- Attachment: OOZIE-2613-03.patch > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15445087#comment-15445087
]
Abhishek Bafna commented on OOZIE-2613:
---
[~asasvari] Thanks for the suggestion.
Uploading patch {{OOZIE-2613-03.patch}}.
The hive version for profile {{hadoop-1}} is same. The {{hive.version}} and
{{jline.version}} are explicitly set into the hadoop-1 profile.
{code}
0.13.1
0.9.94
{code}
For the rest, hive version is {{1.2.0}} and jline version {{2.12}}.
As currently we are running the Oozie UT with default {{hadoop-1}} profile,
{{hive-1.2.0}} specific changes for running hive and some other UT's are more
made.
Tested the Hive and Hive2 examples with Oozie tar build using
{{-Phadoop-2,uber}}.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-1173) Refactor: use ParamChecker inXOozieClient
[
https://issues.apache.org/jira/browse/OOZIE-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15444692#comment-15444692
]
Abhishek Bafna commented on OOZIE-1173:
---
Thanks [~jaydeepvishwakarma] for the review and committing it.
> Refactor: use ParamChecker inXOozieClient
> -
>
> Key: OOZIE-1173
> URL: https://issues.apache.org/jira/browse/OOZIE-1173
> Project: Oozie
> Issue Type: Task
> Components: client, core
>Reporter: jun aoki
>Assignee: Abhishek Bafna
>Priority: Trivial
> Labels: code-cleanup, newbie
> Fix For: 4.3.0
>
> Attachments: OOZIE-1173-00.patch, OOZIE-1173-01.patch
>
>
> In
> [XOozieClient.java|http://svn.apache.org/viewvc/oozie/trunk/client/src/main/java/org/apache/oozie/client/XOozieClient.java?revision=1401367=markup],
> you can find a piece of code like this and should be replaced with
> ParamChecker.
> {code}
> if (conf == null) {
> throw new IllegalArgumentException("conf cannot be null");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-1173) Refactor: use ParamChecker inXOozieClient
[
https://issues.apache.org/jira/browse/OOZIE-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440764#comment-15440764
]
Abhishek Bafna commented on OOZIE-1173:
---
[~jaydeepvishwakarma] Can you please take a look? Thanks.
> Refactor: use ParamChecker inXOozieClient
> -
>
> Key: OOZIE-1173
> URL: https://issues.apache.org/jira/browse/OOZIE-1173
> Project: Oozie
> Issue Type: Task
> Components: client, core
>Reporter: jun aoki
>Assignee: Abhishek Bafna
>Priority: Trivial
> Labels: code-cleanup, newbie
> Fix For: 4.3.0
>
> Attachments: OOZIE-1173-00.patch, OOZIE-1173-01.patch
>
>
> In
> [XOozieClient.java|http://svn.apache.org/viewvc/oozie/trunk/client/src/main/java/org/apache/oozie/client/XOozieClient.java?revision=1401367=markup],
> you can find a piece of code like this and should be replaced with
> ParamChecker.
> {code}
> if (conf == null) {
> throw new IllegalArgumentException("conf cannot be null");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2243) Kill Command does not kill the child job for java action
[ https://issues.apache.org/jira/browse/OOZIE-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440756#comment-15440756 ] Abhishek Bafna commented on OOZIE-2243: --- [~jaydeepvishwakarma] Can you please rebase the patch. Thanks. > Kill Command does not kill the child job for java action > > > Key: OOZIE-2243 > URL: https://issues.apache.org/jira/browse/OOZIE-2243 > Project: Oozie > Issue Type: Bug >Reporter: Narayan Periwal >Assignee: Jaydeep Vishwakarma > Fix For: 4.3.0 > > Attachments: OOZIE-2243-v0.patch, OOZIE-2243-v1.patch, > OOZIE-2243-v2.patch, OOZIE-2243-v3.patch, OOZIE-2243-v4.patch, > OOZIE-2243-v5.patch, OOZIE-2243-v6.patch, OOZIE-2243-v7.patch > > > Lets say, there is launcher job that launches another map-reduce job through > java-action. When we kill the launcher job, the child job launched by it does > not get killed and only the launcher job gets killed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2134) Remove references to Services.get().getConf() in code
[ https://issues.apache.org/jira/browse/OOZIE-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440753#comment-15440753 ] Abhishek Bafna commented on OOZIE-2134: --- [~seoeun25] Can you please rebase the patch. Thanks. > Remove references to Services.get().getConf() in code > - > > Key: OOZIE-2134 > URL: https://issues.apache.org/jira/browse/OOZIE-2134 > Project: Oozie > Issue Type: Task >Reporter: Rohini Palaniswamy >Assignee: Azrael Seoeun > Labels: newbie > Attachments: OOZIE-2134.1.patch, OOZIE-2134.2.patch, > OOZIE-2134.3.patch > > >Make getConf() package protected and switch all references of > Services.get().getConf() to ConfigurationService. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2653) Close active connection to hcat server in fs action
[
https://issues.apache.org/jira/browse/OOZIE-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440700#comment-15440700
]
Abhishek Bafna commented on OOZIE-2653:
---
+1 {{non-binding}}
> Close active connection to hcat server in fs action
> ---
>
> Key: OOZIE-2653
> URL: https://issues.apache.org/jira/browse/OOZIE-2653
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2653-1.patch
>
>
> In FsActionExecutor.java, after deleting the uri, Oozie does not close the
> hcat connection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-1173) Refactor: use ParamChecker inXOozieClient
[
https://issues.apache.org/jira/browse/OOZIE-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-1173:
--
Labels: code-cleanup newbie (was: newbie)
> Refactor: use ParamChecker inXOozieClient
> -
>
> Key: OOZIE-1173
> URL: https://issues.apache.org/jira/browse/OOZIE-1173
> Project: Oozie
> Issue Type: Task
> Components: client, core
>Reporter: jun aoki
>Assignee: Abhishek Bafna
>Priority: Trivial
> Labels: code-cleanup, newbie
> Fix For: 4.3.0
>
> Attachments: OOZIE-1173-00.patch, OOZIE-1173-01.patch
>
>
> In
> [XOozieClient.java|http://svn.apache.org/viewvc/oozie/trunk/client/src/main/java/org/apache/oozie/client/XOozieClient.java?revision=1401367=markup],
> you can find a piece of code like this and should be replaced with
> ParamChecker.
> {code}
> if (conf == null) {
> throw new IllegalArgumentException("conf cannot be null");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2657) Clean up redundant access modifiers from oozie interfaces
[
https://issues.apache.org/jira/browse/OOZIE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15440589#comment-15440589
]
Abhishek Bafna commented on OOZIE-2657:
---
Thanks [~jaydeepvishwakarma] for the review and committing it.
> Clean up redundant access modifiers from oozie interfaces
> -
>
> Key: OOZIE-2657
> URL: https://issues.apache.org/jira/browse/OOZIE-2657
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Minor
> Labels: code-cleanup
> Fix For: 4.3.0
>
> Attachments: OOZIE-2657-00.patch
>
>
> By default java {{interface}} fields are {{public static final}}. Some of the
> Oozie interface still explicitly declare these redundant access modifier. I
> think we can clean it.
> Similarly, methods declared in the interface are {{public}}. This redundant
> declaration can be cleaned up.
> {code}
> public interface RestConstants {
> public static final String VERSIONS = "versions";
> public static final String JOB = "job";
> ...
> }
> public interface JsonTags {
> public static final String OOZIE_SAFE_MODE = "safeMode"; //Applicable for
> V0 only
> public static final String OOZIE_SYSTEM_MODE = "systemMode";
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2657) Clean up redundant access modifiers from oozie interfaces
[
https://issues.apache.org/jira/browse/OOZIE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-2657:
--
Fix Version/s: 4.3.0
> Clean up redundant access modifiers from oozie interfaces
> -
>
> Key: OOZIE-2657
> URL: https://issues.apache.org/jira/browse/OOZIE-2657
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Minor
> Labels: code-cleanup
> Fix For: 4.3.0
>
> Attachments: OOZIE-2657-00.patch
>
>
> By default java {{interface}} fields are {{public static final}}. Some of the
> Oozie interface still explicitly declare these redundant access modifier. I
> think we can clean it.
> Similarly, methods declared in the interface are {{public}}. This redundant
> declaration can be cleaned up.
> {code}
> public interface RestConstants {
> public static final String VERSIONS = "versions";
> public static final String JOB = "job";
> ...
> }
> public interface JsonTags {
> public static final String OOZIE_SAFE_MODE = "safeMode"; //Applicable for
> V0 only
> public static final String OOZIE_SYSTEM_MODE = "systemMode";
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2657) Clean up redundant access modifiers from oozie interfaces
[
https://issues.apache.org/jira/browse/OOZIE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439654#comment-15439654
]
Abhishek Bafna commented on OOZIE-2657:
---
Testcase failure is not related. Test passes locally.
> Clean up redundant access modifiers from oozie interfaces
> -
>
> Key: OOZIE-2657
> URL: https://issues.apache.org/jira/browse/OOZIE-2657
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Minor
> Labels: code-cleanup
> Attachments: OOZIE-2657-00.patch
>
>
> By default java {{interface}} fields are {{public static final}}. Some of the
> Oozie interface still explicitly declare these redundant access modifier. I
> think we can clean it.
> Similarly, methods declared in the interface are {{public}}. This redundant
> declaration can be cleaned up.
> {code}
> public interface RestConstants {
> public static final String VERSIONS = "versions";
> public static final String JOB = "job";
> ...
> }
> public interface JsonTags {
> public static final String OOZIE_SAFE_MODE = "safeMode"; //Applicable for
> V0 only
> public static final String OOZIE_SYSTEM_MODE = "systemMode";
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2657) Clean up redundant access modifiers from oozie interfaces
[
https://issues.apache.org/jira/browse/OOZIE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439233#comment-15439233
]
Abhishek Bafna commented on OOZIE-2657:
---
[~rkanter], [~jaydeepvishwakarma] Can you guys please take? Thanks.
> Clean up redundant access modifiers from oozie interfaces
> -
>
> Key: OOZIE-2657
> URL: https://issues.apache.org/jira/browse/OOZIE-2657
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Minor
> Labels: code-cleanup
> Attachments: OOZIE-2657-00.patch
>
>
> By default java {{interface}} fields are {{public static final}}. Some of the
> Oozie interface still explicitly declare these redundant access modifier. I
> think we can clean it.
> Similarly, methods declared in the interface are {{public}}. This redundant
> declaration can be cleaned up.
> {code}
> public interface RestConstants {
> public static final String VERSIONS = "versions";
> public static final String JOB = "job";
> ...
> }
> public interface JsonTags {
> public static final String OOZIE_SAFE_MODE = "safeMode"; //Applicable for
> V0 only
> public static final String OOZIE_SYSTEM_MODE = "systemMode";
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2657) Clean up redundant access modifiers from oozie interfaces
[
https://issues.apache.org/jira/browse/OOZIE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-2657:
--
Attachment: OOZIE-2657-00.patch
> Clean up redundant access modifiers from oozie interfaces
> -
>
> Key: OOZIE-2657
> URL: https://issues.apache.org/jira/browse/OOZIE-2657
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Minor
> Labels: code-cleanup
> Attachments: OOZIE-2657-00.patch
>
>
> By default java {{interface}} fields are {{public static final}}. Some of the
> Oozie interface still explicitly declare these redundant access modifier. I
> think we can clean it.
> Similarly, methods declared in the interface are {{public}}. This redundant
> declaration can be cleaned up.
> {code}
> public interface RestConstants {
> public static final String VERSIONS = "versions";
> public static final String JOB = "job";
> ...
> }
> public interface JsonTags {
> public static final String OOZIE_SAFE_MODE = "safeMode"; //Applicable for
> V0 only
> public static final String OOZIE_SYSTEM_MODE = "systemMode";
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OOZIE-2657) Clean up redundant access modifiers from oozie interfaces
Abhishek Bafna created OOZIE-2657:
-
Summary: Clean up redundant access modifiers from oozie interfaces
Key: OOZIE-2657
URL: https://issues.apache.org/jira/browse/OOZIE-2657
Project: Oozie
Issue Type: Bug
Components: core
Reporter: Abhishek Bafna
Assignee: Abhishek Bafna
Priority: Minor
By default java {{interface}} fields are {{public static final}}. Some of the
Oozie interface still explicitly declare these redundant access modifier. I
think we can clean it.
Similarly, methods declared in the interface are {{public}}. This redundant
declaration can be cleaned up.
{code}
public interface RestConstants {
public static final String VERSIONS = "versions";
public static final String JOB = "job";
...
}
public interface JsonTags {
public static final String OOZIE_SAFE_MODE = "safeMode"; //Applicable for
V0 only
public static final String OOZIE_SYSTEM_MODE = "systemMode";
...
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2041) Add an admin command to run the PurgeXCommand
[
https://issues.apache.org/jira/browse/OOZIE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-2041:
--
Attachment: OOZIE-2041-00.patch
> Add an admin command to run the PurgeXCommand
> -
>
> Key: OOZIE-2041
> URL: https://issues.apache.org/jira/browse/OOZIE-2041
> Project: Oozie
> Issue Type: New Feature
> Components: core
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Abhishek Bafna
> Attachments: OOZIE-2041-00.patch
>
>
> Some users may find it useful to be able to run the PurgeXCommand on-demand.
> We can add a new admin command to run this. e.g.
> {noformat}
> oozie admin -purge
> {noformat}
> With no args, it can use the "older than" values from oozie-site, but we
> could have it take some arguments to override those for the command.
> Another thing to worry about is making sure that we don't run this if either
> it's already running (i.e. the user sent it twice) or if the scheduled
> PurgeService is already running it. On top of that, we may need extra
> consideration for HA setups where we currently only run it on the leader.
> We should probably also have a to not schedule the PurgeService in ooize-site
> for users who only want to run it manually.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2041) Add an admin command to run the PurgeXCommand
[
https://issues.apache.org/jira/browse/OOZIE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438942#comment-15438942
]
Abhishek Bafna commented on OOZIE-2041:
---
By default {{PurgeService}} executes every hour to clean up old oozie
workflows, coordinators and bundles from Oozie DB. With the new {{oozie admin
-purge wf=1\;coord=2\;bundle=3\;limit=100\;oldCoordAction=true/false>}}
command, users (admin users) can execute {{PurgeService}} on demand.
# Allow users to specify older than values for (workflow, coordinator and
bundle) in {{days}}, limit and turn {{on/off}} for old coordinator actions. At
least one parameter needs to be specified.
# If user does not specify one of parameter than {{PurgeService}} will use the
default value of it from {{oozie-default.xml}} or {{oozie-site.xml}}.
# The execution of the Purge Command will require a lock for execution, so at
the same time two {{PurgeXCommand}} will not execute. In the case, when lock is
not acquired, it will queue the command.
# Currently purge command is implemented as blocking command. Users will need
to wait until command execution completes.
# In the HA mode, purge command can be executed only on the leader Oozie server.
# purge command can be enabled/disabled using
{{oozie.service.PurgeService.enable.command.line}} property. By default it is
enabled.
> Add an admin command to run the PurgeXCommand
> -
>
> Key: OOZIE-2041
> URL: https://issues.apache.org/jira/browse/OOZIE-2041
> Project: Oozie
> Issue Type: New Feature
> Components: core
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Abhishek Bafna
>
> Some users may find it useful to be able to run the PurgeXCommand on-demand.
> We can add a new admin command to run this. e.g.
> {noformat}
> oozie admin -purge
> {noformat}
> With no args, it can use the "older than" values from oozie-site, but we
> could have it take some arguments to override those for the command.
> Another thing to worry about is making sure that we don't run this if either
> it's already running (i.e. the user sent it twice) or if the scheduled
> PurgeService is already running it. On top of that, we may need extra
> consideration for HA setups where we currently only run it on the leader.
> We should probably also have a to not schedule the PurgeService in ooize-site
> for users who only want to run it manually.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2525) SchemaChecker fails with NPE
[
https://issues.apache.org/jira/browse/OOZIE-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438537#comment-15438537
]
Abhishek Bafna commented on OOZIE-2525:
---
+1 {{non-binding}}.
> SchemaChecker fails with NPE
>
>
> Key: OOZIE-2525
> URL: https://issues.apache.org/jira/browse/OOZIE-2525
> Project: Oozie
> Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
> Attachments: OOZIE-2525.001.patch
>
>
> {code}
> 2016-05-03 14:38:03,851 WARN SchedulerService:523 [pool-1-thread-2] -
> SERVER[-] Error executing runnable [SchemaCheckerRunnable], null
> java.lang.NullPointerException
> at
> org.apache.oozie.service.SchemaCheckerService.access$002(SchemaCheckerService.java:29)
> at
> org.apache.oozie.service.SchemaCheckerService$SchemaCheckerRunnable.run(SchemaCheckerService.java:120)
> at
> org.apache.oozie.service.SchedulerService$2.run(SchedulerService.java:175)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> It;s trying to use SchemaCheckerService before it is initialized.
> {code:title=SchemaCheckerService.java}
> Services.get().get(SchemaCheckerService.class).status = "DISABLED (not leader
> in HA)";
> Services.get().get(SchemaCheckerService.class).lastCheck =
> "N/A";
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (OOZIE-2041) Add an admin command to run the PurgeXCommand
[
https://issues.apache.org/jira/browse/OOZIE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna reassigned OOZIE-2041:
-
Assignee: Abhishek Bafna
> Add an admin command to run the PurgeXCommand
> -
>
> Key: OOZIE-2041
> URL: https://issues.apache.org/jira/browse/OOZIE-2041
> Project: Oozie
> Issue Type: New Feature
> Components: core
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Abhishek Bafna
>
> Some users may find it useful to be able to run the PurgeXCommand on-demand.
> We can add a new admin command to run this. e.g.
> {noformat}
> oozie admin -purge
> {noformat}
> With no args, it can use the "older than" values from oozie-site, but we
> could have it take some arguments to override those for the command.
> Another thing to worry about is making sure that we don't run this if either
> it's already running (i.e. the user sent it twice) or if the scheduled
> PurgeService is already running it. On top of that, we may need extra
> consideration for HA setups where we currently only run it on the leader.
> We should probably also have a to not schedule the PurgeService in ooize-site
> for users who only want to run it manually.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2041) Add an admin command to run the PurgeXCommand
[
https://issues.apache.org/jira/browse/OOZIE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436684#comment-15436684
]
Abhishek Bafna commented on OOZIE-2041:
---
[~rkanter] Can I take up this issue?
> Add an admin command to run the PurgeXCommand
> -
>
> Key: OOZIE-2041
> URL: https://issues.apache.org/jira/browse/OOZIE-2041
> Project: Oozie
> Issue Type: New Feature
> Components: core
>Affects Versions: trunk
>Reporter: Robert Kanter
>
> Some users may find it useful to be able to run the PurgeXCommand on-demand.
> We can add a new admin command to run this. e.g.
> {noformat}
> oozie admin -purge
> {noformat}
> With no args, it can use the "older than" values from oozie-site, but we
> could have it take some arguments to override those for the command.
> Another thing to worry about is making sure that we don't run this if either
> it's already running (i.e. the user sent it twice) or if the scheduled
> PurgeService is already running it. On top of that, we may need extra
> consideration for HA setups where we currently only run it on the leader.
> We should probably also have a to not schedule the PurgeService in ooize-site
> for users who only want to run it manually.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2650) Retry coord start on database exceptions
[
https://issues.apache.org/jira/browse/OOZIE-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436646#comment-15436646
]
Abhishek Bafna commented on OOZIE-2650:
---
I think we can define a new error code instead of using {{E1304, "Duplicate
bundle application coordinator name"}}
{code}
@Override
protected void verifyPrecondition() throws CommandException {
super.verifyPrecondition();
if (wfId != null) {
LOG.warn("Workflow is already submitted for Coord Action [{0}]",
getParentId());
throw new CommandException(ErrorCode.E1304, getParentId());
}
}
{code}
> Retry coord start on database exceptions
>
>
> Key: OOZIE-2650
> URL: https://issues.apache.org/jira/browse/OOZIE-2650
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2650-1.patch
>
>
> {code:title=CoordActionStartXCommand.java}
> updateList.add(new UpdateEntry(
> WorkflowJobQuery.UPDATE_WORKFLOW_PARENT_MODIFIED,
> wfJob));
> updateList.add(new UpdateEntry(
> CoordActionQuery.UPDATE_COORD_ACTION_FOR_START,
> coordAction));
> try {
> executor.executeBatchInsertUpdateDelete(insertList,
> updateList, null);
> queue(new
> CoordActionNotificationXCommand(coordAction), 100);
> if (EventHandlerService.isEnabled()) {
> generateEvent(coordAction, user, appName,
> wfJob.getStartTime());
> }
> }
> catch (JPAExecutorException je) {
> throw new CommandException(je);
> }
> .
> ...
>
> finally {
> if (makeFail == true) { // No DB exception occurs
>
>
>
> queue(new
> CoordActionReadyXCommand(coordAction.getJobId()));
> }
> }
> {code}
> If there is any Database issue while starting coord action, we fail the coord
> action. We should retry.
> CoordActionStartXCommand submits workflow. Workflow gets linked to the coord
> action if workflow submission succeeds. But if coord action update fails due
> to database exception, recovery service should be able to recover it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2617) Read properties files in action configurations
[
https://issues.apache.org/jira/browse/OOZIE-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436618#comment-15436618
]
Abhishek Bafna commented on OOZIE-2617:
---
+1 {{non-binding}}.
> Read properties files in action configurations
> --
>
> Key: OOZIE-2617
> URL: https://issues.apache.org/jira/browse/OOZIE-2617
> Project: Oozie
> Issue Type: Improvement
> Components: core
>Affects Versions: trunk
>Reporter: Taklon Stephen Wu
> Labels: patch
> Fix For: 4.3.0
>
> Attachments: OOZIE-2617-1.patch, OOZIE-2617-2.patch,
> OOZIE-2617-3.patch
>
>
> Current logic of acton configuration only READ xml files within Oozie action
> directory, but for pig and other applications, properties files are supported
> and may be default configuration file format. To simplify the logic of
> reusing these properties files when using Oozie with them, we add properties
> file reading in action conf.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2517) Add support for startCreatedTime and endCreatedTime filters for coord and bundles
[
https://issues.apache.org/jira/browse/OOZIE-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434162#comment-15434162
]
Abhishek Bafna commented on OOZIE-2517:
---
Thanks [~jaydeepvishwakarma] for review and committing.
> Add support for startCreatedTime and endCreatedTime filters for coord and
> bundles
> -
>
> Key: OOZIE-2517
> URL: https://issues.apache.org/jira/browse/OOZIE-2517
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2517-001.patch, OOZIE-2517-003.patch,
> OOZIE-2517-005.patch, OOZIE-2517-007.patch, OOZIE-2517-008.patch,
> OOZIE-2517-009.patch, OOZIE-2517-010.patch
>
>
> Support for the 'startCreatedTime' and 'endCreatedTime' is not implemented
> for the coordinators and bundle job.
> Curl command with jobtype coordinator and bundle fails where as jobtype=wf
> executes successfully.
> https://oozie.apache.org/docs/4.2.0/WebServicesAPI.html#Jobs_Information
> {noformat}
> curl
> "http://host:11000/oozie/v2/jobs?filter=startCreatedTime%3D2016-04-28T00%3A00Z=bundle;
> curl
> "http://host:11000/oozie/v2/jobs?filter=startCreatedTime%3D2016-04-28T00%3A00Z=coordinator;
> curl
> "http://host:11000/oozie/v2/jobs?filter=startCreatedTime%3D2016-04-28T00%3A00Z=wf;
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2517) Add support for startCreatedTime and endCreatedTime filters for coord and bundles
[
https://issues.apache.org/jira/browse/OOZIE-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432689#comment-15432689
]
Abhishek Bafna commented on OOZIE-2517:
---
[~jaydeepvishwakarma] Ping.
> Add support for startCreatedTime and endCreatedTime filters for coord and
> bundles
> -
>
> Key: OOZIE-2517
> URL: https://issues.apache.org/jira/browse/OOZIE-2517
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2517-001.patch, OOZIE-2517-003.patch,
> OOZIE-2517-005.patch, OOZIE-2517-007.patch, OOZIE-2517-008.patch,
> OOZIE-2517-009.patch, OOZIE-2517-010.patch
>
>
> Support for the 'startCreatedTime' and 'endCreatedTime' is not implemented
> for the coordinators and bundle job.
> Curl command with jobtype coordinator and bundle fails where as jobtype=wf
> executes successfully.
> https://oozie.apache.org/docs/4.2.0/WebServicesAPI.html#Jobs_Information
> {noformat}
> curl
> "http://host:11000/oozie/v2/jobs?filter=startCreatedTime%3D2016-04-28T00%3A00Z=bundle;
> curl
> "http://host:11000/oozie/v2/jobs?filter=startCreatedTime%3D2016-04-28T00%3A00Z=coordinator;
> curl
> "http://host:11000/oozie/v2/jobs?filter=startCreatedTime%3D2016-04-28T00%3A00Z=wf;
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426216#comment-15426216
]
Abhishek Bafna commented on OOZIE-2613:
---
I am not able to get these two testcases working. I can use some help/feedback
from the fellow developers in the community.
{noformat}
org.apache.oozie.action.hadoop.TestJavaActionExecutor.testACLModifyJob
org.apache.oozie.action.hadoop.TestHiveMain.testMain
{noformat}
{{TestJavaActionExecutor.testACLModifyJob}} is failing because FileSystem is
initialized with the {{test}} user and launcher job is launched with
{{user.name}} (due to {{XHCatTestCase#getTestUser}}, added into this patch).
The Hive testcase works fine with hadoop-2 profile, but fails with hadoop-1
profile.
{noformat}
2016-08-18 14:43:47,507 [main] ERROR org.apache.hadoop.hive.ql.exec.Task -
Failed with exception Unable to rename:
hdfs://localhost:56649/user/test/95bd1a4c-2629-47bd-a347-f3901b757832/output/.hive-staging_hive_2016-08-18_14-41-58_397_1680638062022362363-1/-ext-1
to: /user/test/95bd1a4c-2629-47bd-a347-f3901b757832/output
org.apache.hadoop.hive.ql.metadata.HiveException: Unable to rename:
hdfs://localhost:56649/user/test/95bd1a4c-2629-47bd-a347-f3901b757832/output/.hive-staging_hive_2016-08-18_14-41-58_397_1680638062022362363-1/-ext-1
to: /user/test/95bd1a4c-2629-47bd-a347-f3901b757832/output
at org.apache.hadoop.hive.ql.exec.MoveTask.moveFile(MoveTask.java:114)
at org.apache.hadoop.hive.ql.exec.MoveTask.execute(MoveTask.java:222)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:88)
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1650)
at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1409)
at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1192)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1059)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1049)
at
org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:213)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:165)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:376)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:311)
at
org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:409)
at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:425)
at
org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:714)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:681)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:621)
at org.apache.oozie.action.hadoop.HiveMain.runHive(HiveMain.java:334)
at org.apache.oozie.action.hadoop.HiveMain.run(HiveMain.java:311)
at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:49)
at org.apache.oozie.action.hadoop.HiveMain.main(HiveMain.java:69)
at
org.apache.oozie.action.hadoop.TestHiveMain.call(TestHiveMain.java:138)
at
org.apache.oozie.action.hadoop.TestHiveMain.call(TestHiveMain.java:34)
at
org.apache.oozie.action.hadoop.MainTestCase$1.run(MainTestCase.java:33)
at
org.apache.oozie.action.hadoop.MainTestCase$1.run(MainTestCase.java:31)
at java.security.AccessController.doPrivileged(Native Method)
{noformat}
For the hadoop-1, would it be a good idea to keep the hive version same as
{{hive-0.13.1}}.
cc: [~rkanter] [~jaydeepvishwakarma] [~puru] [~rohini] [~asasvari] [~gezapeti]
[~satishsaley]
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2231) Upgrade curator to latest version 2.11.0
[
https://issues.apache.org/jira/browse/OOZIE-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-2231:
--
Attachment: OOZIE-2231-03.patch
[~rkanter], Uploading a patch with {{curator-2.11.0}} and {{guava-16.0.1}}.
1. The {{Stopwatch#elapsedMillis()}} is not available in guava-16. Updated
Stopwatch initialization instead of a deprecated constructor to static method
{{Stopwatch.createStarted()}}.
2. Indentation fixed. Refactored the indentation for property section of the
main {{pom.xml}}.
3. Defined a global {{}}.
4. This should not be a problem. I was able to execute Oozie example workflows
without any issue. This is how lib's look like with patch.
{noformat}
$find . -name guava*
./share/lib/hive/guava-16.0.1.jar
./share/lib/spark/guava-14.0.1.jar
./share/lib/pig/guava-11.0.2.jar
./oozie-client/lib/guava-16.0.1.jar
./lib/guava-16.0.1.jar
./oozie-server/webapps/oozie/WEB-INF/lib/guava-16.0.1.jar
{noformat}
[~puru], [~rohini] Please have a look and let me know your feedback. Thanks.
> Upgrade curator to latest version 2.11.0
>
>
> Key: OOZIE-2231
> URL: https://issues.apache.org/jira/browse/OOZIE-2231
> Project: Oozie
> Issue Type: Bug
> Components: HA
>Reporter: Purshotam Shah
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2231-00.patch, OOZIE-2231-01.patch,
> OOZIE-2231-02.patch, OOZIE-2231-02.patch, OOZIE-2231-03.patch
>
>
> It have some fix related to InterProcessReadWriteLock, ChildReaper,
> LeaderSelector which we use.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2231) Upgrade curator to latest version 2.11.0
[
https://issues.apache.org/jira/browse/OOZIE-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424932#comment-15424932
]
Abhishek Bafna commented on OOZIE-2231:
---
[~rkanter] I think we need to bring in guava-16, because curator-2.11.0 uses
it. Otherwise many ZK related testcases fails with following exception: (some
other errors)
{noformat}
java.lang.NoSuchMethodError:
com.google.common.collect.Sets.newConcurrentHashSet()Ljava/util/Set;
at
org.apache.curator.framework.recipes.locks.ChildReaper.(ChildReaper.java:63)
at
org.apache.curator.framework.recipes.locks.ChildReaper.(ChildReaper.java:124)
at org.apache.oozie.service.ZKLocksService.init(ZKLocksService.java:71)
at
org.apache.oozie.service.TestZKLocksService.testRegisterUnregister(TestZKLocksService.java:47)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
at
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
{noformat}
I will be prepare a patch and testing the UTs and all the examples which we
bundle with Oozie for this. Let me know if this sounds good to you. If there is
any other testing I should be doing, please let me know. Thanks.
> Upgrade curator to latest version 2.11.0
>
>
> Key: OOZIE-2231
> URL: https://issues.apache.org/jira/browse/OOZIE-2231
> Project: Oozie
> Issue Type: Bug
> Components: HA
>Reporter: Purshotam Shah
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2231-00.patch, OOZIE-2231-01.patch,
> OOZIE-2231-02.patch, OOZIE-2231-02.patch
>
>
> It have some fix related to InterProcessReadWriteLock, ChildReaper,
> LeaderSelector which we use.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2231) Upgrade curator to latest version 2.11.0
[ https://issues.apache.org/jira/browse/OOZIE-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424318#comment-15424318 ] Abhishek Bafna commented on OOZIE-2231: --- I will upload a correct patch soon. [~rkanter] Please ignore my previous comment. Thanks. > Upgrade curator to latest version 2.11.0 > > > Key: OOZIE-2231 > URL: https://issues.apache.org/jira/browse/OOZIE-2231 > Project: Oozie > Issue Type: Bug > Components: HA >Reporter: Purshotam Shah >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2231-00.patch, OOZIE-2231-01.patch, > OOZIE-2231-02.patch, OOZIE-2231-02.patch > > > It have some fix related to InterProcessReadWriteLock, ChildReaper, > LeaderSelector which we use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna updated OOZIE-2613: -- Attachment: OOZIE-2613-02.patch > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-2231) Upgrade curator to latest version 2.11.0
[ https://issues.apache.org/jira/browse/OOZIE-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bafna updated OOZIE-2231: -- Attachment: OOZIE-2231-02.patch > Upgrade curator to latest version 2.11.0 > > > Key: OOZIE-2231 > URL: https://issues.apache.org/jira/browse/OOZIE-2231 > Project: Oozie > Issue Type: Bug > Components: HA >Reporter: Purshotam Shah >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2231-00.patch, OOZIE-2231-01.patch, > OOZIE-2231-02.patch, OOZIE-2231-02.patch > > > It have some fix related to InterProcessReadWriteLock, ChildReaper, > LeaderSelector which we use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
