DMS/Lakehouse Sync: removal notice #6436
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
gvasquezvargas
added
the
deploy
gvasquezvargas
requested review from
ksnavely,
jperozoa,
nidhibhammar and
mlewandowski-edb
jperozoa
approved these changes
Jan 29, 2025
Merged
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.
What Changed?
As of 28.01.2025 Cloud Service no longer offers Data Migration Service and Lakehouse Sync capabilities.
The Data Migration Service will only be available in HCP deployments.
For the Lakehouse Sync, it is not yet clear if we'll eventually move it to the HCP or if there will be no support at all.
Hence the differentiated Notice banners.
https://enterprisedb.atlassian.net/browse/DOCS-1182