[
https://issues.apache.org/jira/browse/FALCON-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680196#comment-13680196
]
Srikanth Sundarrajan commented on FALCON-16:
--------------------------------------------
org.apache.falcon.logging.LogMover refers to OozieClient directly. This is an
issue and wont work with Kerberos security enabled Oozie. Besides in an offline
discussion with [~vseetharam], [~vseetharam] pointed out a gap where the moved
logs are world readable and writable. One possible fix for both is that the
LogMover can be moved onto the JMS message processing path (post process
messaging on FALCON.ENTITY.TOPIC) and can be run inside the Falcon Server. This
however would mean that more work is being done on the server, which is fine if
we migrated the single threaded message processing to use a thread pool
instead, else that might become a bottleneck.
public int run(String[] arguments) throws Exception {
try {
ARGS args = new ARGS();
setupArgs(arguments, args);
OozieClient client = new OozieClient(args.oozieUrl);
WorkflowJob jobInfo;
....
> 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
