Repository files navigation

For any question not answered in this file or inH2O-3 Documentation, please use:

H2O is an in-memory platform for distributed, scalable machine learning. H2O uses familiar interfaces like R, Python, Scala, Java, JSON and the Flow notebook/web interface, and works seamlessly with big data technologies like Hadoop and Spark. H2O provides implementations of many popularalgorithms such as Generalized Linear Models (GLM), Gradient Boosting Machines (including XGBoost), Random Forests, Deep Neural Networks, Stacked Ensembles, Naive Bayes, Generalized Additive Models (GAM), Cox Proportional Hazards, K-Means, PCA, Word2Vec, as well as a fully automatic machine learning algorithm (H2O AutoML).

H2O is extensible so that developers can add data transformations and custom algorithms of their choice and access them through all of those clients. H2O models can bedownloaded and loaded into H2O memory for scoring, or exported into POJO or MOJO format for extemely fast scoring inproduction. More information can be found in theH2O User Guide.

H2O-3 (this repository) is the third incarnation of H2O, and the successor toH2O-2.

• Downloading H2O-3
• Open Source Resources
  • Issue Tracking and Feature Requests
  • List of H2O Resources
• Using H2O-3 Code Artifacts (libraries)
• Building H2O-3
• Launching H2O after Building
• Building H2O on Hadoop
• Sparkling Water
• Documentation
• Citing H2O
• Community /Advisors /Investors

While most of this README is written for developers who do their own builds, most H2O users just download and use a pre-built version. If you are a Python or R user, the easiest way to install H2O is viaPyPI orAnaconda (for Python) orCRAN (for R):

pip install h2o

install.packages("h2o")

For the latest stable, nightly, Hadoop (or Spark / Sparkling Water) releases, or the stand-alone H2O jar, please visit:https://h2o.ai/download

More info on downloading & installing H2O is available in theH2O User Guide.

