docs: Added pg to alloy migration guide #249
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
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 <akitsch@google.com>
averikitsch
approved these changes
Oct 4, 2024
|
Can you also add this to the table in https://github.com/googleapis/langchain-google-alloydb-pg-python/blob/main/samples/README.md? Thanks! |
dishaprakash
pushed a commit
that referenced
this pull request
Oct 16, 2024
* feat: Added migrator module for PGToAlloy * Allow ids of all types * Rearrange methods * Add async tests * Fixed lint * Made tests more robust * Fixed tests * Lint fix * Changed method and class names * Used fetchone instead of fetchall * Fixed typos/formatting * Added public and private params * Fixed formatting * Clean code * Remove loop and run_in_sync * Remove unused imports * Hardcoded collections and embeddings tables * Minor fix * Lint fix * Created tables * Users give column names instead of defining columns * Removed extra migrator class * Fixed lint errors * Minor fix: Does not work * Changed insert queries * Added data batching * Changed indentation to tabs * Minor cleanup * Remove pgvector_migrator from init * Await all insert tasks at once * Fixed linting errors * Corrected docstrings * Made interface similar to vector store customisation * Changed docstrings * Corrected error * Moved sql statements * Migrate methods take vector store objects * Sqlalchmey directly yields data batches * Removed unused imports * lint * Lint fix * code cleanup * lint * Code cleanup * docs: Added pg to alloy migration guide * small change * Update samples/migrations/pg_to_alloy.md Co-authored-by: Averi Kitsch <akitsch@google.com> * Small changes * Small change * Small change * Changed to correct file * Deleted migrator code * Doc cleanup * Small change * Added info on how to use search methods without data migration * Outlined connection simplicity * corrected docs * Dedup vector store and destination table * better naming * Added docs in content table --------- Co-authored-by: Averi Kitsch <akitsch@google.com>
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.