Convert v2 ORC Expected JSON
Json semantic reference for the five-row P8 employee conversion table, preserving ids, names, departments, booleans, and scores. Stable P8 artifact p8-convert-orc-json.
[
{
"active": true,
"department": "Engineering",
"email": "ada.lovelace@example.com",
"id": 1001,
"joined": "2021-03-01",
"name": "Ada Lovelace",
"score": 98.5
},
{
"active": true,
"department": "Research",
"email": "alan.turing@example.com",
"id": 1002,
"joined": "2020-06-15",
"name": "Alan Turing",
"score": 95.0
},
{
"active": false,
"department": "Engineering",
"email": "grace.hopper@example.com",
"id": 1003,
"joined": "2019-11-20",
"name": "Grace Hopper",
"score": 91.2
},
{
"active": true,
"department": "Operations",
"email": "katherine.johnson@example.com",
"id": 1004,
"joined": "2022-01-10",
"name": "Katherine Johnson",
"score": 96.8
},
{
"active": false,
"department": "Research",
"email": "edsger.dijkstra@example.com",
"id": 1005,
"joined": "2018-09-05",
"name": "Edsger Dijkstra",
"score": 89.4
}
]
Specifications
- Rows
- 5
- Columns
- 7
- Source Format
- orc
- Delivery Mode
- download-only
- Provider
- converter-v2
- Provenance
- Synthetic deterministic P8 fixture generated by generation/p8_content.py; seed namespace 2026082300
- Fixture Reserve
- convert-v2
Testing contract
Reference control- Scenario
- Read the JSON artifact and project the five contract columns in row order.
- Expected result
- Five rows and all seven columns match ids 1001 through 1005; Ada's email and 2021-03-01 join date survive, Grace is inactive, and scores remain exact.
What is a .json file?
JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.
How to use this file
Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.
How to use this file for testing
“Convert v2 ORC Expected JSON” is a deterministic Testaroo fixture for Conversion testing, Data engineering, Serialization testing. 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. 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.
Code examples
import json
with open("employees-expected.json") as f:
data = json.load(f)
print(type(data), len(data))Generated by generation/p8_content.py. Free for any use, no attribution required, license.
Related files
- pbConvert v2 Protobuf Creator RecordValid Protobuf wire record with string, uint32, and string fields for schema-guided decoding. Stable P8 artifact p8-convert-protobuf-source.

- jsonConvert v2 Protobuf Expected JSONExpected JSON semantic result for the schema-guided Protobuf decode. Stable P8 artifact p8-convert-protobuf-expected.

- pbConvert v2 Protobuf Missing-Schema Controlled FailureValid wire bytes intentionally supplied without a matching schema so tools must preserve unknown field 15. Stable P8 artifact p8-convert-protobuf-missing-schema.

- protoConvert v2 Protobuf Schema CompanionProto3 schema companion declaring the three fields used by the binary creator record. Stable P8 artifact p8-convert-protobuf-schema.

- avroAvro: Row Binary + SchemaThe same records as Apache Avro: a compact row-based binary format that embeds its own schema, widely used in Kafka pipelines. For testing Avro decoders and schema evolution.

- bsonBSON: Binary JSON (MongoDB)The records as BSON: the binary-JSON encoding MongoDB stores documents in. For testing BSON decoders and JSON↔BSON conversion.
