Skip to content

Reject a DataSourceConfig with no uri or format in DataFusionEngine - #73287

Draft
pankajastro wants to merge 2 commits into
apache:mainfrom
pankajastro:datafusion-register-datasource-guard-afl-214
Draft

pankajastro wants to merge 2 commits into
apache:mainfrom
pankajastro:datafusion-register-datasource-guard-afl-214

Conversation

@pankajastro

Copy link
Copy Markdown
Member

Depends on #73273 — the plain-database-table DataSourceConfig shape this fixes doesn't exist until that merges. The diff below includes #73273's commit; check the "Commits" tab to see just this PR's own commit. Rebasing onto main once #73273 merges.

Follow-up per review feedback on #73273.

LLMSQLOperator, DataFusionToolset, and AnalyticsOperator hand DataFusionEngine.register_datasource whatever DataSourceConfig the caller supplies, unlike LLMSchemaCompareOperator which checks the connection kind first. A plain-database-table config reaching any of them failed deep inside credential resolution with a confusing Unknown connection type error instead of a clear message. register_datasource now rejects that shape immediately.


Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Sonnet 5)

Generated-by: Claude Code (Sonnet 5) following the guidelines

pankajastro and others added 2 commits September 17, 2026 18:28
LLMSchemaCompareOperator accepts a DataSourceConfig with only conn_id
and table_name, introspected via DbApiHook instead of DataFusion, but
construction failed for that shape. Also close a related gap in the
same validation: an object-store DataSourceConfig with storage_type
set but no uri.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
LLMSQLOperator, DataFusionToolset, and AnalyticsOperator hand
DataFusionEngine.register_datasource whatever DataSourceConfig the
caller supplies, unlike LLMSchemaCompareOperator which checks the
connection kind first. A plain-database-table config reaching any of
them failed deep inside credential resolution with a confusing
"Unknown connection type" error instead of a clear message.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant