hard20 pts · first answer countsstreamingfeature-store

Streaming counts that run high

A streaming job counts purchases per user for a real-time feature. After a consumer restart, some counts are higher than the source data. What is the cause and fix?

A.Clock skew; switch every server to UTCB.The model needs retrainingC.The feature store is too slow; add cachingD.Messages were redelivered under at-least-once delivery; deduplicate by event ID or make updates idempotent

Discussion 0

Join free to post in the discussion.

Streaming counts that run high

Discussion 0

Related questions