Skip to content
Sample UDF and UDAs for Impala.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
java Add FuzzyEquals example. Jan 22, 2014
.gitignore Initial commit. Oct 17, 2013
CMakeLists.txt Removed -O3 flag for IR compiling. Nov 2, 2015
LICENSE.txt Add Apache 2.0 license Mar 21, 2017
README.md Improve contribution guidelines Aug 13, 2018
hyperloglog-uda.cc Update UDFs and UDAs to handle failed allocations. Jan 18, 2018
uda-sample-test.cc Fix build against pre-2.9 headers Mar 13, 2017
uda-sample.cc Update UDFs and UDAs to handle failed allocations. Jan 18, 2018
uda-sample.h Remove spurious const specifiers Mar 3, 2017
udf-sample-test.cc Impala 1.3.1 API updates May 21, 2014
udf-sample.cc
udf-sample.h Impala 1.3.1 API updates May 21, 2014
variance-uda.cc Update UDFs and UDAs to handle failed allocations. Jan 18, 2018

README.md

This repo contains sample user defined functions (UDFs) and user defined aggregate functions (UDAs) built against the Impala UDF/UDA framework.

To get started:

  1. Install the impala udf development package: http://archive.cloudera.com/cdh5/
  2. cmake .
  3. make

The samples will get built to build/. This contains test executables that you can run locally, without the impala service installed as well as the shared object artifacts that we can run on impala.

How do I contribute code?

You need to first sign and return an ICLA and CCLA before we can accept and redistribute your contribution. Once these are submitted you are free to start contributing to impala-udf-samples. Submit these to CLA@cloudera.com.

Find

We use Github issues to track bugs for this project. Find an issue that you would like to work on (or file one if you have discovered a new issue!). If no-one is working on it, assign it to yourself only if you intend to work on it shortly.

It’s a good idea to discuss your intended approach on the issue. You are much more likely to have your patch reviewed and committed if you’ve already got buy-in from the impala-udf-samples community before you start.

Fix

Now start coding! As you are writing your patch, please keep the following things in mind:

First, please include tests with your patch. If your patch adds a feature or fixes a bug and does not include tests, it will generally not be accepted. If you are unsure how to write tests for a particular component, please ask on the issue for guidance.

Second, please keep your patch narrowly targeted to the problem described by the issue. It’s better for everyone if we maintain discipline about the scope of each patch. In general, if you find a bug while working on a specific feature, file a issue for the bug, check if you can assign it to yourself and fix it independently of the feature. This helps us to differentiate between bug fixes and features and allows us to build stable maintenance releases.

Finally, please write a good, clear commit message, with a short, descriptive title and a message that is exactly long enough to explain what the problem was, and how it was fixed.

Please post your patch to the impala-udf-samples project at https://gerrit.cloudera.org for review. See Impala's guide on using gerrit to submit and review patches for instructions on how to send patches to http://gerrit.cloudera.org, except make sure to send your patch to the impala-udf-samples project instead of Impala-ASF.

You can’t perform that action at this time.