You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org> on 2014/11/04 07:46:34 UTC
[jira] [Commented] (FALCON-263) API to get workflow parameters
[ https://issues.apache.org/jira/browse/FALCON-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195794#comment-14195794 ]
Srikanth Sundarrajan commented on FALCON-263:
---------------------------------------------
Hi [~pavan kumar], Are you adding the docs as suggested by [~shwethags] and [~svenkat].
[~svenkat] & [~shwethags], Do you think we should track the FalconPostProcessing refactoring based on Workflow params in a separate JIRA. While we are at it, wanted to hear your thoughts on how the OozieAPI can be called from within FalconPostProcessing on behalf of the application user, If I recall correctly the task doesn't have the kerberos ticket, but merely the FS & JT delegation tokens.
> API to get workflow parameters
> ------------------------------
>
> Key: FALCON-263
> URL: https://issues.apache.org/jira/browse/FALCON-263
> Project: Falcon
> Issue Type: New Feature
> Reporter: Shwetha G S
> Assignee: pavan kumar kolamuri
>
> We should expose an API to return workflow config. If the workflow fails for some reason, this will help to fix the config and re-run the workflow with new config
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)