commit | 7354f870b2bff7b5f0451a792cb06d2eee00ff38 | [log] [tgz] |
---|---|---|
author | sandeep <sandysmdl@gmail.com> | Wed Aug 17 09:27:31 2016 +0530 |
committer | Pallavi Rao <pallavi.rao@inmobi.com> | Wed Aug 17 09:27:31 2016 +0530 |
tree | 43b073c8c693dc00e11e5f8596c3d0a89db8aebd | |
parent | 2bea7f4742374e6b38228a798a4ab7fbf2d18507 [diff] |
FALCON-2096 Feed instance listing doesn't give instance status of all the clusters Author: sandeep <sandysmdl@gmail.com> Reviewers: @pallavi-rao, @PraveenAdlakha Closes #261 from sandeepSamudrala/FALCON-2096 and squashes the following commits: c9030e6 [sandeep] FALCON-2096. Fixed checkstyle issues 4c9c655 [sandeep] FALCON-2096. Incorporated review comments. Extracted frequently used constants 9f0d751 [sandeep] Falcon 2096. Feed instance listing doesn't give instance status of all the clusters 97d2a8f [sandeep] Falcon 2096. Feed instance listing doesn't give instance status of all the clusters d853c76 [sandeep] Merge branch 'master' of https://github.com/apache/falcon into FALCON-2096 fa8f8ad [sandeep] FALCON-2096. Feed instance listing doesn't give instance status of all the clusters. 89def80 [sandeep] Merge branch 'master' of https://github.com/apache/falcon into FALCON-2096 9e68a57 [sandeep] FALCON-298. Feed update with replication delay creates holes
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.