Up to date. #3
Merged
Up to date. #3
Conversation
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
* add supabase + pgvector datastore provider * fix conflicts: move supabase docs from readme * add supabase to unused deps doc * add supabase local setup docs and tests * small improvements in setup.md * add pure postgres implementation and more tests * add postgres datastore docs to readme * rebase to latest main * fix typo in readme - postgres envs * add some indexes and pgvector idx strategy in docs * enable RLS by default
Initalize -> Initialize
* Update README.md * Update README.md
The text in the postgres section specifically called out supabase, but pgvector is available on many vendors this points directly to the pgvector repo so that users can choose
* UPgraded fastapi and redis to fix security vulnerabilities * Could not justify fastapi upgrade
…ding the embedding field name (#260)
* Add a full PostgresSQL syntax distributed database AnalyticDB as a datastore. * Replace psycopg2 with psycopg2cffi to compatibility with Python >=3.10 and Refactor AnalyticDB related ENV * Change the `psycopg2cfii` package to optional and update setup.md with PostgreSQL dependency installation instructions * Use a connection pool to replace connect with the PostgreSQl vector store directly. To prevent connection lost problem. * Modify READEME. Add `analyticdb` into `DATASTORE`
* Add loguru for logging * Add logger * Replace exception with error --------- Co-authored-by: Raghu Ganapathi <[email protected]>
* add PR checklist for contributions * add PR checklist template
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.
Pull Request (PR) Checklist
If you'd like to contribute, please follow the checklist below when submitting a PR. This will help us review and merge your changes faster! Thank you for contributing!
Type of PR: Indicate the type of PR by adding a label in square brackets at the beginning of the title, such as
[Bugfix],[Feature],[Enhancement],[Refactor], or[Documentation].Short Description: Provide a brief, informative description of the PR that explains the changes made.
Issue(s) Linked: Mention any related issue(s) by using the keyword
FixesorClosesfollowed by the respective issue number(s) (e.g., Fixes upsert-file endpoint accepts metadata openai/chatgpt-retrieval-plugin#123, Closes Update LICENSE, fix copyright license year openai/chatgpt-retrieval-plugin#456).Branch: Ensure that you have created a new branch for the changes, and it is based on the latest version of the
mainbranch.Code Changes: Make sure the code changes are minimal, focused, and relevant to the issue or feature being addressed.
Commit Messages: Write clear and concise commit messages that explain the purpose of each commit.
Tests: Include unit tests and/or integration tests for any new code or changes to existing code. Make sure all tests pass before submitting the PR.
Documentation: Update relevant documentation (e.g., README, inline comments, or external documentation) to reflect any changes made.
Review Requested: Request a review from at least one other contributor or maintainer of the repository.
Video Submission (For Complex/Large PRs): If your PR introduces significant changes, complexities, or a large number of lines of code, submit a brief video walkthrough along with the PR. The video should explain the purpose of the changes, the logic behind them, and how they address the issue or add the proposed feature. This will help reviewers to better understand your contribution and expedite the review process.
Pull Request Naming Convention
Use the following naming convention for your PR branches:
<type>: The type of PR, such asbugfix,feature,enhancement,refactor, ordocs. Multiple types are ok and should appear as ,<short-description>: A brief description of the changes made, using hyphens to separate words.<issue-number>: The issue number associated with the changes made (if applicable).Example: