[
https://issues.apache.org/jira/browse/FALCON-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873187#comment-13873187
]
Shaik Idris Ali edited comment on FALCON-220 at 1/16/14 9:27 AM:
-----------------------------------------------------------------
Hi,
Will this be backward compatible?
String workflowUser =
mapMessage.getString(ARG.workflowUser.getArgName());
When we upgrade Falcon, the older scheduled workflows will not send
workflowUser.
So, "null" user in LateDataHandler and RetryHandler should be fine?
was (Author: shaik.idris):
Hi,
Will this be backward compatible?
String workflowUser =
mapMessage.getString(ARG.workflowUser.getArgName());
When we upgrade Falcon, the older scheduled workflows will not send workflow.
So, "null" user in LateDataHandler and RetryHandler should be fine?
> Post processing should propagate user information in messages for offline
> processing
> ------------------------------------------------------------------------------------
>
> Key: FALCON-220
> URL: https://issues.apache.org/jira/browse/FALCON-220
> Project: Falcon
> Issue Type: Sub-task
> Components: messaging
> Affects Versions: 0.4, 0.3
> Reporter: Venkatesh Seetharam
> Assignee: Venkatesh Seetharam
> Labels: security
> Attachments: FALCON-220.patch
>
>
> Late data handling, retries need to execute the jobs as the user who
> submitted it requiring propagation of user information.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
