Skip Dag params with no value when forwarding them to Databricks - #71782
Draft
rjgoyln wants to merge 1 commit into
Draft
Skip Dag params with no value when forwarding them to Databricks#71782rjgoyln wants to merge 1 commit into
rjgoyln wants to merge 1 commit into
Conversation
A Dag that declares a nullable Param and leaves it unset could no longer submit a Databricks run: the auto-forwarding added for job parameters put the None into the payload, where it either failed local payload validation or reached the API as null. A param without a value is nothing to forward, so leaving it out is what the author asked for.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A Dag that declares a nullable
Paramand leaves it unset can no longer submit a Databricks run: the params are auto-forwarded into each task's dict-shaped parameter slot, and theNonefails payload validation before any API call. A param with no value is nothing to forward, so it is now skipped.DatabricksRunNowOperatorandDatabricksCreateJobsOperatorforward Dag params the same way but inject after validation, so there theNonereached the Databricks API asnullinstead of failing locally; all three now filter identically.closes: #71776
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 5) following the guidelines