Skip to content

BED-8175: Handle DuckDB exceptions when performing lookups or when generating lookup tables#4

Open
d3vzer0 wants to merge 6 commits intomainfrom
fix/duckdbexceptions
Open

BED-8175: Handle DuckDB exceptions when performing lookups or when generating lookup tables#4
d3vzer0 wants to merge 6 commits intomainfrom
fix/duckdbexceptions

Conversation

@d3vzer0
Copy link
Copy Markdown
Contributor

@d3vzer0 d3vzer0 commented Apr 30, 2026

Description

The preprocessing phase may crash if missing tables are referenced. This can occur when a particular tenant does not have a particular resource type enabled/configured. Edge cases include Github organizations without repositories, Okta tenants without groups etc.

Additionally, the OpenGraph convert phase may fail when a lookup is executed but the table does not exist. The included fix will log the error but continue converting resources to OpenGraph by returning None or an empty list.

Motivation and Context

This fixes the issue as described above.

Resolves: BED-8175

How Has This Been Tested?

  • Added unit test to verify if a lookup returns None or an empty array when the target table does not exist + check if the error is logged correctly.
  • Added unit test to verify if the preprocessing phase properly logs the missing table and continues the pipeline when transforming tables that don't exist

Screenshots (if appropriate):

Types of changes

  • Chore (a change that does not modify the application functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

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.

2 participants