-
Notifications
You must be signed in to change notification settings - Fork 72
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
Use schema field for pipeline in builtin template #2347
base: main
Are you sure you want to change the base?
Conversation
The presence of this field implies that the pipeline is in direct publishing mode. This is can be used only with Unity Catalog, so the template only configures it if it detects Unity Catalog.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, let me ask the team to double-check this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Conditional LGTM, minor change requested after checking in with the backend team.
...ates/default-python/template/{{.project_name}}/resources/{{.project_name}}.pipeline.yml.tmpl
Outdated
Show resolved
Hide resolved
...ates/default-python/template/{{.project_name}}/resources/{{.project_name}}.pipeline.yml.tmpl
Outdated
Show resolved
Hide resolved
Holding off on merge until the rollout is fully complete. |
@pietern 👍 this should be good to merge now, the new backend errors for existing pipelines landed last Thursday |
Changes
The
schema
field implies the lifecycle of tables is no longer tied to the lifecycle of the pipeline, as was the case with thetarget
field.More information about using the "catalog" and "schema" properties can be found here: https://docs.databricks.com/en/delta-live-tables/target-schema.html
Tests
n/a