Skip to content

BatchGet Timeout #495

Open
Open
@azam-gsm

Description

@azam-gsm

In my go program I do BatchGet read with about 10-15 keys, assuming If there is issue with fetching I will get client error and will drop the request accordingly.

But I have recently came across articles which suggest that BatchGet will be successful even if there are issue with fetching few keys and those will be there in result set as nil.

And it seems like correct as my logic is failing, how do I avoid such situation so as to be sure that if I am getting response from batch operation if should be of success and anything returned nil is actually not present in database.

Any help/suggestion here?

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions