Replies: 1 comment
-
Where are we with this? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Checked
Feature request
PGVector currently creates two new tables, langchain_pg_embedding and langchain_pg_collection, if they do not already exist. If the table exists it loads the data into existing tables. However, if I want to create and segregate embedding results into different tables based on different search scopes,it is not available. For Example -
current
Proposed
Q) What happens to langchain_pg_collection ?
A: langchain_pg_collection stays same with additional column for 'table_name'
Motivation
Providing option to segregate enables the implementation of Fine Grain Access Control .Here is a discussion - #6045
Proposal (If applicable)
Proposed
Q) What happens to langchain_pg_collection ?
A: langchain_pg_collection stays same with additional column for 'table_name'
Beta Was this translation helpful? Give feedback.
All reactions