[jira] [Commented] (OOZIE-2751) LocalOozieClient is missing methods from OozieClient

[Abhishek Bafna (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937753#comment-15937753
 ] 

Abhishek Bafna commented on OOZIE-2751:
---

Ping [~gezapeti] and [~pbacsko]. Thanks.

> LocalOozieClient is missing methods from OozieClient
> 
>
> Key: OOZIE-2751
> URL: https://issues.apache.org/jira/browse/OOZIE-2751
> Project: Oozie
>  Issue Type: Bug
>Reporter: Robert Kanter
>Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2751-00.patch, OOZIE-2751-01.patch, 
> OOZIE-2751-02.patch, OOZIE-2751-03.patch, OOZIE-2751-04.patch, 
> OOZIE-2751-05.patch, OOZIE-2751-06.patch, OOZIE-2751-07.patch
>
>
> {{LocalOozieClient}} works by wrapping direct calls to {{DagEngine}} in the 
> normal {{OozieClient}} methods instead of making REST calls to an Oozie 
> Server.  However, it currently doesn't override all methods, which means you 
> hit the {{OozieClient}} implementation, which tries to make a REST call and 
> will fail (because it's not setup for that).  For example, {{getStatus(String 
> jobId)}} isn't overridden, and doesn't work when used from 
> {{LocalOozieClient}}.
> We should also create a test that verifies that all methods are overridden.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2701) Oozie to support Multiple HCatalog URIs

[Abhishek Bafna (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhishek Bafna updated OOZIE-2701:
--
Attachment: OOZIE-2701-04.patch

The regex pattern in oozie-default.xml is updated after OOZIE-2393.

{noformat}

oozie.hcat.uri.regex.pattern
([a-z]+://[\w+\.\-\w+]+:\d+[,]*)+/\w+/\w+[/\w+=;\-]*
Regex pattern for HCat URIs. The regex can be modified by 
users as per requirement
for parsing/splitting the HCat URIs.

{noformat}

CC: [~gezapeti] and [~andras.piros].

> Oozie to support Multiple HCatalog URIs
> ---
>
> Key: OOZIE-2701
> URL: https://issues.apache.org/jira/browse/OOZIE-2701
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2701-00.patch, OOZIE-2701-01.patch, 
> OOZIE-2701-02.patch, OOZIE-2701-03.patch, OOZIE-2701-04.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Welcome new Oozie Committers - Peter Bacsko and Peter Cseh

[Peter Cseh]

Thanks everyone! :)


On Tue, Mar 21, 2017 at 11:43 PM, satish saley 
wrote:

>
> |
> |
> ||
>
>   |
> |
> |   Congrats to both.|
>
>   |
> |
> ||
>
>   |
>
>  |
> |
> || Yahoo Mail Stationery |
>
>   |
>
>
>
> On Tuesday, March 21, 2017 3:37 PM, Attila Sasvari <
> asasv...@cloudera.com> wrote:
>
>
>  Congratulations!
>
> On Tue, Mar 21, 2017 at 3:36 PM, Abhishek Bafna 
> wrote:
>
> > Congrats (Peter)^2.
> >
> > > On Mar 21, 2017, at 6:58 AM, goun na  wrote:
> > >
> > > Congrats!
> > >
> > > 2017-03-21 7:37 GMT+09:00 Robert Kanter :
> > >
> > >> Hi everyone,
> > >>
> > >> It is my pleasure to announce that the Oozie PMC has invited
> > >> Peter Bacsko and Peter (Geza) Cseh to become Oozie committers
> > >> and they have both accepted our invitation.
> > >>
> > >> Please join me congratulating them.
> > >> Congrats!
> > >>
> > >>
> > >> - Robert, on behalf of the Oozie PMC
> > >>
> >
> >
>
>
>
>



-- 
Peter Cseh
Software Engineer

[jira] [Commented] (OOZIE-2812) SparkConfigurationService should support loading configurations from multiple Spark versions

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937447#comment-15937447
 ] 

Hadoop QA commented on OOZIE-2812:
--

Testing JIRA OOZIE-2812

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 1 line(s) longer than 132 
characters
.{color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:red}-1{color} There are [444] new bugs found below threshold in total 
that must be fixed.
.{color:red}-1{color} There are [98] new bugs found below threshold in 
[server] that must be fixed.
.You can find the FindBugs diff here (look for the red and orange ones): 
server/findbugs-new.html
.The most important FindBugs errors are:
.At CLIParser.java:[line 169]: Found reliance on default encoding in 
org.apache.oozie.cli.CLIParser.showHelp(CommandLine): new 
java.io.PrintWriter(OutputStream)
.At CLIParser.java:[line 57]: new org.apache.oozie.cli.CLIParser(String, 
String[]) may expose internal representation by storing an externally mutable 
object into CLIParser.cliHelp
.At CLIParser.java:[lines 80-104]: Should 
org.apache.oozie.cli.CLIParser$Command be a _static_ inner class?
.At OozieCLI.java:[line 845]: Found reliance on default encoding in 
org.apache.oozie.cli.OozieCLI.getConfiguration(OozieClient, CommandLine): new 
java.io.FileReader(File)
.At OozieCLI.java:[line 2175]: Found reliance on default encoding in 
org.apache.oozie.cli.OozieCLI.validateCommandV41(CommandLine): new 
java.io.FileReader(File)
.Obligation to clean up resource created at OozieCLI.java:[line 848] is not 
discharged: org.apache.oozie.cli.OozieCLI.getConfiguration(OozieClient, 
CommandLine) may fail to clean up java.io.InputStream
.Path continues at OozieCLI.java:[line 858]: Path continues at 
OozieCLI.java:[line 854]
.Obligation to clean up resource created at OozieCLI.java:[line 845] is not 
discharged: org.apache.oozie.cli.OozieCLI.getConfiguration(OozieClient, 
CommandLine) may fail to clean up java.io.Reader
.Path continues at OozieCLI.java:[line 858]: Path continues at 
OozieCLI.java:[line 854]
.At OozieCLI.java:[line 845]: 
org.apache.oozie.cli.OozieCLI.getConfiguration(OozieClient, CommandLine) may 
fail to close stream
.At OozieCLI.java:[line 2178]: Exception is caught when Exception is not 
thrown in org.apache.oozie.cli.OozieCLI.validateCommandV41(CommandLine)
.At OozieCLI.java:[line 1407]: Format-string method String.format(String, 
Object[]) called with format string "%-43s%-10s%-37s%-10s%-21s%-21s" wants 6 
arguments but is given 7 in 
org.apache.oozie.cli.OozieCLI.printCoordJob(CoordinatorJob, String, boolean)
.At AuthOozieClient.java:[line 218]: Found reliance on default encoding in 
org.apache.oozie.client.AuthOozieClient.readAuthToken(): new 
java.io.FileReader(File)
.At AuthOozieClient.java:[line 248]: Found reliance on default encoding in 
org.apache.oozie.client.AuthOozieClient.writeAuthToken(AuthenticatedURL$Token): 
new java.io.FileWriter(File)
.At AuthOozieClient.java:[line 285]: Load of known null value in 
org.apache.oozie.client.AuthOozieClient.getAuthenticator()
.At AuthOozieClient.java:[line 326]: Load of known null value in 
org.apache.oozie.client.AuthOozieClient.getAuthenticator()
.Obligation to clean up resource created at AuthOozieClient.java:[line 248] 
is not discharged: 
org.apache.oozie.client.AuthOozieClient.writeAuthToken(AuthenticatedURL$Token) 
may fail to clean up java.io.Writer on checked exception
.Path continues at AuthOozieClient.java:[line 257]: Path continues at 
AuthOozieClient.java:[line 249]
.Path continues at AuthOozieClient.java:[line 264]: Path continues at 
AuthOozieClient.java:[line 261]
.At AuthOozieClient.java:[line 129]: Exceptional return value of 
java.io.File.delete() ignored in 
org.apache.oozie.client.AuthOozieClient.createConnection(URL, String)
.Another occurrence at AuthOozieClient.java:[line 159]: Another occurrence 
at AuthOozieClient.java:[line 143]
.Exceptional return value of java.io.File.delete() ignored in 

Build failed in Jenkins: oozie-trunk-precommit-build #3720

[Apache Jenkins Server]

See 


--
[...truncated 1.21 MB...]
At HCatAccessorService.java:[line 74]: Write to static field 
org.apache.oozie.service.HCatAccessorService.LOG from instance method 
org.apache.oozie.service.HCatAccessorService.init(Services)
Obligation to clean up resource created at HadoopAccessorService.java:[line 
426] is not discharged: 
org.apache.oozie.service.HadoopAccessorService.readActionConfFile(File) may 
fail to clean up java.io.InputStream
Path continues at HadoopAccessorService.java:[line 428]: Path continues at 
HadoopAccessorService.java:[line 427]
Path continues at HadoopAccessorService.java:[line 433]: Path continues at 
HadoopAccessorService.java:[line 432]
Path continues at HadoopAccessorService.java:[line 440]: Path continues at 
HadoopAccessorService.java:[line 434]
At InstrumentationService.java:[line 42]: 
org.apache.oozie.service.InstrumentationService.instrumentation should be 
package protected
At InstrumentationService.java:[line 122]: Write to static field 
org.apache.oozie.service.InstrumentationService.instrumentation from instance 
method org.apache.oozie.service.InstrumentationService.destroy()
At InstrumentationService.java:[line 121]: Write to static field 
org.apache.oozie.service.InstrumentationService.isEnabled from instance method 
org.apache.oozie.service.InstrumentationService.destroy()
At InstrumentationService.java:[line 74]: Write to static field 
org.apache.oozie.service.InstrumentationService.instrumentation from instance 
method org.apache.oozie.service.InstrumentationService.init(Services)
At InstrumentationService.java:[line 75]: Write to static field 
org.apache.oozie.service.InstrumentationService.isEnabled from instance method 
org.apache.oozie.service.InstrumentationService.init(Services)
Unsynchronized access at JMSAccessorService.java:[line 331]: Inconsistent 
synchronization of 
org.apache.oozie.service.JMSAccessorService.jmsProducerConnContext; locked 42% 
of time
Unsynchronized access at JMSAccessorService.java:[line 278]: Unsynchronized 
access at JMSAccessorService.java:[line 332]
Unsynchronized access at JMSAccessorService.java:[line 279]: Unsynchronized 
access at JMSAccessorService.java:[line 278]
Synchronized access at JMSAccessorService.java:[line 283]: Unsynchronized 
access at JMSAccessorService.java:[line 298]
Synchronized access at JMSAccessorService.java:[line 285]: Synchronized 
access at JMSAccessorService.java:[line 283]
Synchronized access at JMSAccessorService.java:[line 287]: Synchronized 
access at JMSAccessorService.java:[line 286]
Write to static field org.apache.oozie.service.JMSAccessorService.LOG from 
instance method org.apache.oozie.service.JMSAccessorService.init(Services): 
Synchronized access at JMSAccessorService.java:[line 287]
Write to static field org.apache.oozie.service.JMSTopicService.LOG from 
instance method org.apache.oozie.service.JMSTopicService.init(Services): At 
JMSAccessorService.java:[line 85]
Write to static field org.apache.oozie.service.JPAService.LOG from instance 
method org.apache.oozie.service.JPAService.init(Services): At 
JMSTopicService.java:[line 99]
Write to static field org.apache.oozie.service.JobsConcurrencyService.urls 
from instance method 
org.apache.oozie.service.JobsConcurrencyService.init(Services): At 
JPAService.java:[line 141]
Write to static field 
org.apache.oozie.service.MetricsInstrumentationService.isEnabled from instance 
method org.apache.oozie.service.MetricsInstrumentationService.destroy(): At 
JobsConcurrencyService.java:[line 47]
Write to static field 
org.apache.oozie.service.InstrumentationService.instrumentation from instance 
method org.apache.oozie.service.MetricsInstrumentationService.init(Services): 
At MetricsInstrumentationService.java:[line 54]
Write to static field 
org.apache.oozie.service.MetricsInstrumentationService.isEnabled from instance 
method org.apache.oozie.service.MetricsInstrumentationService.init(Services): 
At MetricsInstrumentationService.java:[line 45]
Unread field: 
org.apache.oozie.service.PartitionDependencyManagerService$CachePurgeWorker.cache:
 At MetricsInstrumentationService.java:[line 46]
Possible null pointer dereference of bundleJob in 
org.apache.oozie.service.RecoveryService$RecoveryRunnable.runBundleRecovery(): 
At PartitionDependencyManagerService.java:[line 96]
Null value at RecoveryService.java:[line 208]: Dereferenced at 
RecoveryService.java:[line 213]
Initialization of org.apache.oozie.service.Service accesses class 
org.apache.oozie.service.ConfigurationService, which isn't initialized yet: 
Known null at RecoveryService.java:[line 209]
Incorrect lazy initialization of static field 
org.apache.oozie.service.Services.SERVICES in new 
org.apache.oozie.service.Services(): At Service.java:[line 56]

[jira] [Commented] (OOZIE-1770) Create Oozie Application Master for YARN

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937339#comment-15937339
 ] 

Hadoop QA commented on OOZIE-1770:
--

Testing JIRA OOZIE-1770

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:red}-1{color} the patch contains 75 line(s) with tabs
.{color:red}-1{color} the patch contains 17 line(s) with trailing spaces
.{color:red}-1{color} the patch contains 10 line(s) longer than 132 
characters
.{color:green}+1{color} the patch does adds/modifies 60 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:red}-1 JAVADOC{color}
.{color:red}-1{color} the patch seems to introduce 6 new Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:red}-1{color} There are [341] new bugs found below threshold in total 
that must be fixed.
.{color:green}+1{color} There are no new bugs found in [client].
.{color:red}-1{color} There are [19] new bugs found below threshold in 
[sharelib/hive] that must be fixed.
.You can find the FindBugs diff here (look for the red and orange ones): 
sharelib/hive/findbugs-new.html
.The most important FindBugs errors are:
.At LauncherMain.java:[line 89]: Found reliance on default encoding in 
org.apache.oozie.action.hadoop.LauncherMain.getHadoopJobIds(String, Pattern[]): 
new java.io.FileReader(String)
.At LauncherMain.java:[line 125]: Found reliance on default encoding in 
org.apache.oozie.action.hadoop.LauncherMain.writeExternalChildIDs(String, 
Pattern[], String): String.getBytes()
.At LauncherMain.java:[line 75]: 
org.apache.oozie.action.hadoop.LauncherMain.HADOOP_SITE_FILES should be both 
final and package protected
.At LauncherMain.java:[line 345]: Exceptional return value of 
java.io.File.mkdirs() ignored in 
org.apache.oozie.action.hadoop.LauncherMain.writeHadoopConfig(String, File)
.At LauncherMapper.java:[line 410]: Found reliance on default encoding in 
org.apache.oozie.action.hadoop.LauncherMapper.getLocalFileContentStr(File, 
String, int): new java.io.FileReader(File)
.At LauncherMapper.java:[line 358]: Found reliance on default encoding in 
org.apache.oozie.action.hadoop.LauncherMapper.propagateToHadoopConf(): new 
java.io.FileWriter(String)
.At LauncherMapper.java:[line 359]: Found reliance on default encoding in 
org.apache.oozie.action.hadoop.LauncherMapper.propagateToHadoopConf(): new 
java.io.OutputStreamWriter(OutputStream)
.At LauncherMapper.java:[line 108]: Found reliance on default encoding in 
org.apache.oozie.action.hadoop.LauncherMapper.setRecoveryId(Configuration, 
Path, String): new java.io.InputStreamReader(InputStream)
.At LauncherMapper.java:[line 98]: Found reliance on default encoding in 
org.apache.oozie.action.hadoop.LauncherMapper.setRecoveryId(Configuration, 
Path, String): new java.io.OutputStreamWriter(OutputStream)
.Obligation to clean up resource created at LauncherMapper.java:[line 410] 
is not discharged: 
org.apache.oozie.action.hadoop.LauncherMapper.getLocalFileContentStr(File, 
String, int) may fail to clean up java.io.Reader on checked exception
.Path continues at LauncherMapper.java:[line 413]: Path continues at 
LauncherMapper.java:[line 411]
.org.apache.oozie.action.hadoop.LauncherMapper.propagateToHadoopConf() may 
fail to clean up java.io.Writer on checked exception: Path continues at 
LauncherMapper.java:[line 414]
.Write to static field 
org.apache.oozie.action.hadoop.LauncherSecurityManager.exitCode from instance 
method org.apache.oozie.action.hadoop.LauncherSecurityManager.checkExit(int): 
Obligation to clean up resource created at LauncherMapper.java:[line 358] is 
not discharged
.Write to static field 
org.apache.oozie.action.hadoop.LauncherSecurityManager.exitInvoked from 
instance method 
org.apache.oozie.action.hadoop.LauncherSecurityManager.checkExit(int): At 
LauncherMapper.java:[line 687]
.Found reliance on default encoding in 
org.apache.oozie.action.hadoop.MapReduceMain.writeJobIdFile(File, String): 
String.getBytes(): At LauncherMapper.java:[line 686]
.org.apache.oozie.action.hadoop.MapReduceMain.writeJobIdFile(File, String) 
may fail to clean up java.io.OutputStream on checked exception: At 
MapReduceMain.java:[line 85]
.Path continues at MapReduceMain.java:[line 85]: Obligation to clean up 
resource created at MapReduceMain.java:[line 84] is not discharged
.At ShellMain.java:[line 228]: Found reliance on default encoding in 

[jira] [Resolved] (OOZIE-2762) Oozie workflow stuck in RUNNING state and does not progress to next action due to unique contraint violation exception for "wf_actions_pkey"

[Gopi Krishnan Nambiar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gopi Krishnan Nambiar resolved OOZIE-2762.
--
Resolution: Not A Bug

> Oozie workflow stuck in RUNNING state and does not progress to next action 
> due to unique contraint violation exception for "wf_actions_pkey"
> 
>
> Key: OOZIE-2762
> URL: https://issues.apache.org/jira/browse/OOZIE-2762
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.1
>Reporter: Gopi Krishnan Nambiar
>
> -bash-4.1$ oozie job -oozie http://localhost:11000/oozie --info  
> 141-161216105202698-oozie-oozi-C
> Job ID : 141-161216105202698-oozie-oozi-C
> 
> Job Name: coord
> App Path: hdfs://URL/user/oozie/examples/apps/applog/coordinator.xml
> Status  : RUNNING
> Start Time  : 2016-10-05 00:00 GMT
> End Time: 2016-10-05 23:59 GMT
> Pause Time  : -
> Concurrency : 2
> 
> ID StatusExt ID   
> Err Code  Created  Nominal Time 
> 141-161216105202698-oozie-oozi-C@1 RUNNING   
> 142-161216105202698-oozie-oozi-W - 2016-12-21 18:08 GMT 
> 2016-10-05 00:00 GMT 
> 
> -bash-4.1$ oozie job -oozie http://localhost:11000/oozie --info 
> 142-161216105202698-oozie-oozi-W
> Job ID : 142-161216105202698-oozie-oozi-W
> 
> Workflow Name : conversion-wf
> App Path  : hdfs://URL/user/oozie/examples/apps/applog
> Status: RUNNING
> Run   : 0
> User  : sfdc
> Group : -
> Created   : 2016-12-21 18:08 GMT
> Started   : 2016-12-21 18:08 GMT
> Last Modified : 2016-12-21 18:39 GMT
> Ended : -
> CoordAction ID: 141-161216105202698-oozie-oozi-C@1
> Actions
> 
> ID
> StatusExt ID Ext Status Err Code  
> 
> 142-161216105202698-oozie-oozi-W@:start:  
> OK-  OK - 
> 
> 142-161216105202698-oozie-oozi-W@decisionNode 
> OK-  conversionJob- 
> 
> 142-161216105202698-oozie-oozi-W@conversionJob
> OKjob_1481654882437_6310 SUCCEEDED  - 
> 
> 142-161216105202698-oozie-oozi-W@findHivePartitions   OK  
>   job_1481654882437_6325 SUCCEEDED  - 
> 
> Exception:
> {noformat}
> Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: ERROR: 
> duplicate key value violates unique constraint "wf_actions_pkey"
>   Detail: Key 
> (id)=(142-161216105202698-oozie-oozi-W@findHiveInstancePartitions) 
> already exists. {prepstmnt 67637986 INSERT INTO WF_ACTIONS (id, conf, 
> console_url, cred, data, error_code, error_message, external_child_ids, 
> external_id, external_status, name, retries, stats, tracker_uri, transition, 
> type, user_retry_count, user_retry_interval, user_retry_max, bean_type, 
> end_time, execution_path, last_check_time, log_token, pending, pending_age, 
> signal_value, sla_xml, start_time, status, wf_id) VALUES (?, ?, ?, ?, ?, ?, 
> ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)} 
> [code=0, state=23505]
>   at 
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
>   at 
> 

Build failed in Jenkins: oozie-trunk-precommit-build #3719

[Apache Jenkins Server]

See 


Changes:

[gezapeti] OOZIE-2817 amend Increase test case stability in pre-commit job

[gezapeti] OOZIE-2811 amend Add support for filtering out properties from

--
[...truncated 1.11 MB...]
Dead store to actionList in 
org.apache.oozie.executor.jpa.WorkflowActionSubsetGetJPAExecutor.execute(EntityManager):
 At SLASummaryQueryExecutor.java:[lines 122-126]

org.apache.oozie.executor.jpa.sla.SLASummaryGetForFilterJPAExecutor$SLASummaryFilter.getNominalEnd()
 may expose internal representation by returning 
SLASummaryGetForFilterJPAExecutor$SLASummaryFilter.nominalEnd: At 
WorkflowActionSubsetGetJPAExecutor.java:[line 64]

org.apache.oozie.executor.jpa.sla.SLASummaryGetForFilterJPAExecutor$SLASummaryFilter.getNominalStart()
 may expose internal representation by returning 
SLASummaryGetForFilterJPAExecutor$SLASummaryFilter.nominalStart: At 
SLASummaryGetForFilterJPAExecutor.java:[line 310]

org.apache.oozie.executor.jpa.sla.SLASummaryGetForFilterJPAExecutor$SLASummaryFilter.setNominalEnd(Date)
 may expose internal representation by storing an externally mutable object 
into SLASummaryGetForFilterJPAExecutor$SLASummaryFilter.nominalEnd: At 
SLASummaryGetForFilterJPAExecutor.java:[line 302]

org.apache.oozie.executor.jpa.sla.SLASummaryGetForFilterJPAExecutor$SLASummaryFilter.setNominalStart(Date)
 may expose internal representation by storing an externally mutable object 
into SLASummaryGetForFilterJPAExecutor$SLASummaryFilter.nominalStart: At 
SLASummaryGetForFilterJPAExecutor.java:[line 314]
Result of integer multiplication cast to long in 
org.apache.oozie.executor.jpa.sla.SLASummaryGetRecordsOnRestartJPAExecutor.execute(EntityManager):
 At SLASummaryGetForFilterJPAExecutor.java:[line 306]
Write to static field org.apache.oozie.jms.JMSJobEventListener.LOG from 
instance method org.apache.oozie.jms.JMSJobEventListener.init(Configuration): 
At SLASummaryGetRecordsOnRestartJPAExecutor.java:[line 53]
Write to static field org.apache.oozie.jms.JMSSLAEventListener.LOG from 
instance method org.apache.oozie.jms.JMSSLAEventListener.init(Configuration): 
At JMSJobEventListener.java:[line 68]
Synchronization performed on java.util.concurrent.ConcurrentMap in 
org.apache.oozie.lock.MemoryLocks.getLock(String, MemoryLocksService$Type, 
long): At JMSSLAEventListener.java:[line 54]
Should org.apache.oozie.lock.MemoryLocks$MemoryLockToken be a _static_ 
inner class?: At MemoryLocks.java:[line 109]
Write to static field 
org.apache.oozie.service.AbandonedCoordCheckerService.serverURL from instance 
method org.apache.oozie.service.AbandonedCoordCheckerService.init(Services): At 
MemoryLocks.java:[lines 43-62]
Write to static field 
org.apache.oozie.service.AbandonedCoordCheckerService.to from instance method 
org.apache.oozie.service.AbandonedCoordCheckerService.init(Services): At 
AbandonedCoordCheckerService.java:[line 177]
Result of integer multiplication cast to long in 
org.apache.oozie.service.AbandonedCoordCheckerService$AbandonedCoordCheckerRunnable.checkCoordJobs():
 At AbandonedCoordCheckerService.java:[line 174]
Found reliance on default encoding in 
org.apache.oozie.service.AuthorizationService.loadAdminUsers(): new 
java.io.InputStreamReader(InputStream): At 
AbandonedCoordCheckerService.java:[line 96]
org.apache.oozie.service.AuthorizationService.loadAdminUsers() may fail to 
close stream: At AuthorizationService.java:[line 172]
org.apache.oozie.service.CallableQueueService$CompositeCallable.toString() 
may return null: At AuthorizationService.java:[line 172]
org.apache.oozie.service.ConfigurationService.loadConf() may fail to clean 
up java.io.InputStream: At CallableQueueService.java:[line 357]
Path continues at ConfigurationService.java:[line 240]: Obligation to clean 
up resource created at ConfigurationService.java:[line 239] is not discharged
Path continues at ConfigurationService.java:[line 242]: Path continues at 
ConfigurationService.java:[line 241]
Path continues at ConfigurationService.java:[line 249]: Path continues at 
ConfigurationService.java:[line 247]
Path continues at ConfigurationService.java:[line 265]: Path continues at 
ConfigurationService.java:[line 264]
Path continues at ConfigurationService.java:[line 276]: Path continues at 
ConfigurationService.java:[line 269]
Path continues at ConfigurationService.java:[line 296]: Path continues at 
ConfigurationService.java:[line 288]
At ConfigurationService.java:[line 143]: Write to static field 
org.apache.oozie.service.ConfigurationService.log from instance method new 
org.apache.oozie.service.ConfigurationService()
At ConfigurationService.java:[lines 315-420]: Should 
org.apache.oozie.service.ConfigurationService$LogChangesConfiguration be a 
_static_ inner class?
At 

[jira] [Commented] (OOZIE-2762) Oozie workflow stuck in RUNNING state and does not progress to next action due to unique contraint violation exception for "wf_actions_pkey"

[Gopi Krishnan Nambiar (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937333#comment-15937333
 ] 

Gopi Krishnan Nambiar commented on OOZIE-2762:
--

Related to oozie HA. Non HA versions deployed on multiple hosts caused the 
issue. Hence closing this.

> Oozie workflow stuck in RUNNING state and does not progress to next action 
> due to unique contraint violation exception for "wf_actions_pkey"
> 
>
> Key: OOZIE-2762
> URL: https://issues.apache.org/jira/browse/OOZIE-2762
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.1
>Reporter: Gopi Krishnan Nambiar
>
> -bash-4.1$ oozie job -oozie http://localhost:11000/oozie --info  
> 141-161216105202698-oozie-oozi-C
> Job ID : 141-161216105202698-oozie-oozi-C
> 
> Job Name: coord
> App Path: hdfs://URL/user/oozie/examples/apps/applog/coordinator.xml
> Status  : RUNNING
> Start Time  : 2016-10-05 00:00 GMT
> End Time: 2016-10-05 23:59 GMT
> Pause Time  : -
> Concurrency : 2
> 
> ID StatusExt ID   
> Err Code  Created  Nominal Time 
> 141-161216105202698-oozie-oozi-C@1 RUNNING   
> 142-161216105202698-oozie-oozi-W - 2016-12-21 18:08 GMT 
> 2016-10-05 00:00 GMT 
> 
> -bash-4.1$ oozie job -oozie http://localhost:11000/oozie --info 
> 142-161216105202698-oozie-oozi-W
> Job ID : 142-161216105202698-oozie-oozi-W
> 
> Workflow Name : conversion-wf
> App Path  : hdfs://URL/user/oozie/examples/apps/applog
> Status: RUNNING
> Run   : 0
> User  : sfdc
> Group : -
> Created   : 2016-12-21 18:08 GMT
> Started   : 2016-12-21 18:08 GMT
> Last Modified : 2016-12-21 18:39 GMT
> Ended : -
> CoordAction ID: 141-161216105202698-oozie-oozi-C@1
> Actions
> 
> ID
> StatusExt ID Ext Status Err Code  
> 
> 142-161216105202698-oozie-oozi-W@:start:  
> OK-  OK - 
> 
> 142-161216105202698-oozie-oozi-W@decisionNode 
> OK-  conversionJob- 
> 
> 142-161216105202698-oozie-oozi-W@conversionJob
> OKjob_1481654882437_6310 SUCCEEDED  - 
> 
> 142-161216105202698-oozie-oozi-W@findHivePartitions   OK  
>   job_1481654882437_6325 SUCCEEDED  - 
> 
> Exception:
> {noformat}
> Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: ERROR: 
> duplicate key value violates unique constraint "wf_actions_pkey"
>   Detail: Key 
> (id)=(142-161216105202698-oozie-oozi-W@findHiveInstancePartitions) 
> already exists. {prepstmnt 67637986 INSERT INTO WF_ACTIONS (id, conf, 
> console_url, cred, data, error_code, error_message, external_child_ids, 
> external_id, external_status, name, retries, stats, tracker_uri, transition, 
> type, user_retry_count, user_retry_interval, user_retry_max, bean_type, 
> end_time, execution_path, last_check_time, log_token, pending, pending_age, 
> signal_value, sla_xml, start_time, status, wf_id) VALUES (?, ?, ?, ?, ?, ?, 
> ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)} 
> [code=0, state=23505]
>   at 
> 

[jira] [Updated] (OOZIE-2812) SparkConfigurationService should support loading configurations from multiple Spark versions

[Peter Cseh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Cseh updated OOZIE-2812:
--
Attachment: OOZIE-2812.004.patch

Updating the patch based on RB.
I still have to add some tests.

> SparkConfigurationService should support loading configurations from multiple 
> Spark versions
> 
>
> Key: OOZIE-2812
> URL: https://issues.apache.org/jira/browse/OOZIE-2812
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2812.001.patch, OOZIE-2812.002.patch, 
> OOZIE-2812.003.patch, OOZIE-2812.004.patch
>
>
> Right now SparkConfigruationService serves one Spark configuration set by
> {{oozie.service.SparkConfigurationService.spark.configurations}}
> We cloud improve this to support more versions depending on the name of the 
> sharelib.
> E.g. the property could change to
> oozie.service.SparkConfigurationService..configurations
> This would be backward compatible as the name for the default Spark sharelib 
> is spark while it would be possible to add a sharelib named spark2 or 
> spark2.1 and define itheir configuration via 
> oozie.service.SparkConfigurationService.spark2.configurations and
> oozie.service.SparkConfigurationService.spark2.1.configurations.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (OOZIE-2812) SparkConfigurationService should support loading configurations from multiple Spark versions

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937259#comment-15937259
 ] 

Peter Cseh edited comment on OOZIE-2812 at 3/22/17 10:12 PM:
-

Thanks for the feedback! Updating the patch based on RB.
I still have to add some tests.


was (Author: gezapeti):
Updating the patch based on RB.
I still have to add some tests.

> SparkConfigurationService should support loading configurations from multiple 
> Spark versions
> 
>
> Key: OOZIE-2812
> URL: https://issues.apache.org/jira/browse/OOZIE-2812
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2812.001.patch, OOZIE-2812.002.patch, 
> OOZIE-2812.003.patch, OOZIE-2812.004.patch
>
>
> Right now SparkConfigruationService serves one Spark configuration set by
> {{oozie.service.SparkConfigurationService.spark.configurations}}
> We cloud improve this to support more versions depending on the name of the 
> sharelib.
> E.g. the property could change to
> oozie.service.SparkConfigurationService..configurations
> This would be backward compatible as the name for the default Spark sharelib 
> is spark while it would be possible to add a sharelib named spark2 or 
> spark2.1 and define itheir configuration via 
> oozie.service.SparkConfigurationService.spark2.configurations and
> oozie.service.SparkConfigurationService.spark2.1.configurations.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 57680: OOZIE-2812 SparkConfigurationService should support loading configurations from multiple Spark versions

[Peter Cseh]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/57680/
---

(Updated March 22, 2017, 10:10 p.m.)


Review request for oozie.


Bugs: OOZIE-2812
https://issues.apache.org/jira/browse/OOZIE-2812


Repository: oozie-git


Description
---

OOZIE-2812
SparkConfigurationService should support loading configurations from multiple 
Spark versions


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java 
1a3197abb52f80b545dcc8634a8cac7a281a9eac 
  core/src/main/java/org/apache/oozie/service/SparkConfigurationService.java 
b15cce0d6813375778abf1d2bbe09e83734d19f0 
  
core/src/main/java/org/apache/oozie/service/sparkconfiguration/SparkConfigReader.java
 PRE-CREATION 
  
core/src/main/java/org/apache/oozie/service/sparkconfiguration/SparkConfigurationStorage.java
 PRE-CREATION 
  core/src/main/resources/oozie-default.xml 
03f428a47e34f2d07ea8fff755f29d222d6aeb9a 
  
core/src/test/java/org/apache/oozie/service/TestSparkConfigurationService.java 
1278efa0775c32c16cb38309ab8e92e08d4eb2ec 
  
core/src/test/java/org/apache/oozie/service/sparkconfiguration/TestSparkConfigurationStorage.java
 PRE-CREATION 
  docs/src/site/twiki/DG_SparkActionExtension.twiki 
863bd89cf576d2fb7be76c61ca139218c33a5f66 


Diff: https://reviews.apache.org/r/57680/diff/3/

Changes: https://reviews.apache.org/r/57680/diff/2-3/


Testing
---


Thanks,

Peter Cseh

Re: Review Request 57680: OOZIE-2812 SparkConfigurationService should support loading configurations from multiple Spark versions

[Peter Cseh]

> On March 21, 2017, 11:05 p.m., Robert Kanter wrote:
> > core/src/main/resources/oozie-default.xml
> > Lines 2893-2903 (original)
> > 
> >
> > Shouldn't we leave this here for now?

I don't know how log we should keep this. The blacklist property already serves 
the same purpose and the code is in place to handle backwards compatiblity. We 
can keep it here until the next release or so.


- Peter


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/57680/#review169633
---


On March 21, 2017, 1:50 p.m., Peter Cseh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57680/
> ---
> 
> (Updated March 21, 2017, 1:50 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2812
> https://issues.apache.org/jira/browse/OOZIE-2812
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2812
> SparkConfigurationService should support loading configurations from multiple 
> Spark versions
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java 
> 1a3197abb52f80b545dcc8634a8cac7a281a9eac 
>   core/src/main/java/org/apache/oozie/service/SparkConfigurationService.java 
> b15cce0d6813375778abf1d2bbe09e83734d19f0 
>   
> core/src/main/java/org/apache/oozie/service/sparkconfiguration/SparkConfigReader.java
>  PRE-CREATION 
>   
> core/src/main/java/org/apache/oozie/service/sparkconfiguration/SparkConfigurationStorage.java
>  PRE-CREATION 
>   core/src/main/resources/oozie-default.xml 
> b481887122be0112c763ad667d1de18747d1ad9b 
>   
> core/src/test/java/org/apache/oozie/service/TestSparkConfigurationService.java
>  0e00a457890d1f4b8e86c19043cd597928cdd9bb 
>   
> core/src/test/java/org/apache/oozie/service/sparkconfiguration/TestSparkConfigurationStorage.java
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/57680/diff/2/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Peter Cseh
> 
>

Re: Review Request 54705: OOZIE-1770: Create Oozie Application Master for YARN

[Peter Cseh]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54705/
---

(Updated March 22, 2017, 8:34 p.m.)


Review request for oozie, Purshotam Shah, Robert Kanter, and Rohini Palaniswamy.


Repository: oozie-git


Description
---

Replacing the launcher MR job with a launcher AM


Diffs (updated)
-

  bin/test-patch-20-tests 22f472c07e80fdb38c632329a5707998ab352172 
  client/pom.xml f99366c90887a5a45f3942291c90e1cdbfd84b3f 
  client/src/main/java/org/apache/oozie/cli/OozieCLI.java 
38fb84e8a8918aee6ae57d19a29cdf181aba1955 
  client/src/main/java/org/apache/oozie/cli/ValidationUtil.java 
b1da2af070970add01031d6208a395520cd7055c 
  client/src/main/java/org/apache/oozie/client/OozieClient.java 
73708080e624e775f7d058cd3377ad69d8399264 
  client/src/main/java/org/apache/oozie/client/XOozieClient.java 
8538ec7c742cc013f7c18eaff3ecf61c2835cc8a 
  client/src/main/java/org/apache/oozie/client/rest/JsonTags.java 
ca168e084998b5dd564536078a7a69efd7291828 
  client/src/main/java/org/apache/oozie/client/rest/RestConstants.java 
8ddb1f873f0c69aadf5f4a5161d8b21f7392fa1e 
  core/pom.xml 1dd104581ccab7976d788b674d2200e48a70c27f 
  core/src/main/java/org/apache/oozie/WorkflowJobBean.java 
55d79a5d5e5e4efab9eb832e9341a16bcf8959cc 
  core/src/main/java/org/apache/oozie/action/ActionExecutor.java 
1d6456b236bf9e27c0f55d9f9e3b4bd94517c797 
  core/src/main/java/org/apache/oozie/action/hadoop/Credentials.java 
eadb47b07d157f45f086517ab41c4b9826f003f0 
  core/src/main/java/org/apache/oozie/action/hadoop/CredentialsProvider.java 
6fe22fbd2fca5d873d58ece60f20d0f131371475 
  
core/src/main/java/org/apache/oozie/action/hadoop/CredentialsProviderFactory.java
 PRE-CREATION 
  core/src/main/java/org/apache/oozie/action/hadoop/DistcpActionExecutor.java 
78cd257a836707c1efeac13566d6285d42970545 
  core/src/main/java/org/apache/oozie/action/hadoop/FsActionExecutor.java 
27654741101d2056b25626fbbe345183eafd612d 
  core/src/main/java/org/apache/oozie/action/hadoop/FsELFunctions.java 
801bfe6eb212b549888f0e9fb7df7b65bcf59393 
  core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentialHelper.java 
36ad1df727e869b8051481ad969771e91bc6ae07 
  core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentials.java 
d7689a924059e553abaeed374eed4072933292cb 
  core/src/main/java/org/apache/oozie/action/hadoop/HadoopELFunctions.java 
ad2a71d641caa71efc098ad00bfbab3cec4d9506 
  core/src/main/java/org/apache/oozie/action/hadoop/HbaseCredentials.java 
307f565786ad77f5a35b5790bd5b052b04c6eac8 
  core/src/main/java/org/apache/oozie/action/hadoop/Hive2ActionExecutor.java 
2aed936af75da38c433be5d202bdc01c2f612c76 
  core/src/main/java/org/apache/oozie/action/hadoop/Hive2Credentials.java 
bd2f1f768c5b04bef4a33613baede9202144c747 
  core/src/main/java/org/apache/oozie/action/hadoop/HiveActionExecutor.java 
8e2453ef4f78f4a5f1f95b1ca2793f5d7e07ad81 
  core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
39daca7b3050c259a36d54710b4c1279f3acdeac 
  core/src/main/java/org/apache/oozie/action/hadoop/LauncherMapperHelper.java 
9609fdc2f3440fb176b659ef16c2a23451724cf9 
  
core/src/main/java/org/apache/oozie/action/hadoop/MapReduceActionExecutor.java 
55c937249ac35e14bd63dd0c1fa962ea636afa3a 
  core/src/main/java/org/apache/oozie/action/hadoop/OozieJobInfo.java 
581d3b3219eff882f961c8e495611e873c6a5a52 
  core/src/main/java/org/apache/oozie/action/hadoop/PigActionExecutor.java 
8b2dc16db80ad602911f1f64e60cfad41b198922 
  
core/src/main/java/org/apache/oozie/action/hadoop/ScriptLanguageActionExecutor.java
 92e149d5cac6509893c8507b776263a38312a53b 
  core/src/main/java/org/apache/oozie/action/hadoop/ShellActionExecutor.java 
b9ffa7ab7ec87db8a76a3653c74974d296c8cd17 
  core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java 
1a3197abb52f80b545dcc8634a8cac7a281a9eac 
  core/src/main/java/org/apache/oozie/action/hadoop/SqoopActionExecutor.java 
22e28746a9a39ae6c1e22326cc4f8f759d820b20 
  core/src/main/java/org/apache/oozie/action/ssh/SshActionExecutor.java 
5fd30f7858c5c4c70dcbdb6df86904518d92f7f3 
  core/src/main/java/org/apache/oozie/client/rest/BulkResponseImpl.java 
fb021bd022d199f93fc5674843514abf45ae12a5 
  core/src/main/java/org/apache/oozie/command/PurgeXCommand.java 
2ba1999ba7d5e892bd7e37d5fd8d1f926a84b48b 
  core/src/main/java/org/apache/oozie/command/XCommand.java 
bdf13f65ea25e8e0f5125e2798568a2c03fffe81 
  core/src/main/java/org/apache/oozie/command/wf/SubmitHttpXCommand.java 
d2a2742ae418070a1cd0a889f14194224bc944a6 
  core/src/main/java/org/apache/oozie/command/wf/SubmitMRXCommand.java 
cc61d3de813c75c7f1cf4d405fc043253e3ca4ea 
  
core/src/main/java/org/apache/oozie/command/wf/SubmitScriptLanguageXCommand.java
 9d413059e99bc676feb63e02a2f704048eb4a355 
  core/src/main/java/org/apache/oozie/command/wf/SubmitSqoopXCommand.java 

[jira] [Updated] (OOZIE-1770) Create Oozie Application Master for YARN

[Peter Cseh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Cseh updated OOZIE-1770:
--
Attachment: OOZIE-1770-010.patch

Addressing reviewboard issues. Thank you for the comments [~abhishekbafna]!

> Create Oozie Application Master for YARN
> 
>
> Key: OOZIE-1770
> URL: https://issues.apache.org/jira/browse/OOZIE-1770
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Bowen Zhang
>Assignee: Peter Cseh
> Attachments: OOZIE-1770-001.patch, OOZIE-1770-002.patch, 
> OOZIE-1770-003.patch, OOZIE-1770-004.patch, OOZIE-1770-005.patch, 
> OOZIE-1770-006.patch, OOZIE-1770-007.patch, OOZIE-1770-008.patch, 
> OOZIE-1770-009.patch, OOZIE-1770-010.patch, OozieYarnAM.pdf, oya.patch, 
> oya-rm-screenshot.jpg, OYA Scoping Doc 001.pdf, Prelim OYA Scoping Doc 
> 001.pdf, Prelim OYA Scoping Doc 002.pdf, Prelim OYA Scoping Doc 003.pdf
>
>
> After the first release of oozie on hadoop 2, it will be good if users can 
> set execution engine in oozie conf, be it YARN AM or traditional MR. We can 
> target this for post oozie 4.1 release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 54705: OOZIE-1770: Create Oozie Application Master for YARN

[Peter Cseh]

> On March 20, 2017, 5:34 p.m., Abhishek Bafna wrote:
> > core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java
> > Lines 1376 (patched)
> > 
> >
> > should not this be a error level message instead of debug?

We have a secondary mechanism to check the action status based on a file on 
HDFS. We'll throw an exception in line 1391 if the fallback mechanism fails. 
I've increased the log level to info to make it easier to find out why the 
initial check failed.


> On March 20, 2017, 5:34 p.m., Abhishek Bafna wrote:
> > core/src/main/java/org/apache/oozie/service/Services.java
> > Lines 307 (patched)
> > 
> >
> > Can we use a log instance to capture the stack trace?

I think it gets logged because of the exeption later. I've added a log entry to 
make it sure.


> On March 20, 2017, 5:34 p.m., Abhishek Bafna wrote:
> > core/src/main/resources/META-INF/persistence.xml
> > Lines 79 (patched)
> > 
> >
> > Will this print user credential information as well?
> > 
> > From 
> > here:https://openjpa.apache.org/builds/1.2.3/apache-openjpa/docs/ref_guide_dbsetup.html
> > 
> > PrintParameters: A boolean indicating whether SQL parameter values will 
> > be included in exception text and when logging is enabled. Since the 
> > parameter values may contain sensitive information the default value is 
> > false.

Good catch! This was added for development reasons.


> On March 20, 2017, 5:34 p.m., Abhishek Bafna wrote:
> > core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java
> > Line 122 (original), 113 (patched)
> > 
> >
> > I believe "yarn.resourcemanager.address" is defined as constant some 
> > where, can we use that. If not, please define as constant. Thanks.
> 
> Robert Kanter wrote:
> There's sort of two camps on this, but for tests, I like to hardcode 
> these sorts of things.  That way, if we (accidently) change the constant, it 
> breaks the test so we notice.

I think I'll create a constant for it in the test though.


- Peter


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54705/#review169460
---


On Jan. 23, 2017, 11:43 a.m., Peter Cseh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54705/
> ---
> 
> (Updated Jan. 23, 2017, 11:43 a.m.)
> 
> 
> Review request for oozie, Purshotam Shah, Robert Kanter, and Rohini 
> Palaniswamy.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Replacing the launcher MR job with a launcher AM
> 
> 
> Diffs
> -
> 
>   client/pom.xml f99366c90887a5a45f3942291c90e1cdbfd84b3f 
>   client/src/main/java/org/apache/oozie/cli/OozieCLI.java 
> 6e30d7eb667fe74440281fab3ca06c9f4df7bcf7 
>   client/src/main/java/org/apache/oozie/client/XOozieClient.java 
> 8538ec7c742cc013f7c18eaff3ecf61c2835cc8a 
>   core/pom.xml 1dd104581ccab7976d788b674d2200e48a70c27f 
>   core/src/main/java/org/apache/oozie/WorkflowJobBean.java 
> 55d79a5d5e5e4efab9eb832e9341a16bcf8959cc 
>   core/src/main/java/org/apache/oozie/action/ActionExecutor.java 
> 1d6456b236bf9e27c0f55d9f9e3b4bd94517c797 
>   core/src/main/java/org/apache/oozie/action/hadoop/Credentials.java 
> eadb47b07d157f45f086517ab41c4b9826f003f0 
>   core/src/main/java/org/apache/oozie/action/hadoop/CredentialsProvider.java 
> 6fe22fbd2fca5d873d58ece60f20d0f131371475 
>   
> core/src/main/java/org/apache/oozie/action/hadoop/CredentialsProviderFactory.java
>  PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/hadoop/DistcpActionExecutor.java 
> 78cd257a836707c1efeac13566d6285d42970545 
>   core/src/main/java/org/apache/oozie/action/hadoop/FsActionExecutor.java 
> 27654741101d2056b25626fbbe345183eafd612d 
>   core/src/main/java/org/apache/oozie/action/hadoop/FsELFunctions.java 
> 801bfe6eb212b549888f0e9fb7df7b65bcf59393 
>   core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentialHelper.java 
> 36ad1df727e869b8051481ad969771e91bc6ae07 
>   core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentials.java 
> d7689a924059e553abaeed374eed4072933292cb 
>   core/src/main/java/org/apache/oozie/action/hadoop/HadoopELFunctions.java 
> ad2a71d641caa71efc098ad00bfbab3cec4d9506 
>   core/src/main/java/org/apache/oozie/action/hadoop/HbaseCredentials.java 
> 307f565786ad77f5a35b5790bd5b052b04c6eac8 
>   core/src/main/java/org/apache/oozie/action/hadoop/Hive2ActionExecutor.java 
> 2aed936af75da38c433be5d202bdc01c2f612c76 

Re: Review Request 54705: OOZIE-1770: Create Oozie Application Master for YARN

[Peter Cseh]

> On Jan. 6, 2017, 7:19 a.m., Robert Kanter wrote:
> > core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java
> > Lines 262-266 (patched)
> > 
> >
> > We'll probably need to change the OozieActionConfigurator 
> > interface to use a Configuration object instead of a 
> > JobConf object.

The OozieActionConfigurator is used only for MR actions based on it's apidoc. 
Is the launchermapper itself configurable via this? If so we might want to drop 
that option. If it's related only for MR actions, we can keep the JobConf here.


- Peter


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54705/#review160656
---


On Jan. 23, 2017, 11:43 a.m., Peter Cseh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54705/
> ---
> 
> (Updated Jan. 23, 2017, 11:43 a.m.)
> 
> 
> Review request for oozie, Purshotam Shah, Robert Kanter, and Rohini 
> Palaniswamy.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Replacing the launcher MR job with a launcher AM
> 
> 
> Diffs
> -
> 
>   client/pom.xml f99366c90887a5a45f3942291c90e1cdbfd84b3f 
>   client/src/main/java/org/apache/oozie/cli/OozieCLI.java 
> 6e30d7eb667fe74440281fab3ca06c9f4df7bcf7 
>   client/src/main/java/org/apache/oozie/client/XOozieClient.java 
> 8538ec7c742cc013f7c18eaff3ecf61c2835cc8a 
>   core/pom.xml 1dd104581ccab7976d788b674d2200e48a70c27f 
>   core/src/main/java/org/apache/oozie/WorkflowJobBean.java 
> 55d79a5d5e5e4efab9eb832e9341a16bcf8959cc 
>   core/src/main/java/org/apache/oozie/action/ActionExecutor.java 
> 1d6456b236bf9e27c0f55d9f9e3b4bd94517c797 
>   core/src/main/java/org/apache/oozie/action/hadoop/Credentials.java 
> eadb47b07d157f45f086517ab41c4b9826f003f0 
>   core/src/main/java/org/apache/oozie/action/hadoop/CredentialsProvider.java 
> 6fe22fbd2fca5d873d58ece60f20d0f131371475 
>   
> core/src/main/java/org/apache/oozie/action/hadoop/CredentialsProviderFactory.java
>  PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/hadoop/DistcpActionExecutor.java 
> 78cd257a836707c1efeac13566d6285d42970545 
>   core/src/main/java/org/apache/oozie/action/hadoop/FsActionExecutor.java 
> 27654741101d2056b25626fbbe345183eafd612d 
>   core/src/main/java/org/apache/oozie/action/hadoop/FsELFunctions.java 
> 801bfe6eb212b549888f0e9fb7df7b65bcf59393 
>   core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentialHelper.java 
> 36ad1df727e869b8051481ad969771e91bc6ae07 
>   core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentials.java 
> d7689a924059e553abaeed374eed4072933292cb 
>   core/src/main/java/org/apache/oozie/action/hadoop/HadoopELFunctions.java 
> ad2a71d641caa71efc098ad00bfbab3cec4d9506 
>   core/src/main/java/org/apache/oozie/action/hadoop/HbaseCredentials.java 
> 307f565786ad77f5a35b5790bd5b052b04c6eac8 
>   core/src/main/java/org/apache/oozie/action/hadoop/Hive2ActionExecutor.java 
> 2aed936af75da38c433be5d202bdc01c2f612c76 
>   core/src/main/java/org/apache/oozie/action/hadoop/Hive2Credentials.java 
> bd2f1f768c5b04bef4a33613baede9202144c747 
>   core/src/main/java/org/apache/oozie/action/hadoop/HiveActionExecutor.java 
> 8e2453ef4f78f4a5f1f95b1ca2793f5d7e07ad81 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> 4beeb965a461e246479c3e8ad88f92ecafca13c1 
>   core/src/main/java/org/apache/oozie/action/hadoop/LauncherMapperHelper.java 
> 9609fdc2f3440fb176b659ef16c2a23451724cf9 
>   
> core/src/main/java/org/apache/oozie/action/hadoop/MapReduceActionExecutor.java
>  55c937249ac35e14bd63dd0c1fa962ea636afa3a 
>   core/src/main/java/org/apache/oozie/action/hadoop/OozieJobInfo.java 
> 581d3b3219eff882f961c8e495611e873c6a5a52 
>   core/src/main/java/org/apache/oozie/action/hadoop/PigActionExecutor.java 
> 8b2dc16db80ad602911f1f64e60cfad41b198922 
>   
> core/src/main/java/org/apache/oozie/action/hadoop/ScriptLanguageActionExecutor.java
>  f2541265ca71fb7f3b053c59775ef5e23d0d8f94 
>   core/src/main/java/org/apache/oozie/action/hadoop/ShellActionExecutor.java 
> b9ffa7ab7ec87db8a76a3653c74974d296c8cd17 
>   core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java 
> 8e8d7d308b294efd91e3057e0d88ee06643ab2d4 
>   core/src/main/java/org/apache/oozie/action/hadoop/SqoopActionExecutor.java 
> 6cee32aa8f5b8b36c9c7a98bb738f50b18b64624 
>   core/src/main/java/org/apache/oozie/client/rest/BulkResponseImpl.java 
> fb021bd022d199f93fc5674843514abf45ae12a5 
>   core/src/main/java/org/apache/oozie/command/XCommand.java 
> bdf13f65ea25e8e0f5125e2798568a2c03fffe81 
>   core/src/main/java/org/apache/oozie/command/wf/SubmitHttpXCommand.java 
> 

[jira] [Commented] (OOZIE-2811) Add support for filtering out properties from SparkConfigurationService

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936989#comment-15936989
 ] 

Peter Cseh commented on OOZIE-2811:
---

Thanks Robert, committed to master!

> Add support for filtering out properties from SparkConfigurationService
> ---
>
> Key: OOZIE-2811
> URL: https://issues.apache.org/jira/browse/OOZIE-2811
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Fix For: 5.0.0
>
> Attachments: OOZIE-2811-001.patch, OOZIE-2811-002.patch, 
> OOZIE-2811-003.patch, OOZIE-2811-004.patch, OOZIE-2811-005.patch, 
> OOZIE-2811-amend.patch
>
>
> There is support for filtering out 
> [spark.yarn.jar|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/SparkConfigurationService.java#L89],
>  but it's changed to spark.yarn.jars in Spark2. 
> We should add a general blacklist of properties instead of the current 
> boolean of {{spark.configurations.ignore.spark.yarn.jar}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Jenkins build is back to normal : oozie-trunk-find-patches-available #154188

[Apache Jenkins Server]

See 

Build failed in Jenkins: oozie-trunk-find-patches-available #154187

[Apache Jenkins Server]

See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 6199ecac13c0fc4bf8b9775693e805a10b7219ee 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 6199ecac13c0fc4bf8b9775693e805a10b7219ee
 > git rev-list 6199ecac13c0fc4bf8b9775693e805a10b7219ee # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson7850110161960312948.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:--  0:00:01 --:--:-- 0  0 
00 00 0  0  0 --:--:--  0:00:02 --:--:-- 0  0   
  00 00 0  0  0 --:--:--  0:00:03 --:--:-- 0  0 
00 00 0  0  0 --:--:--  0:00:04 --:--:-- 0  0 0 
   0 00 0  0  0 --:--:--  0:00:05 --:--:-- 0  0 0   
 0 00 0  0  0 --:--:--  0:00:05 --:--:-- 0100  287k
0  287k0 0  45184  0 --:--:--  0:00:06 --:--:-- 73450100  991k0 
 991k0 0   131k  0 --:--:--  0:00:07 --:--:--  245k100 1047k0 
1047k0 0   135k  0 --:--:--  0:00:07 --:--:--  325k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

Build failed in Jenkins: oozie-trunk-precommit-build #3718

[Apache Jenkins Server]

See 


Changes:

[abafna] OOZIE-2041 Add an admin command to run the PurgeXCommand 
(abhishekbafna)

--
[...truncated 1.00 MB...]
[INFO] Copying leveldbjni-all-1.8.jar to 

[INFO] Copying jetty-util-6.1.26.jar to 

[INFO] Copying velocity-1.5.jar to 

[INFO] Copying apache-log4j-extras-1.2.17.jar to 

[INFO] Copying xmlenc-0.52.jar to 

[INFO] Copying httpcore-4.3.3.jar to 

[INFO] Copying jetty-io-9.2.19.v20160908.jar to 

[INFO] Copying commons-beanutils-core-1.8.0.jar to 

[INFO] Copying antlr-2.7.7.jar to 

[INFO] Copying slf4j-log4j12-1.6.6.jar to 

[INFO] Copying datanucleus-api-jdo-3.2.6.jar to 

[INFO] Copying jung-api-2.0.1.jar to 

[INFO] Copying jta-1.1.jar to 

[INFO] Copying kryo-2.22.jar to 

[INFO] Copying hive-serde-1.2.0.jar to 

[INFO] Copying jetty-client-9.2.19.v20160908.jar to 

[INFO] Copying hadoop-yarn-server-web-proxy-2.6.0.jar to 

[INFO] Copying jetty-rewrite-9.2.19.v20160908.jar to 

[INFO] Copying hadoop-yarn-common-2.6.0.jar to 

[INFO] Copying hadoop-auth-2.4.0.jar to 

[INFO] Copying commons-collections-3.2.1.jar to 

[INFO] Copying geronimo-jpa_2.0_spec-1.1.jar to 

[INFO] Copying json-20090211.jar to 

[INFO] Copying jersey-client-1.9.jar to 

[INFO] Copying jetty-schemas-3.1.M0.jar to 

[INFO] Copying hadoop-annotations-2.4.0.jar to 

[INFO] Copying xbean-asm5-shaded-3.17.jar to 

[INFO] Copying oozie-client-4.4.0-SNAPSHOT.jar to 

[INFO] Copying serp-1.15.1.jar to 

[INFO] Copying asm-5.0.1.jar to 

[INFO] Copying openjpa-lib-2.4.1.jar to 

[jira] [Commented] (OOZIE-2701) Oozie to support Multiple HCatalog URIs

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936725#comment-15936725
 ] 

Hadoop QA commented on OOZIE-2701:
--

Testing JIRA OOZIE-2701

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
.{color:green}+1{color} There are no new bugs found in [core].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1912
.Tests failed: 2
.Tests errors: 2

.The patch failed the following testcases:

.  

.Tests failing with errors:
.  testDatabase(org.apache.oozie.coord.TestHCatELFunctions)
.  testTable(org.apache.oozie.coord.TestHCatELFunctions)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3718/

> Oozie to support Multiple HCatalog URIs
> ---
>
> Key: OOZIE-2701
> URL: https://issues.apache.org/jira/browse/OOZIE-2701
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2701-00.patch, OOZIE-2701-01.patch, 
> OOZIE-2701-02.patch, OOZIE-2701-03.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2811) Add support for filtering out properties from SparkConfigurationService

[Robert Kanter (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936606#comment-15936606
 ] 

Robert Kanter commented on OOZIE-2811:
--

Hmm, that's weird - Jenkins' RAT report didn't catch that.

Anyway +1 on the amend patch

> Add support for filtering out properties from SparkConfigurationService
> ---
>
> Key: OOZIE-2811
> URL: https://issues.apache.org/jira/browse/OOZIE-2811
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Fix For: 5.0.0
>
> Attachments: OOZIE-2811-001.patch, OOZIE-2811-002.patch, 
> OOZIE-2811-003.patch, OOZIE-2811-004.patch, OOZIE-2811-005.patch, 
> OOZIE-2811-amend.patch
>
>
> There is support for filtering out 
> [spark.yarn.jar|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/SparkConfigurationService.java#L89],
>  but it's changed to spark.yarn.jars in Spark2. 
> We should add a general blacklist of properties instead of the current 
> boolean of {{spark.configurations.ignore.spark.yarn.jar}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (OOZIE-2840) Fix jobs API servlet mapping for EmbeddedOozieServer - again

[Peter Cseh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Cseh resolved OOZIE-2840.
---
Resolution: Not A Problem

Nevermind, I've mixed up the mapping between the job and the job*s* endpoint.

> Fix jobs API servlet mapping for EmbeddedOozieServer - again
> 
>
> Key: OOZIE-2840
> URL: https://issues.apache.org/jira/browse/OOZIE-2840
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>
> OOZIE-2788 fixed some servlet mappings, but not all of them.
> V2servletmapping is still broken



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OOZIE-2840) Fix jobs API servlet mapping for EmbeddedOozieServer - again

[Peter Cseh (JIRA)]

Peter Cseh created OOZIE-2840:
-

 Summary: Fix jobs API servlet mapping for EmbeddedOozieServer - 
again
 Key: OOZIE-2840
 URL: https://issues.apache.org/jira/browse/OOZIE-2840
 Project: Oozie
  Issue Type: Bug
Reporter: Peter Cseh


OOZIE-2788 fixed some servlet mappings, but not all of them.
V2servletmapping is still broken



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2817) Increase test case stability in pre-commit job

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936504#comment-15936504
 ] 

Peter Cseh commented on OOZIE-2817:
---

Thanks for the review! Committed to master!


> Increase test case stability in pre-commit job
> --
>
> Key: OOZIE-2817
> URL: https://issues.apache.org/jira/browse/OOZIE-2817
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Fix For: 5.0.0
>
> Attachments: OOZIE-2817-001.patch, OOZIE-2817-002.patch, 
> OOZIE-2817-003.patch, OOZIE-2817-amend.patch
>
>
> We could collect the failed tests and rerun them in the pre-commit hook.
> They will still fail if they are broken, but they'll probably pass if they 
> are just flaky.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2817) Increase test case stability in pre-commit job

[Abhishek Bafna (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936503#comment-15936503
 ] 

Abhishek Bafna commented on OOZIE-2817:
---

+1.

> Increase test case stability in pre-commit job
> --
>
> Key: OOZIE-2817
> URL: https://issues.apache.org/jira/browse/OOZIE-2817
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Fix For: 5.0.0
>
> Attachments: OOZIE-2817-001.patch, OOZIE-2817-002.patch, 
> OOZIE-2817-003.patch, OOZIE-2817-amend.patch
>
>
> We could collect the failed tests and rerun them in the pre-commit hook.
> They will still fail if they are broken, but they'll probably pass if they 
> are just flaky.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2817) Increase test case stability in pre-commit job

[Peter Cseh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Cseh updated OOZIE-2817:
--
Attachment: OOZIE-2817-amend.patch

The number of test failures was checked from the output of the first run.
It should be checked from the rerun's output. If a test is broken, it will fail 
again.
[~abhishekbafna], can you review this amend patch?


> Increase test case stability in pre-commit job
> --
>
> Key: OOZIE-2817
> URL: https://issues.apache.org/jira/browse/OOZIE-2817
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Fix For: 5.0.0
>
> Attachments: OOZIE-2817-001.patch, OOZIE-2817-002.patch, 
> OOZIE-2817-003.patch, OOZIE-2817-amend.patch
>
>
> We could collect the failed tests and rerun them in the pre-commit hook.
> They will still fail if they are broken, but they'll probably pass if they 
> are just flaky.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2701) Oozie to support Multiple HCatalog URIs

[Abhishek Bafna (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhishek Bafna updated OOZIE-2701:
--
Attachment: OOZIE-2701-03.patch

Uploading a rebase patch for Jenkin, before it gets committed. Thanks.

> Oozie to support Multiple HCatalog URIs
> ---
>
> Key: OOZIE-2701
> URL: https://issues.apache.org/jira/browse/OOZIE-2701
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2701-00.patch, OOZIE-2701-01.patch, 
> OOZIE-2701-02.patch, OOZIE-2701-03.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2041) Add an admin command to run the PurgeXCommand

[Abhishek Bafna (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936459#comment-15936459
 ] 

Abhishek Bafna commented on OOZIE-2041:
---

Sure. Thanks for let me know. I will keep in mind until we fix this. :)

> 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
> Fix For: 5.0.0
>
> Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.patch, 
> OOZIE-2041-02.patch, OOZIE-2041-03.patch, OOZIE-2041-04.patch, 
> OOZIE-2041-05.patch, OOZIE-2041-06.patch, OOZIE-2041-07.patch, 
> OOZIE-2041-08.patch, OOZIE-2041-09.patch, OOZIE-2041-10.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.15#6346)

[jira] [Commented] (OOZIE-2817) Increase test case stability in pre-commit job

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936433#comment-15936433
 ] 

Peter Cseh commented on OOZIE-2817:
---

Thanks for the review! Committed to master


> Increase test case stability in pre-commit job
> --
>
> Key: OOZIE-2817
> URL: https://issues.apache.org/jira/browse/OOZIE-2817
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Fix For: 5.0.0
>
> Attachments: OOZIE-2817-001.patch, OOZIE-2817-002.patch, 
> OOZIE-2817-003.patch
>
>
> We could collect the failed tests and rerun them in the pre-commit hook.
> They will still fail if they are broken, but they'll probably pass if they 
> are just flaky.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2041) Add an admin command to run the PurgeXCommand

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936448#comment-15936448
 ] 

Peter Cseh commented on OOZIE-2041:
---

It's because OOZIE-2817. 
If you check the logs:
https://builds.apache.org/job/oozie-trunk-precommit-build/3716/consoleFull
...
Rerunning failed tests: org.apache.oozie.jms.TestJMSJobEventListener,
...
And it succeeded after rerun. 
The reporting is broken though so I'll have to improve on that.

> 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
> Fix For: 5.0.0
>
> Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.patch, 
> OOZIE-2041-02.patch, OOZIE-2041-03.patch, OOZIE-2041-04.patch, 
> OOZIE-2041-05.patch, OOZIE-2041-06.patch, OOZIE-2041-07.patch, 
> OOZIE-2041-08.patch, OOZIE-2041-09.patch, OOZIE-2041-10.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.15#6346)

[jira] [Commented] (OOZIE-2393) Allow table drop in hcat prepare

[Abhishek Bafna (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936444#comment-15936444
 ] 

Abhishek Bafna commented on OOZIE-2393:
---

Thanks [~gezapeti] and others for the review. Committed to master.

> Allow table drop in hcat prepare
> 
>
> Key: OOZIE-2393
> URL: https://issues.apache.org/jira/browse/OOZIE-2393
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Muhammad Ehsan ul Haque
>Assignee: Abhishek Bafna
>Priority: Minor
>  Labels: hcatalog, prepare
> Fix For: 5.0.0
>
> Attachments: OOZIE-2393-00.patch, OOZIE-2393-01.patch
>
>
> The hcat prepare only allows to drop partitions. It would be nice to also 
> allow dropping of table, depending on the URL. The current format of the URL 
> is
> {code}hcat://[metastore server]:[port]/[database name]/[table 
> name]/[partkey1]=[value];[partkey2]=[value]{code}
> where at least one partition must be provided, otherwise the prepare step 
> fails with the fololwing exception.
> {code}
> Starting the execution of prepare actions
> Creating HCatClient for user=ehsan.haq (auth:SIMPLE) and 
> server=thrift://datavault-prod-app2.internal.machines:9083
> Prepare execution in the Launcher Mapper has failed
> Failing Oozie Launcher, Main class 
> [org.apache.oozie.action.hadoop.SqoopMain], exception invoking main(), Error 
> trying to drop 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> org.apache.oozie.action.hadoop.LauncherException: Error trying to drop 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> at org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:178)
> at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
> at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:450)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:163)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
> Caused by: org.apache.oozie.action.hadoop.LauncherException: Error trying to 
> drop 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> at 
> org.apache.oozie.action.hadoop.HCatLauncherURIHandler.delete(HCatLauncherURIHandler.java:64)
> at 
> org.apache.oozie.action.hadoop.PrepareActionsDriver.execute(PrepareActionsDriver.java:89)
> at 
> org.apache.oozie.action.hadoop.PrepareActionsDriver.doOperations(PrepareActionsDriver.java:67)
> at 
> org.apache.oozie.action.hadoop.LauncherMapper.executePrepare(LauncherMapper.java:446)
> at org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:174)
> ... 8 more
> Caused by: java.net.URISyntaxException: URI path is not in expected format: 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> at org.apache.oozie.util.HCatURI.parse(HCatURI.java:66)
> at org.apache.oozie.util.HCatURI.(HCatURI.java:52)
> at org.apache.oozie.util.HCatURI.(HCatURI.java:48)
> at 
> org.apache.oozie.action.hadoop.HCatLauncherURIHandler.delete(HCatLauncherURIHandler.java:52)
> ... 12 more
> Oozie Launcher failed, finishing Hadoop job gracefully
> {code}
> h3. Suggestion
> In the URL if the partition is not provided then it should delete the entire 
> table.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2041) Add an admin command to run the PurgeXCommand

[Abhishek Bafna (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936439#comment-15936439
 ] 

Abhishek Bafna commented on OOZIE-2041:
---

Committed to master. Thanks [~gezapeti] and others for review.

> 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
> Fix For: 5.0.0
>
> Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.patch, 
> OOZIE-2041-02.patch, OOZIE-2041-03.patch, OOZIE-2041-04.patch, 
> OOZIE-2041-05.patch, OOZIE-2041-06.patch, OOZIE-2041-07.patch, 
> OOZIE-2041-08.patch, OOZIE-2041-09.patch, OOZIE-2041-10.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.15#6346)

[jira] [Commented] (OOZIE-2041) Add an admin command to run the PurgeXCommand

[Abhishek Bafna (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936432#comment-15936432
 ] 

Abhishek Bafna commented on OOZIE-2041:
---

Did not find any test failure in the Jenkins job, though here it say one.

> 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
> Fix For: 5.0.0
>
> Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.patch, 
> OOZIE-2041-02.patch, OOZIE-2041-03.patch, OOZIE-2041-04.patch, 
> OOZIE-2041-05.patch, OOZIE-2041-06.patch, OOZIE-2041-07.patch, 
> OOZIE-2041-08.patch, OOZIE-2041-09.patch, OOZIE-2041-10.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.15#6346)

Build failed in Jenkins: oozie-trunk-precommit-build #3716

[Apache Jenkins Server]

See 


Changes:

[rkanter] OOZIE-2819 amend to cleanup

[gezapeti] OOZIE-2817 Increase test case stability in pre-commit job (gezapeti)

[pbacsko] OOZIE-2835 TestIOUtils shall not be an XTestCase (asasvari via 
pbacsko)

--
[...truncated 1.01 MB...]
[INFO] Copying jetty-util-6.1.26.jar to 

[INFO] Copying velocity-1.5.jar to 

[INFO] Copying apache-log4j-extras-1.2.17.jar to 

[INFO] Copying xmlenc-0.52.jar to 

[INFO] Copying httpcore-4.3.3.jar to 

[INFO] Copying jetty-io-9.2.19.v20160908.jar to 

[INFO] Copying commons-beanutils-core-1.8.0.jar to 

[INFO] Copying antlr-2.7.7.jar to 

[INFO] Copying slf4j-log4j12-1.6.6.jar to 

[INFO] Copying datanucleus-api-jdo-3.2.6.jar to 

[INFO] Copying jung-api-2.0.1.jar to 

[INFO] Copying jta-1.1.jar to 

[INFO] Copying kryo-2.22.jar to 

[INFO] Copying hive-serde-1.2.0.jar to 

[INFO] Copying jetty-client-9.2.19.v20160908.jar to 

[INFO] Copying hadoop-yarn-server-web-proxy-2.6.0.jar to 

[INFO] Copying jetty-rewrite-9.2.19.v20160908.jar to 

[INFO] Copying hadoop-yarn-common-2.6.0.jar to 

[INFO] Copying hadoop-auth-2.4.0.jar to 

[INFO] Copying commons-collections-3.2.1.jar to 

[INFO] Copying geronimo-jpa_2.0_spec-1.1.jar to 

[INFO] Copying json-20090211.jar to 

[INFO] Copying jersey-client-1.9.jar to 

[INFO] Copying jetty-schemas-3.1.M0.jar to 

[INFO] Copying hadoop-annotations-2.4.0.jar to 

[INFO] Copying xbean-asm5-shaded-3.17.jar to 

[INFO] Copying oozie-client-4.4.0-SNAPSHOT.jar to 

[INFO] Copying serp-1.15.1.jar to 

[INFO] Copying asm-5.0.1.jar to 

[INFO] Copying openjpa-lib-2.4.1.jar to 

[jira] [Commented] (OOZIE-2041) Add an admin command to run the PurgeXCommand

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936386#comment-15936386
 ] 

Hadoop QA commented on OOZIE-2041:
--

Testing JIRA OOZIE-2041

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:orange}0{color} There are [1] new bugs found in total that would be nice 
to have fixed.
.{color:orange}0{color} There are [1] new bugs found in [client] that would 
be nice to have fixed.
.You can find the FindBugs diff here: client/findbugs-new.html
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1901
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  

