Need help with cdap?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

600 Stars 296 Forks Other 50.7K Commits 64 Opened issues


An open source framework for building data analytic applications.

Services available


Need anything else?

Contributors list

.. meta:: :author: Cask Data, Inc. :copyright: Copyright © 2015-2019 Cask Data, Inc.

.. image:: :target:

.. image:: :target:

.. image:: :target:


CDAP is an integrated, open source application development platform for the Hadoop ecosystem that provides developers with data and application abstractions to simplify and accelerate application development, address a broader range of real-time and batch use cases, and deploy applications into production while satisfying enterprise requirements.

CDAP is a layer of software running on top of Apache Hadoop® platforms such as the Cloudera Enterprise Data Hub or the Hortonworks® Data Platform. CDAP provides these essential capabilities:

  • Abstraction of data in the Hadoop environment through logical representations of underlying data;
  • Portability of applications through decoupling underlying infrastructures;
  • Services and tools that enable faster application creation in development;
  • Integration of the components of the Hadoop ecosystem into a single platform;
  • Metadata management that automatically captures metadata and lineage;
  • CDAP pipelines with an integrated UI for click-and-drag development; and
  • Higher degrees of operational control in production through enterprise best-practices.

CDAP exposes developer APIs (Application Programming Interfaces) for creating applications and accessing core CDAP services. CDAP defines and implements a diverse collection of services that land applications and data on existing Hadoop infrastructure such as HBase, HDFS, YARN, MapReduce, Hive, and Spark.

You can run applications ranging from simple MapReduce Jobs and complete ETL (extract, transform, and load) pipelines all the way up to complex, enterprise-scale data-intensive applications.

Developers can build and test their applications end-to-end in a full-stack, single-node installation. CDAP can be run either as a Sandbox, deployed within the Enterprise on-premises or hosted in the Cloud.

For more information, see our collection of

Developers' Manual and other documentation

Getting Started


To install and use CDAP, there are a few simple prerequisites:

  1. JDK 8+ (required to run CDAP; note that $JAVAHOME should be set) #.
    _ (required to run the CDAP UI; we recommend any version greater than v4.5.0) #. Apache Maven 3.0+ (required to build the example applications; 3.1+ to build CDAP itself)


You can get started with CDAP by building directly from the latest source code::

git clone cd cdap mvn clean package

After the build completes, you will have built all modules for CDAP.

For more build options, please refer to the

build instructions 

Introductory Tutorial

Visit our web site for an

introductory tutorial for developers
__ that will guide you through installing CDAP and running an example application.

Where to Go Next

Now that you've had a look at the CDAP Sandbox, take a look at:

  • Developers' Manual, located in the source distribution in
  • CDAP Releases and timeline 

How to Contribute

Interested in helping to improve CDAP? We welcome all contributions, whether in filing detailed bug reports, submitting pull requests for code changes and improvements, or by asking questions and assisting others on the mailing list.

For quick guide to getting your system setup to contribute to CDAP, take a look at our

Contributor Quickstart Guide 

Filing Issues: Bug Reports & Feature Requests

Bugs and suggestions should be made by

filing an issue 

Existing issues can be browsed at

the CDAP project issues

Pull Requests

We have a simple pull-based development model with a consensus-building phase, similar to Apache's voting process. If you’d like to help make CDAP better by adding new features, enhancing existing features, or fixing bugs, here's how to do it:

  1. If you are planning a large change or contribution, discuss your plans on the
    [email protected] 
    __ mailing list first. This will help us understand your needs and best guide your solution in a way that fits the project.
  2. Fork CDAP into your own GitHub repository.
  3. Create a topic branch with an appropriate name.
  4. Work on the code to your heart's content.
  5. Once you’re satisfied, create a pull request from your GitHub repo (it’s helpful if you fill in all of the description fields).
  6. After we review and accept your request, we’ll commit your code to the caskdata/cdap repository.

Thanks for helping to improve CDAP!

Mailing Lists

CDAP User Group and Development Discussions:

The cdap-user mailing list is primarily for users using the product to develop applications. You can expect questions from users, release announcements, and any other discussions that we think will be helpful to the users.

The cdap-dev mailing list is essentially for developers actively working on the product, and should be used for all our design, architecture and technical discussions moving forward. This mailing list will also receive all JIRA and GitHub notifications.

License and Trademarks

Copyright © 2014-2017 Cask Data, Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Cask is a trademark of Cask Data, Inc. All rights reserved.

Apache, Apache HBase, and HBase are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.