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

Andras Piros commented on OOZIE-2877:
-------------------------------------

[~gezapeti] 
[*OOZIE-2877.011.patch*|https://issues.apache.org/jira/secure/attachment/12921392/OOZIE-2877.011.patch]
 targets already some of your comments.

[~clayb] you can take the latest patch as a base. I've tested on 
{{5.1.0-SNAPSHOT}} as follows:
{noformat}
bin/oozie job -oozie http://localhost:11000/oozie -config 
$OOZIE_DIR/oozie/examples/src/main/apps/git/job.properties -run 
-DnameNode=hdfs://localhost:9000 -DjobTracker=localhost:8032
{noformat}

YARN logs:
{noformat}
>>> Invoking Main class now >>>

Launcher class: class org.apache.oozie.action.hadoop.GitMain
INFO: loading log4j config file log4j.properties.
INFO: log4j config file log4j.properties loaded successfully.
{"properties":[{"key":"oozie.launcher.job.id","value":"0000006-180430151425398-oozie-fors-W","isFinal":false,"resource":"programatically"},{"key":"oozie.job.id","value":"0000006-180430151425398-oozie-fors-W","isFinal":false,"resource":"programatically"},{"key":"oozie.action.id","value":"0000006-180430151425398-oozie-fors-W@git-node","isFinal":false,"resource":"programatically"},{"key":"mapreduce.job.tags","value":"oozie-ea3672d1be92e54dc781eca1b88666a6","isFinal":false,"resource":"programatically"}]}
Oozie Git Action Configuration
=============================================
Local mkdir called creating temp. dir at: 
/private/tmp/hadoop-forsage/nm-local-dir/usercache/forsage/appcache/application_1525160126433_0002/container_1525160126433_0002_01_000001/./git_20081494081518844967816698870085523
Finished cloning to local
Finished the copy to 
hdfs://localhost:9000/user/forsage/examples/output-data/git/scoozie!

<<< Invocation of Main class completed <<<
{noformat}

> Oozie Git Action
> ----------------
>
>                 Key: OOZIE-2877
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2877
>             Project: Oozie
>          Issue Type: Sub-task
>          Components: action
>            Reporter: Clay B.
>            Assignee: Clay B.
>            Priority: Major
>              Labels: action
>             Fix For: trunk
>
>         Attachments: 0001-OOZIE-2877-Oozie-Git-Action.patch, 
> 0002-OOZIE-2877-Oozie-Git-Action.patch, 
> 0003-OOZIE-2877-Oozie-Git-Action.patch, 
> 0004-OOZIE-2877-Oozie-Git-Action.patch, 
> 0005-OOZIE-2877-Oozie-Git-Action.patch, 
> 0006-OOZIE-2877-Oozie-Git-Action.patch, 
> 0007-OOZIE-2877-Oozie-Git-Action.patch, 
> 0008-OOZIE-2877-Oozie-Git-Action.patch, 
> 0009-OOZIE-2877-Oozie-Git-Action.patch, OOZIE-2877.010.patch, 
> OOZIE-2877.011.patch
>
>
> To aide in deploying ASCII artifacts to clusters, let's provide a tie-in for 
> a source-code management system. Git would be my preferred choice.
> Ideally, this could handle a user's key material e.g. for an ssh key to pull 
> down from a secured repository. This would free users from handling their own 
> key staging and clean-up on YARN nodes and only require them to store the key 
> secured in HDFS.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to