.Tests failing with errors:
.  

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3716/

> 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
> Fix For: 5.0.0
>
> Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.patch, 
> OOZIE-2041-02.patch, OOZIE-2041-03.patch, OOZIE-2041-04.patch, 
> OOZIE-2041-05.patch, OOZIE-2041-06.patch, OOZIE-2041-07.patch, 
> OOZIE-2041-08.patch, OOZIE-2041-09.patch, OOZIE-2041-10.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.15#6346)

[jira] [Commented] (OOZIE-2827) More directly view of the coordinator’s history from perspective of workflow action.

[Andras Piros (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936336#comment-15936336
 ] 

Andras Piros commented on OOZIE-2827:
-

[~zhoushch] thanks for the patch! {{testConnectionDrop}} seems unrelated.

Can you pls. create a ReviewBoard patch and attach the link to the issue?

> More directly view of the coordinator’s history from perspective of workflow 
> action.
> 
>
> Key: OOZIE-2827
> URL: https://issues.apache.org/jira/browse/OOZIE-2827
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Alonzo Zhou
> Attachments: OOZIE-2827-0001.patch, OOZIE-2827-0002.patch
>
>
> Background: 
> When we monitor a coordinator job, statistics of historical workflow 
> instances such as running time can be directly visualized.
> But, we lack the ability to monitor historical statistics of coordinator from 
> perspective of  workflow action.For example, running time of a coordinator 
> action is longer than before, but we can't see the exact change tendency of a 
> sepcific workflow action in it。
> Functional optimization: 
> More detailed view of the coordinator’s history can be observed from 
> perspective of  workflow action.Furthermore,  the trend of a workflow action 
> can be shown directly on front-end graph.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2701) Oozie to support Multiple HCatalog URIs

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936291#comment-15936291
 ] 

