Support for SCD2 with hudi
- Dominant language
- Java
- Stars
- 6.2k
- Forks
- 2.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 111
Description
Sometimes users have requirements to support SCD2 with hudi. Let's see if we need a custom payload or if we can write a transformer in deltastreamer to achieve this.
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-5730
- Type: Improvement
---
## Comments
08/Feb/23 08:36;shivnarayan;For deltastreamer transformer, here is how one can achieve this.
Pseudo code for the transformer:
// Input batch could have mix of inserts and updates. We need to split this into 3 categories, namely, insert only records, records which are getting updated and will be active, records that are overridden will belong to inactive batch.
1. Read all records from hudi
2. Find inserts by doing left-anti join w/ target hudi table. (input df). lets call this insertDf
3. Join (inner join) inputDf w/ target Df to find the set of records that are being updated. Split this into two dataframes. a: to be updated df (end time is inifinite/max) and activeIndex = 1. b: to be overwritten df (endtime = new start time -1 and active index = 0).
4. Once we have all 3 dfs, we need to union them and then return from the transformer.
Notes:
* Record key should be complex and should have "active_index" as part of the record key fields. If not, older version of records could be deleted.
I have a runbook which achieves SCD2. [https://gist.github.com/nsivabalan/e0153f07f972d02e111761243190e7d1]
this leverages our quick start guide as an example. Feel free to fix the schema, partitioning columns, etc as you see fit.
;;;
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the DeltaStreamer transformer proposal in the issue and the linked SCD2 runbook. Clarify whether the work requires a custom payload or a transformer, then define the supported schema, partitioning, record-key behavior, and acceptance criteria before locating the implementation and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100