Skip to content
Testaroo
feather1.8 KB

Feather: Arrow IPC Table

The same table as Feather (Arrow IPC file): the zero-copy on-disk form of an Apache Arrow table. For testing Arrow readers and fast columnar interchange.

Preview: schema + first 5 rowsfeather
idint64namestringemailstringdepartmentstringactiveboolscoredoublejoineddate
1001Ada Lovelaceada.lovelace@example.comEngineeringtrue98.52021-03-01
1002Alan Turingalan.turing@example.comResearchtrue952020-06-15
1003Grace Hoppergrace.hopper@example.comEngineeringfalse91.22019-11-20
1004Katherine Johnsonkatherine.johnson@example.comOperationstrue96.82022-01-10
1005Edsger Dijkstraedsger.dijkstra@example.comResearchfalse89.42018-09-05
Decoded table: all 5 rows shown.

Specifications

Rows
5
Columns
7
Format
Feather v2 (Arrow IPC)
Layout
columnar

Testing contract

Expected to pass
Scenario
Exercise Feather: Arrow IPC Table in its binary workflow. The same table as Feather (Arrow IPC file): the zero-copy on-disk form of an Apache Arrow table.
Expected result
5 rows, 7 columns; fields: id: int64; name: string; email: string; department: string; active: bool; score: double; joined: string; column null counts=[0, 0, 0, 0, 0, 0, 0]. Declared feature checks: columns=7; layout=columnar.

What is a .feather file?

Feather (.feather) is a fast on-disk representation of Apache Arrow tables designed for zero-copy, language-agnostic data exchange between Python (pandas/pyarrow) and R. It preserves column types and structure exactly.

How to use this file

Use an example .feather file to test Arrow/Feather readers, round-trip type fidelity, and Feather-to-Parquet/CSV conversion.

How to use this file for testing

“Feather: Arrow IPC Table” is a deterministic Testaroo fixture for Conversion testing, Data engineering. The same content exported across many formats and linked as a group, so you can convert one and diff against the expected twin.

Documented properties for this file: 5 rows · 7 columns · Feather v2 (Arrow IPC). Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

Generated by generation/data_binary.py. Free for any use, no attribution required, license.