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
Currently JSON API limits maximum Vector ($vector) dimension to rather high limit -- 16,000 -- which was simply chosen as "big enough not to matter". But it appears that there is a true limit as per:
which limits indexable entry to 16kB, and with float-vector (4 bytes for float32) it means actual upper max dimension of 4,096.
So let's align this limit so JSON API can validate creation without hitting DB guardrails (esp. since test DB may not even have guardrails enabled).
New limit should still be above sizes needed in practice (f.ex, OpenAI's "standard" 1,536 ).
The text was updated successfully, but these errors were encountered:
tatu-at-datastax
changed the title
Reduce max Vector dimension limit from 16,000 to 4,096 not to fail due to SAI/ANN limit
Reduce max Vector dimension limit from 10,000 to 4,096 not to fail due to SAI/ANN limit
Jan 5, 2024
Currently JSON API limits maximum Vector (
$vector
) dimension to rather high limit -- 16,000 -- which was simply chosen as "big enough not to matter". But it appears that there is a true limit as per:https://github.com/riptano/VECTOR-SEARCH/issues/73
which limits indexable entry to 16kB, and with
float
-vector (4 bytes forfloat32
) it means actual upper max dimension of 4,096.So let's align this limit so JSON API can validate creation without hitting DB guardrails (esp. since test DB may not even have guardrails enabled).
New limit should still be above sizes needed in practice (f.ex, OpenAI's "standard" 1,536 ).
The text was updated successfully, but these errors were encountered: