Closed wsugarman closed 1 year ago
Adding @nytian to help review this PR and answer Will’s questions.
The change looks good to me. I just have a problem about changing TableClient to Table class. Why are we doing this, I assume is it because we cannot apply Azure.Data.Tables packages? Thanks!
Oh, I changed it as all other interactions with Azure Storage, including the existing partition manager, leverage these client wrappers. For example, the BlobPartitionManager
used by the LegacyPartitionManager
uses the internal Blob
type. Probably the biggest advantage is that they are configured with various policies for retrying and logging connection attempts.
main
including the new table partition manager into the feature branchTablePartitionManager
to use theTable
class instead of theTableClient
directlyTableLease
toTablePartitionLease
to align withBlobPartitionLease
This change should not be squashed as I will eventually need to merge with
main
too.