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
After basic "JSON number array" input, also need to add support for optimized variant for vectors: Base64-encoded "packed floats" binary, in which client:
First converts from float[] (or platform equivalent) into IEEE-754 packed (4 bytes per float) byte sequence
Encodes resulting byte sequence into padded "MIME" Base64 String
Encloses String into EJSON "$binary" wrapping -- same as blob values
and Data API will decode, unpack things, passes to CQL driver in structure it expects.
This issue DOES NOT change handling on return path: it will use "simple"/"plain" JSON Number array representation -- this because we do not know which representation was used for insert/update (unlike with Collections where we keep a copy in doc_json)
For further work we'd file another issue as necessary to allow requesting optimal representation in results.
The text was updated successfully, but these errors were encountered:
(note: follow up to #1492)
After basic "JSON number array" input, also need to add support for optimized variant for vectors: Base64-encoded "packed floats" binary, in which client:
float[]
(or platform equivalent) into IEEE-754 packed (4 bytes per float) byte sequenceblob
valuesand Data API will decode, unpack things, passes to CQL driver in structure it expects.
This issue DOES NOT change handling on return path: it will use "simple"/"plain" JSON Number array representation -- this because we do not know which representation was used for insert/update (unlike with Collections where we keep a copy in
doc_json
)For further work we'd file another issue as necessary to allow requesting optimal representation in results.
The text was updated successfully, but these errors were encountered: