# Intake-avro
[](https://travis-ci.org/ContinuumIO/intake-avro) [](http://intake-avro.readthedocs.io/en/latest/?badge=latest)
The [Apache Avro](https://avro.apache.org/) format is a popular method for information exchange, particularly for message and reord distribution in high-throughput systems.
In [Intake](https://github.com/ContinuumIO/intake/), there are two plugins provided for reading avro data:
avro_table is appropriate for data which have a schema simple enough to be represented as columns with simple types, i.e., flat schema. The output of this plugin are dataframes, and the reading is optimized for speed.
avro_sequence is more generic and can handle all possible avro schema, but it produces generic python sequences of dictionaries, and is consequently much slower than the table reader.
### Installation
The conda install instructions are:
` conda install -c conda-forge fastavro uavro conda install -c intake intake_avro `
### Examples
See the notebook in the examples/ directory.
Metadata
Release files for intake-avro 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| intake-avro-0.2.1.tar.gz | 30.5 kB | Without provenance | Details for intake-avro-0.2.1.tar.gz |
Release files / intake-avro-0.2.1.tar.gz
| Download URL | intake-avro-0.2.1.tar.gz |
|---|---|
| Size | 30.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
741196488f0bc92b4d269a11f5d8fb502ff93d9eafde98d732ec7cd3a9e0daf3
|
|
BLAKE2b-256 checksum How to use checksums |
400851ffb2b233f3023303e5f90d79ee1453db70726e7e7da15ffe9232318c90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.25.0 CPython/3.6.4
|
Security for intake-avro 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.