You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 06:55:09 UTC
[jira] [Created] (OOZIE-245) GH-327: Generalize the SLA feed for
all job/status changes
GH-327: Generalize the SLA feed for all job/status changes
----------------------------------------------------------
Key: OOZIE-245
URL: https://issues.apache.org/jira/browse/OOZIE-245
Project: Oozie
Issue Type: Bug
Reporter: Hadoop QA
Current notifications of job/status changes is on per job basis as a callback HTTP call. This solution poses several issues (security, network access, non-guaranteed delivery, resources looking on Oozie side, single point notification).
Oozie SLA end point works as an RSS feed but it is limited to applications using the <sla:sla> extension which have been defined out Y! specific needs.
Either the SLA endpoint should be generalized or a new one should be created to deliver job/status changes with minimal query support (USER/NAME/JOBTYPE).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OOZIE-245) GH-327: Generalize the SLA feed for
all job/status changes
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadoop QA resolved OOZIE-245.
-----------------------------
Resolution: Fixed
> GH-327: Generalize the SLA feed for all job/status changes
> ----------------------------------------------------------
>
> Key: OOZIE-245
> URL: https://issues.apache.org/jira/browse/OOZIE-245
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> Current notifications of job/status changes is on per job basis as a callback HTTP call. This solution poses several issues (security, network access, non-guaranteed delivery, resources looking on Oozie side, single point notification).
> Oozie SLA end point works as an RSS feed but it is limited to applications using the <sla:sla> extension which have been defined out Y! specific needs.
> Either the SLA endpoint should be generalized or a new one should be created to deliver job/status changes with minimal query support (USER/NAME/JOBTYPE).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (OOZIE-245) GH-327: Generalize the SLA feed for
all job/status changes
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik reopened OOZIE-245:
------------------------------------
> GH-327: Generalize the SLA feed for all job/status changes
> ----------------------------------------------------------
>
> Key: OOZIE-245
> URL: https://issues.apache.org/jira/browse/OOZIE-245
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> Current notifications of job/status changes is on per job basis as a callback HTTP call. This solution poses several issues (security, network access, non-guaranteed delivery, resources looking on Oozie side, single point notification).
> Oozie SLA end point works as an RSS feed but it is limited to applications using the <sla:sla> extension which have been defined out Y! specific needs.
> Either the SLA endpoint should be generalized or a new one should be created to deliver job/status changes with minimal query support (USER/NAME/JOBTYPE).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira