Join customer segments as of the revenue event date
Historical enterprise revenue changes whenever sales updates a customer's current segment.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Temporal joins · Slowly changing dimensions
Estimated field mix
- Data engineering70%
- Database engineering30%
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 SaaS analyst reports expansion revenue differently from finance because snapshots, refunds and contract changes are joined at incompatible grains.
Setup prerequisites
- Create a synthetic source schema and local transformation project.
- Use integer minor units and distinct reporting currencies.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Use valid-time segment intervals for the event date.
- Detect overlapping or missing segment intervals explicitly.
- Preserve the event's original reporting currency.
Implementation constraints
- Do not fill missing historical segments with the current value.
Verification to include
- Change today's segment and keep prior periods unchanged.
- Create overlapping segment periods and fail the temporal join check.
Deliverables
- As-of join model and interval assertions
Rollout and recovery
Build a comparison table; switch readers after historical differences are reviewed.
Value of the work
For the engineer: Practice analytical modeling and explainable transformation contracts.
For the team: Review trustworthy reporting definitions and the cost of correcting historical reports.
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.