Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
With multiple implementations of vector index types we're burdening the application and the database to be in sync over the type of index. A wrong step means there will be a table scan.
Simplifying it for the user is a generic VEC_DISTANCE function that will operate on the index that's there.
If two indexes are possible I guess we select the first and push a warning?