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
Asking for to the client for a collection name with includes "/" in the name raises UnexpectedResponse. Can this be validated in the client site before calling the remote qdrant server ?
With make sense, since this implies a call to a remote API like "GET http://localhost:6333/collections/example/collection1/exists" with do not exists .. maybe it make sense to validate collection_name before calling the remote API. Or use some type of encoding to avoid this
The text was updated successfully, but these errors were encountered:
Asking for to the client for a collection name with includes "/" in the name raises UnexpectedResponse. Can this be validated in the client site before calling the remote qdrant server ?
for example:
With make sense, since this implies a call to a remote API like "GET http://localhost:6333/collections/example/collection1/exists" with do not exists .. maybe it make sense to validate
collection_name
before calling the remote API. Or use some type of encoding to avoid thisThe text was updated successfully, but these errors were encountered: