Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accept task_key as an argument in DatabricksNotebookOperator #44960

Merged

Conversation

hardeybisey
Copy link
Contributor

@hardeybisey hardeybisey commented Dec 16, 2024

This PR introduces the ability for users to explicitly specify databricks_task_key as a parameter for the DatabricksNotebookOperator. If databricks_task_key is not provided, a default value is generated using the hash of the dag_id and task_id.

Key Changes:

  • Users can now define databricks_task_key explicitly.
  • When not provided, the key defaults to a deterministic hash based on dag_id and task_id.

Fixes: #41816
Fixes: #44250
related: #43106


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

@hardeybisey hardeybisey force-pushed the accept_task_key_in_databricks_taskoperator branch 2 times, most recently from 55100c3 to 11ff19e Compare December 16, 2024 16:52
@eladkal eladkal requested a review from rawwar December 17, 2024 06:39
@hardeybisey hardeybisey force-pushed the accept_task_key_in_databricks_taskoperator branch from 11ff19e to 0862491 Compare December 17, 2024 13:12
@rawwar rawwar requested a review from pankajkoti December 17, 2024 13:18
@hardeybisey hardeybisey force-pushed the accept_task_key_in_databricks_taskoperator branch from 0862491 to 676e00f Compare December 17, 2024 14:02
@hardeybisey hardeybisey force-pushed the accept_task_key_in_databricks_taskoperator branch 2 times, most recently from 7560470 to 3d10268 Compare December 19, 2024 08:47
@hardeybisey hardeybisey force-pushed the accept_task_key_in_databricks_taskoperator branch from 3d10268 to fe641e4 Compare December 19, 2024 08:51
Copy link
Member

@pankajkoti pankajkoti left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks for the great fix and your efforts in resolving this @hardeybisey

@pankajkoti pankajkoti merged commit 1ee6971 into apache:main Dec 26, 2024
64 checks passed
LefterisXefteris pushed a commit to LefterisXefteris/airflow that referenced this pull request Jan 5, 2025
…e#44960)

This PR introduces the ability for users to explicitly specify databricks_task_key as a parameter for the DatabricksNotebookOperator. If databricks_task_key is not provided, a default value is generated using the hash of the dag_id and task_id.

Key Changes:

Users can now define databricks_task_key explicitly.
When not provided, the key defaults to a deterministic hash based on dag_id and task_id.
Fixes: apache#41816
Fixes: apache#44250
related: apache#43106
agupta01 pushed a commit to agupta01/airflow that referenced this pull request Jan 6, 2025
…e#44960)

This PR introduces the ability for users to explicitly specify databricks_task_key as a parameter for the DatabricksNotebookOperator. If databricks_task_key is not provided, a default value is generated using the hash of the dag_id and task_id.

Key Changes:

Users can now define databricks_task_key explicitly.
When not provided, the key defaults to a deterministic hash based on dag_id and task_id.
Fixes: apache#41816
Fixes: apache#44250
related: apache#43106
got686-yandex pushed a commit to got686-yandex/airflow that referenced this pull request Jan 30, 2025
…e#44960)

This PR introduces the ability for users to explicitly specify databricks_task_key as a parameter for the DatabricksNotebookOperator. If databricks_task_key is not provided, a default value is generated using the hash of the dag_id and task_id.

Key Changes:

Users can now define databricks_task_key explicitly.
When not provided, the key defaults to a deterministic hash based on dag_id and task_id.
Fixes: apache#41816
Fixes: apache#44250
related: apache#43106
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants