[FEATURE] 163 - For each task #185
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…line workflow task generation
refactor: DatabricksBundleCodegen to improve task handling and stream…
…ask type also in case of nested task being of Brickflow type
…t' into feature/for_each_model_settings
Feature/for each model settings
riccamini
requested review from
asingamaneni,
stikkireddy,
newfront and
a team
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds support for for each task type
Related Issue
#163
Motivation and Context
The for each task was recently introduced in Databricks workflows as a way iterate tasks on a set of inout parameters. With this PR we will be able to use the for each task type in Brickflow defined workflows
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: