[kailash360]

Summary

When the collection does not exist, the server answers DeleteCollection with result: false and no gRPC error. The client turned that into a plain errors.New("failed to delete collection"), which has no gRPC status, so status.Code(err) returned codes.Unknown. Every other method I tried reports a missing collection as codes.NotFound (GetCollectionInfo, ListSnapshots, Count), so callers could not tell "the collection is already gone" apart from a real failure without matching the error text.

DeleteCollection now returns a NotFound status error in this case. QdrantError already unwraps to its inner error, so status.Code(err) and status.FromError(err) return NotFound:

if err := client.DeleteCollection(ctx, name); err != nil && status.Code(err) != codes.NotFound {
	return err
}

The error message changes from:

DeleteCollection() failed: missing: failed to delete collection

to:

DeleteCollection() failed: missing: rpc error: code = NotFound desc = collection "missing" does not exist

Behavior change: callers that only check err != nil are unaffected. Code that matched the old text "failed to delete collection" needs to check status.Code(err) == codes.NotFound instead.

Fixes #

Changes

• qdrant/collections.go: return status.Errorf(codes.NotFound, ...) wrapped in QdrantError when the server reports result: false
• qdrant_test/collections_test.go: DeleteNonExistentCollection now also checks status.Code(err) == codes.NotFound

Checks

• go test ./... passes, including the integration tests
• The updated DeleteNonExistentCollection check fails on master (Unknown instead of NotFound) and passes with this change
• golangci-lint run reports 0 issues
• gofmt -s -l qdrant qdrant_test reports nothing

Closes #180

[anush008]

Thanks!