falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadava (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (FALCON-1313) Generate notification for Falcon job status
Date Wed, 29 Jul 2015 17:52:05 GMT

    [ https://issues.apache.org/jira/browse/FALCON-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646498#comment-14646498
] 

Ajay Yadava edited comment on FALCON-1313 at 7/29/15 5:51 PM:
--------------------------------------------------------------

[~peeyushb]

{quote}
As you have asked question what defines job, here job means hadoop based job within oozie
action workflow.
{quote}
I will try to rephrase my question: Falcon understands feeds and processes and not jobs. For
a feed which job are you referring to replication/retention/import - one of them or all of
them? These details are missing from the doc.


{quote}
But it looks like that your use case is fit for SLA monitoring and the scope of this issue
is to generate email notification of finished workflow job
{quote}
Can you please provide me a couple of use cases for this feature in case of feeds which will
not be solved by SLA monitoring? 

Similarly can you please provide couple of use cases for this feature for processes which
will not be solved by SLA monitoring of processes? 

In above two examples if you can also list what advantages will be there of providing this
feature in Falcon over a user directly making changes to workflow then it will really help
understand the true potential of this feature. e.g. you may want to highlight the cases where
it is not possible to have those notifications without making changes to Falcon etc.



was (Author: ajayyadava):
[~peeyushb]

{quote}
As you have asked question what defines job, here job means hadoop based job within oozie
action workflow.
{quote}
I will try to rephrase my question: Falcon understands feeds and processes and not jobs. For
a feed which job are you referring to replication/retention/import - one of them or all of
them? These details are missing from the doc.


{quote}
But it looks like that your use case is fit for SLA monitoring and the scope of this issue
is to generate email notification of finished workflow job
{quote}
Can you please provide me a couple of use cases in case for this feature in case of feeds
which will not be solved by SLA monitoring? 

Similarly can you please provide couple of use cases for this feature for processes which
will not be solved by SLA monitoring of processes? 

In above two examples if you can also list what advantages will be there of providing this
feature in Falcon over a user directly making changes to workflow then it will really help
understand the true potential of this feature. e.g. you may want to highlight the cases where
it is not possible to have those notifications without making changes to Falcon etc.


> Generate notification for Falcon job status
> -------------------------------------------
>
>                 Key: FALCON-1313
>                 URL: https://issues.apache.org/jira/browse/FALCON-1313
>             Project: Falcon
>          Issue Type: New Feature
>          Components: common
>    Affects Versions: 0.6.1
>            Reporter: Peeyush Bishnoi
>            Assignee: Peeyush Bishnoi
>         Attachments: Falconjobstatusnotification-1.pdf, Falconjobstatusnotification.pdf
>
>
> Falcon should generate Email based notification for job status to the user/group when
job finish either with success/failure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message