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
19 files changed
tree: e4b37484ebd66e428ea9b648e13b17bb71c45903
  1. acquisition/
  2. addons/
  3. archival/
  4. build-tools/
  5. cli/
  6. client/
  7. common/
  8. distro/
  9. docs/
  10. examples/
  11. extensions/
  12. falcon-regression/
  13. falcon-ui/
  14. hadoop-dependencies/
  15. html5-ui/
  16. lifecycle/
  17. messaging/
  18. metrics/
  19. monitoring/
  20. oozie/
  21. oozie-el-extensions/
  22. prism/
  23. release-docs/
  24. replication/
  25. rerun/
  26. retention/
  27. scheduler/
  28. shell/
  29. src/
  30. test-tools/
  31. test-util/
  32. titan/
  33. unit/
  34. webapp/
  35. .gitignore
  36. .reviewboardrc
  37. CHANGES.txt
  38. falcon_merge_pr.py
  39. Installation-steps.txt
  40. LICENSE.txt
  41. NOTICE.txt
  42. pom.xml
  43. README.md
README.md

Apache Falcon

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.

Why Apache Falcon?

  • 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)

Online Documentation

You can find the documentation on Apache Falcon website.

How to Contribute

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

Release Notes

You can download release notes of previous releases from the following links.

0.8

0.7