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
The offset property of PointsScrollRequest has a similar issue. This one however is a bit more complex since it wants either an integer or a UUID. Giving it a non-UUID string results in:
{
"status": {
"error": "Format error in JSON body: value 0 is not a valid point ID, valid values are either an unsigned integer or a UUID at line 1 column 24"
},
"time": 0.0
}
Their documentation certainly implies that they return an Integer as well, but that doesn't appear to be true.
The current version of the client only supports Qdrant v1.2.0 - Unfortunately the API is not versioned and this makes backwards compatibility hard to achieve. I have not yet worked on v1.3.x support.
I'm not sure whether they changed the datatype but this has happened in the past. Changes such as these unfortunately can break the client implementation.
Currently this is typed as a
Long
, but QDrant 1.3.1 is returningString
(appears to be a UUID).The text was updated successfully, but these errors were encountered: