Skip to content

[FEATURE] Better support of direct publishing mode in databricks_pipeline #4567

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.

Sign up for GitHub

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

Jump to bottom
Open
alexott opened this issue Mar 11, 2025 · 0 comments
Open

[FEATURE] Better support of direct publishing mode in databricks_pipeline #4567

alexott opened this issue Mar 11, 2025 · 0 comments
Labels
feature New feature or request

Comments

@alexott
Copy link
Contributor

alexott commented Mar 11, 2025

Right now, the catalog field is marked as ForceNew in databricks_pipeline (src. With the release of direct publishing mode it's now possible to change catalog without the need to recreate a pipeline.

But we still need to recreate a pipeline when switching from storage to catalog or vice versa.
@alexott alexott added the feature New feature or request label Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alexott