This requires extending the filters

Is your feature request related to a problem? Please describe.
Feature request to be able to check connection is alive.

Describe the solution you'd like
Add a ping command in the https://github.com/tigrisdata/tigrisdb-client-go

Describe alternatives you've considered

Additional context

The requests in the context of a transaction must go to the same app worker.

Forwarding logic will be implemented on the server so that the request is forwarded to the correct app worker.

Describe the bug
For tests, I run several requests to create databases in parallel.
Sometimes the error for database creation is nil however database is absent.
Sometimes the error does appear.

To Reproduce

1. put files in one folder, run go mod tidy
2. run go test -count=1 ./...

Expected behavior
Expected 3 databases to be present:

skydancer:~/tigriscli$ tigris list databases
testthree
testtwo
testone

Screenshots
Instead, the error appears:

skydancer:~/tigriscli$ go test -count=1 ./... 
--- FAIL: TestThree (0.01s)
    tigriscli_test.go:37: recreate db testthree
    tigriscli_test.go:40: 
        	Error Trace:	tigriscli_test.go:40
        	            				tigriscli_test.go:25
        	Error:      	Received unexpected error:
        	            	database already exist
        	Test:       	TestThree
FAIL
FAIL	tigriscli	0.054s
FAIL

and the databases list if not full,

skydancer:~/tigriscli$ tigris list databases
testthree
testtwo

The name of the absent database testone is not the testthree that appeared in the error message.

Desktop (please complete the following information):
Linux skydancer 5.11.0-49-generic #55-Ubuntu SMP Wed Jan 12 17:36:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Additional context

• cli tigris version v1.0.0-alpha.8
• tigris container date docker inspect --format '{{ .Created }}' tigrisdata/tigris:latest 2022-05-04T01:53:00.992143876Z
• github.com/tigrisdata/tigris-client-go v1.0.0-alpha.10

Is your feature request related to a problem? Please describe.
It's a feature request to let know the collection size

Describe the solution you'd like

• Approximate or precise size of the collection in the in a new method totalSize in a /api/v1/databases/{db}/collections/{collection}/ namespace
• Includes all: indexes, keys, fields, etc.
• Implementations in the tigrisdb and support it in the client

Describe alternatives you've considered

• Just to start a 0 value can be returned. The actual size value can be added later.
• Give a size value in the ListCollectionsResponse method is not really meant for presenting the size information

Additional context

Description
It's a feature request.
If one inserts data with scheme that differs from the collection creation call, by default, the tigris server allows to do so.
It's must have been impossible to do so, because it's impossible to read data after that in the gRPC client.
But it did.

Describe the solution you'd like

Set "additionalProperties": false by default.

Describe alternatives you've considered

However, tigris-cli allows to read data afterwards, maybe the solution is to make it possible to read data in gRPC client afterwards? But how, taking into account that there must be strict values (use json.RawMessage?).

Additional context

Add any other context or screenshots about the feature request here.

Is your feature request related to a problem? Please describe.

It's a feature request to add details / change the error code to distinguish whether the collection not found or the database not found in:

• collection requests (read, update, replace, delete documents) and in the
• database requests (list collections, drop, create or update collections)

Describe the solution you'd like

Preferably using https://pkg.go.dev/google.golang.org/genproto/googleapis/rpc/status#Status and standardized details.
https://cloud.google.com/apis/design/errors#error_details

Describe alternatives you've considered

In the current solution the gRPC code codes.InvalidArgument hides this details

server/services/v1/query_runner.go-123		
     return nil, api.Errorf(codes.InvalidArgument, "database doesn't exists '%s'", dbName)

It's not convenient to parse string "database doesn't exists '%s'" which would vary from database to database and can be easily changed by developers.

Additional context