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

Persist Databricks xcom value #175

Merged
merged 2 commits into from
Apr 1, 2022
Merged

Conversation

pankajastro
Copy link
Contributor

Issue: #167

  • Pushing xcom values in in execute_complete() method for both DatabricksRunNowOperatorAsync and DatabricksSubmitRunOperatorAsync.
  • Keeping the logic as it is in execute method so that value would be available also during execution

@pankajastro pankajastro force-pushed the databricks_persist_xcom_value branch from 9d2c7e9 to fef389e Compare March 31, 2022 07:32
@codecov
Copy link

codecov bot commented Mar 31, 2022

Codecov Report

Merging #175 (fef389e) into main (80210db) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #175      +/-   ##
==========================================
+ Coverage   95.76%   95.78%   +0.01%     
==========================================
  Files          39       39              
  Lines        2104     2111       +7     
==========================================
+ Hits         2015     2022       +7     
  Misses         89       89              
Impacted Files Coverage Δ
...nomer/providers/databricks/operators/databricks.py 89.13% <100.00%> (+1.63%) ⬆️
...onomer/providers/databricks/triggers/databricks.py 96.87% <100.00%> (+0.10%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 80210db...fef389e. Read the comment docs.

@phanikumv phanikumv merged commit ce7681b into main Apr 1, 2022
@phanikumv phanikumv deleted the databricks_persist_xcom_value branch April 1, 2022 15:49
@kaxil kaxil added this to the 1.2.0 milestone Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Databricks operator does not persist xcom values
3 participants