Skip to content

DEVELOP.md

Latest commit

 

History

History
91 lines (57 loc) · 2.11 KB

DEVELOP.md

File metadata and controls

91 lines (57 loc) · 2.11 KB

Contribute

The code is currently being developed on GitHub: https://github.com/cloudera/impyla

Fork the repo and send a pull request against master. Contributions welcome!

Thrift Codegen

  1. To clean up

    rm -rf $IMPYLA_REPO/impala/_thrift_gen
rm -rf $IMPYLA_REPO/impala/thrift/*.thrift

  2. cp $IMPALA_REPO/common/thrift/ImpalaService.thrift $IMPYLA_REPO/impala/thrift

Hand edit ImpalaService.thrift to exclude files, API and definitions unrelated to query profile such as Frontend.thrift, BackendGflags.thrift, and Query.thrift.

  1. Execute $IMPYLA_REPO/impala/thrift/process_thrift.sh

This should only need to be done very irregularly, as the generated code is committed to the repo. Only when the original thrift IDL files change. People checking out the repo to develop on it do NOT need to run the codegen. Codegen performed with Thrift 0.16.x.

UDF maintenance

Copy a fresh copy of the udf.h header file

```bash
cp $IMPALA_REPO/be/src/udf/udf.h $IMPYLA_REPO/impala/udf/precompiled
```

Release

  1. Generate a summary of all the commits since the last release

    git log $LAST_RELEASE_TAG..HEAD

  2. Set the release version in setup.py (remove the .dev0 tag if applicable) and commit the version number change. Also set the new version number in the readme (under "Installation") and update accordingly.

  3. Tag version number and summarize changes in the tag message

    git tag -a vX.Y.Z

  4. Push the tag upstream

    git push upstream vX.Y.Z

    or

    git push upstream --tags

  5. Register the release with PyPI

    python setup.py register sdist bdist_egg upload

  6. If working on master, bump up to the next anticipated version with a .dev0 tag and commit

Backporting

  1. Checkout the tag for the version to backport onto and create a new branch

    git checkout vX.Y.Z
git checkout -b backport

  2. Cherry pick the relevant commits onto the backport branch

  3. Goto #1 for main release flow

  4. Remove the backport branch
⚡