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?
RafaelCFC
Highly Voted 1 year, 6 months agoterrku
Highly Voted 1 year, 3 months ago363c4c5
Most Recent 5 days, 9 hours agothotwielder
1 month agothotwielder
1 month agoKadELbied
2 months, 1 week agoJoG1221
2 months, 3 weeks agoTedet
4 months, 2 weeks agoAnanth4Sap
8 months, 3 weeks agobenni_ale
8 months, 3 weeks agoDhusanth
11 months, 1 week agofaraaz132
11 months, 2 weeks agoKarunakaran_R
1 year, 1 month agoFreyr
1 year, 1 month agoPrashantTiwari
1 year, 5 months agoDAN_H
1 year, 5 months agospaceexplorer
1 year, 5 months agokz_data
1 year, 6 months ago