commit | 7d9687bcbc8a978ad361498084f3e473fd69fc9b | [log] [tgz] |
---|---|---|
author | Praveen Adlakha <adlakha.praveen@gmail.com> | Fri Aug 05 09:55:49 2016 +0530 |
committer | Pallavi Rao <pallavi.rao@inmobi.com> | Fri Aug 05 09:55:49 2016 +0530 |
tree | e4b37484ebd66e428ea9b648e13b17bb71c45903 | |
parent | 723f1f7f1bb1cd052e81f757629f750393ae6a80 [diff] |
FALCON-2039 Move falcon post processing to falcon server and remove post processing Author: Praveen Adlakha <adlakha.praveen@gmail.com> Reviewers: @pallavi-rao, @vrangan Closes #244 from PraveenAdlakha/2039 and squashes the following commits: b71290a [Praveen Adlakha] process removed 26ddc02 [Praveen Adlakha] comments addressed d4f4cf8 [Praveen Adlakha] fixed test cases cdf9ae1 [Praveen Adlakha] documentation added 9aee018 [Praveen Adlakha] multithread added b3115de [Praveen Adlakha] Agebased boolean check removed 22c25a3 [Praveen Adlakha] Startup properties 1bc278f [Praveen Adlakha] minor fixes done 71b8d1a [Praveen Adlakha] check added in service dd58642 [Praveen Adlakha] FALCON-2039 Move falcon post processing to falcon server and remove post processing action from falcon workflow
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.