You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
provide a feature or tooling to allow a user to take embeddings from one table and make it such that pg_vectorize can manage those embeddings. for example, assume a user has a table already with a content column and an embeddings column generated from the sentence-transformers/all-MiniLM-L6-v2 model. Rather than recomputing embeddings for all of the content column, we should be able to just insert those into the new embeddings table or column. I think it would be safe and fairly straight forward to manually insert embeddings into vectorize.<project_name>_embeddings after the project is created. If the project is using schedule => 'realtime', then creating a new project on a table will immediately create jobs to generate embeddings for all the text, so we might wamt to delete those jobs if we dont want to execute the jobs. In summary, I think the steps to do this could be:
create vectorize by calling vectorize.table()
insert embeddings into the embedding column on vectorize.<project_name>_embeddings
optionally delete from pgmq where message ->> 'name' = '<project_name>'
The text was updated successfully, but these errors were encountered:
provide a feature or tooling to allow a user to take embeddings from one table and make it such that pg_vectorize can manage those embeddings. for example, assume a user has a table already with a
content
column and anembeddings
column generated from thesentence-transformers/all-MiniLM-L6-v2
model. Rather than recomputing embeddings for all of thecontent
column, we should be able to just insert those into the new embeddings table or column. I think it would be safe and fairly straight forward to manually insert embeddings intovectorize.<project_name>_embeddings
after the project is created. If the project is usingschedule => 'realtime'
, then creating a new project on a table will immediately create jobs to generate embeddings for all the text, so we might wamt to delete those jobs if we dont want to execute the jobs. In summary, I think the steps to do this could be:vectorize.table()
vectorize.<project_name>_embeddings
delete from pgmq where message ->> 'name' = '<project_name>'
The text was updated successfully, but these errors were encountered: