Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Handling job creation when using jobs_runs_submit_by_id_and_wait_for_completion #88

Closed
1 task done
edmondop opened this issue Oct 27, 2023 · 1 comment
Closed
1 task done

Comments

@edmondop
Copy link
Contributor

edmondop commented Oct 27, 2023

At the moment, when using the jobs_runs_submit_by_id_and_wait_for_completion, the details of the Databricks job are not available in the parent flow or task until the job completes, and they are returned. However, for long running job one could desire to store the Databricks Job URL as an artifact, for example

https://github.com/PrefectHQ/prefect-databricks/blob/main/prefect_databricks/flows.py#L462

Expectation / Proposal

Traceback / Example

@edmondop
Copy link
Contributor Author

edmondop commented Mar 5, 2024

We can close this ! it's fixed with #89

@edmondop edmondop closed this as completed Mar 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant