The normal SSTable files store key/value mappins of the form id -> vector (id could be ybctid of the primary table, or something else)
Next to each SSTable file, we generate the vector search file (IVFFLAT, HNSW or other type of index) using the appropriate library, such as FAISS or Usearch.
On the read path, we can provide the vector in read options, and Seek/Next will navigate the result set of the vector search, which could be consumed by the downstream DocDB framework in the usual manner.
Issue Type
kind/enhancement
Warning: Please confirm that this issue does not contain any sensitive information
[X] I confirm this issue does not contain any sensitive information.
Jira Link: DB-10645
Description
Approach:
Issue Type
kind/enhancement
Warning: Please confirm that this issue does not contain any sensitive information