| commit | b6d2c134b979ce1bb130916992553a54c5e911ed | [log] [tgz] |
|---|---|---|
| author | yzheng-hortonworks <yzheng@hortonworks.com> | Fri Jul 15 21:16:03 2016 +0530 |
| committer | peeyush b <pbishnoi@hortonworks.com> | Fri Jul 15 21:16:03 2016 +0530 |
| tree | 04745cb117f2ccef518185457e508baef1970ae4 | |
| parent | 0da2074040b95c64b49ab6fb65e57644bb022e55 [diff] |
FALCON-2073 Handle with NULL corner case Changes: 1. EntityGraph::getDependents should return empty list instead of NULL value if there is no dependent entities. Affected method include OozieWorkflowEngine::updateDependant and AbstractEntityManager::getDependencies. Also removed unnecessary existing NULL checks after the change. 2. In LogProvider::populateActionLogUrls, handle with the NULL case where there is no file status under the specified path. 3. FalconClient::getDependency should return empty list instead of NULL value if there is no dependent entities. Affected method include FalconEntityCLI::entityCommand. Extra minor changes in this patch: 4. A regular expression misusage in LogProvider::getActionName. To match special character ".", should use "[.]" instead of "." which will try to match any character. 5. Fix a rat check error in Falcon CLI due to the introduction of Spring shell commands. Author: yzheng-hortonworks <yzheng@hortonworks.com> Reviewers: Peeyush <peeyushb@apache.org>, Balu <balu@apache.org> Closes #223 from yzheng-hortonworks/FALCON-2073 and squashes the following commits: 526b0ad [yzheng-hortonworks] review by balu 33c5420 [yzheng-hortonworks] revision c69f9a4 [yzheng-hortonworks] FALCON-2073 Handle with NULL corner case
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.