Most people interact with three or four primary open source resources:GitHub (which you've already found),GitHub issues (for bug reports and issue tracking),Stack Overflow for H2O code/software-specific questions, andh2ostream (a Google Group / email discussion forum) for questions not suitable for Stack Overflow. There is also aGitter H2O developer chat group, however for archival purposes & to maximize accessibility, we'd prefer that standard H2O Q&A be conducted on Stack Overflow.

You can browse and create new issues in our GitHub repository:https://github.com/h2oai/h2o-3

• You canbrowse and search forissues without logging in to Github:
  1. Click theIssues tab on the top of the page
  2. Apply filter to search for particular issues
• Tocreate anissue (either a bug or a feature request):
  • Create H2O-3 issues on the pagehttps://github.com/h2oai/h2o-3/issues/new/choose. (Note: Sparkling Water questions should be addressed under theSparkling Water repository.)

• GitHub

  • https://github.com/h2oai/h2o-3

• GitHub issues -- file bug reports / track issues here

  • Thehttps://github.com/h2oai/h2o-3/issues page contains issues for the current H2O-3 project)

• Stack Overflow -- ask all code/software questions here

  • http://stackoverflow.com/questions/tagged/h2o

• Cross Validated (Stack Exchange) -- ask algorithm/theory questions here

  • https://stats.stackexchange.com/questions/tagged/h2o

• h2ostream Google Group -- ask non-code related questions here

  • Web:https://groups.google.com/d/forum/h2ostream
  • Mail to:h2ostream@googlegroups.com

• Gitter H2O Developer Chat

  • https://gitter.im/h2oai/h2o-3

• Documentation

  • H2O User Guide (main docs):http://docs.h2o.ai/h2o/latest-stable/h2o-docs/index.html
  • All H2O documenation links:http://docs.h2o.ai
  • Nightly build page (nightly docs linked in page):https://s3.amazonaws.com/h2o-release/h2o/master/latest.html

• Download (pre-built packages)

  • http://h2o.ai/download

• Website

  • http://h2o.ai

• Twitter -- follow us for updates and H2O news!

  • https://twitter.com/h2oai

• Awesome H2O -- share your H2O-powered creations with us

  • https://github.com/h2oai/awesome-h2o

Every nightly build publishes R, Python, Java, and Scala artifacts to a build-specific repository. In particular, you can find Java artifacts in the maven/repo directory.

Here is an example snippet of a gradle build file using h2o-3 as a dependency. Replace x, y, z, and nnnn with valid numbers.

// h2o-3 dependency informationdef h2oBranch = 'master'def h2oBuildNumber = 'nnnn'def h2oProjectVersion = "x.y.z.${h2oBuildNumber}"repositories {  // h2o-3 dependencies  maven {    url "https://s3.amazonaws.com/h2o-release/h2o-3/${h2oBranch}/${h2oBuildNumber}/maven/repo/"  }}dependencies {  compile "ai.h2o:h2o-core:${h2oProjectVersion}"  compile "ai.h2o:h2o-algos:${h2oProjectVersion}"  compile "ai.h2o:h2o-web:${h2oProjectVersion}"  compile "ai.h2o:h2o-app:${h2oProjectVersion}"}

Refer to the latest H2O-3 bleeding edgenightly build page for information about installing nightly build artifacts.

Refer to theh2o-droplets GitHub repository for a working example of how to use Java artifacts with gradle.

Note: Stable H2O-3 artifacts are periodically published to Maven Central (click here to search) but may substantially lag behind H2O-3 Bleeding Edge nightly builds.

Getting started with H2O development requiresJDK 1.8+,Node.js,Gradle,Python andR. We use the Gradle wrapper (calledgradlew) to ensure up-to-date local versions of Gradle and other dependencies are installed in your development directory.

Buildingh2o requires a properly set up R environment withrequired packages and Python environment with the following packages:

griptabulaterequestswheel

To install these packages you can usepip orconda.If you have troubles installing these packages onWindows, please follow sectionSetup on Windows of this guide.

(Note: It is recommended to use some virtual environment such asVirtualEnv, to install all packages. )

To build H2O from the repository, perform the following steps.

# Build H2Ogit clone https://github.com/h2oai/h2o-3.gitcd h2o-3./gradlew build -x testYou may encounter problems: e.g. npm missing. Install it:brew install npm# Start H2Ojava -jar build/h2o.jar# Point browser to http://localhost:54321

git clone https://github.com/h2oai/h2o-3.gitcd h2o-3./gradlew syncSmalldata./gradlew syncRPackages./gradlew build

Notes:

• Running tests starts five test JVMs that form an H2O cluster and requires at least 8GB of RAM (preferably 16GB of RAM).
• Running./gradlew syncRPackages is supported on Windows, OS X, and Linux, and is strongly recommended but not required../gradlew syncRPackages ensures a complete and consistent environment with pre-approved versions of the packages required for tests and builds. The packages can be installed manually, but we recommend setting an ENV variable and using./gradlew syncRPackages. To set the ENV variable, use the following format (where `${WORKSPACE} can be any path):

mkdir -p ${WORKSPACE}/Rlibraryexport R_LIBS_USER=${WORKSPACE}/Rlibrary

git pull./gradlew syncSmalldata./gradlew syncRPackages./gradlew clean./gradlew build

• We recommend using./gradlew clean after eachgit pull.

• Skip tests by adding-x test at the end the gradle build command line. Tests typically run for 7-10 minutes on a Macbook Pro laptop with 4 CPUs (8 hyperthreads) and 16 GB of RAM.

• Syncing smalldata is not required after each pull, but if tests fail due to missing data files, then try./gradlew syncSmalldata as the first troubleshooting step. Syncing smalldata downloads data files from AWS S3 to the smalldata directory in your workspace. The sync is incremental. Do not check in these files. The smalldata directory is in .gitignore. If you do not run any tests, you do not need the smalldata directory.

• Running./gradlew syncRPackages is supported on Windows, OS X, and Linux, and is strongly recommended but not required../gradlew syncRPackages ensures a complete and consistent environment with pre-approved versions of the packages required for tests and builds. The packages can be installed manually, but we recommend setting an ENV variable and using./gradlew syncRPackages. To set the ENV variable, use the following format (where${WORKSPACE} can be any path):

  mkdir -p ${WORKSPACE}/Rlibraryexport R_LIBS_USER=${WORKSPACE}/Rlibrary

./gradlew clean && ./gradlew build -x test && (export DO_FAST=1; ./gradlew dist)open target/docs-website/h2o-docs/index.html

Root of the git repository contains a Makefile with convenient shortcuts for frequent build targets used in development.To buildh2o.jar while skipping tests and also the building of alternative assemblies, execute

make

To buildh2o.jar using the minimal assembly, run

make minimal

The minimal assembly is well suited for developement of H2O machine learning algorithms. It doesn't bundle some heavyweightdependencies (like Hadoop) and using it saves build time as well as need to download large libraries from Maven repositories.

From the command line, validatepython is using the newly installed package by usingwhich python (orsudo which python).Update the Environment variable with the WinPython path.

pip install grip tabulate wheel

InstallJava 1.8+ and add the appropriate directoryC:\Program Files\Java\jdk1.7.0_65\bin with java.exe to PATH in Environment Variables. To make sure the command prompt is detecting the correct Java version, run:

javac -version

The CLASSPATH variable also needs to be set to the lib subfolder of the JDK:

CLASSPATH=/<path>/<to>/<jdk>/lib

InstallNode.js and add the installed directoryC:\Program Files\nodejs, which must include node.exe and npm.cmd to PATH if not already prepended.

InstallR and add the bin directory to your PATH if not already included.

Install the following R packages:

• RCurl
• jsonlite
• statmod
• devtools
• roxygen2
• testthat

To install these packages from within an R session:

pkgs<- c("RCurl","jsonlite","statmod","devtools","roxygen2","testthat")for (pkginpkgs) {if (! (pkg%in% rownames(installed.packages()))) install.packages(pkg)}

Note thatlibcurl is required for installation of theRCurl R package.

Note that this packages don't cover running tests, they for building H2O only.

Finally, installRtools, which is a collection of command line tools to facilitate R development on Windows.

NOTE: During Rtools installation, donot install Cygwin.dll.

NOTE: During installation of Cygwin, deselect the Python packages to avoid a conflict with the Python.org package.

If Cygwin is already installed, remove the Python packages or ensure that Native Python is before Cygwin in the PATH variable.

If you don't already have a Git client, please install one. The default one can be found herehttp://git-scm.com/downloads. Make sure that command prompt support is enabled before the installation.

Download and update h2o-3 source codes:

git clone https://github.com/h2oai/h2o-3

cd h2o-3./gradlew.bat build

If you encounter errors run again with--stacktrace for more instructions on missing dependencies.

If you don't haveHomebrew, we recommend installing it. It makes package management for OS X easy.

InstallJava 1.8+. To make sure the command prompt is detecting the correct Java version, run:

javac -version

Using Homebrew:

brew install node

Otherwise, install from theNodeJS website.

InstallR and add the bin directory to your PATH if not already included.

Install the following R packages:

• RCurl
• jsonlite
• statmod
• devtools
• roxygen2
• testthat

To install these packages from within an R session:

pkgs<- c("RCurl","jsonlite","statmod","devtools","roxygen2","testthat")for (pkginpkgs) {if (! (pkg%in% rownames(installed.packages()))) install.packages(pkg)}

Note thatlibcurl is required for installation of theRCurl R package.

Note that this packages don't cover running tests, they for building H2O only.

Install python:

brew install python

Install pip package manager:

sudo easy_install pip

Next install required packages:

sudo pip install wheel requests tabulate

OS X should already have Git installed. To download and update h2o-3 source codes:

git clone https://github.com/h2oai/h2o-3

cd h2o-3./gradlew build

Note: on a regular machine it may take very long time (about an hour) to run all the tests.

If you encounter errors run again with--stacktrace for more instructions on missing dependencies.

curl -sL https://deb.nodesource.com/setup_0.12 | sudo bash -sudo apt-get install -y nodejs

InstallJava 8. Installation instructions can be found hereJDK installation. To make sure the command prompt is detecting the correct Java version, run:

javac -version

Installation instructions can be found hereR installation. Click “Download R for Linux”. Click “ubuntu”. Follow the given instructions.

To install the required packages, follow thesame instructions as for OS X above.

Note: If the process fails to install RStudio Server on Linux, run one of the following:

sudo apt-get install libcurl4-openssl-dev

or

sudo apt-get install libcurl4-gnutls-dev

If you don't already have a Git client:

sudo apt-get install git

Download and update h2o-3 source codes:

git clone https://github.com/h2oai/h2o-3

cd h2o-3./gradlew build

If you encounter errors, run again using--stacktrace for more instructions on missing dependencies.

Make sure that you are not running as root, sincebower will reject such a run.

curl -sL https://deb.nodesource.com/setup_16.x | sudo bash -sudo apt-get install -y nodejs

cd /optsudo wget --no-cookies --no-check-certificate --header "Cookie: gpw_e24=http%3A%2F%2Fwww.oracle.com%2F; oraclelicense=accept-securebackup-cookie" "http://download.oracle.com/otn-pub/java/jdk/7u79-b15/jdk-7u79-linux-x64.tar.gz"sudo tar xzf jdk-7u79-linux-x64.tar.gzcd jdk1.7.0_79sudo alternatives --install /usr/bin/java java /opt/jdk1.7.0_79/bin/java 2sudo alternatives --install /usr/bin/jar jar /opt/jdk1.7.0_79/bin/jar 2sudo alternatives --install /usr/bin/javac javac /opt/jdk1.7.0_79/bin/javac 2sudo alternatives --set jar /opt/jdk1.7.0_79/bin/jarsudo alternatives --set javac /opt/jdk1.7.0_79/bin/javaccd /optsudo wget http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpmsudo rpm -ivh epel-release-7-5.noarch.rpmsudo echo "multilib_policy=best" >> /etc/yum.confsudo yum -y updatesudo yum -y install R R-devel git python-pip openssl-devel libxml2-devel libcurl-devel gcc gcc-c++ make openssl-devel kernel-devel texlive texinfo texlive-latex-fonts libX11-devel mesa-libGL-devel mesa-libGL nodejs npm python-devel numpy scipy python-pandassudo pip install scikit-learn grip tabulate statsmodels wheelmkdir ~/Rlibraryexport JAVA_HOME=/opt/jdk1.7.0_79export JRE_HOME=/opt/jdk1.7.0_79/jreexport PATH=$PATH:/opt/jdk1.7.0_79/bin:/opt/jdk1.7.0_79/jre/binexport R_LIBS_USER=~/Rlibrary# install local R packagesR -e 'install.packages(c("RCurl","jsonlite","statmod","devtools","roxygen2","testthat"), dependencies=TRUE, repos="http://cran.rstudio.com/")'cdgit clone https://github.com/h2oai/h2o-3.gitcd h2o-3# Build H2O./gradlew syncSmalldata./gradlew syncRPackages./gradlew build -x test

To start the H2O cluster locally, execute the following on the command line:

java -jar build/h2o.jar

A list of available start-up JVM and H2O options (e.g.-Xmx,-nthreads,-ip), is available in theH2O User Guide.

Pre-built H2O-on-Hadoop zip files are available on thedownload page. Each Hadoop distribution version has a separate zip file in h2o-3.

To build H2O with Hadoop support yourself, first install sphinx for python:pip install sphinxThen start the build by entering the following from the top-level h2o-3 directory:

export BUILD_HADOOP=1;./gradlew build -x test;./gradlew dist;

This will create a directory called 'target' and generate zip files there. Note thatBUILD_HADOOP is the default behavior when the username isjenkins (refer tosettings.gradle); otherwise you have to request it, as shown above.

To build the zip files only for selected distributions use theH2O_TARGET env variable together withBUILD_HADOOP, for example:

export BUILD_HADOOP=1;export H2O_TARGET=hdp2.5,hdp2.6./gradlew build -x test;./gradlew dist;

In theh2o-hadoop directory, each Hadoop version has a build directory for the driver and an assembly directory for the fatjar.

You need to:

1. Add a new driver directory and assembly directory (each with abuild.gradle file) inh2o-hadoop
2. Add these new projects toh2o-3/settings.gradle
3. Add the new Hadoop version toHADOOP_VERSIONS inmake-dist.sh
4. Add the new Hadoop version to the list inh2o-dist/buildinfo.json

Hadoop supportssecure user impersonation through its Java API. A kerberos-authenticated user can be allowed to proxy any username that meets specified criteria entered in the NameNode's core-site.xml file. This impersonation only applies to interactions with the Hadoop API or the APIs of Hadoop-related services that support it (this is not the same as switching to that user on the machine of origin).

Setting up secure user impersonation (for h2o):

1. Create or find an id to use as proxy which has limited-to-no access to HDFS or related services; the proxy user need only be used to impersonate a user
2. (Required if not using h2odriver) If you are not using the driver (e.g. you wrote your own code against h2o's API using Hadoop), make the necessary code changes to impersonate users (seeorg.apache.hadoop.security.UserGroupInformation)
3. In either of Ambari/Cloudera Manager or directly on the NameNode's core-site.xml file, add 2/3 properties for the user we wish to use as a proxy (replace with the simple user name - not the fully-qualified principal name).
   • hadoop.proxyuser.<proxyusername>.hosts: the hosts the proxy user is allowed to perform impersonated actions on behalf of a valid user from
   • hadoop.proxyuser.<proxyusername>.groups: the groups an impersonated user must belong to for impersonation to work with that proxy user
   • hadoop.proxyuser.<proxyusername>.users: the users a proxy user is allowed to impersonate
   • Example:<property> <name>hadoop.proxyuser.myproxyuser.hosts</name> <value>host1,host2</value> </property> <property> <name>hadoop.proxyuser.myproxyuser.groups</name> <value>group1,group2</value> </property> <property> <name>hadoop.proxyuser.myproxyuser.users</name> <value>user1,user2</value> </property>
4. Restart core services such as HDFS & YARN for the changes to take effect

Impersonated HDFS actions can be viewed in the hdfs audit log ('auth:PROXY' should appear in theugi= field in entries where this is applicable). YARN similarly should show 'auth:PROXY' somewhere in the Resource Manager UI.

To use secure impersonation with h2o's Hadoop driver:

Before this is attempted, see Risks with impersonation, below

When using the h2odriver (e.g. when running withhadoop jar ...), specify-principal <proxy user kerberos principal>,-keytab <proxy user keytab path>, and-run_as_user <hadoop username to impersonate>, in addition to any other arguments needed. If the configuration was successful, the proxy user will log in and impersonate the-run_as_user as long as that user is allowed by either the users or groups configuration property (configured above); this is enforced by HDFS & YARN, not h2o's code. The driver effectively sets its security context as the impersonated user so all supported Hadoop actions will be performed as that user (e.g. YARN, HDFS APIs support securely impersonated users, but others may not).

• The target use case for secure impersonation is applications or services that pre-authenticate a user and then use (in this case) the h2odriver on behalf of that user. H2O's Steam is a perfect example: auth user in web app over SSL, impersonate that user when creating the h2o YARN container.
• The proxy user should have limited permissions in the Hadoop cluster; this means no permissions to access data or make API calls. In this way, if it's compromised it would only have the power to impersonate a specific subset of the users in the cluster and only from specific machines.
• Use thehadoop.proxyuser.<proxyusername>.hosts property whenever possible or practical.
• Don't give the proxyusername's password or keytab to any user you don't want to impersonate another user (this is generallyany user). The point of impersonation is not to allow users to impersonate each other. See the first bullet for the typical use case.
• Limit user logon to the machine the proxying is occurring from whenever practical.
• Make sure the keytab used to login the proxy user is properly secured and that users can't login as that id (viasu, for instance)
• Never set hadoop.proxyuser..{users,groups} to '*' or 'hdfs', 'yarn', etc. Allowing any user to impersonate hdfs, yarn, or any other important user/group should be done with extreme caution andstrongly analyzed before it's allowed.

• The id performing the impersonation can be compromised like any other user id.
• Setting anyhadoop.proxyuser.<proxyusername>.{hosts,groups,users} property to '*' can greatly increase exposure to security risk.
• When users aren't authenticated before being used with the driver (e.g. like Steam does via a secure web app/API), auditability of the process/system is difficult.

$ git diffdiff --git a/h2o-app/build.gradle b/h2o-app/build.gradleindex af3b929..097af85 100644--- a/h2o-app/build.gradle+++ b/h2o-app/build.gradle@@ -8,5 +8,6 @@ dependencies {   compile project(":h2o-algos")   compile project(":h2o-core")   compile project(":h2o-genmodel")+  compile project(":h2o-persist-hdfs") }diff --git a/h2o-persist-hdfs/build.gradle b/h2o-persist-hdfs/build.gradleindex 41b96b2..6368ea9 100644--- a/h2o-persist-hdfs/build.gradle+++ b/h2o-persist-hdfs/build.gradle@@ -2,5 +2,6 @@ description = "H2O Persist HDFS" dependencies {   compile project(":h2o-core")-  compile("org.apache.hadoop:hadoop-client:2.0.0-cdh4.3.0")+  compile("org.apache.hadoop:hadoop-client:2.4.1-mapr-1408")+  compile("org.json:org.json:chargebee-1.0") }

Sparkling Water combines two open-source technologies: Apache Spark and the H2O Machine Learning platform. It makes H2O’s library of advanced algorithms, including Deep Learning, GLM, GBM, K-Means, and Distributed Random Forest, accessible from Spark workflows. Spark users can select the best features from either platform to meet their Machine Learning needs. Users can combine Spark's RDD API and Spark MLLib with H2O’s machine learning algorithms, or use H2O independently of Spark for the model building process and post-process the results in Spark.

Sparkling Water Resources:

• Download page for pre-built packages
• Sparkling Water GitHub repository
• README
• Developer documentation

The main H2O documentation is theH2O User Guide. Visithttp://docs.h2o.ai for the top-level introduction to documentation on H2O projects.

To generate the REST API documentation, use the following commands:

cd ~/h2o-3cd pypython ./generate_rest_api_docs.py  # to generate Markdown onlypython ./generate_rest_api_docs.py --generate_html  --github_user GITHUB_USER --github_password GITHUB_PASSWORD # to generate Markdown and HTML

The default location for the generated documentation isbuild/docs/REST.

If the build fails, trygradlew clean, thengit clean -f.

Documentation for each bleeding edge nightly build is available on thenightly build page.

If you use H2O as part of your workflow in a publication, please cite your H2O resource(s) using the following BibTex entry:

@Manual{h2o_package_or_module,    title = {package_or_module_title},    author = {H2O.ai},    year = {year},    month = {month},    note = {version_information},    url = {resource_url},}

Formatted H2O Software citation examples:

• H2O.ai (Oct. 2016).Python Interface for H2O, Python module version 3.10.0.8.https://github.com/h2oai/h2o-3.
• H2O.ai (Oct. 2016).R Interface for H2O, R package version 3.10.0.8.https://github.com/h2oai/h2o-3.
• H2O.ai (Oct. 2016).H2O, H2O version 3.10.0.8.https://github.com/h2oai/h2o-3.

H2O algorithm booklets are available at theDocumentation Homepage.

@Manual{h2o_booklet_name,    title = {booklet_title},    author = {list_of_authors},    year = {year},    month = {month},    url = {link_url},}

Formatted booklet citation examples:

Arora, A., Candel, A., Lanford, J., LeDell, E., and Parmar, V. (Oct. 2016).Deep Learning with H2O.http://docs.h2o.ai/h2o/latest-stable/h2o-docs/booklets/DeepLearningBooklet.pdf.

Click, C., Lanford, J., Malohlava, M., Parmar, V., and Roark, H. (Oct. 2016).Gradient Boosted Models with H2O.http://docs.h2o.ai/h2o/latest-stable/h2o-docs/booklets/GBMBooklet.pdf.

H2O has been built by a great many number of contributors over the years both within H2O.ai (the company) and the greater open source community. You can begin to contribute to H2O by answeringStack Overflow questions orfiling bug reports. Please join us!

SriSatish AmbatiCliff ClickTom KraljevicTomas NykodymMichal MalohlavaKevin NormoyleSpencer AielloAnqi FuNidhi MehtaArno CandelJosephine WangAmy WangMax SchloemerRay PeckPrithvi PrabhuBrandon HillJeff GamberaAriel RaoViraj ParmarKendall HarrisAnand AvatiJessica LanfordAlex TellezAllison WashburnAmy WangErik EckstrandNeeraja MadabhushiSebastian VidrioBen SabrinMatt DowleMark LandryErin LeDellAndrey SpiridonovOleg RogynskyyNick MartinNancy JordanNishant KaloniaNadine HussamiJeff CramerStacie SpreitzerVinod IyengarCharlene WindomParag SanghaviNavdeep GillLauren DiPernaAnmol BalMark ChanNick KarpovAvni WadhwaAshrith BarthurKaren HayrapetyanJo-fai ChowDmitry LarkoBranden MurrayJakub HavaWen PhanMagnus StensmoPasha StetsenkoAngela BartzMateusz DymczykMicah StubbsIvy WangTerone WardLeland WilkinsonWendy WongNikhil ShekharPavel PscheidlMichal KurkaVeronika MaurerovaJan SterbaJan JendrusakSebastien PoirierTomáš FrýdaArd KelmendiYuliia SyzonAdam ValentaMarek NovotnyZuzana Olajcova

Scientific Advisory Council

Stephen BoydRob TibshiraniTrevor Hastie

Systems, Data, FileSystems and Hadoop

Doug LeaChris PouliotDhruba Borthakur

Jishnu Bhattacharjee, Nexus Venture PartnersAnand Babu PeriasamyAnand RajaramanAsh BhardwajRakesh MathurMichael MarksEgbert BiermanRajesh Ambati