5 releases (breaking)

✓ Uses Rust 2018 edition

0.13.0 Apr 1, 2019
0.12.0 Jan 19, 2019
0.11.0 Oct 23, 2018
0.10.0 Aug 7, 2018
0.1.0 Mar 29, 2018

#3 in #arrow

Download history 167/week @ 2018-12-20 81/week @ 2018-12-27 23/week @ 2019-01-03 26/week @ 2019-01-10 63/week @ 2019-01-17 64/week @ 2019-01-24 20/week @ 2019-01-31 147/week @ 2019-02-07 58/week @ 2019-02-14 35/week @ 2019-02-21 84/week @ 2019-02-28 166/week @ 2019-03-07 28/week @ 2019-03-14 74/week @ 2019-03-21 126/week @ 2019-03-28

304 downloads per month
Used in 2 crates

Apache-2.0

398KB
9K SLoC

Native Rust implementation of Apache Arrow

Build Status Coverage Status

Status

This is a native Rust implementation of Apache Arrow. Currently the project is developed and tested against nightly Rust. The current status is:

  • Primitive Arrays
  • List Arrays
  • Struct Arrays
  • CSV Reader
  • CSV Writer
  • Parquet Reader
  • Parquet Writer
  • Arrow IPC
  • Interop tests with other implementations

Examples

The examples folder shows how to construct some different types of Arrow arrays, including dynamic arrays created at runtime.

Examples can be run using the cargo run --example command. For example:

cargo run --example builders
cargo run --example dynamic_types
cargo run --example read_csv

IPC

The IPC flatbuffer code was generated by running this command from the root of the project, using flatc version 1.10.0:

flatc --rust -o rust/arrow/src/ipc/gen/ format/*.fbs

Some manual steps were then performed:

  • Replace type__type with type_type
  • Remove org::apache::arrow::flatbuffers namespace
  • Add includes to each generated file

Publishing to crates.io

An Arrow committer can publish this crate after an official project release has been made to crates.io using the following instructions.

Follow these instructions to create an account and login to crates.io before asking to be added as an owner of the arrow crate.

Checkout the tag for the version to be released. For example:

git checkout apache-arrow-0.11.0

If the Cargo.toml in this tag already contains version = "0.11.0" (as it should) then the crate can be published with the following command:

cargo publish

If the Cargo.toml does not have the correct version then it will be necessary to modify it manually. Since there is now a modified file locally that is not committed to github it will be necessary to use the following command.

cargo publish --allow-dirty

Dependencies

~6.5MB
~111K SLoC