| commit | c7996deb76819fc7ef98dd28fd4dff19474b7602 | [log] [tgz] |
|---|---|---|
| author | pavan.kolamuri <pavan.kolamuri@gmail.com> | Fri Jul 29 08:40:49 2016 +0530 |
| committer | Pallavi Rao <pallavi.rao@inmobi.com> | Fri Jul 29 08:40:49 2016 +0530 |
| tree | 184a7119e9c5588227e40f1ad8a6791585a80352 | |
| parent | e94dd72fad805eed25f4d035ffc90e7e71e3dffd [diff] |
FALCON-2059 BacklogMetricEmitter Service for Falcon Processes Author: pavan.kolamuri <pavan.kolamuri@gmail.com> Author: Pavan Kolamuri <pavan.kolamuri@appdynamics.com> Reviewers: @pallavi-rao Closes #212 from pavankumar526/master and squashes the following commits: ad84f0f [Pavan Kolamuri] Fixed checkstyle issues dea8f93 [pavan.kolamuri] Added doc in startup.properties dbe3a7f [pavan.kolamuri] Added more log statements d72d228 [pavan.kolamuri] Exception changed to throwable 46dcef8 [pavan.kolamuri] Fixed bug in oozieworkflowengine FALCON-2059 e92d3bc [pavan.kolamuri] Add isMissing method FALCON-2059 6d6cf81 [pavan.kolamuri] Handled when entity was deleted FALCON-2059 6c03701 [pavan.kolamuri] Fixed User authentication issue in oozie 81f0b03 [pavan.kolamuri] Rebased the patch e3dbe88 [pavan.kolamuri] Handled multiple pipelines processes FALCON-2059 b5d9e70 [pavan.kolamuri] Addressed based on comments FALCON-2059 fb78fba [pavan.kolamuri] Refactored changes based on EntitySLAAlert service 80c015a [pavan.kolamuri] FALCON-2059 BacklogMetricEmitter Service for Falcon Processes
Falcon is a feed processing and feed management system aimed at making it easier for end consumers to onboard their feed processing and feed management on hadoop clusters.
Dependencies across various data processing pipelines are not easy to establish. Gaps here typically leads to either incorrect/partial processing or expensive reprocessing. Repeated duplicate definition of a single feed multiple times can lead to inconsistencies / issues.
Input data may not arrive always on time and it is required to kick off the processing without waiting for all data to arrive and accommodate late data separately
Feed management services such as feed retention, replications across clusters, archival etc are tasks that are burdensome on individual pipeline owners and better offered as a service for all customers.
It should be easy to onboard new workflows/pipelines
Smoother integration with metastore/catalog
Provide notification to end customer based on availability of feed groups (logical group of related feeds, which are likely to be used together)
You can find the documentation on Apache Falcon website.
Before opening a pull request, please go through the Contributing to Apache Falcon wiki. It lists steps that are required before creating a PR and the conventions that we follow. If you are looking for issues to pick up then you can look at starter tasks or open tasks
You can download release notes of previous releases from the following links.