Open
Conversation
calvarjorge
reviewed
Feb 13, 2026
Contributor
calvarjorge
left a comment
calvarjorge
left a comment
There was a problem hiding this comment.
Q - why do we want to deprecate Lakebase V1? Looking at the docs, it seems that there are valid use cases for it (high availability guarantee / manually scaling compute)
MarioCadenas
approved these changes
Feb 13, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Reason
We deprecate the Lakebase V1 connector as the Lakebase Autoscaling driver is coming very soon.
https://databricks.atlassian.net/browse/LKB-9058