You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/09/25 17:10:00 UTC
[jira] [Updated] (SPARK-59786) SCD1 Ignore-null support; Populate version map per event row at ingest
[ https://issues.apache.org/jira/browse/SPARK-59786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated SPARK-59786:
-----------------------------------
Labels: pull-request-available (was: )
> SCD1 Ignore-null support; Populate version map per event row at ingest
> ----------------------------------------------------------------------
>
> Key: SPARK-59786
> URL: https://issues.apache.org/jira/browse/SPARK-59786
> Project: Spark
> Issue Type: Sub-task
> Components: Declarative Pipelines
> Affects Versions: 4.4.0
> Reporter: Anish Mahto
> Priority: Major
> Labels: pull-request-available
>
> When processing an incoming microbatch, if ignore-null is enabled for the AutoCDC flow, a non-null version map is populated for every upsert row. Delete rows retain a null version map and are handled as row-wide authorship during later reconciliation.
> Per the version-map contract documented in `Scd1VersionMap`, the map contains authorship information for every non-key user-data leaf in the target-aligned row. This ticket stamps each upsert independently, using only that row’s values and sequencing value.
> This ticket does not reconcile microbatch version maps with existing auxiliary or target-table state, nor does it reconcile multiple microbatch rows targeting the same key.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org