commit | 3e7e08f77225d09250d0ac8a9d9fa38c5f69c3f5 | [log] [tgz] |
---|---|---|
author | sandeep <sandysmdl@gmail.com> | Mon Dec 12 09:42:35 2016 +0530 |
committer | Pallavi Rao <pallavi.rao@inmobi.com> | Mon Dec 12 09:42:35 2016 +0530 |
tree | 254ac2b681090aa69f8b9362b79062e59fde531c | |
parent | c79e5e4d3a68edb021db28c68f6797c2a3641efe [diff] |
FALCON-2210 Server side changes in submit and submitAndSchedule apis to accept list of feeds and processes Author: sandeep <sandysmdl@gmail.com> Reviewers: @pallavi-rao Closes #313 from sandeepSamudrala/FALCON-2210 and squashes the following commits: 3b7a3ae [sandeep] FALCON-2210 applied tags to the entities for user extensions f08cf15 [sandeep] FALCON-2210 Fixed falcon unit client build issues 98d382e [sandeep] FALCON-2210 Incorporated review comments 4004ae7 [sandeep] FALCON-2210 Incorporated review comments d5e4c53 [sandeep] FALCON-2210 Server side changes in submit and submitAndSchedule apis to accept list of feeds and processes 05b87fb [sandeep] Merge branch 'master' of https://github.com/apache/falcon into FALCON-2210 2bd685f [sandeep] FALCON-2201 Fixed checkstyle issues c7422e6 [sandeep] FALCON-2201 Incorporated review comments. Removed applying tags from client. I will move that to Server side in the server side changes 86446ad [sandeep] Merge branch 'master' of https://github.com/apache/falcon into FALCON-2201 432cdfd [sandeep] FALCON-2201 Incorporated review comments a0ce5e0 [sandeep] Merge branch 'master' of https://github.com/apache/falcon into FALCON-2201 519a877 [sandeep] FALCON-2201 Fixed checkstyle issues c101c7b [sandeep] FALCON-2201 Incorporated review comments bf0e6ed [sandeep] FALCON-2201 Incorporated review comments and few client side changes adfd318 [sandeep] FALCON-2201 Falcon Unit changes for extension support and falcon unit tests for extensions and fixes. 03f0c3c [sandeep] Merge branch 'master' of https://github.com/apache/falcon into FALCON-2201 9cf36e9 [sandeep] Merge branch 'master' of https://github.com/apache/falcon bbca081 [sandeep] Merge branch 'master' of https://github.com/apache/falcon 48f6afa [sandeep] Merge branch 'master' of https://github.com/apache/falcon 250cc46 [sandeep] Merge branch 'master' of https://github.com/apache/falcon d0393e9 [sandeep] Merge branch 'master' of https://github.com/apache/falcon a178805 [sandeep] Merge branch 'master' of https://github.com/apache/falcon d6dc8bf [sandeep] Merge branch 'master' of https://github.com/apache/falcon 1bb8d3c [sandeep] Merge branch 'master' of https://github.com/apache/falcon c065566 [sandeep] reverting last line changes made 1a4dcd2 [sandeep] rebased and resolved the conflicts from master 271318b [sandeep] FALCON-2097. Adding UT to the new method for getting next instance time with Delay. a94d4fe [sandeep] rebasing from master 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.