[
https://issues.apache.org/jira/browse/FALCON-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680752#comment-13680752
]
Venkatesh Seetharam commented on FALCON-16:
-------------------------------------------
[~sriksun] Thanks for your comments. Yes, I remember speaking to you about this
but largely missed it in the code.
There are a few options that come to my mind:
* Move this to falcon and execute it in process with in falcon as part of
consuming the message as you suggested which will burden falcon
* Instead of an in process execution, how about launching yet another workflow
to move logs on behalf of the user which will keep falcon light but makes it a
burden on oozie
* Add a feature in oozie to capture logs as part of an action or a workflow
with a path and it copies the job logs automatically. Sweet huh? :-)
* This may be a stretch but could add delegation token based authentication in
Oozie. FalconPostProcessing action is launched as a mapper with delegation
token checked out by oozie and we could send that to authenticate with oozie
and get access.
We also need to address a related issue of capturing job metrics, specifically
counters and persist 'em as well.
How about commenting that part in this patch and addressing that in a separate
jira issue since it is a task on its own. That way I can get closure on
security and work on this as a separate task.
Makes sense?
> Secure Oozie client interface
> -----------------------------
>
> Key: FALCON-16
> URL: https://issues.apache.org/jira/browse/FALCON-16
> Project: Falcon
> Issue Type: Sub-task
> Affects Versions: 0.3
> Reporter: Venkatesh Seetharam
> Assignee: Venkatesh Seetharam
> Labels: security
> Fix For: 0.3
>
> Attachments: FALCON-16.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
