[Spike] [Maintenance] Define late arrival event strategy and idem-potent backfilling concept.
Open, Needs TriagePublic3 Estimated Story Points
Actions

Edit Task
Edit Related Tasks...
Create Subtask
Edit Parent Tasks
Edit Subtasks
Merge Duplicates In
Close As Duplicate
Edit Related Objects...
Edit Commits
Edit Mocks
Mute Notifications
Protect as security issue
Award Token
Flag For Later

Assigned To

None

Authored By

	Ahoelzl
	Apr 1 2024, 5:58 PM

Description

We currently address the problem differently for different pipelines.
For the new config store driven, Iceberg based architecture we should a concept and practical approach we should aim for in our implementation to provide consistency for data processing.

Event Timeline

Ahoelzl created this task.Apr 1 2024, 5:58 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 1 2024, 5:58 PM

Ahoelzl set the point value for this task to 3.Apr 1 2024, 5:58 PM

[Spike] [Maintenance] Define late arrival event strategy and idem-potent backfilling concept.Open, Needs TriagePublic3 Estimated Story PointsActions

Description

Event Timeline

[Spike] [Maintenance] Define late arrival event strategy and idem-potent backfilling concept.
Open, Needs TriagePublic3 Estimated Story Points
Actions