An hourly batch job is configured to ingest data files from a cloud object storage container where each batch represent all records produced by the source system in a given hour. The batch job to process these records into the Lakehouse is sufficiently delayed to ensure no late-arriving data is missed. The user_id field represents a unique key for the data, which has the following schema: user_id BIGINT, username STRING, user_utc STRING, user_region STRING, last_login BIGINT, auto_pay BOOLEAN, last_updated BIGINT
New records are all ingested into a table named account_history which maintains a full record of all data in the same schema as the source. The next table in the system is named account_current and is implemented as a Type 1 table representing the most recent value for each unique user_id.
Assuming there are millions of user accounts and tens of thousands of records processed hourly, which implementation can be used to efficiently update the described account_current table as part of each hourly batch job?
terrku
Highly Voted 8 months, 2 weeks agoRafaelCFC
Highly Voted 10 months, 2 weeks agoAnanth4Sap
Most Recent 1 month agobenni_ale
1 month, 1 week agoDhusanth
3 months, 3 weeks agofaraaz132
3 months, 3 weeks agoKarunakaran_R
5 months, 3 weeks agoFreyr
6 months agoPrashantTiwari
9 months, 2 weeks agoDAN_H
9 months, 4 weeks agospaceexplorer
10 months agokz_data
10 months, 2 weeks agoATLTennis
10 months, 3 weeks agoAndreFR
3 months agosturcu
1 year, 1 month agosturcu
1 year, 1 month agopetrv
12 months agoEertyy
1 year, 2 months agothxsgod
1 year, 2 months ago