Quarantine malformed readings with usable row coordinates
A malformed timestamp makes the ingestion job fail with a stack trace and no indication of the source row.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Data quality · Error reporting
Estimated field mix
- Data engineering100%
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
- Report manifest ID, row number and stable reason code.
- Keep rejected values out of generic logs.
- Publish accepted and rejected counts under the declared partial-load policy.
Implementation constraints
- Choose and document all-or-nothing versus row quarantine for this dataset.
Verification to include
- Load a batch containing valid rows under the chosen policy.
- Insert malformed timestamps and verify coordinates and count invariants.
Deliverables
- Quarantine report and policy tests
Rollout and recovery
Enable reports before changing load policy; replay corrected manifests as new attempts.
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.