We’re missing any kind of timestamp in associations, like a created_at, updated_at, etc., that could be used for incremental loading of associations tables into our datawarehouse. Association tables grow big quickly, and they’re consuming a lot of ingested rows.
Hi, we have the same use case on our side
Complementary comment: add a Search method on Associations to enable time-conditional filtering based on a provided timestamp
Upvote ! ![]()