Skip to content
This repository has been archived by the owner on Oct 9, 2023. It is now read-only.

Use GetExecutionData instead #573

Merged
merged 11 commits into from
Jun 13, 2023
Merged

Use GetExecutionData instead #573

merged 11 commits into from
Jun 13, 2023

Conversation

EngHabu
Copy link
Contributor

@EngHabu EngHabu commented Jun 7, 2023

TL;DR

Removes deprecated code path to retrieve LP's outputs and moves to the separate GetExecutionData() call.

Type

  • Bug Fix
  • Feature
  • Plugin

Are all requirements met?

  • Code completed
  • Smoke tested
  • Unit tests added
  • Code documentation added
  • Any pending items have an associated Issue

Tracking Issue

fixes flyteorg/flyte#3753

Signed-off-by: Haytham Abuelfutuh <haytham@afutuh.com>
Signed-off-by: Haytham Abuelfutuh <haytham@afutuh.com>
Signed-off-by: Haytham Abuelfutuh <haytham@afutuh.com>
Signed-off-by: Haytham Abuelfutuh <haytham@afutuh.com>
@codecov
Copy link

codecov bot commented Jun 7, 2023

Codecov Report

Merging #573 (eff8194) into master (2086bb9) will decrease coverage by 0.09%.
The diff coverage is 31.03%.

❗ Current head eff8194 differs from pull request most recent head b61125d. Consider uploading reports for the commit b61125d to get more accurate results

Signed-off-by: Haytham Abuelfutuh <haytham@afutuh.com>
@EngHabu EngHabu requested review from katrogan and hamersaw June 8, 2023 01:06
katrogan
katrogan previously approved these changes Jun 12, 2023
Copy link
Contributor

@katrogan katrogan left a comment

Choose a reason for hiding this comment

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

Would we want to similarly propage

@@ -246,12 +247,30 @@ func (a *adminLaunchPlanExecutor) syncItem(ctx context.Context, batch cache.Batc
continue
}

execData, err := a.adminClient.GetExecutionData(ctx, &admin.WorkflowExecutionGetDataRequest{
Copy link
Contributor

Choose a reason for hiding this comment

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

For performance reasons, would it be worthwhile to wrap this call in an if block and only fetch execution data when RawOutputPolicy is set to inline?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Discussed offline. We always need to call GetExecutionData()

@EngHabu EngHabu marked this pull request as ready for review June 13, 2023 14:59
@EngHabu EngHabu requested a review from kumare3 as a code owner June 13, 2023 14:59
@EngHabu EngHabu requested a review from katrogan June 13, 2023 14:59
@EngHabu EngHabu merged commit 89dfd5b into master Jun 13, 2023
13 checks passed
@EngHabu EngHabu deleted the sub-lp-outputs branch June 13, 2023 16:27
eapolinario pushed a commit to eapolinario/flytepropeller that referenced this pull request Aug 9, 2023
* Use GetExecutionData instead

Signed-off-by: Haytham Abuelfutuh <haytham@afutuh.com>

* bump

Signed-off-by: Haytham Abuelfutuh <haytham@afutuh.com>

* fix unit tests

Signed-off-by: Haytham Abuelfutuh <haytham@afutuh.com>

* more fixes

Signed-off-by: Haytham Abuelfutuh <haytham@afutuh.com>

* fix more

Signed-off-by: Haytham Abuelfutuh <haytham@afutuh.com>

* Regenerate

Signed-off-by: Haytham Abuelfutuh <haytham@afutuh.com>

* Only call GetExecutionData when the workflow succeeds

Signed-off-by: Haytham Abuelfutuh <haytham@afutuh.com>

---------

Signed-off-by: Haytham Abuelfutuh <haytham@afutuh.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants