Table query not extracting and following continuation token properly

[djyou]

Bug Report

Azure Storage table query may return results with non-empty x-ms-continuation-NextPartitionKey but empty x-ms-continuation-NextRowKey, see https://docs.microsoft.com/en-us/rest/api/storageservices/query-timeout-and-pagination

The current Go SDK implementation couldn't extract and follow the continuation token for these cases due to the assumption that both have to exist

azure-sdk-for-go/storage/table.go

Line 374 in 7a9d276

if ct.NextPartitionKey != "" && ct.NextRowKey != "" {

The expectation is that (also how other SDKs handle continuation token), the pagination headers don't have dependencies on each other, and any non-empty ones should formulate a continuation token and be added to the URL of the next request.

[jhendrixMSFT]

Fixed in https://github.com/Azure/azure-sdk-for-go/releases/tag/v32.1.0