[
https://issues.apache.org/jira/browse/OOZIE-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062583#comment-16062583
]
Andras Piros commented on OOZIE-2877:
-------------------------------------
[~clayb] can you please address also following:
* -1 RAW_PATCH_ANALYSIS
** -1 the patch contains 5 line(s) with tabs
** -1 the patch contains 28 line(s) with trailing spaces
** -1 the patch contains 5 line(s) longer than 132 characters
* -1 COMPILE
** +1 HEAD compiles
** -1 patch does not compile
and [*update
diff*|https://www.reviewboard.org/docs/manual/1.5/users/review-requests/updating/#uploading-diffs]
within your review request at ReviewBoard? Thanks!
> 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.
> 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
>
>
> 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
(v6.4.14#64029)
