commit | fc27ebb84b692a7d6e961b1a1e00821ad2a3df51 | [log] [tgz] |
---|---|---|
author | yzheng-hortonworks <yzheng@hortonworks.com> | Wed Aug 17 17:05:53 2016 -0700 |
committer | bvellanki <bvellanki@hortonworks.com> | Wed Aug 17 17:05:53 2016 -0700 |
tree | 60d8428fea3fe71982532c86393bf1d352d81884 | |
parent | 3a7c993b55564d11ae79d25d32fd5fbd63ce4fe9 [diff] |
FALCON-1776 Process instance update in titan DB based on JMS notifications on coordinator actions In JMS notifications from the coordinator action, it is not guaranteed to provide information on timestamp and user workflow version. Need to allow these properties to be optional when adding process instance to titan DB. Also need to address the different format when there is no input/output feed. See the picture below for an example result (i.e. WAITING instance). <img width="1083" alt="screen shot 2016-08-12 at 4 50 59 pm" src="https://cloud.githubusercontent.com/assets/10202347/17640302/aec16864-60b1-11e6-9a38-b6dc5cd8b890.png"> Author: yzheng-hortonworks <yzheng@hortonworks.com> Reviewers: "sandeep <sandysmdl@gmail.com>, Peeyush<peeyushb@apache.org>, Balu <balu@apache.org>" Closes #263 from yzheng-hortonworks/FALCON-1776
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.