Skip to content

fix issue: #64828, repair missing job parameters if exists#67055

Merged
eladkal merged 2 commits into
apache:mainfrom
sydongda:feature/databricks-provider-repair-job-missing-parameters
May 18, 2026
Merged

fix issue: #64828, repair missing job parameters if exists#67055
eladkal merged 2 commits into
apache:mainfrom
sydongda:feature/databricks-provider-repair-job-missing-parameters

Conversation

@sydongda
Copy link
Copy Markdown
Contributor

@sydongda sydongda commented May 17, 2026

Closes: #64828, repair missing job parameters if exists.

While do repair Databricks job run, job_parameters missed if exists.

Was generative AI tooling used to co-author this PR?
  • None

@sydongda
Copy link
Copy Markdown
Contributor Author

@eladkal , could you review this PR?

@eladkal eladkal requested a review from jroachgolf84 May 18, 2026 03:48
@potiuk potiuk added the ready for maintainer review Set after triaging when all criteria pass. label May 18, 2026
Copy link
Copy Markdown
Collaborator

@jroachgolf84 jroachgolf84 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sydongda - can we add a unit test (or two) for these changes?

@sydongda
Copy link
Copy Markdown
Contributor Author

@jroachgolf84 , sure, unit test case added.

@jroachgolf84
Copy link
Copy Markdown
Collaborator

LGTM

Copy link
Copy Markdown
Collaborator

@jroachgolf84 jroachgolf84 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding unit-tests :) checks are all looking green!

@eladkal eladkal merged commit 69c0d7c into apache:main May 18, 2026
94 checks passed
@sydongda sydongda deleted the feature/databricks-provider-repair-job-missing-parameters branch May 19, 2026 01:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DatabricksRunNowOperator: Repair run doesnt pass job parameters and a retry on a job with an idempotency token results always results in succes.

4 participants