Time-series — Sparse Events (JSONL)
Sparse event log in JSON Lines — two events hours apart for event-stream ingestion tests.
{"ts": "2026-01-15T08:00:00Z", "event": "login", "user": "usr_001"}
{"ts": "2026-01-15T14:22:11Z", "event": "purchase", "user": "usr_001"}
Specifications
- Records
- 2
- Edge
- sparse event stream
What is a .jsonl file?
JSONL (JSON Lines) is a text format where each line is a complete, independent JSON value, allowing records to be streamed and appended without parsing the whole file. It is not itself a JSON array and each line must stand alone. It is common in logging, machine learning datasets, and data pipelines.
How to use this file
Use an example JSONL to test line-by-line streaming parsers, append-and-resume ingestion, and batch pipelines that process one record per line.
How to use this file for testing
“Time-series — Sparse Events (JSONL)” is a deterministic Novus Examples fixture for Time-series data, Data import, CSV parsing, JSON parsing. Irregular timestamps, DST gaps, and duplicate keys for time-series importers and charting libraries.
Documented properties for this file: 2 records. 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.
Valid and intentionally invalid siblings are labelled in title and description. Assert parsers accept the valid twin and fail loudly on the invalid one; for time series, check DST gaps and duplicate keys against the spec table.
Code examples
import json
with open("sparse-events.jsonl") as f:
rows = [json.loads(line) for line in f]
print(len(rows), rows[0])Related files
- csvTime-series — Business HoursHourly order counts weekdays only (09–16 UTC) across three SAMPLE days.
- csvTime-series — DST Fall Back Duplicate Hour (CSV)Load readings with a repeated 01:00 local hour on fall-back DST — tests ambiguous timestamp handling.
- csvTime-series — DST Spring Forward Gap (CSV)Hourly load data skipping the 03:00 hour on DST spring-forward day — tests timezone/DST gap handling.
- csvTime-series — Duplicate Timestamp Keys (CSV)Two rows share the same timestamp key — tests deduplication and last-write-wins policies.
- jsonTime-series — Duplicate Timestamp Keys (JSON)JSON array with duplicate timestamp keys for ingestion pipeline tests.
- jsonTime-series — Epoch BoundaryTimestamps at Unix epoch and classic 32-bit Y2038 boundary.
Generated by generation/data_wave_f.py. Free for any use, no attribution required — license.