Hadoop QA commented on OOZIE-2701:
--

Testing JIRA OOZIE-2701

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



> Oozie to support Multiple HCatalog URIs
> ---
>
> Key: OOZIE-2701
> URL: https://issues.apache.org/jira/browse/OOZIE-2701
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2701-00.patch, OOZIE-2701-01.patch, 
> OOZIE-2701-02.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Build failed in Jenkins: oozie-trunk-precommit-build #3717

[Apache Jenkins Server]

See 


Changes:

[abafna] OOZIE-2393 Allow table drop in hcat prepare (abhishekbafna)

--
[...truncated 361.85 KB...]
:88:
 warning: Line is longer than 132 characters.
:114:
 warning: Line is longer than 132 characters.
:134:
 warning: Line is longer than 132 characters.
:211:
 warning: Line is longer than 132 characters.
:244:
 warning: Line is longer than 132 characters.
:120:
 warning: Line is longer than 132 characters.
:121:
 warning: Line is longer than 132 characters.
:124:
 warning: Line is longer than 132 characters.
:124:
 warning: Line is longer than 132 characters.
:127:
 warning: Line is longer than 132 characters.
:130:
 warning: Line is longer than 132 characters.
:138:
 warning: Line is longer than 132 characters.
:139:
 warning: Line is longer than 132 characters.
:154:
 warning: Line is longer than 132 characters.
:155:
 warning: Line is longer than 132 characters.
:183:
 warning: Line is longer than 132 characters.
:184:
 warning: Line is longer than 132 characters.
:222:
 warning: Line is longer than 132 characters.
:45:
 warning: Line is longer than 132 characters.
:420:
 warning: Line is longer than 132 characters.
:43:
 warning: Line is longer than 132 characters.
:49:
 warning: Line is longer than 132 characters.
:73:
 warning: Line is longer than 132 characters.
:128:
 warning: Line is longer than 132 characters.
:182:
 warning: Line is longer than 132 characters.
:236:
 warning: Line is longer than 132 characters.

[jira] [Commented] (OOZIE-2041) Add an admin command to run the PurgeXCommand

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936207#comment-15936207
 ] 

Peter Cseh commented on OOZIE-2041:
---

Thanks for the rebase [~abhishekbafna]!
+1

> 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
> Fix For: 5.0.0
>
> Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.patch, 
> OOZIE-2041-02.patch, OOZIE-2041-03.patch, OOZIE-2041-04.patch, 
> OOZIE-2041-05.patch, OOZIE-2041-06.patch, OOZIE-2041-07.patch, 
> OOZIE-2041-08.patch, OOZIE-2041-09.patch, OOZIE-2041-10.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.15#6346)

[jira] [Resolved] (OOZIE-2839) Fix maven warning about parent.relativePath

