Cap decompressed telemetry bytes before archive expansion
A tiny compressed batch expands far beyond the ingestion worker's memory budget.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Streaming · Resource limits
Estimated field mix
- Data engineering40%
- Performance engineering30%
- Security30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional energy dashboard receives hourly device batches. Corrupt archives and late corrections leave operators unsure which readings reached reports.
Setup prerequisites
- Create synthetic device batches and local object-store fixtures.
- Understand checksums and bounded streaming.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Enforce compressed, expanded-byte and row limits.
- Stop streaming as soon as a bound is crossed.
- Quarantine with a reason without loading partial rows.
Implementation constraints
- Do not unpack paths or execute files from archives.
Verification to include
- Ingest a valid compressed synthetic batch.
- Exercise excessive expansion and path-like entry names without writing outside staging.
Deliverables
- Bounded decoder and hostile archive fixtures
Rollout and recovery
Enable bounded decoding before partner intake; keep rejected objects quarantined.
Value of the work
For the engineer: Practice batch integrity, replay and data-quality boundaries.
For the team: Review whether operational data can be traced, corrected and recovered.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.