Google Git
Sign in
apache / arrow / 567e33b5dd23dd236be46bbd90b15d85b8847775
commit567e33b5dd23dd236be46bbd90b15d85b8847775[log] [tgz]
authorPhillip Cloud <cpcloud@gmail.com>Wed Aug 01 12:53:50 2018 -0400
committerPhillip Cloud <cpcloud@gmail.com>Wed Aug 01 12:53:50 2018 -0400
tree904e4005ed2800672301be29e36bcefa660bb29f
parent0fc224bd746c4936286e7fa031d9b350877a55bb [diff]
ARROW-2960: [Packaging] Fix verify-release-candidate for binary packages and fix release cutting script for lib64 cmake issue

Author: Phillip Cloud <cpcloud@gmail.com>

Closes #2356 from cpcloud/ARROW-2960 and squashes the following commits:

5f92c9f6 <Phillip Cloud> ARROW-2960:  Fix verify-release-candidate for binary packages and fix release cutting script for lib64 cmake issue
2 files changed
tree: 904e4005ed2800672301be29e36bcefa660bb29f
  1. .github/
  2. c_glib/
  3. ci/
  4. cpp/
  5. dev/
  6. format/
  7. go/
  8. integration/
  9. java/
  10. js/
  11. python/
  12. ruby/
  13. rust/
  14. site/
  15. .gitignore
  16. .readthedocs.yml
  17. .travis.yml
  18. appveyor.yml
  19. CHANGELOG.md
  20. header
  21. LICENSE.txt
  22. NOTICE.txt
  23. README.md
README.md

Apache Arrow

Powering In-Memory Analytics

Apache Arrow is a development platform for in-memory analytics. It contains a set of technologies that enable big data systems to process and move data fast.

Major components of the project include:

Arrow is an Apache Software Foundation project. Learn more at arrow.apache.org.

What's in the Arrow libraries?

The reference Arrow libraries contain a number of distinct software components:

  • Columnar vector and table-like containers (similar to data frames) supporting flat or nested types
  • Fast, language agnostic metadata messaging layer (using Google's Flatbuffers library)
  • Reference-counted off-heap buffer memory management, for zero-copy memory sharing and handling memory-mapped files
  • Low-overhead IO interfaces to files on disk, HDFS (C++ only)
  • Self-describing binary wire formats (streaming and batch/file-like) for remote procedure calls (RPC) and interprocess communication (IPC)
  • Integration tests for verifying binary compatibility between the implementations (e.g. sending data from Java to C++)
  • Conversions to and from other in-memory data structures

Getting involved

Even if you do not plan to contribute to Apache Arrow itself or Arrow integrations in other projects, we'd be happy to have you involved:

How to Contribute

We prefer to receive contributions in the form of GitHub pull requests. Please send pull requests against the github.com/apache/arrow repository.

If you are looking for some ideas on what to contribute, check out the JIRA issues for the Apache Arrow project. Comment on the issue and/or contact dev@arrow.apache.org with your questions and ideas.

If you’d like to report a bug but don’t have time to fix it, you can still post it on JIRA, or email the mailing list dev@arrow.apache.org

To contribute a patch:

  1. Break your work into small, single-purpose patches if possible. It’s much harder to merge in a large change with a lot of disjoint features.
  2. Create a JIRA for your patch on the Arrow Project JIRA.
  3. Submit the patch as a GitHub pull request against the master branch. For a tutorial, see the GitHub guides on forking a repo and sending a pull request. Prefix your pull request name with the JIRA name (ex: https://github.com/apache/arrow/pull/240).
  4. Make sure that your code passes the unit tests. You can find instructions how to run the unit tests for each Arrow component in its respective README file.
  5. Add new unit tests for your code.

Thank you in advance for your contributions!