[Attila Sasvari (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari resolved OOZIE-2839.
---
Resolution: Not A Problem

Incorrect jira, wanted to open it on Crunch 

> Fix maven warning about parent.relativePath
> ---
>
> Key: OOZIE-2839
> URL: https://issues.apache.org/jira/browse/OOZIE-2839
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Priority: Trivial
>
> When running {{mvn test}} the following warnings are printed:
> {noformat}
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.crunch:crunch-core:jar:1.0.0-SNAPSHOT
> [WARNING] 'parent.relativePath' of POM 
> org.apache.crunch:crunch-parent:1.0.0-SNAPSHOT 
> (/Users/asasvari/workspace/crunch_dup/pom.xml) points at 
> org.apache.crunch:crunch-parent instead of org.apache:apache, please verify 
> your project structure @ org.apache.crunch:crunch-parent:1.0.0-SNAPSHOT, 
> /Users/asasvari/workspace/crunch_dup/pom.xml, line 22, column 11
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.crunch:crunch-hbase:jar:1.0.0-SNAPSHOT
> [WARNING] 'parent.relativePath' of POM 
> org.apache.crunch:crunch-parent:1.0.0-SNAPSHOT 
> (/Users/asasvari/workspace/crunch_dup/pom.xml) points at 
> org.apache.crunch:crunch-parent instead of org.apache:apache, please verify 
> your project structure @ org.apache.crunch:crunch-parent:1.0.0-SNAPSHOT, 
> /Users/asasvari/workspace/crunch_dup/pom.xml, line 22, column 11
> [WARNING] 
> {noformat}
> It can be easily resolved by adding an empty {{}} tag to the 
> {{}} element in the root pom.xml.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OOZIE-2839) Fix maven warning about parent.relativePath

[Attila Sasvari (JIRA)]

Attila Sasvari created OOZIE-2839:
-

 Summary: Fix maven warning about parent.relativePath
 Key: OOZIE-2839
 URL: https://issues.apache.org/jira/browse/OOZIE-2839
 Project: Oozie
  Issue Type: Bug
Reporter: Attila Sasvari
Priority: Trivial


When running {{mvn test}} the following warnings are printed:

{noformat}
[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.crunch:crunch-core:jar:1.0.0-SNAPSHOT
[WARNING] 'parent.relativePath' of POM 
org.apache.crunch:crunch-parent:1.0.0-SNAPSHOT 
(/Users/asasvari/workspace/crunch_dup/pom.xml) points at 
org.apache.crunch:crunch-parent instead of org.apache:apache, please verify 
your project structure @ org.apache.crunch:crunch-parent:1.0.0-SNAPSHOT, 
/Users/asasvari/workspace/crunch_dup/pom.xml, line 22, column 11
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.crunch:crunch-hbase:jar:1.0.0-SNAPSHOT
[WARNING] 'parent.relativePath' of POM 
org.apache.crunch:crunch-parent:1.0.0-SNAPSHOT 
(/Users/asasvari/workspace/crunch_dup/pom.xml) points at 
org.apache.crunch:crunch-parent instead of org.apache:apache, please verify 
your project structure @ org.apache.crunch:crunch-parent:1.0.0-SNAPSHOT, 
/Users/asasvari/workspace/crunch_dup/pom.xml, line 22, column 11
[WARNING] 
{noformat}

It can be easily resolved by adding an empty {{}} tag to the 
{{}} element in the root pom.xml.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2041) Add an admin command to run the PurgeXCommand

[Abhishek Bafna (JIRA)]

 [ 
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-10.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
> Fix For: 5.0.0
>
> Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.patch, 
> OOZIE-2041-02.patch, OOZIE-2041-03.patch, OOZIE-2041-04.patch, 
> OOZIE-2041-05.patch, OOZIE-2041-06.patch, OOZIE-2041-07.patch, 
> OOZIE-2041-08.patch, OOZIE-2041-09.patch, OOZIE-2041-10.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.15#6346)

[jira] [Commented] (OOZIE-2835) TestIOUtils shall not be an XTestCase

[Attila Sasvari (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936182#comment-15936182
 ] 

Attila Sasvari commented on OOZIE-2835:
---

Thanks!

> TestIOUtils shall not be an XTestCase
> -
>
> Key: OOZIE-2835
> URL: https://issues.apache.org/jira/browse/OOZIE-2835
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Fix For: 5.0.0
>
> Attachments: OOZIE-2835.01.patch, OOZIE-2835.02.patch
>
>
> TestIOUtils unnecessary extends XTestCase that makes the execution time of 
> the test case really long:
> {code}
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.675 sec
> Results :
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
> {code}
> XTestCase sets up Oozie services which is not needed for testing IOUtils, 
> that's why it takes ~20 seconds.
> If we make TestIOUtils a true unit test class, the execution time of the 
> tests could be drastically reduced:
> {code}
> Running org.apache.oozie.util.TestIOUtils
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec
> Results :
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
> {code} 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2811) Add support for filtering out properties from SparkConfigurationService

[Peter Cseh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Cseh updated OOZIE-2811:
--
Attachment: OOZIE-2811-amend.patch

My patch messed up the license header in TestSparkConfigurationService.java. 
This patch fixes that.
[~rkanter], please review this.

> Add support for filtering out properties from SparkConfigurationService
> ---
>
> Key: OOZIE-2811
> URL: https://issues.apache.org/jira/browse/OOZIE-2811
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Fix For: 5.0.0
>
> Attachments: OOZIE-2811-001.patch, OOZIE-2811-002.patch, 
> OOZIE-2811-003.patch, OOZIE-2811-004.patch, OOZIE-2811-005.patch, 
> OOZIE-2811-amend.patch
>
>
> There is support for filtering out 
> [spark.yarn.jar|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/SparkConfigurationService.java#L89],
>  but it's changed to spark.yarn.jars in Spark2. 
> We should add a general blacklist of properties instead of the current 
> boolean of {{spark.configurations.ignore.spark.yarn.jar}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2835) TestIOUtils shall not be an XTestCase

[Peter Bacsko (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936169#comment-15936169
 ] 

Peter Bacsko commented on OOZIE-2835:
-

+1 

thanks [~asasvari], committed to master!

> TestIOUtils shall not be an XTestCase
> -
>
> Key: OOZIE-2835
> URL: https://issues.apache.org/jira/browse/OOZIE-2835
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2835.01.patch, OOZIE-2835.02.patch
>
>
> TestIOUtils unnecessary extends XTestCase that makes the execution time of 
> the test case really long:
> {code}
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.675 sec
> Results :
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
> {code}
> XTestCase sets up Oozie services which is not needed for testing IOUtils, 
> that's why it takes ~20 seconds.
> If we make TestIOUtils a true unit test class, the execution time of the 
> tests could be drastically reduced:
> {code}
> Running org.apache.oozie.util.TestIOUtils
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec
> Results :
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
> {code} 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2041) Add an admin command to run the PurgeXCommand

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936148#comment-15936148
 ] 

Peter Cseh commented on OOZIE-2041:
---

[~abhishekbafna], could you rebase the 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
> Fix For: 5.0.0
>
> Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.patch, 
> OOZIE-2041-02.patch, OOZIE-2041-03.patch, OOZIE-2041-04.patch, 
> OOZIE-2041-05.patch, OOZIE-2041-06.patch, OOZIE-2041-07.patch, 
> OOZIE-2041-08.patch, OOZIE-2041-09.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.15#6346)

[jira] [Commented] (OOZIE-2701) Oozie to support Multiple HCatalog URIs

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936145#comment-15936145
 ] 

Peter Cseh commented on OOZIE-2701:
---

+1 

> Oozie to support Multiple HCatalog URIs
> ---
>
> Key: OOZIE-2701
> URL: https://issues.apache.org/jira/browse/OOZIE-2701
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2701-00.patch, OOZIE-2701-01.patch, 
> OOZIE-2701-02.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2393) Allow table drop in hcat prepare

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936143#comment-15936143
 ] 

Peter Cseh commented on OOZIE-2393:
---

+1 
Thanks for the patch [~abhishekbafna]!

> Allow table drop in hcat prepare
> 
>
> Key: OOZIE-2393
> URL: https://issues.apache.org/jira/browse/OOZIE-2393
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Muhammad Ehsan ul Haque
>Assignee: Abhishek Bafna
>Priority: Minor
>  Labels: hcatalog, prepare
> Fix For: 5.0.0
>
> Attachments: OOZIE-2393-00.patch, OOZIE-2393-01.patch
>
>
> The hcat prepare only allows to drop partitions. It would be nice to also 
> allow dropping of table, depending on the URL. The current format of the URL 
> is
> {code}hcat://[metastore server]:[port]/[database name]/[table 
> name]/[partkey1]=[value];[partkey2]=[value]{code}
> where at least one partition must be provided, otherwise the prepare step 
> fails with the fololwing exception.
> {code}
> Starting the execution of prepare actions
> Creating HCatClient for user=ehsan.haq (auth:SIMPLE) and 
> server=thrift://datavault-prod-app2.internal.machines:9083
> Prepare execution in the Launcher Mapper has failed
> Failing Oozie Launcher, Main class 
> [org.apache.oozie.action.hadoop.SqoopMain], exception invoking main(), Error 
> trying to drop 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> org.apache.oozie.action.hadoop.LauncherException: Error trying to drop 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> at org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:178)
> at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
> at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:450)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:163)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
> Caused by: org.apache.oozie.action.hadoop.LauncherException: Error trying to 
> drop 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> at 
> org.apache.oozie.action.hadoop.HCatLauncherURIHandler.delete(HCatLauncherURIHandler.java:64)
> at 
> org.apache.oozie.action.hadoop.PrepareActionsDriver.execute(PrepareActionsDriver.java:89)
> at 
> org.apache.oozie.action.hadoop.PrepareActionsDriver.doOperations(PrepareActionsDriver.java:67)
> at 
> org.apache.oozie.action.hadoop.LauncherMapper.executePrepare(LauncherMapper.java:446)
> at org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:174)
> ... 8 more
> Caused by: java.net.URISyntaxException: URI path is not in expected format: 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> at org.apache.oozie.util.HCatURI.parse(HCatURI.java:66)
> at org.apache.oozie.util.HCatURI.(HCatURI.java:52)
> at org.apache.oozie.util.HCatURI.(HCatURI.java:48)
> at 
> org.apache.oozie.action.hadoop.HCatLauncherURIHandler.delete(HCatLauncherURIHandler.java:52)
> ... 12 more
> Oozie Launcher failed, finishing Hadoop job gracefully
> {code}
> h3. Suggestion
> In the URL if the partition is not provided then it should delete the entire 
> table.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2739) Remove property expansion pattern from ShellMain's log4j properties content

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936141#comment-15936141
 ] 

Peter Cseh commented on OOZIE-2739:
---

+1 
Thanks for the contribution [~qwertymaniac]!

> Remove property expansion pattern from ShellMain's log4j properties content
> ---
>
> Key: OOZIE-2739
> URL: https://issues.apache.org/jira/browse/OOZIE-2739
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.3.0
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: OOZIE-2739-4.patch, OOZIE-2739.patch, OOZIE-2739.patch, 
> OOZIE-2739.patch, Screen Shot 2016-11-25 at 7.55.49 PM.png
>
>
> In OOZIE-2504 the following XML was added:
> {code}
> 
> oozie.action.shell.setup.hadoop.conf.dir.log4j.content
> 
> log4j.rootLogger=${hadoop.root.logger}
> hadoop.root.logger=INFO,console
> log4j.appender.console=org.apache.log4j.ConsoleAppender
> log4j.appender.console.target=System.err
> log4j.appender.console.layout=org.apache.log4j.PatternLayout
> log4j.appender.console.layout.ConversionPattern=%d{yy/MM/dd 
> HH:mm:ss} %p %c{2}: %m%n
> 
> {code}
> The intention was to place the value of this configuration as-is into a 
> generated log4j.properties when the ShellMain prepares the sub-environment. 
> However, due to Apache Hadoop Common's Configuration class recognizing the 
> dollar-brace syntax as a substitution variable, and also subsequently finding 
> {{hadoop.root.logger}} set as a system property within task container 
> environments, sets the written file to carry the line 
> "log4j.rootLogger=INFO,CLA" or "log4j.rootLogger=INFO,CLRA".
> This in turn causes odd warnings from log4j to appear, about there being no 
> such appender defined (which was intentional, i.e. to move out of CLA and 
> onto console for the sub-commands).
> There's no way to write out the substitution syntax in a way that 
> Configuration class wouldn't substitute it, so we should likely hard-code the 
> value to be {{INFO,console}}. Those who wish to change it can do so at action 
> levels with the whole new content anyway.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Jenkins build is back to normal : oozie-trunk-find-patches-available #154139

[Apache Jenkins Server]

See 

Build failed in Jenkins: oozie-trunk-find-patches-available #154138

[Apache Jenkins Server]

See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 559595dc6f4e93b0917e72377a931de973b61e88 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 559595dc6f4e93b0917e72377a931de973b61e88
 > git rev-list 559595dc6f4e93b0917e72377a931de973b61e88 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson583679432128634146.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0100 
 447k0  447k0 0   302k  0 --:--:--  0:00:01 --:--:--  302k100 
1126k0 1126k0 0   469k  0 --:--:--  0:00:02 --:--:--  469k100 
1630k0 1630k0 0   484k  0 --:--:--  0:00:03 --:--:--  484k100 
2317k0 2317k0 0   528k  0 --:--:--  0:00:04 --:--:--  528k100 
2421k0 2421k0 0   516k  0 --:--:--  0:00:04 --:--:--  586k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure