Azure / Azure/elastic-db-tools

Fully async MSQ scenario is not possible due to necessary shardMap.GetShards() call

Open
#59 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
147
Forks
108
PR merge metrics
No merged PRs in 30d

Description

It's not possible to write fully async MSQ code because MultiShardConnection is created with a list of shards, which can only be retrieved using shardMap.GetShards() which is synchronous.

Possible solutions:
1. Implement GetShardsAsync()
2. Implement a MultiShardConnection constructor that takes a ShardMap as a parameter. This can call an internal GetShardsAsync() method.
3. Both of the above?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.