docs: Added pg to alloy migration guide #249
Open
+212
−0
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
product-auto-label
bot
added
the
api: alloydb
averikitsch
reviewed
Sep 30, 2024
samples/migrations/pg_to_alloy.md
Outdated
| await amigrate_pgvector_collection( | ||
| engine, | ||
| collection_name="collection_name", | ||
| vector_store=vector_store, |
There was a problem hiding this comment.
We could point out that if they are moving to a different instance or database they could use different engines
There was a problem hiding this comment.
We do not yet have functionality to allow users to migrate across databases. Should we add it?
Co-authored-by: Averi Kitsch <[email protected]>
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.
No description provided.