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
However, this will not work for the VectorConfig options since that one has two values as input. But I'm not sure, I have never created vector based indexes.
When creating composite_index using firedantic it only supports the
order
option.That makes not possible to create index for eg
array_contains
.The documentation has three options for creating composite index,
order
,array_config
,vector_config
see documentation
Maybe expand the second field value to have more values, and toggle the create on the value?
Or make it similar to the
filter_
in.find
where a single value is assumed to beorder
but if you set it as dict you can set it how it should be used?more options
If you add
CONTAINS
as an option you could toggle the create on that.eg
and set the
field_mode
based on the valueHowever, this will not work for the
VectorConfig
options since that one has two values as input. But I'm not sure, I have never created vector based indexes.support both
str
anddict
eg
suboptimal since the name is of the field is
order
The text was updated successfully, but these errors were encountered: