date:20160118

[jira] Subscription: Oozie Patch Available

2016-01-18 Thread jira

Issue Subscription
Filter: Oozie Patch Available (66 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2438  Oozie client "jobs -filter" diagnostic message clarification
https://issues.apache.org/jira/browse/OOZIE-2438
OOZIE-2434  inconsistent coord action status and workflow job status
https://issues.apache.org/jira/browse/OOZIE-2434
OOZIE-2433  oozie restart required if oozie metrics to graphing tool broken
https://issues.apache.org/jira/browse/OOZIE-2433
OOZIE-2432  TestPurgeXCommand fails
https://issues.apache.org/jira/browse/OOZIE-2432
OOZIE-2431  Support hive.metastore.uris as alias for hcat.metastore.uri
https://issues.apache.org/jira/browse/OOZIE-2431
OOZIE-2430  Add root logger for hive,sqoop action
https://issues.apache.org/jira/browse/OOZIE-2430
OOZIE-2429  TestEventGeneration test is flakey
https://issues.apache.org/jira/browse/OOZIE-2429
OOZIE-2427  With Kerberos enabled, the authentication failure for the 
javascript resources under /ext-2.2 
https://issues.apache.org/jira/browse/OOZIE-2427
OOZIE-2419  HBase credentials are not correctly proxied
https://issues.apache.org/jira/browse/OOZIE-2419
OOZIE-2409  hive2 action with hive 1.2.1 failed
https://issues.apache.org/jira/browse/OOZIE-2409
OOZIE-2400  Workflow xml configuration parser cannot deal with namespace prefix
https://issues.apache.org/jira/browse/OOZIE-2400
OOZIE-2396  oozie compile with hadoop 2.7.1 failed
https://issues.apache.org/jira/browse/OOZIE-2396
OOZIE-2394  Oozie can execute command without holding lock
https://issues.apache.org/jira/browse/OOZIE-2394
OOZIE-2390  Rerun with failed option removing completed output data
https://issues.apache.org/jira/browse/OOZIE-2390
OOZIE-2370  Docs for Coordinator Action Status Notification has wrong property 
name
https://issues.apache.org/jira/browse/OOZIE-2370
OOZIE-2362  SQL injection in BulkJPAExecutor
https://issues.apache.org/jira/browse/OOZIE-2362
OOZIE-2349  Method getCoordJobInfo(String jobId, String filter, int offset, int 
length, boolean desc) is not present in LocalOozieClientCoord
https://issues.apache.org/jira/browse/OOZIE-2349
OOZIE-2338  Invalid configuration defined reported for some valid configs
https://issues.apache.org/jira/browse/OOZIE-2338
OOZIE-2312  oozie doesn't purge audit and error log
https://issues.apache.org/jira/browse/OOZIE-2312
OOZIE-2273  MiniOozie does not work outside of Oozie
https://issues.apache.org/jira/browse/OOZIE-2273
OOZIE-2259  Create a callback action 
https://issues.apache.org/jira/browse/OOZIE-2259
OOZIE-2258  Introducing a new counter in the instrumentation log to distinguish 
between the reasons for launcher failure
https://issues.apache.org/jira/browse/OOZIE-2258
OOZIE-2253  Spark Job is failing when it is running in standalone server
https://issues.apache.org/jira/browse/OOZIE-2253
OOZIE-2244  Oozie should mask passwords in the logs when logging command 
arguments
https://issues.apache.org/jira/browse/OOZIE-2244
OOZIE-2243  Kill Command does not kill the child job for java action
https://issues.apache.org/jira/browse/OOZIE-2243
OOZIE-2203  Fix the login example
https://issues.apache.org/jira/browse/OOZIE-2203
OOZIE-2196  Create Local Client for Bundle
https://issues.apache.org/jira/browse/OOZIE-2196
OOZIE-2172  ZooKeeper Security Tests failed with JVM IBM JAVA
https://issues.apache.org/jira/browse/OOZIE-2172
OOZIE-2165  Job log fetching can fail in Oozie HA mode when using doAs 
impersonation
https://issues.apache.org/jira/browse/OOZIE-2165
OOZIE-2134  Remove references to Services.get().getConf() in code
https://issues.apache.org/jira/browse/OOZIE-2134
OOZIE-2106  Make tomcat download url configurable in the pom file
https://issues.apache.org/jira/browse/OOZIE-2106
OOZIE-2105  Make version of submodules configurable with parent version 
https://issues.apache.org/jira/browse/OOZIE-2105
OOZIE-2099  Add test-patch support for patches generated without --no-prefix
https://issues.apache.org/jira/browse/OOZIE-2099
OOZIE-2081  WorkflowJob notification to include coordinator action id 
https://issues.apache.org/jira/browse/OOZIE-2081
OOZIE-2060  Incorrect documentation of Java action config XML filename
https://issues.apache.org/jira/browse/OOZIE-2060
OOZIE-2044  ssh action succeed with a not exists command which should be fail.
https://issues.apache.org/jira/browse/OOZIE-2044
OOZIE-2020  Rerun all Failed/killed/timedout coordinator actions rather than 
specifying action numbers
https://issues.apache.org/jira/browse/OOZIE-2020
OOZIE-1980  Sql error should not fail coord job
https://issue

[jira] [Updated] (OOZIE-2419) HBase credentials are not correctly proxied

2016-01-18 Thread Harsh J (JIRA)


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

Harsh J updated OOZIE-2419:
---
Attachment: OOZIE-2419.002.patch

This new patch should compile fine.

I rechecked and we default our pom.xml to 0.94.2 and 0.94.2 source trees do 
have the token package/classes. However, it was not until later that the HBase 
project actually put a -Psecurity based build up in maven, so those packages 
are missing in 0.94.2 jars. I've kept the 0.94 as is but have switched the dot 
release to 0.94.27, which is the latest available. This maven jar version has 
the packages we need for this change, as its properly built with the security 
profile by the HBase folks.

> HBase credentials are not correctly proxied
> ---
>
> Key: OOZIE-2419
> URL: https://issues.apache.org/jira/browse/OOZIE-2419
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Harsh J
>Assignee: Harsh J
> Attachments: OOZIE-2419.001.patch, OOZIE-2419.002.patch
>
>
> The method we are using for obtaining tokens from HBase in 
> HbaseCredentials.java does not appear to be proxying correctly. It obtains a 
> token for the Oozie server user instead of the proxied user, causing a 
> problem inside workflow actions that reference it.
> Here's a demonstration (the first method is how Oozie does it today, and the 
> second method is a more manual one which works correctly instead):
> {code}
> import org.apache.hadoop.hbase.HBaseConfiguration;
> import org.apache.hadoop.hbase.security.User;
> import org.apache.hadoop.hbase.security.token.AuthenticationTokenIdentifier;
> import org.apache.hadoop.hbase.security.token.TokenUtil;
> import org.apache.hadoop.mapred.JobConf;
> import org.apache.hadoop.security.UserGroupInformation;
> import org.apache.hadoop.security.token.Token;
> import org.apache.hadoop.security.token.TokenIdentifier;
> import java.security.PrivilegedAction;
> import java.security.PrivilegedExceptionAction;
> public class Main {
> public static void main(String[] args) throws Exception {
> String user = "harsh";
> UserGroupInformation ugi =  
> UserGroupInformation.createProxyUser(user, 
> UserGroupInformation.getLoginUser());
> User u = User.create(ugi);
> JobConf conf = new JobConf(HBaseConfiguration.create());
> u.obtainAuthTokenForJob(conf);
> for (Token token : 
> conf.getCredentials().getAllTokens()) {
> System.out.println(token.getKind());
> System.out.println(token.decodeIdentifier().getUser());
> }
> System.out.println();
> final JobConf conf2 = new JobConf(HBaseConfiguration.create());
> Token token = u.runAs(new 
> PrivilegedExceptionAction>() {
> public Token run() throws 
> Exception {
> return TokenUtil.obtainToken(conf2);
> }
> });
> conf2.getCredentials().addToken(token.getService(), token);
> for (Token token2 : 
> conf2.getCredentials().getAllTokens()) {
> System.out.println(token2.getKind());
> System.out.println(token2.decodeIdentifier().getUser());
> }
> }
> }
> // kinit -kt oozie.keytab oozie/$(hostname -f)
> // javac -cp $(hbase classpath) Main.java
> // java -cp $PWD:$(hbase classpath) Main
> {code}
> This prints:
> {code}
> HBASE_AUTH_TOKEN
> oo...@example.com (auth:SIMPLE)
> HBASE_AUTH_TOKEN
> harsh (auth:SIMPLE)
> {code}
> The first token is identified as the server user, vs. the required proxied 
> user string.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 36123: OOZIE-2259 : Callback Action Executor

2016-01-18 Thread Rohini Palaniswamy

> On Jan. 18, 2016, 5:31 a.m., Rohini Palaniswamy wrote:
> > client/src/main/resources/callback-action-0.1.xsd, lines 28-31
> > 
> >
> > Would suggest two additions - type and configuration.
> > 
> > url
> > type
> > method
> > configuration
> > arg
> > capture-output
> > 
> > - type can be http or jms. This can be used to abstract the diffent 
> > options supported in different classes and instantiated via factory making 
> > it more clean and extensible. With type, method can then just be GET, PUT 
> > and POST. 
> > - Use configuration instead of arg if it is property with name and 
> > value. 
> > - Can still keep arg to pass arguments like in pig/hive/spark actions 
> > and use Options parser to parse the arguments if needed.
> 
> Jaydeep Vishwakarma wrote:
> In future we can have some other way of sending notification.  GET, PUT 
> and POST cannot be generic,  As these terminology are only meaningful for 
> http calls.
> It does not belongs to configuration category according to it 
> characterstics. 
> I always felt to have more cleaner way for  pig/hive/spark action as 
> well. The current format making it more cleaner. 
> Please let me know if you have diffrent thought.

> In future we can have some other way of sending notification.  GET, PUT and 
> POST cannot be generic,  As these terminology are only meaningful for http 
> calls.

  Yes. For that very reason, you definitely need type. When type is defined as 
HTTP, method values will be GET, PUT and POST. That is more clean instead of 
adding multiple different kinds of methods like HTTP_GET, HTTP_PUT, 
QUEUE_PUBLISH and some XXX in future without any relation between them.

> I always felt to have more cleaner way for  pig/hive/spark action as well.

  Pig/hive/spark/distcp are clean. They have configuration which means actual 
configuration used while running and arg to mean the command line arguments 
they take. It is easy for a commandline user to relate to as there is direct 
correlation. I agree with you configuration does not make sense in this case as 
it is actual data that you are passing there and not configuration. But arg 
does not make sense either as it is not arguments. In traditional sense, 
arguments should be based on commandline options like (-key1 val1 -key2 val2) 
or atleast positional (first argument is is value for key1, second argument is 
value for key2, etc). You can go probably go with params instead.

> On Jan. 18, 2016, 5:31 a.m., Rohini Palaniswamy wrote:
> > docs/src/site/twiki/DG_CallbackActionExtension.twiki, lines 64-66
> > 
> >
> > Currently it only seems to be contents of body of MapMessage. In 
> > future, if support for Message properties has to be added how is that 
> > supposed to be done? Or if different type of Message - says TextMessage has 
> > to be supported.
> > 
> > In case of http get, it seems to be query params and with post it seems 
> > to be form params (application/x-www-form-urlencoded). What if 
> > application/octet-stream needs to be supported in the future? 
> > 
> > I think we need to define and document all this clearly and also make 
> > sure it is not difficult to enhance in future. As I see it, the current 
> > form of definition makes it hard to support additional features of HTTP or 
> > JMS in future without hacking around how arguments are defined as we are 
> > assuming now by default there is only one way of doing it.
> 
> Jaydeep Vishwakarma wrote:
> I agree,  I will detail out all the details in doc. 
> I have created a jira OOZIE-2403 for custom method. I will take care the 
> future enchancement part there.

