Skip to content

fix(customize): skip orphaned _raw_data_id rows instead of aborting extraction#8946

Open
danielemoraschi wants to merge 1 commit into
apache:mainfrom
danielemoraschi:fix/customize-orphaned-raw-data-abort
Open

fix(customize): skip orphaned _raw_data_id rows instead of aborting extraction#8946
danielemoraschi wants to merge 1 commit into
apache:mainfrom
danielemoraschi:fix/customize-orphaned-raw-data-abort

Conversation

@danielemoraschi

@danielemoraschi danielemoraschi commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Summary

ExtractCustomizedFields used a LEFT JOIN to the raw table, so a domain row whose _raw_data_id has no matching raw record yields NULL data. That hit the type switch default branch, which did return nil and exited the whole subtask, silently leaving every later row in the (unordered) cursor unprocessed while still reporting success.

Change the default branch to continue so an orphaned row is skipped and extraction proceeds with the remaining rows.

Does this close any open issues?

Closes #8945

…xtraction

ExtractCustomizedFields used a LEFT JOIN to the raw table, so a domain row
whose _raw_data_id has no matching raw record yields NULL data. That hit the
type switch default branch, which did 'return nil' and exited the whole
subtask, silently leaving every later row in the (unordered) cursor
unprocessed while still reporting success.

Change the default branch to 'continue' so an orphaned row is skipped and
extraction proceeds with the remaining rows.

Closes apache#8945
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug][customize] ExtractCustomizedFields aborts the whole scan on the first row with an orphaned _raw_data_id

1 participant