I am not asking about adding those future enhancements. The current xsd and 
argument/data passing interface is not clean enough to extend in future. That 
needs to be fixed here taking future enhancements into account. Even current 
usage is not even clear from documentation. I had to look into code to 
understand what kind of data and parameters are constructed for all methods and 
what needs to be actually passed in the arg section by the user for them to be 
used.

> On Jan. 18, 2016, 5:31 a.m., Rohini Palaniswamy wrote:
> > core/src/main/resources/oozie-default.xml, line 2577
> > 
> >
> > Can you keep this setting similar to 
> > oozie.jms.producer.connection.properties? It will allow specifying more 
> > properties if needed.
> 
> Jaydeep Vishwakarma wrote:
> oozie.jms.producer.connection.properties have # and ;  to separate 
> multiple properties which is not looking clean from my view. Currently I am 
> not seeing the use of multiple values to provide in jms callback.

Sounds good

- Rohini

-

[jira] [Commented] (OOZIE-2259) Create a callback action

2016-01-18 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2259:
--

Testing JIRA OOZIE-2259

Cleaning local git workspace



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



> Create a callback action 
> -
>
> Key: OOZIE-2259
> URL: https://issues.apache.org/jira/browse/OOZIE-2259
> Project: Oozie
>  Issue Type: New Feature
>  Components: action
>Reporter: Jaydeep Vishwakarma
>Assignee: Jaydeep Vishwakarma
> Attachments: OOZIE-2259-v1.patch, OOZIE-2259-v3.patch, 
> OOZIE-2259-v4.patch, OOZIE-2259-v5.patch, OOZIE-2259-v8.patch, 
> OOZIE-2259-v9.patch, OOZIE-2259_v6.patch, OOZIE-2259_v7.patch
>
>
> Need an action to send notification to external server by oozie. We should be 
> able to do multiple types of callback, Currently I know jms and http call. It 
> should suppose to have capability to call diffrent types of methods along 
> with n number of arguments. 
> The sample workflow with callback action 
> {code:xml}
> 
> ...
> 
> 
>   [HOST]
>   [METHOD]
>   
>   [KEY][VALUE]
>   
> ...
> 
> ...
> 
> ...
> 
> {code}
> HOST : by the host system can figure out if it is http or jms callback 
> action. System will send the notification to that host.
> METHOD : it can be POST/GET/QUEUE/TOPIC



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-01-18 Thread Apache Jenkins Server

See 

--
[...truncated 2492 lines...]
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ oozie-mini ---
[INFO] Deleting 

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Compiling 1 source file to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie WorkflowGenerator 4.3.0-SNAPSHOT
[INFO] 
Downloading: 
http://gwt-links.googlecode.com/svn/repository/com/orange/links/gwt-links/1.3-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/com/orange/links/gwt-links/1.3-SNAPSHOT/maven-metadata.xml
Downloading: 
https://repository.apache.org/content/groups/snapshots/com/orange/links/gwt-links/1.3-SNAPSHOT/maven-metadata.xml



Downloading: 
http://gwt-links.googlecode.com/svn/repository/com/orange/links/gwt-links-parent/1.3-SNAPSHOT/maven-metadata.xml
Downloading: 
https://repository.apache.org/content/groups/snapshots/com/orange/links/gwt-links-parent/1.3-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/com/orange/links/gwt-links-parent/1.3-SNAPSHOT/maven-metadata.xml


605/605 B   

Downloaded: 
http://gwt-links.googlecode.com/svn/repository/com/orange/links/gwt-links-parent/1.3-SNAPSHOT/maven-metadata.xml
 (605 B at 0.8 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
oozie-workflowgenerator ---
[INFO] Deleting 

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
oozie-workflowgenerator ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-workflowgenerator ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 24 resources to ../../img
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ 
oozie-workflowgenerator ---
[INFO] Compiling 39 source files to 

[WARNING] 
:[243,30]
 [deprecation] TreeItem(String) in TreeItem has been deprecated
[WARNING] 
:[270,30]
 [deprecation] TreeItem(String) in TreeItem has been deprecated
[WARNING] 
:[271,26]
 [deprecation] TreeItem(String) in TreeItem has been deprecated
[WARNING] 
:[272,14]
 [deprecation] addItem(String) in TreeItem has been deprecated
[WARNING] 
:[273,14]
 [deprecation] addItem(String) in TreeItem has been deprecated
[WARNING]

[jira] [Updated] (OOZIE-2259) Create a callback action

2016-01-18 Thread Jaydeep Vishwakarma (JIRA)


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

Jaydeep Vishwakarma updated OOZIE-2259:
---
Attachment: OOZIE-2259-v9.patch

> Create a callback action 
> -
>
> Key: OOZIE-2259
> URL: https://issues.apache.org/jira/browse/OOZIE-2259
> Project: Oozie
>  Issue Type: New Feature
>  Components: action
>Reporter: Jaydeep Vishwakarma
>Assignee: Jaydeep Vishwakarma
> Attachments: OOZIE-2259-v1.patch, OOZIE-2259-v3.patch, 
> OOZIE-2259-v4.patch, OOZIE-2259-v5.patch, OOZIE-2259-v8.patch, 
> OOZIE-2259-v9.patch, OOZIE-2259_v6.patch, OOZIE-2259_v7.patch
>
>
> Need an action to send notification to external server by oozie. We should be 
> able to do multiple types of callback, Currently I know jms and http call. It 
> should suppose to have capability to call diffrent types of methods along 
> with n number of arguments. 
> The sample workflow with callback action 
> {code:xml}
> 
> ...
> 
> 
>   [HOST]
>   [METHOD]
>   
>   [KEY][VALUE]
>   
> ...
> 
> ...
> 
> ...
> 
> {code}
> HOST : by the host system can figure out if it is http or jms callback 
> action. System will send the notification to that host.
> METHOD : it can be POST/GET/QUEUE/TOPIC



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 36123: OOZIE-2259 : Callback Action Executor

2016-01-18 Thread Jaydeep Vishwakarma



> On Jan. 18, 2016, 5:31 a.m., Rohini Palaniswamy wrote:
> > core/src/main/resources/oozie-default.xml, line 2577
> > 
> >
> > Can you keep this setting similar to 
> > oozie.jms.producer.connection.properties? It will allow specifying more 
> > properties if needed.

oozie.jms.producer.connection.properties have # and ;  to separate multiple 
properties which is not looking clean from my view. Currently I am not seeing 
the use of multiple values to provide in jms callback.


> On Jan. 18, 2016, 5:31 a.m., Rohini Palaniswamy wrote:
> > client/src/main/resources/callback-action-0.1.xsd, lines 28-31
> > 
> >
> > Would suggest two additions - type and configuration.
> > 
> > url
> > type
> > method
> > configuration
> > arg
> > capture-output
> > 
> > - type can be http or jms. This can be used to abstract the diffent 
> > options supported in different classes and instantiated via factory making 
> > it more clean and extensible. With type, method can then just be GET, PUT 
> > and POST. 
> > - Use configuration instead of arg if it is property with name and 
> > value. 
> > - Can still keep arg to pass arguments like in pig/hive/spark actions 
> > and use Options parser to parse the arguments if needed.

In future we can have some other way of sending notification.  GET, PUT and 
POST cannot be generic,  As these terminology are only meaningful for http 
calls.
It does not belongs to configuration category according to it characterstics. 
I always felt to have more cleaner way for  pig/hive/spark action as well. The 
current format making it more cleaner. 
Please let me know if you have diffrent thought.


> On Jan. 18, 2016, 5:31 a.m., Rohini Palaniswamy wrote:
> > docs/src/site/twiki/DG_CallbackActionExtension.twiki, lines 64-66
> > 
> >
> > Currently it only seems to be contents of body of MapMessage. In 
> > future, if support for Message properties has to be added how is that 
> > supposed to be done? Or if different type of Message - says TextMessage has 
> > to be supported.
> > 
> > In case of http get, it seems to be query params and with post it seems 
> > to be form params (application/x-www-form-urlencoded). What if 
> > application/octet-stream needs to be supported in the future? 
> > 
> > I think we need to define and document all this clearly and also make 
> > sure it is not difficult to enhance in future. As I see it, the current 
> > form of definition makes it hard to support additional features of HTTP or 
> > JMS in future without hacking around how arguments are defined as we are 
> > assuming now by default there is only one way of doing it.

I agree,  I will detail out all the details in doc. 
I have created a jira OOZIE-2403 for custom method. I will take care the future 
enchancement part there.


- Jaydeep


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


On Jan. 18, 2016, 1:28 p.m., Jaydeep Vishwakarma wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/36123/
> ---
> 
> (Updated Jan. 18, 2016, 1:28 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2259
> https://issues.apache.org/jira/browse/OOZIE-2259
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Adding callback as an action, It have support for HTTP and JMS server. Not 
> covering Excecutor level queue, I will create a separate jira for it.
> 
> 
> Diffs
> -
> 
>   client/src/main/java/org/apache/oozie/cli/OozieCLI.java 48bac7d 
>   client/src/main/resources/callback-action-0.1.xsd PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/callback/CallBack.java 
> PRE-CREATION 
>   
> core/src/main/java/org/apache/oozie/action/callback/CallbackActionExecutor.java
>  PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/callback/HTTPCallBack.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/callback/JMSCallBack.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/callback/JMSNotification.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/service/CallbackActionService.java 
> PRE-CREATION 
>   core/src/main/resources/oozie-default.xml 0a7e250 
>   
> core/src/test/java/org/apache/oozie/action/callback/TestCallbackActionExecutor.java
>  PRE-CREATION 
>   docs/src/site/twiki/DG_CallbackActionExtension.twiki PRE-CREATION 
>   docs/src/site/twiki/DG_CommandLineTool.twiki 1823247 
>   docs/src/site/t

Re: Review Request 36123: OOZIE-2259 : Callback Action Executor

2016-01-18 Thread Jaydeep Vishwakarma


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

(Updated Jan. 18, 2016, 1:28 p.m.)


Review request for oozie.


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


Repository: oozie-git


Description
---

Adding callback as an action, It have support for HTTP and JMS server. Not 
covering Excecutor level queue, I will create a separate jira for it.


Diffs (updated)
-

  client/src/main/java/org/apache/oozie/cli/OozieCLI.java 48bac7d 
  client/src/main/resources/callback-action-0.1.xsd PRE-CREATION 
  core/src/main/java/org/apache/oozie/action/callback/CallBack.java 
PRE-CREATION 
  
core/src/main/java/org/apache/oozie/action/callback/CallbackActionExecutor.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/action/callback/HTTPCallBack.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/action/callback/JMSCallBack.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/action/callback/JMSNotification.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/service/CallbackActionService.java 
PRE-CREATION 
  core/src/main/resources/oozie-default.xml 0a7e250 
  
core/src/test/java/org/apache/oozie/action/callback/TestCallbackActionExecutor.java
 PRE-CREATION 
  docs/src/site/twiki/DG_CallbackActionExtension.twiki PRE-CREATION 
  docs/src/site/twiki/DG_CommandLineTool.twiki 1823247 
  docs/src/site/twiki/index.twiki 8591530 

Diff: https://reviews.apache.org/r/36123/diff/


Testing
---

Done, 
Will add more test cases.


Thanks,

Jaydeep Vishwakarma

[jira] Subscription: Oozie Patch Available

[jira] [Updated] (OOZIE-2419) HBase credentials are not correctly proxied

Re: Review Request 36123: OOZIE-2259 : Callback Action Executor

[jira] [Commented] (OOZIE-2259) Create a callback action

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

[jira] [Updated] (OOZIE-2259) Create a callback action

Re: Review Request 36123: OOZIE-2259 : Callback Action Executor

Re: Review Request 36123: OOZIE-2259 : Callback Action Executor

8 matches

Site Navigation

Mail list logo

Footer information